A polished demo proves that software can follow a script. Multi-site operators need to know what happens when the work refuses to cooperate.
The demo begins exactly as expected. A clean request enters the system. The right person receives it. The provider accepts it. The job closes with a photo, the work order moves to complete, and the record looks clean. Everyone nods.
Let’s be honest with ourselves, though: that isn’t a test. It’s well-rehearsed choreography.
Multi-site facilities work is defined by exceptions: incomplete requests, conflicting priorities, provider coverage gaps, changing scopes, approval thresholds, access problems, partial completion, and invoices that arrive with their own interpretation of history. A scripted workflow can make almost any platform look capable because it removes the exceptions that would expose how the system would actually perform under real operating pressure.
“A serious CMMS evaluation should test how the system preserves control when the work stops following the script.“
Replace the feature list with an exception test
When exploring new CMMS options, give every new vendor the same imperfect scenario and require the presenter to work it live. Don’t accept a quick detour into a different environment. The point is to see the operating consequence of each decision: who can act, what becomes visible, what is recorded, and what must be repaired by hand later.
These 12 questions bring real facility conditions into the demo, creating a more credible test of how the system performs when work doesn’t go exactly as planned.
- What happens when the request is missing the asset, trade, or exact location?
- How does the system respond when three people report the same problem differently?
- Who can change the priority, and where is the reason recorded?
- What happens when the preferred provider declines or never responds?
- Can the scope or not-to-exceed limit change while preserving the original request, authorization, and complete change history?
- What happens when the technician can’t access the site or locates the wrong or even a different asset?
- How are approval thresholds applied across locations, trades and roles?
- Can a provider submit partial completion without closing the whole job?
- What prevents incomplete evidence from becoming a closed work order?
- How does the workflow handle disagreement about whether an issue is fixed?
- Can finance trace an invoice back to approved scope and completion evidence?
- Can the operating model change without rebuilding across the portfolio?
Score the evidence, not the performance
Use a simple 0–2 score for each question: 0 means the answer depends on manual work or cannot be shown; 1 means the platform can handle it with material configuration or a workaround; 2 means the workflow is demonstrated, governed, and reportable. Record the evidence shown and the follow-up owner. A persuasive presenter should not receive points for a future feature, however warmly described.
- Require the same scenario from every vendor.
- Include a facilities operator, an administrator, a finance reviewer and one field or provider user.
- Capture every off-system step the vendor asks the team to accept.
- Retest the three weakest exceptions in a configured proof of concept.
The demo should make the difficult work visible
A CMMS earns its place when it helps people make and defend decisions under imperfect conditions. The polished request is easy. The real evaluation begins when information is missing, responsibility shifts, or the cost changes. Bring those moments into the demo.
If you’re evaluating a new CMMS platform, discover how myWork can help you own the work even across your difficult scenarios. Book a demo today.