Buy too little, and your maintenance team may struggle to get its work done. Buy more than you can use, and you may pay for software that takes unnecessary effort to set up, maintain, or use.

Even software with the right features needs reliable equipment records, trained people, and clear responsibilities. Choose the capabilities your work requires and check whether your team can put them to use.

Start with the work your team needs to do

Before comparing software, identify the maintenance work the system must support. Think about receiving work requests, scheduling preventive maintenance, tracking equipment history, assigning technicians, recording labor and parts, and reporting on completed work.

Which tasks are essential from day one? Which could wait? Which activities should stay in another system, such as your accounting software, enterprise resource planning (ERP) system, or fleet-management platform?

For example, a team may need work requests, preventive maintenance, and equipment history immediately. Detailed parts tracking could come later if nobody is ready to maintain the parts records. Write down what must work now, what can wait, and who will keep each part working.

Use How to Build Your CMMS Requirements to describe those tasks in detail. This guide helps you decide how much of that work to put into the purchase and whether your team is ready to support it.

Make sure your team can use what you're buying

A CMMS may offer preventive maintenance, cost tracking, mobile work orders, and detailed reporting. Those features depend on complete enough equipment records, trained technicians, and people responsible for keeping information accurate.

A 2022 audit of Washington, D.C.'s Department of General Services found weaknesses in work-order cost tracking, supporting documentation, preventive maintenance, and operational controls. [1]

The audit compared approximately $31.3 million captured in the work-order system with $311.8 million in broader Facility Operations expenditures. The underlying system data covered calendar years 2020–2021; the larger expenditure figure covered fiscal years 2020–2021. The auditors also cautioned that the larger total may include expenses outside work-order activity. The figures therefore differ in scope and are not a matching-period accounting comparison. [1]

The findings identify weaknesses in cost visibility and recordkeeping. They do not establish that the entire difference was missing maintenance spending, that the agency bought the wrong software, or that replacing it would have solved the problems.

For the work involved in setup, training, testing, and taking responsibility for the system, see What to Expect During CMMS Implementation.

Test the important tasks before committing

Ask vendors to show how the system handles your actual maintenance processes using realistic examples. A demonstration shows what happened in that demonstration; your team still needs to test the conditions that matter to its work.

  • Can a technician complete a work order, attach photographs, record parts used, and update equipment history?
  • Can a supervisor check whether the work was completed satisfactorily?
  • Can your team find the records later and trust what they show?
  • What happens when information is missing, incorrect, or incomplete?

Decide what successful implementation looks like before signing off on the project. For example, agree on a sample work order that the technician completes, the supervisor checks, and another employee can find later with its equipment history and supporting records intact.

Use CMMS Software Comparison to give shortlisted systems the same important tasks and judge the evidence on a consistent basis.

The Work Order Integrity Amendment Act of 2023, effective March 5, 2024, established duties for DGS Facilities Management and relevant D.C. Public Schools staff. It requires at least annual training on work-order requests, automatic email notices of status changes, and a completion-feedback mechanism open for at least 14 calendar days. [2]

If school staff report unsatisfactory work, the work order must remain open and be completed satisfactorily. If staff do not respond within the specified period, cannot physically review the work, or believe they lack sufficient training to assess it, a DGS representative must verify completion using available evidence before closure. [2]

The law establishes responsibilities for those school-facility work orders. Its enactment does not show that the requirements were successfully implemented or that the earlier problems were resolved.

Decide what your CMMS should—and shouldn't—handle

A particular maintenance task may fit an existing platform or require a specialized system. Check the work each system can support and the effort needed to keep information consistent between them.

Stockton, California, provides an example from fleet management, a related operational field. A December 2021 staff report describes an evaluation of fleet software while Cityworks was already among the tools used for fleet tracking. Staff recommended a dedicated fleet-management system. The supplied record does not confirm an executed purchase or completed implementation. [3]

A March 2026 staff report documents continued Cityworks use for Municipal Utilities and Public Works and recommends another contract extension. It describes broader maintenance work involving utilities infrastructure and public assets. The supplied record does not establish approval of that proposed extension. [4]

Together, these records show a specialized fleet procurement recommendation alongside reported continued use of Cityworks for broader operations. They do not establish exclusive system boundaries, prove a successful fleet implementation, or show that separate systems are always better.

When systems share information, decide which one holds the official record, what information moves between them, and who is responsible for keeping it accurate. For example, agree where equipment identities are maintained and how work costs reach the accounting system.

If you are considering wider asset planning and management responsibilities, read CMMS vs EAM: What's the Difference?. Compare the responsibilities you need to support before choosing a software category.

Six Questions to Ask Before Choosing a CMMS

  1. What problems are we trying to solve? Identify the maintenance tasks and decisions the software must improve.
  2. What should the CMMS handle? Decide which tasks belong in the CMMS and which belong in other systems.
  3. Can the software do our actual work? Ask vendors to demonstrate important tasks using realistic examples.
  4. Is our team ready? Identify who will maintain equipment records, train employees, manage work orders, and keep the system running.
  5. How will we know it's working? Set clear requirements for testing the software and checking the accuracy of its records.
  6. What will it really cost? Include setup, moving or cleaning up your information, training, integrations, support, renewals, and ongoing work. Check which costs are included in the software price and which are extra.

Use these questions to identify decisions and work that need attention. They are not a score, and they do not provide a universal formula for choosing a basic CMMS, a more advanced CMMS, or an enterprise asset management (EAM) system.

Buy what you can explain and support

Start with the work your maintenance team needs to do. Make sure you have the people, training, equipment information, and processes to support it. Test important tasks before accepting the system, and check the full costs of setting it up and keeping it working.

Add capabilities or complexity when you can explain why they are needed and how your team will use them. The choice depends on your work, risks, budget, and ability to implement the software.

The D.C. and Stockton examples illustrate specific documentation, responsibility, and system-scope questions. They do not establish how often organizations buy too much or too little CMMS software.

For the wider evidence and its limits, browse the Public CMMS Procurement Database and the research methodology.

Choose a system that supports the work you need and that your organization can put to use and keep working.

Sources

  1. Office of the D.C. Auditor — Multiple Failures in Department of General Services Management of Work Orders (November 28, 2022)

    Printed report pages 12 and 14 explain the expenditure figures and their scope; pages 14–21 cover cost capture, supporting records, preventive maintenance, and operational controls.

  2. D.C. Law 25-139 — Work Order Integrity Amendment Act of 2023

    Section 2(b) sets the school-facility training, notification, feedback, and conditional verification duties. The law became effective March 5, 2024.

  3. City of Stockton — Fleet Management and GPS Telematics Procurement, File 21-0614 (December 14, 2021)

    Staff recommendation and Background/Present Situation describe the evaluation and existing fleet tools. This record does not confirm purchase execution or implementation outcomes.

  4. City of Stockton — CMMS Agreement Amendment No. 2, File 26-0057 (March 3, 2026)

    Staff report describes continued Cityworks use and earlier agreements, and recommends a second extension. The supplied record does not confirm approval of that extension.