CAFM Software Features: The 2026 Feature Checklist for a US Corporate Facility and Workplace Operations Team

This article is part of our series on Custom Facility Management CAFM Platform Development for US Corporate Real Estate Teams: Building a Space, Work Order and Vendor SLA System

Introduction: Get the Space Model Right or Nothing Else Reconciles

For corporate facilities teams, the right CAFM software features can determine whether a facility platform becomes the organization’s system of record or another system people keep a spreadsheet alongside. Getting there takes solid web application development.

The foundation is the space model. It needs to hold multiple measurement definitions such as rentable, usable, assignable, and occupiable and express the relationships between them. Different departments may be contractually and financially committed to different numbers, so forcing everyone onto one definition often creates external reconciliation and undermines trust.

That is why the space model comes first. Work order intake follows because it is the daily operational surface employees see, while vendor performance follows because managing the people delivering services is a core facilities responsibility.

Organizations considering custom software development and web application development should evaluate these capabilities in this order.

These features are the product layer of the full custom facility management platform development guide.

Portfolio, Space and Floor Plans — Build First

Several Measurements, Held Together

A facility platform should support the area measurements that matter to different teams while clearly naming the measurement standard being used. The same term can mean different things under different standards. Relationships between measurements should also be expressed as factors, allowing a change to one figure to propagate instead of requiring multiple manual updates. This gives finance and real estate a shared system without forcing either team to abandon the conventions it relies on.

The Hierarchy That Reflects Reality

The platform should represent the facility hierarchy from portfolio and site through building, floor, and space. It should also accommodate spaces that span floors, buildings that share a site, and clear distinctions between leased and owned property. Lease information should sit alongside the locations where the team has responsibility, with critical dates surfaced clearly.

Floor Plans as Live Data, Not Attachments

Drawings should be synchronized from the source of record, with spaces polygonally defined so area can be derived rather than manually entered. Plans can be viewed by department, vacancy, or work order. A floor plan stored as a document is a picture; a floor plan represented as data becomes the interface.

Allocation and Chargeback

Space should be assigned to organizational units using the basis finance actually applies, with historical allocations reproducible when a previous chargeback needs to be reconstructed. This should be done so teams can explain and verify past chargebacks without reconstructing them from spreadsheets or emails.

Work Orders and the Request Portal — Build First

Effective work order management should bring employee requests, building system alarms, scheduled maintenance, and inspection findings into one operational model, with routing rules suited to each source. 

The employee request portal should be simple enough for people unfamiliar with facilities terminology. Employees should be able to describe the issue, identify its location from a floor plan rather than enter an unfamiliar room number, and receive confirmation that the request was received. Most of those reports come from a phone, which puts the request portal in custom Android app development and custom iOS app development scope

Accurate location capture helps prevent wasted technician visits. Routing should consider trade, site, and whether work is handled internally or by a contractor. Where a vendor is responsible, the system should trigger the vendor’s dispatch process.

Priority should reflect business impact rather than the requester’s urgency, using defined criteria. Technicians should be able to execute work through mobile devices, including offline operation in areas without reliable connectivity. Offline execution of that kind is native work, which puts it in custom iOS app development and custom Android app development scope.

Closure should record the actual outcome, particularly for inspection findings, while requesters should be able to see status without repeatedly contacting facilities.

The obligations behind several of these features are set out in OSHA General Duty and Lockout/Tagout Records, ADA Accessibility Audits, ASHRAE Indoor Air Quality Documentation and State Energy Benchmarking Ordinances: Compliance for US Facility Software.

The sensor, routing, floor plan and scorecard mechanics behind these features are covered in Building Management System Sensor Ingestion, CMMS Work Order Routing, CAD Floor Plan Sync and Vendor SLA Scorecard Integration for a Custom US Facility Platform.

Assets and Preventive Maintenance

A facility platform should maintain detailed records for the equipment the team is responsible for, with each asset tied directly to the space model. A chiller, for example, should be associated with the roof of a specific building rather than stored against a free-text location.

Asset criticality should also be classified. Treating a lobby light and a data center cooling unit in the same way can lead to poor maintenance priorities and unnecessary operational risk.

Maintenance programs should be generated according to the basis appropriate to each asset, whether that is a calendar schedule, runtime, or condition where sensing capabilities support it.

The platform should distinguish compliance-driven maintenance from discretionary work. Compliance requirements may not be deferrable during budget pressure, and failing to separate the two can result in the wrong work being postponed.

Each asset should have a service history to support repair-versus-replacement decisions and capital planning. Warranty information, spares, and consumables should also be tracked so teams do not approve repair costs that should be covered by a manufacturer or service agreement. 

Asset condition assessments should feed directly into the capital plan, rather than being assembled manually in a spreadsheet just before the budget cycle.

Vendors, Contracts and SLA Scorecards

A strong facilities management platform should give organizations a complete, measurable view of their vendor relationships. This starts with vendor records that capture contracts, scope, term, rates, and the sites each vendor covers.

Service levels should be expressed in measurable terms. Contract language often needs to be translated into computable rules: response time to which event, measured from when, and subject to what exclusions. A commitment that cannot be measured cannot be effectively managed.

Performance should be calculated using the platform’s own timestamps rather than relying solely on vendor-supplied reports so vendors are not effectively grading their own contractual performance. Scorecards can track response and completion against agreed commitments, first-time fix rates, rework, callbacks within a defined period, and costs against contracted rates.

The platform should also manage insurance certificates, including coverage types, limits, and expiry dates, with work automatically flagged or blocked when coverage lapses. Contractor safety documentation should include energy-control coordination, recognizing that site safety is a shared host responsibility.

Purchase orders and invoices should be reconciled against contracted rates to identify overcharges, while renewal dates should surface early enough for teams to negotiate using performance and cost evidence.

Inspections, Compliance Records and Analytics

Inspection rounds should be scheduled and executed through mobile devices, allowing technicians to capture findings, photographs, and locations directly against the space model. Mobile execution reduces delays between discovering an issue and recording it, while custom mobile app development can support technician and inspection use cases.

Findings should remain open until they have a documented outcome and a named person responsible for closure. They should not be bulk-closed, automatically aged out, or edited after the fact, because an unresolved finding can demonstrate that the organization was aware of a potential hazard. 

The platform should retain compliance records for fire and life safety testing, elevator and pressure equipment inspections, water system management, energy-control procedures, and training, with current authorization status clearly visible. 

Energy consumption should be tracked reliably by building for reporting and performance requirements. Occupancy analytics should use aggregated data and avoid unnecessary individual tracking.

Reporting should cover cost per square foot, planned versus reactive work, criticality-based backlog, vendor performance, and capital planning.

Where Facility Portfolios Diverge

A single-campus headquarters can support deeper space planning, occupancy analytics, and employee experience capabilities because one team manages a defined group of buildings.

A multi-site office portfolio needs stronger standardization. With dozens of locations following local practices, inconsistent data becomes difficult to aggregate, making consistency more valuable than unnecessary sophistication.

Laboratory and manufacturing estates add process equipment, stricter safety requirements, validation obligations in some sectors, and downtime consequences that can fundamentally change maintenance priorities.

Distribution and logistics portfolios typically require less space planning but much stronger equipment maintenance, because facility availability can directly affect operations.

Retail estates often have many small sites, limited in-house staff, and heavy vendor dependence, making vendor management a central platform capability because external providers often perform most facility work across dispersed sites. Healthcare and education estates bring additional regulatory requirements that significantly influence recordkeeping.

Despite these differences, two challenges remain common: defining spaces consistently and maintaining disciplined closure of findings, work, and compliance records.

Final Thoughts

Teams that build a space model capable of holding multiple definitions create a platform that finance and real estate can both use, rather than one that requires constant reconciliation. Work order intake and the request portal follow because they represent daily operations and the organization’s view of the function. Vendor performance comes next, reflecting the people who deliver the work. If you are defining requirements, ask whether your current system can hold two square-footage figures for the same space. NewAgeSysIT helps organizations build tailored technology solutions that align facility operations, workflows, data, and reporting with their specific business requirements. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.

FAQ