Construction App vs Excel for Compliance: Which Works Better on Multi-Site Projects?

Why Do So Many Contractors Run Compliance in Excel?

Because it works, at first.

A spreadsheet is free with software you already own. Everyone knows how to use one. It can hold a register, an inspection log, a certificate tracker or an action list, and you can start in ten minutes with no procurement, no training and no vendor.

For a single site with one or two people maintaining the records, that is often enough, and a well-built spreadsheet is a respectable compliance tool.

The trouble rarely appears on day one. It appears when the business grows: a second site, then a third, then subcontractors who need access, then a client who asks for evidence and a manager who wants one view across all the projects. The spreadsheet that was fine for one site becomes five, then fifteen, each slightly different, each maintained by a different person.

This article compares the two approaches at that point. It is not an argument that Excel is bad. It is an attempt to be specific about where it holds up, where it strains and where an app earns its cost.

What Does Compliance on a Multi-Site Project Actually Require?

"Compliance" is a broad word. In practice, for site teams it usually means being able to do and show these things.

Judge each tool against that list, not against a feature brochure.

How Is Excel Typically Used for Compliance?

Most multi-site setups follow one of a few patterns.

One workbook per site. Each site has its own register and logs, built from a template that has probably drifted.

One master workbook. A single file with a sheet per site, edited by several people.

Inspection forms in Excel or Word, printed, completed by hand and typed in later.

A roll-up workbook. A manager's file that pulls figures from the site workbooks, by link or by copy and paste.

Email as the transport. Files are sent for update and returned, with several versions in circulation.

Each pattern has its own failure modes, covered below.

What Does Excel Do Well?

It deserves a fair hearing.

Flexibility. You can build almost any list or calculation, and change it instantly.

Familiarity. Almost everybody can open and use a spreadsheet.

Low cost. There is no extra licence if you already have Microsoft 365 or Excel.

Analysis. Filters, pivot tables and charts are powerful, particularly for one-off analysis.

Control for the owner. You decide the structure and nobody can change it without you.

Good enough for simple records. A tidy certificate tracker or equipment register for a small team can work for years.

Real collaboration features, with conditions. Microsoft's guidance says Excel for Microsoft 365 supports several people editing a workbook at once and keeps a version history. That requires a Microsoft 365 subscription, a supported file format and the file to be stored in OneDrive, OneDrive for Business or SharePoint Online. If someone opens the file in a version that does not support co-authoring, others may get a "file is locked" message, and when two people change the same cell the last save generally wins. Changes made offline sync only when the computer reconnects.

Data entry controls, if you use them. Excel offers features such as data validation and cell protection that restrict what can be entered and prevent accidental overwriting. Many compliance spreadsheets do not use them.

Where Does Excel Strain on Multi-Site Compliance?

Each of these is manageable on its own. Together, at scale, they are where the cost builds up.

1. Capturing data on site

Excel is not designed for use on a phone in a basement. Entering data into a spreadsheet on a small screen, with gloves, is slow, and many teams fall back to paper and type it in later. That reintroduces the delay, the re-keying and the gap between what happened and what was recorded.

2. Evidence lives elsewhere

A spreadsheet can hold text and links. Photographs, video and documents are stored in folders or phone galleries, and matching them to the right row relies on naming discipline.

3. Version control

With a file per site, plus a master, plus copies sent by email, it can be unclear which is current. Co-authoring helps if everyone uses it properly, but it needs the right set-up and subscriptions, and workbooks that are emailed around bypass it.

4. Concurrent editing and conflicts

When several people edit the same sheet, the last save generally wins for the same cell, so a change can be silently overwritten. Assigning sheets or areas to individuals reduces the risk but is a process you have to maintain.

5. The audit trail

Version history shows earlier copies of a file. It is not the same as a record showing who changed which entry, when and from what. For compliance records, where you may need to show that something was recorded at the time and not altered, a clear entry-level history is valuable. Check carefully what your set-up actually captures.

6. Data quality

Spreadsheets will accept anything. Free-text dates, inconsistent names, blank cells and "N/A" in place of a real answer are common, and they make roll-ups unreliable. Validation and protection can help, but they have to be designed in and maintained.

7. Reminders and follow-up

A spreadsheet can highlight an overdue date with a formula, but it does not notify anyone. Chasing is manual, and it depends on someone opening the file.

8. Access control

You can restrict who can open a file or edit a sheet, but fine-grained control, such as a subcontractor seeing only their own actions on one site, is awkward to arrange and easy to get wrong.

9. Roll-up across sites

A manager's summary built by linking to several files is fragile. A moved file, a renamed column or a site that did not update can break it, often silently. If sites define "overdue" or "high priority" differently, the roll-up compares things that are not alike.

10. Key-person dependency

The spreadsheet often reflects how one person thinks. When they leave, or are on leave, nobody quite knows how it works.

11. Errors

Spreadsheet error is a well-studied problem. A 2000 review by Raymond Panko, presented to the European Spreadsheet Risks Interest Group, reported that field audits of real organisational spreadsheets found errors in 24% of 367 spreadsheets overall, and in 91% of 54 spreadsheets audited from 1997 onwards. In laboratory experiments, around half of the spreadsheets built from simple word problems contained errors. He concluded that errors can be reduced but not eliminated, that systematic cell-by-cell inspection by a group was the technique shown to be effective, and that protecting cells is easy and effective but rarely used.

Be careful how far this applies to compliance. That review is old, many of the audits were small, the audit methods varied, and the spreadsheets studied were largely calculation models. A compliance register is mostly a list, so the risks are less about formula errors and more about missing entries, stale data, inconsistent entries and overwritten cells. The general lesson still holds, which is that spreadsheet records need active checking, and that "it looks right" is not a test.

What Do Construction Apps Do Well?

Capture on the device. Purpose-built forms for phones and tablets, usually with offline use, so records are made at the time.

Structured records. Required fields and consistent forms make records complete and comparable.

Evidence attached. Photographs, video and voice notes sit with the record, with a time and often a location.

Entry-level history. Who recorded or changed what, and when.

Actions and reminders. Findings become assigned actions with due dates and status, and notifications reach people on site.

Certificates and expiry. Dates tracked with reminders.

Access control. Roles and permissions by project, with limited access for subcontractors where supported.

Cross-site views. Because every site records into the same structure, overdue items and open issues can be viewed together.

Reporting. Reports drawn from recorded data rather than retyped.

Where Do Construction Apps Struggle?

Cost. There is a subscription, and per-user or per-project pricing can add up as you grow.

Adoption. A tool that site teams find slow or awkward will be abandoned, and you will have both a system and a workaround.

Setup and change. Forms, permissions and training take effort, and productivity may dip at first.

Rigidity. An app is less flexible than a blank spreadsheet. Something you could do in Excel in a minute may be awkward or impossible in the product.

Signal. Apps that need a connection fail where connections fail. Offline capability must be tested.

Lock-in. Your records live in the vendor's system, so you need an export route that includes attachments.

Data protection. Records can include personal data, so check where it is stored and how it is protected.

Over-buying. A large platform may include far more than you need.

Not a cure for poor process. A confusing form is confusing on a phone too.

Side by Side: Construction App vs Excel for Compliance

Three Illustrative Failure Scenarios

These are invented examples of the kind of problem that appears as spreadsheets scale. They are not case studies.

The overwritten action. Two people update the same site workbook on the same morning. One closes an action and saves. The other, working from an older copy, saves later. The closed action reappears as open, and nobody notices until a client asks why it has been outstanding for a month.

The silent roll-up break. A manager's summary pulls from four site files. One site renames a column and moves the file. The summary carries on showing last month's figures for that site, with no warning, and the director sees a site that looks fine.

The lapsed certificate. A certificate tracker sits in a workbook owned by an office administrator. They are on leave, nobody else checks it and a subcontractor's certificate expires during that time. The error is found at an audit, not in the spreadsheet.

None of these requires Excel to be badly used. They are what tends to happen when records are maintained by hand, in separate files, by different people.

Which Works Better, and When?

There is no universal answer, but there are patterns. This is rough guidance, not a rule.

A useful test is whether your problem is capturing and following up (where apps tend to win) or analysing and calculating (where Excel tends to win).

Can You Use Both?

Often, yes, and it is a sensible position.

App for capture, Excel for analysis. Record inspections, issues and certificates in the app, then export data to Excel for custom analysis or board reporting.

Excel for registers, app for inspections. Keep a simple register in a spreadsheet, and use the app for the repeated, evidence-heavy work.

Excel as a bridge. Use spreadsheets to hold your existing records while you pilot an app on one workflow.

The key is to decide which system is the record for each type of information, and to avoid keeping the same data in two places that must be updated by hand.

If You Stay With Excel: How to Do It Properly

If Excel is the right choice for you now, these practices reduce the risks above.

• Use one master template, and treat changes to it as controlled.
• Store files in one shared location such as SharePoint or OneDrive with co-authoring, and ban emailed copies.
• Use data validation, such as drop-down lists for statuses and date fields for dates.
• Protect formulas and structure, leaving only input cells editable.
• Define terms, such as "overdue" and "high priority", in a visible key.
• Name an owner for each workbook, and a deputy.
• Make roll-ups robust, for example by consolidating into one table instead of linking to loose files, and add a check that flags missing or stale data.
• Review periodically. Have someone other than the author check a sample of entries and the formulas. Panko's review found that independent group inspection was the technique shown to work, and that informal reasonableness checks were not.
• Back up and keep history, and test restoring.
• Keep evidence in a consistent folder structure, linked from the relevant row.

How to Test Both Before You Commit

Try the same six scenarios in each.

1. An inspection in poor signal. Complete an inspection with photographs in a basement or in flight mode, then reconnect. See what arrives and in what state.
2. Two people, one record. Have two people update the same action at the same time. See what happens.
3. An action from finding to close-out. Raise, assign, resolve and verify a defect, and see how easily the history can be read.
4. A lapsing certificate. Enter one that expires soon and see who is told.
5. A roll-up across three sites. Produce a single view of overdue items, and then change something in one site and see whether the roll-up notices.
6. An auditor's request. Ask someone to find five random past records and the evidence behind them. Time it.

Add a seventh if you can: ask a supervisor who did not help build either system to use each one on site for a week, and ask which they would choose.

How to Move From Excel to an App Without Losing Your Records

If you decide to change:

• Clean before you move. Fix inconsistent names, dates and statuses first.
• Pick one workflow to pilot, such as inspections or issue tracking, on one or two sites.
• Rebuild the form, don't copy it. Simplify, and make the key fields required.
• Import what you need, such as current registers and certificates, and archive the rest.
• Run in parallel briefly, then set a date to stop updating the spreadsheet for the pilot workflow.
• Keep an export of your old records, including evidence, in a place you can find.
• Review after 30 and 90 days, and compare time, completeness and follow-up with your baseline.

Construction App vs Excel Checklist

• [ ] We know which compliance tasks we need to do and prove, and how many sites are involved.
• [ ] We have identified which tasks currently depend on retyping, chasing or searching.
• [ ] We know how many versions of our key files exist, and which is current.
• [ ] Field teams can record on site without retyping, including where signal is poor.
• [ ] Evidence is linked to the record, not stored separately.
• [ ] We can show who recorded or changed an entry, and when.
• [ ] Actions have owners, due dates and status, and overdue items are visible without searching.
• [ ] Certificates have expiry reminders that reach someone other than the file owner.
• [ ] Access can be limited by site and role, including for subcontractors.
• [ ] Roll-ups across sites are reliable and use common definitions.
• [ ] Someone other than the author checks the records or formulas.
• [ ] We have tested both options with the same scenarios.
• [ ] We know the full cost of each, including time, subscription and risk.
• [ ] We can export our records, including attachments, from whatever we choose.

How KaelSite Fits

KaelSite is a mobile-first construction compliance platform for UK teams, designed for the capture and follow-up end of the spectrum. It offers:

• Regular inspections that work offline-first, with photo, video, voice and geotag capture.
• Form Studio, a no-code builder, so you can recreate your own inspection forms and use the same one across projects.
• An Issue System for near-misses, non-conformances, defects and observations, so findings become tracked actions.
• Certificates and expiry alerts, to replace a spreadsheet tracker.
• Projects and colleagues, with one account across mobile and web.
• A report editor and AI-assisted drafting on the web version, to turn recorded information into reports. Treat any AI draft as a first pass.

For a multi-site business, check the plan limits, such as the number of projects, team members and inspections, against your own sites on the Plans page before assuming a particular plan fits. KaelSite is not a general-purpose analysis tool, so many teams will keep Excel for custom analysis and use KaelSite for the records behind it.

The fairest test is the one above: run your own inspection form on one or two sites and see how it compares with your spreadsheet.

Frequently Asked Questions

Is Excel good enough for construction compliance?

For a single site with simple records and a careful owner, it can be. As the number of sites, people and records grows, the lack of on-site capture, attached evidence, an entry-level history and reliable roll-ups tends to cost more time and create more risk.

What is the main weakness of Excel for multi-site compliance?

There is no single weakness, but a cluster: data entry on site is awkward, evidence is separate, version control and roll-ups depend on discipline and records can be changed without a clear entry-level history. Each is manageable alone, and together they get harder to control as you grow.

Can several people edit the same Excel file?

Yes, with Excel for Microsoft 365 and the file stored in OneDrive or SharePoint Online, according to Microsoft's guidance. Conflicts can still occur, because the last save generally wins when two people change the same cell, and files emailed around bypass the feature.

How common are errors in spreadsheets?

Research reviewed by Panko found errors in a large share of audited spreadsheets and in about half of those built in experiments. That evidence is dated and mostly concerns calculation-heavy spreadsheets, so it does not map exactly to compliance registers, but it supports the view that spreadsheets need active checking.

Can we use Excel and an app together?

Yes. A common pattern is to capture and follow up in the app and export data to Excel for custom analysis. Decide which system is the official record for each type of information.

Is an app always more expensive than Excel?

The subscription is, but the total cost includes time spent retyping, chasing, searching and compiling, and the risk of missing or inconsistent records. Compare the full costs of both over a sensible period, using your own measurements.

Do construction apps work without signal?

Some do and some do not. Test by completing an inspection with photographs in flight mode, then reconnecting.

How do we move from Excel to an app?

Clean your data, pilot one workflow on one or two sites, rebuild the form, import what you need, run in parallel briefly, set a date to stop updating the spreadsheet and keep an export of your old records.

Will an app make us compliant?

No. Compliance depends on competent people and sound procedures. An app can make the records and follow-up behind them easier to create, find and rely on.

Final Thoughts

Excel is a good tool that is often asked to do a job it was not built for. At one site, that can be fine. At several, the weak points, awkward capture, scattered evidence, thin history, fragile roll-ups and dependence on a few people, start to matter.

The honest answer to "which works better?" is that it depends on whether your problem is capturing and following up on site, or analysing and calculating in the office. For multi-site compliance, the first usually dominates, which is why many contractors end up with an app for the records and Excel for the analysis.

Test both with the same scenarios, count the full costs, and make sure that whichever you choose, you can get your records out.

This article is intended as general information for orientation and does not constitute legal or professional advice. Software can support compliance processes but does not replace competent people, project procedures or the responsibilities set out in applicable regulations and standards.

Sources

• Raymond R. Panko, Spreadsheet Errors: What We Know. What We Think We Can Do (EuSpRIG Spreadsheet Risk Symposium, July 2000), for field-audit and laboratory error rates and the effectiveness of group code inspection: arxiv.org
• Microsoft Support, Collaborate on Excel workbooks at the same time with co-authoring, for requirements, version history and limitations: support.microsoft.com