Pre construction planning often starts with perfectly reasonable spreadsheets.
One workbook holds the estimate. Another tracks procurement. A risk register sits elsewhere. Actions and approvals are spread across email and meeting notes.
The problem is not that spreadsheets are automatically unsuitable for construction. The problem appears when the planning workflow depends on several people keeping those records aligned while the project changes.
This guide focuses on that spreadsheet-led operating problem.
The core pre construction workstreams
Most planning teams are coordinating several connected areas:
- scope;
- estimating;
- programme;
- procurement;
- risk;
- design information;
- approvals;
- handover actions.
Each area affects the others.
A design change may alter cost, programme, procurement and risk at the same time.
If those effects are tracked in separate files, the team has to reconcile them manually.
Where Excel works well
Excel remains useful for:
- estimating models;
- flexible cost analysis;
- scenario planning;
- one-off comparisons;
- temporary registers;
- early-stage calculations.
The case for an app is stronger when the workbook is no longer mainly analytical and is instead coordinating a repeatable workflow.
For example, a live procurement tracker may have owners, due dates, approvals, document links, status rules and regular reporting. That is closer to an operational system than a calculation model.
Warning signs the workflow is outgrowing the spreadsheet
Look for repeated operational friction.
Version confusion
Several copies of the same tracker circulate between commercial, design and delivery teams.
Manual reporting
Someone spends hours rebuilding a current position before each meeting.
Approval gaps
A status changes in Excel, but the actual approval exists in an email or message.
One-person dependency
Only one person knows which tabs, formulas or exceptions are trustworthy.
Weak handover
Information has to be re-entered when responsibility moves from pre construction into delivery.
Mobile problems
Site or field users cannot easily update the record where the work happens.
Poor permission control
Different roles need different access, but everyone effectively receives the same workbook.
These are signs that the process may benefit from a controlled application.
Start with one workflow, not a giant construction platform
A common mistake is trying to replace every construction system at once.
A better starting point is one spreadsheet-led process causing measurable friction.
Examples include:
- procurement tracking;
- design actions;
- risk registers;
- pre-start checklists;
- tender returns;
- package approvals;
- handover actions;
- variation tracking;
- inspections;
- subcontractor information.
A focused application can sit alongside existing accounting, document-management or project systems.
It does not need to become an ERP or CDE.
Example: procurement tracker
A procurement workbook may currently contain:
- package;
- supplier;
- required-on-site date;
- enquiry status;
- quote status;
- approval status;
- order date;
- lead time;
- notes.
The actual process may also involve email approvals, documents and repeated chasing.
A web app can turn that into:
Create package → request quotation → review → approve → order → monitor delivery → flag exceptions
with assigned owners and live reporting.
The goal is not to replace Excel because Excel is bad. It is to remove the manual gaps around a repeated business process.
Example: pre-start approvals
A pre-start tracker may cover:
- information required;
- responsible party;
- due date;
- submitted date;
- review status;
- comments;
- final approval.
If approval evidence lives outside the workbook, the spreadsheet only tells part of the story.
A controlled app can store the record, evidence, reviewer, decision and timestamp together.
That becomes especially useful when several projects use the same process.
Keep cost modelling where it belongs
Not every spreadsheet needs to disappear.
A detailed estimating model may continue to be the right tool even if the surrounding workflow moves into an application.
The application can manage:
- project records;
- users;
- tasks;
- approvals;
- documents;
- status;
- reporting.
Excel can remain available for analysis where its flexibility is genuinely useful.
This is a better boundary than attempting to force every calculation into custom software.
How to scope a pre construction app
Ask:
- Which workbook is causing the most repeated administration?
- Who uses it?
- What actions happen around it?
- Which statuses matter?
- Which approvals need evidence?
- Which documents belong to the records?
- Which reports are rebuilt manually?
- What information needs to pass into delivery?
- What should remain in existing systems?
The first release should remove the biggest source of friction, not attempt to digitise the entire construction business.
Database versus spreadsheet
Once records have owners, statuses, permissions and history, a database-backed application provides advantages a shared workbook struggles to enforce.
If you are thinking specifically about connected construction records such as RFIs, defects, approvals and commercial items, see Building a Database for Construction Projects.
That article focuses on record structure. This one focuses on the pre construction workflow.
Where Spreadsheet Upgrade fits
Spreadsheet Upgrade is aimed at businesses that already have an important spreadsheet-led process and want it rebuilt as a managed web application.
The starting point is the free fit check.
If the process is worth progressing, the standard Spreadsheet Assessment is £295 excluding VAT in the selected currency. The assessment maps the workbook, users, workflow, permissions, data and edge cases.
For eligible managed plans, the agreed first build is included subject to the current published scope and terms, with hosting, backups, maintenance, security fixes and support included as part of the service.
If your pre construction team is repeatedly reconciling trackers, chasing approvals or rebuilding reports from Excel, start with the free fit check and use the existing workflow as the basis for the replacement.