Excel to Civil Construction Software: A Migration Guide

Many South African civil contractors run a R100,000,000 order book on a folder of spreadsheets that only one QS understands. It works until it doesn’t. A remeasurement does not tie back to the certificate. A plant sheet misses three weeks of hours. Or the resident engineer queries a variation from eight months ago, and nobody can find the version you submitted.

This guide explains where Excel breaks on a civil site and how to move to construction software step by step without losing your data. It also covers what you should keep in Excel afterwards. It is written for contracts managers, QSs and directors at CIDB CE grade 5 to 9 firms.

Why Do Civil Contractors Still Use Excel?

Excel won on civil sites because it was flexible, cheap and already installed, and most alternatives did not understand civil work. Civil contracts are remeasured by chainage, run on GCC or NEC and make or lose money on plant. Most building software was not designed for any of that, so the commercial team built its own workbooks.

Building software is usually designed around JBCC contracts and progress by floor or unit. A road or a bulk water line runs on the GCC (SAICE’s General Conditions of Contract) or NEC instead.

Excel is a good tool. The trouble is that a live civil contract is a shared, audited record that lasts for years. A spreadsheet is a personal file.

Where Does Excel Break on a Civil Site?

Excel fails in the same six places on almost every civil contract: remeasurement, plant and fuel, payment certificates, several sites at once, file versions and offline work. Each one costs money as well as time. If you recognise three or more on your contracts, your spreadsheets carry more risk than they should.

Where it breaks	What happens in Excel	What it costs you
Remeasurement by chainage	Quantities sit in one workbook, the BOQ in another, the certificate in a third. Links break when someone inserts rows	Under-claimed quantities, or over-claims the engineer cuts and then distrusts
Plant and fuel	Hour-meter readings and fuel slips are typed in weekly from paper, if at all	Use you cannot prove, internal hire rates nobody believes, fuel losses nobody sees
GCC and NEC certificates	Retention, advances, variations and contract price adjustment sit in hand-built formulas	One wrong cell carries forward every month until an audit finds it
Several sites at once	Each site manager uses a slightly different template	Directors only see which contract loses money at month-end, or later
Versions	”Cert 14 FINAL v3 (Thabo edits).xlsx” in an email thread	Nobody can prove what was submitted when a public client queries it two years later
Offline and load shedding	Files sit on one site laptop and move by memory stick or WhatsApp	Lost diaries, missing site instructions, double entry when the office catches up

The audit test. Pick a certificate you submitted to a municipality 18 months ago. Can you show, in under ten minutes, the measured quantities, signed site instructions and variation approvals behind every line? If the answer depends on one person’s laptop, your records will not hold up when the client’s auditors arrive.

Variations need their own warning. Under GCC 2025, an oral instruction is not a variation order. Only a written order, confirmed by the contractor, counts. The notice of claim and the detailed claim also run on separate timelines (see our guide to GCC 2015 vs GCC 2025 payment certificates). Miss a deadline and you risk a time bar, which means you may lose the right to claim. A spreadsheet does not warn you. It only records, too late, that you missed one. On NEC contracts, the same risk applies to the eight-week notice for NEC compensation events.

Measurement is the other weak point. Our guide to remeasurement by chainage shows how to trace every quantity to a signed sheet, and our guide to the GCC payment certificate process sets out the monthly cycle those quantities feed.

Before You Migrate: Know What You Have

Start with an honest inventory of your spreadsheets, because you cannot migrate what you have not mapped. List every active workbook with its owner, purpose, frequency, inputs and risk. Then sort them into contract records, operational data and analysis. Only the first two groups need to move.

A grade 7 contractor with four live contracts can easily have 40 or more active files.

Run a two-week inventory. For every workbook in use, record:

Owner: who updates it and who relies on it.
Purpose: measurement, certificate, plant, cost report, cash flow, tender, HSE.
Frequency: daily, weekly, monthly or once per contract.
Inputs and outputs: where the data comes from and where it goes (the client, the director, your accounting package).
Risk: what happens if it is wrong or lost for a week.

Then sort the list into three groups:

Contract records: BOQ, measurement, certificates, variations, site diaries.
Operational data: plant, timesheets, stores, fuel.
Analysis: what-if models, tender pricing, cash flow forecasts.

You migrate the first two groups. The third group is often fine where it is.

How Do You Migrate From Excel to Civil Software?

A good migration moves one contract at a time, runs in parallel for a short, fixed period, and has a named owner who can say no. Clean your reference data, pilot one contract, import the priced BOQ, run one or two certificate cycles side by side, then move the site and roll out contract by contract. The seven steps below show how.

Step 1: Clean your reference data

Software is only as good as the reference data you load, so fix it before you import anything. Agree one list of cost codes and one plant register with fleet numbers and internal hire rates. Add one list of subcontractors and suppliers, and standard units for each BOQ item. Allow two to four weeks.

Timesheets and supplier lists also hold personal information, such as ID numbers and phone numbers. Under POPIA (the Protection of Personal Information Act), you stay responsible for that data when a software provider stores it for you. Sections 19 to 21 deal with security safeguards and the written contract with that provider. Only migrate what you still need.

Step 2: Pick the right pilot contract

Choose a pilot that is real enough to prove the software, but not so critical that a mistake hurts the business. The best pilot is newly awarded or in its first quarter. It has a cooperative resident engineer and uses a contract form you know well, usually GCC 2015 or GCC 2025. Avoid a contract that is in dispute or two months from practical completion.

Step 3: Load the BOQ and the opening position

Import the priced BOQ instead of retyping it, then load the opening position at a clean cut-off date. Then load quantities measured to date, certificates paid, retention held, approved variations and open claims. Reconcile the opening total to the last certified amount, to the rand, before you move on.

Step 4: Run in parallel, with a deadline

Run the spreadsheet and the software side by side for one or two certificate cycles, then switch Excel off. Agree the rule up front. If certificate two matches within an agreed tolerance, Excel becomes read-only for that contract.

Step 5: Move the site, not just the office

The change only sticks when the site team captures data at source, which means working offline. Daily diaries, plant hours, fuel issues, labour and quantities by chainage should be entered on site. The data then syncs when signal comes back. Train foremen and plant clerks first.

Step 6: Roll out contract by contract

Once the pilot has run two clean cycles, roll out to new contracts first and existing ones at a natural break. Do not migrate a contract in the middle of a claim. This way a typical grade 7 firm can move its whole portfolio in three to six months, with every certificate on its normal cycle.

Step 7: Set governance and lock the old files

Decide who owns each record in the new system, then archive the old workbooks as read-only. Name a system owner, often the senior QS or contracts manager. Set user roles and agree who approves variations and certificates. Archive the Excel files in one place, with a note on where the live data now sits.

Do not delete the old files. Accounting records fall under section 24 of the Companies Act (generally seven years) and section 29 of the Tax Administration Act (generally five years after the return). Ask your auditor which workbooks count.

Still certifying a civil contract from five linked workbooks? Sakha keeps your BOQ, measurement and progress, payment certificates, plant records and an offline site diary in one cloud software built for South African civil contractors: see a product demo.

Which Type of Software Should Replace Excel?

The type of tool you pick decides how much of your civil work leaves Excel, and most options cover only part of it. Field apps handle photos and snags, desktop suites handle estimating, and only civil-specific software carries remeasurement, plant and GCC or NEC certificates in one record. Test each option on your own contract before you choose.

Ask every vendor the same questions, test them on your own BOQ, and compare the answers in writing.

What you need	Excel	Desktop estimating suite	Generic project or field app	Civil-specific cloud software
Remeasurement by chainage	Manual, fragile	Partly, office only	Not built for it	Built in
GCC and NEC certificates	Hand-built formulas	Often still Excel templates	No local contract forms	Built in
Plant, fuel and hire rates	Manual	Limited	Rarely	Built in
Offline site capture	Local files only	Desktop-bound	Usually	Yes
External users (engineer, client)	Email attachments	Extra seats	Usually	Client and engineer portal
Go-live time	Already installed	Weeks, with installation	Days	Days

Field apps are strong on photos and snags but do not produce a GCC certificate. Desktop suites price well but leave remeasurement and plant to spreadsheets. Civil construction software built for South African contracts carries the whole thread in one cloud record, from measured quantity through plant cost to the payment certificate. Our guide to civil engineering software in South Africa covers the full selection criteria.

Migration Checklist

Use this checklist to keep the migration on track and stop it stalling halfway. Tick each item before you move to the next phase.

Inventory complete: every active workbook listed with owner, purpose and risk.
Reference data cleaned, and only the personal data you need migrated.
Pilot contract chosen and the resident engineer briefed.
Priced BOQ imported, not retyped, and checked line by line.
Parallel run limited to one or two certificate cycles, with a written end date.
Site team trained on offline capture and sync.
First certificate from the software checked against the official GCC or NEC wording.
Roles and approvals set for variations, claims and certificates.
Old workbooks archived as read-only, with a pointer to the live record.
Data export tested, so you know you can get your records out.

What Should You Keep in Excel?

Excel is still the best tool for one-off analysis, so keep it for thinking and take it out of record-keeping. Keep tender what-if models, cash flow scenarios and pivots on exported data. Move anything that someone else will sign, certify, audit or rely on into a shared system with an audit trail.

A healthy split looks like this:

Keep in Excel: tender what-if models, early cash flow scenarios, one-off productivity studies, pivots on exported data and personal notes.
Move to software: the BOQ and remeasurement, certificates, variations and claims, site diaries, plant hours and fuel, labour timesheets, stores and procurement, HSE registers and the EMP (environmental management programme).

A simple rule: if someone other than the author will sign, certify, audit or rely on a record, it belongs in a shared system with an audit trail. Export from the software, analyse in Excel, and never paste the result back as the master.

Frequently Asked Questions

What is civil construction software?

It is software that runs the commercial and site record of a civil contract. That covers the BOQ, remeasurement, payment certificates, variations, plant, labour and site diaries. Unlike a spreadsheet, it keeps one shared record with an audit trail. The QS, the site and the director all work from the same numbers.

Can we migrate in the middle of a live contract?

Yes, but pick a clean cut-off, usually straight after a certificate is paid. Load the opening position, reconcile it to the last certified amount, and run one parallel cycle. Avoid switching a contract that is in the middle of a claim or a dispute.

How long does a move from Excel to civil software take?

For a CIDB CE grade 6 or 7 firm, plan two to four weeks for reference data and one or two certificate cycles for the pilot. Moving the full portfolio then takes three to six months, contract by contract. The data clean-up usually takes longer than the software setup.

Is Excel still acceptable for GCC certificates?

The GCC does not prescribe a tool. The risk is in the evidence. Retention, variations and claims spread over several workbooks are hard to prove under audit. Whatever tool you use, check your certificate logic against the official wording published by SAICE.

The Bottom Line

Leaving Excel means turning personal files into a shared contract record. That record has to survive an audit, a staff change and a dispute. Start with an inventory and clean your reference data. Pilot one contract with a hard end to parallel running, and get the site capturing data at source. Keep Excel for thinking and modelling. Move everything that gets signed, certified or audited into one system. Firms that do this quickly see which contracts make money.

Related guides: