Why Spreadsheets and Outlook Are Still Running Most Construction Projects

The Technology Gap Nobody Talks About

The construction technology market has grown enormously over the past decade. Platforms for document management, BIM coordination, site inspections, safety reporting, scheduling, and project cost tracking. Billions of dollars of venture capital have been deployed. The result is that construction teams have more tools than ever before, and they are still tracking their most important obligations in Excel.

This is not a failure of adoption. It is a failure of product design. The software industry looked at construction and saw document volumes, field complexity, and scheduling challenges. They built tools to address those visible problems. What they did not see, because they did not come from the industry, was the problem underneath all of it: the contractual obligations that determine whether the project ends in a handshake or a dispute.

Document management does not track obligations. Field management does not surface contract risk. Scheduling software does not know that a Special Condition amended the standard notice period from 20 working days to 10. The gap between what project teams need and what the market sells them has never been wider.

Why Spreadsheets Survive

Spreadsheets persist in contract administration because they are the only tool flexible enough to do what project teams actually need. A good contract administrator builds a spreadsheet that tracks payment claim deadlines, notice periods, variation registers, and correspondence logs. They customise it for every project because every project has different Special Conditions, different amended timeframes, and different contractual structures.

No off-the-shelf platform offers that flexibility for contract-specific obligation tracking. So the spreadsheet wins, not because it is good, but because it is the least bad option.

The problem is that spreadsheets have fundamental limitations for this purpose:

• They are personal, not institutional. The spreadsheet lives on one person's computer or in their personal OneDrive folder. When that person leaves the project, the spreadsheet either goes with them or becomes an unmaintained artefact that nobody trusts.
• They do not alert. A spreadsheet tracks deadlines but does not tell you when one is approaching. It requires someone to open it, review it, and act on it. If that person is sick, on leave, or simply busy with site issues, deadlines approach unnoticed.
• They do not connect. The payment claim tracker is one spreadsheet. The variation register is another. The correspondence log is a third. None of them talk to each other. When a variation instruction creates a new deadline that affects the payment schedule, someone has to manually update multiple documents.
• They decay. Every spreadsheet starts accurate. Over the life of a project, as hundreds of updates accumulate, formulas break, rows get deleted accidentally, and the document gradually drifts from reality. By month 18, nobody is entirely sure the spreadsheet is right, but nobody has time to audit it.

The spreadsheet is the symptom. The disease is that no tool on the market was purpose-built to track contractual obligations on a live construction project. So every project team builds their own system from scratch, with all the fragility and key person risk that implies.

Why Outlook Is the Real Risk

If spreadsheets are a known compromise, Outlook is the silent risk. On most construction projects, the correspondence history of the entire contract lives in the personal inbox of the lead PM or contract administrator.

Every formal notice, every instruction, every response to a payment claim, every letter about a variation. Filed in personal folders with naming conventions that make sense to one person. When that person hands over the project, the incoming PM inherits a filing structure they did not create, a search function that depends on knowing the right keywords, and no link between any email and the contractual obligation it relates to.

Under NZS 3910, formal notices create legal obligations with specific timeframes. A notice of potential claim under Clause 13.3.1 starts a clock running. A payment claim under the Construction Contracts Act creates a response obligation that, if missed, makes the full claimed amount a debt due immediately. These are not emails that can wait until someone gets around to reviewing the inbox. They are contractual triggers that require tracked, timely responses.

Outlook does not know the difference between a contractual notice and a meeting invitation. It treats them identically. And that is a structural risk on every project where Outlook is the primary communication system.

What the Market Got Wrong

Construction technology vendors approached the industry from the outside. They saw construction as a field operations problem. They built platforms for what happens on site: inspections, defect management, daily logs, safety observations, drawing management.

Those tools are useful. Nobody is arguing otherwise. But they solve the visible 40% of construction project management while ignoring the contractual 60% that determines whether the project ends well or ends in dispute.

For a detailed comparison of what project management platforms do versus what project intelligence does, see our article on Procore vs Provan. And for how AI is beginning to address this gap specifically, read our piece on ChatGPT for construction and why general-purpose AI tools are not the answer either.

The next generation of construction technology will not replace spreadsheets by being a better spreadsheet. It will replace them by being something fundamentally different: a system that understands the contract, tracks obligations automatically, connects correspondence to clauses, and tells you what needs attention before it becomes a problem.

What Needs to Change

The solution is not another platform that requires manual data entry by already overloaded project teams. It is a system that ingests the contract documents, maps the obligations automatically, tracks every deadline without human intervention, and surfaces what matters each day.

That system needs to understand NZS 3910 Special Conditions. It needs to know that this particular contract amended the standard payment response timeframe. It needs to link incoming correspondence to the relevant clause and start the appropriate clock. It needs to work across multiple contracts simultaneously so that a PM managing five subcontracts can see all their obligations in one view.

The spreadsheet survives because nothing better exists for this specific job. The day something better does exist, the spreadsheet will disappear overnight. Not because of a technology mandate from management, but because the project team will choose the tool that makes their life easier and their project safer.