CAFM Software Buyer Worksheet for Contractors
A shortlist is useful only when each supplier answers the same operational questions. Use this worksheet to define your scope, gather comparable evidence, and leave unresolved items visible. It does not rank products or determine legal or regulatory requirements.
1. Set the boundary before comparing products
Complete these fields with your team. Keep assumptions in a separate notes column.
- Countries, business units, and sites in scope: ____________________
- Facilities, assets, spaces, or service requests to include: ____________________
- Teams that will request, approve, assign, perform, and review work: ____________________
- Current records or systems that may need to connect or move: ____________________
- Workflows deliberately outside this evaluation: ____________________
- People who will approve the shortlist and the evidence they need: ____________________
Write one sentence that describes the job the software must help your team complete: “We need to ____________________ for ____________________ across ____________________.” This statement is a test for the shortlist, not a product claim.
2. Agree what you mean by CAFM
The supplied source notes describe related categories differently. GoFMX’s snippet says CMMS specializes in maintenance and asset management. MRI Software’s snippet describes CAFM as more operational and IWMS as more strategic. Use those descriptions as prompts for your evaluation; ask each supplier how it defines the categories and which functions are included in the product you would buy. GoFMX category note · MRI category note
Accruent’s own comparison page lists FAMIS 360, Accruent EMS, Archibus, Planon, IBM TRIRIGA, and Spacewell in its 2026 overview. This records what that publisher lists; it is not an independent ranking, a regional-fit assessment, or evidence that any product supports your workflows. Accruent comparison
3. Turn operations into questions
Choose a small set of real examples from your team. For each one, ask every supplier to show the same start-to-finish path, then record what you observed.
- Requests and work: How does a requester describe a problem? How is it routed, assigned, updated, and closed? What can the requester see?
- Assets and spaces: Which fields, locations, identifiers, histories, and documents can your team record? Show a record using a sample from your operation.
- Planning and approvals: Can you represent your approval steps and responsible roles? Ask the supplier to show what happens when a step is skipped, returned, or reassigned.
- Mobile and site access: Ask the supplier to demonstrate the devices and connectivity conditions your teams actually use. Record any condition that was not demonstrated.
- Reporting: Name the question a manager needs answered, such as open work by site or completion status. Ask the supplier to build or show that view and identify its source fields.
- Connections and migration: List each existing system and record that matters. Ask what data can move, what must be reconciled, and which integration is included in the proposed scope.
- Country-specific setup: List each country and the local process or configuration you need reviewed. Ask the supplier to identify what is available now, show it, and state what remains unverified. Do not treat a sales statement as a legal determination.
4. Run one repeatable demonstration
Select a real, non-sensitive scenario and replace the blanks before the meeting: “At [site], [requester role] reports [issue]. The request should reach [team], pass through [approval], record [asset or space], and end with [completion evidence]. The reviewer needs to see [report or status].”
Ask each supplier to perform the scenario in the product, not just describe it. Record the product name and edition, configuration shown, steps completed, and any workaround. If a step is not shown, mark it “not demonstrated”; do not convert a promise, screenshot, or roadmap statement into a confirmed capability. Ask for a written follow-up with an owner and date for each open item.
5. Keep a comparable evidence table
| Evaluation item | Supplier A: demonstration or document | Supplier B: demonstration or document | Open question / owner |
|---|---|---|---|
| Request-to-close scenario | ____________________ | ____________________ | ____________________ |
| Asset or space record | ____________________ | ____________________ | ____________________ |
| Approval and reassignment | ____________________ | ____________________ | ____________________ |
| Required connection or data move | ____________________ | ____________________ | ____________________ |
| Country-specific setup | ____________________ | ____________________ | ____________________ |
| Reporting view | ____________________ | ____________________ | ____________________ |
Use the same status for every cell: shown, documented, stated but not verified, or not demonstrated. Keep a link or meeting note beside each entry so another reviewer can inspect the evidence.
6. Record the decision and its limits
Before selecting a supplier, write down the needs that are essential, the evidence that supports each one, the unresolved questions, and the person who accepts each remaining gap. Note the edition, implementation work, integrations, and support terms included in the proposal; ask the supplier to clarify anything absent. Revisit the decision if the scope or source evidence changes.
Keep this worksheet with the comparison record. Its purpose is to make the questions, evidence, and unknowns visible—not to certify compliance or announce a winner.
