Spreadsheets can still work for a small, stable estate where one team owns the data and the volume of maintenance, compliance evidence, and contractor activity remains manageable. CAFM software becomes the stronger option when multiple sites need consistent workflows, automated scheduling, clear ownership, live status information, and an audit trail. The real tipping point is not the number of rows in the file. It is the moment the operation depends on information that people can no longer verify quickly or trust.
Why multi-site spreadsheets become difficult to control
When spreadsheets are still a reasonable fit
What CAFM software changes operationally
How the two approaches compare across core FM workflows
Signs you’ve outgrown spreadsheets
What can go wrong moving away from spreadsheets?
What should teams migrate first?
When might CAFM be the wrong next step?
Which approach is better for multi-site FMs?
The first spreadsheet is rarely the problem. It is usually sensible, clearly labelled and owned by somebody who knows exactly what each column means. It records the PPM schedule, contractor contacts, certificate dates and perhaps an asset list. For a while, it does the job perfectly well.
Then the estate changes, and a new site arrives with its own contractor, naming conventions, and inherited asset register. One building logs faults by email, another uses a shared form, and a third calls the Facilities Manager because that has always worked. Local teams add columns to answer local questions. Finance needs costs allocated correctly, compliance needs evidence linked to the right work, and operations expects an estate-wide dashboard before Monday morning has properly begun.
The spreadsheet is still present, but the process now includes inboxes, shared drives, reminders, contractor portals, and the site manager who knows which boiler record is current. The file may look tidy while the operating model around it has become remarkably inventive.
That is why the CAFM-versus-spreadsheet decision is often misunderstood. It is not a contest between modern software and an old-fashioned tool. It is a decision about how much operational control the estate needs, where accountability sits and whether the organisation can prove that work has happened without reconstructing the story afterwards.
Spreadsheets remain reasonable when the operation is simple enough for manual control to be reliable. They are flexible, familiar and good for calculations, one-off analysis and compact registers. Buying CAFM for a handful of predictable tasks can create more administration than it removes.
A spreadsheet-led approach may still suit an organisation where:
Even here, the spreadsheet needs an owner, controlled access, data-quality reviews and a documented response to missed deadlines. Conditional formatting is useful, but turning a cell red does not assign responsibility. It merely makes the problem more colourful.
Spreadsheets should also remain useful after CAFM implementation for analysis and budget modelling. They simply should not compete with the live operational record.
Trust usually breaks before the file itself does. A spreadsheet can hold hundreds of thousands of rows and still open perfectly well, but that says nothing about whether the dates are current, whether the task happened, whether the certificate belongs to the right asset or whether somebody changed a formula three tabs ago.
Multiple sites create multiple contributors, and multiple contributors create local copies unless the process is tightly controlled. Soon there is a master tracker, a site tracker, a contractor tracker, and a file with an evergrowing name.
Conflicting versions make it difficult to establish what is genuinely outstanding. Teams reconcile differences, leaders receive stale reports and site staff keep their own records because they do not trust the central one. Once parallel records become a form of self-defence, the organisation has a system problem.
A spreadsheet can calculate a due date and highlight it. It cannot confirm that the right person has accepted the task, arranged access, completed the work, uploaded evidence and responded to a failed inspection. Those steps usually sit in email, calendars and memory.
This creates key-person dependence. The system works because an experienced coordinator knows which contractors need chasing, which sites require extra notice, and which red cells are genuinely urgent. When that person is on leave, the process develops a sudden interest in suspense.
A row saying “complete” is not the same as evidence of completion. Multi-site teams may need certificates, photographs, engineer notes, remedial actions and approval records linked to the correct building, asset and task. If the schedule lives in a spreadsheet while the evidence lives across folders and inboxes, an audit becomes an exercise in joining the two.
The Health and Safety Executive’s maintenance guidance advises employers to have arrangements that keep work equipment maintained and notes that, where a maintenance log exists, it should be kept up to date. The practical point for FM teams is straightforward: a record only helps if it is current, attributable and connected to the work it is meant to evidence.
CAFM software changes the operation by turning registers into managed workflows. A Computer-Aided Facilities Management platform can connect sites, assets, work orders, planned maintenance, contractors, documents, and reporting so that activity is recorded as it happens rather than reconstructed later.
The important difference is not that CAFM stores more information. A spreadsheet can store plenty. The difference is that a well-configured system can control what happens next: generate recurring tasks, assign owners, notify users, record status changes, retain evidence and show outliers across the estate.
That control should create one agreed process for raising, assigning, updating and closing work, with consistent definitions, visible exceptions and evidence linked to the relevant job, asset and location. It should reduce dependence on one person’s inbox and make contractor performance and reporting easier to assess.
CAFM is not automatically a single source of truth merely because the phrase appeared in a sales presentation. It becomes trusted when responsibilities are clear, users update it at the right point in the workflow, data standards are enforced, and managers use the information to run the operation. A neglected CAFM system can become an expensive spreadsheet with a login screen.
The better fit depends on the workflow, not the label on the tool.
| Decision area | Spreadsheet-led approach | CAFM-led approach |
|---|---|---|
| Planned maintenance | Can list tasks and due dates effectively at low volume. Reminders, assignment and escalation remain manual. | Can generate recurring work, assign responsibility and expose overdue tasks across sites. |
| Reactive work | Often relies on email, calls or forms before somebody updates the tracker. | Provides a consistent route to raise, prioritise, assign and track work orders. |
| Compliance evidence | Usually records dates or document locations. Proof may remain in folders, inboxes or separate systems. | Can link evidence, completion records and remedial actions to the relevant task, asset and site. |
| Contractor coordination | Flexible but dependent on chasing, forwarding and manual status updates. | Can give contractors a structured method for receiving work, reporting progress and returning evidence. |
| Asset records | Easy to start and bulk-edit, but changes can create conflicting registers and uncertain ownership. | Can maintain a governed live record linked to maintenance history, documents and related activity. |
| Multi-site reporting | Requires consolidation and consistent local definitions. Snapshots age quickly. | Can provide portfolio and site-level views from the same live data, subject to adoption and data quality. |
| Audit trail | Change history can be difficult to interpret across files and supporting evidence. | Can retain attributable status changes, timestamps, and supporting records within the workflow. |
| Flexibility | Very high. Teams can add fields and workarounds immediately, including some they will regret later. | More controlled. Configuration takes effort, but consistency reduces local reinvention. |
| Upfront effort | Low to begin. Governance and reconciliation effort grows gradually and is often hidden. | Higher because of selection, configuration, migration, training, and process design. |
| Best fit | Small, stable operations with strong ownership and limited workflow complexity. | Multi-site operations that need repeatable processes, live accountability, evidence, and scalable oversight. |
A spreadsheet can answer “what is due?” if the data is current. A CAFM workflow should also answer “who owns it, what evidence was returned, and what needs attention now?”
This matters because every asset or statutory requirement can generate recurring work across several sites. Automation is valuable when it removes repetitive job creation and chasing, then directs attention towards exceptions.
The system still needs sensible rules. Automating a confused maintenance regime does not make it less confused; it simply produces the confusion on time.
Contractor performance is difficult to manage when instructions, approvals, updates and certificates sit in separate email threads. A CAFM-led process can provide a common workflow for issuing jobs, recording attendance, returning evidence and closing tasks.
It does not remove the need to manage contractors. Guidance on managing contractors still expects organisations to plan, exchange information and monitor work. Software can make those controls visible; it cannot outsource judgement.
An asset register becomes valuable when equipment fails, a compliance task is planned, or a replacement budget is challenged. Until then, an uncertain list can sit undisturbed for years, enjoying the administrative equivalent of a long weekend.
Spreadsheets are useful for surveys and data cleansing, but CAFM can give each asset a controlled record linked to work history and planned tasks, provided the imported data is credible and somebody owns its quality.
SFG20’s published findings from its 2025 State of Facilities Management Survey reported that 43% of organisations believed their asset registers were less than 75% accurate. The exact percentage will vary by sample and organisation, but the operational lesson is more important: software selection cannot substitute for asset verification.
No. CAFM introduces visible costs for licences, implementation, configuration, training, support and data migration. Spreadsheets often appear cheaper because the software is already available and the labour around it is spread across job roles, inboxes and monthly reporting routines.
A fair business case should compare total operating cost rather than purchase price alone, including:
Not every cost will disappear. The business case should identify which steps can genuinely be removed and measure the current process first: job volumes, reporting time, evidence chasing, systems touched and delays.
Otherwise, the ROI calculation becomes a confident-looking estimate of a process nobody has actually timed.
An estate has probably reached the tipping point when manual control is no longer dependable even though the team is working hard to maintain it.
One sign on its own may be manageable. Several together indicate that the organisation is paying for the limitations of the current approach, even if those costs do not appear on a software budget line.
CAFM implementation fails when organisations treat it as a file migration instead of an operating-model change. The software needs agreed workflows, owners, definitions, priorities and user behaviour. Importing inconsistent data into a new platform makes the inconsistency easier to search; it does not make it correct.
Common mistakes include:
Standardisation needs judgement. Sites may genuinely have different assets, risks, access rules and service arrangements. The goal is not to make every building identical. It is to create a common control framework while allowing justified local variation.
Start with the data and workflows that control current risk and repeatable work. Most teams get more value from a smaller, trusted live dataset than from a heroic import of every record created since somebody first discovered freeze panes.
A practical first phase usually includes:
Historical information can be archived or added later where it has a clear operational, contractual or analytical purpose. Retention decisions should reflect legal, regulatory, contractual and organisational requirements. They should not be made solely to keep the import file pleasingly large.
CAFM may be a poor immediate fit where the operation is simple, the team cannot resource implementation, or the organisation is unwilling to standardise basic workflows. Without ownership, it can add another place to update while the original spreadsheets continue “just in case”.
The better next step may be to stabilise the spreadsheet process first: establish one master record, define owners and statuses, remove duplicates and measure the administrative burden. This work provides useful discipline if CAFM follows.
A system may also be unnecessary where the requirement is primarily one-off analysis rather than ongoing workflow. Spreadsheets remain excellent at modelling budgets, testing lifecycle scenarios and exploring data. The dividing line is whether the organisation needs to analyse information or continuously coordinate people, tasks, evidence and exceptions.
Spreadsheets remain useful, but they become a poor primary control system when multi-site FM depends on repeatable workflows, live ownership, connected evidence and consistent reporting. CAFM is usually the stronger fit once the estate can no longer answer basic operational questions without checking several files, inboxes or people.
The decision should not be driven by fashion, estate size alone or a supplier’s feature list. It should be driven by the cost of the current operating model, the consequences of unreliable information and the organisation’s readiness to adopt a more controlled process.
For teams considering a platform such as expansive, the sensible next step is to map one real workflow, perhaps a statutory PPM task or a reactive job involving a contractor, and test whether the platform can simplify it from instruction through to evidence and reporting.
The spreadsheet everyone is afraid to delete may still have a future. It just should not be running the estate by constitutional convention.