Technology and AI

How to move a construction company off spreadsheets

Do not try to replace every spreadsheet at once. Inventory them, move the ones that cost you money first, migrate only active jobs, and lock the old files once each workflow runs in the new system.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

To move a construction company off spreadsheets, list every spreadsheet the business depends on, mark which ones feed money decisions (job cost, change orders, billing, retainage, cash flow), and replace those first with a system where each number is entered once and flows to the next step. Move one workflow at a time, load only active jobs, run the old and new side by side for one billing cycle, then make the old files read-only. Keep the simple personal spreadsheets people like. The goal is to stop retyping and stop guessing which version is current, not to ban Excel.

Spreadsheets are how most contractors start, and for good reason. They are free, flexible, and everyone knows how to use them. The trouble starts around the time the company has more jobs than one person can keep in their head. The change order log, the job cost workbook, the pay app file, and the sub insurance list all hold copies of the same numbers, and they drift.

Signs the spreadsheets are costing you money

  • Two people have different versions of the same job cost file, and nobody is sure which is right.
  • Approved change orders do not show up on the next invoice because the PM's log and the billing file are separate.
  • The owner learns a job lost money after it closes.
  • Month-end takes days because someone copies numbers from five workbooks into the WIP report.
  • A formula broke three months ago and nobody noticed.
  • Nobody can tell who changed a number or when, because there is no audit trail.

How to move off spreadsheets in 7 steps

  1. Inventory every spreadsheet. Ask each person to list the files they open weekly. Note the owner, what it tracks, who else uses it, and where its numbers come from.
  2. Mark the money files. Job cost, budgets, change orders, pay apps, retainage, committed costs, cash flow, and sub compliance. These are the ones worth moving.
  3. Find the retyping. Draw arrows between files where data is copied by hand. Every arrow is a place errors creep in and a place software saves time.
  4. Pick the first workflow. Start with the one that loses the most money. For many contractors that is change orders to billing. See how to track change orders across projects.
  5. Set up the system and load active jobs only. Contract value, approved changes, budget by cost code, billed to date, and retainage. Leave closed jobs in the archive.
  6. Run parallel for one cycle. For one month or one pay app cycle, compare the new system to the old spreadsheet. Fix differences. Then stop updating the spreadsheet.
  7. Lock and move on. Make the old file read-only, note the date, and start the next workflow. Use the implementation checklist for the details.

Which spreadsheets to replace first

Typical order of replacement (adjust to where you lose the most)
SpreadsheetProblem it causesReplace with
Change order logApproved changes never billedChange orders linked to contract value and invoicing
Job cost workbookCosts late or miscoded, margin surprisesBudget vs. committed vs. actual by cost code
Pay app or invoice fileTwo days of copying each monthBilling built from the schedule of values
Sub insurance listExpired certificates missedTracking with expiration alerts
Retainage trackerReleased retainage never invoicedRetainage held and billed per job
Estimating sheetsUsually fine for a whileMove later, once the job side is stable

Estimating is often the last to move. Many estimators have spreadsheets tuned over years, and they work. What matters more is that the estimate's budget lands in the job system in one step. See how to hand off a job from estimating to operations.

Worked example: moving change orders first

Say a general contractor with $9 million in annual revenue runs 14 active jobs. Each PM keeps a change order log in a spreadsheet, and the office manager keeps a separate billing workbook. During the inventory, the office manager finds that on three jobs, approved changes totaling $38,500 are in the PM logs but missing from the billing file. That is money earned and not invoiced.

They move change orders first. In week one they load the 14 jobs with original contract values and all approved and pending changes. In week two PMs start creating every new change order in the system, and the system updates the contract value and schedule of values automatically. For one billing cycle the office manager checks the new numbers against the old workbook. They match except for one change order a PM forgot to approve in the system, which gets fixed. At month end the PM logs become read-only. Next they tackle job cost.

In this example, the inventory alone found $38,500 of unbilled work. That is the kind of number that pays for the move.

Getting the team on board

The hardest part of leaving spreadsheets is not the software. It is the person who built the job cost workbook over eight years and knows every formula in it. Bring that person in early. Ask them to define what the new system has to show, and make them the one who signs off that the numbers match during the parallel run. People resist change that is done to them and support change they helped design.

Field staff need a different pitch. Foremen do not care about the WIP report. They care about fewer phone calls from the office asking for hours and fewer trips to drop off paper. Show them that.

Mistakes to avoid

  • Replacing everything in one weekend. People will quietly keep using the old files. Go one workflow at a time.
  • Rebuilding your spreadsheet inside new software. Take the chance to simplify. If a column has been empty for a year, drop it.
  • Migrating years of history. Closed jobs can stay archived. Keep them accessible for tax and contract records.
  • No cutover date. Without a date when the old file stops being updated, you end up with two sources of truth instead of one.
  • Leaving approvals on email. Electronic signatures and records are generally valid under the federal ESIGN Act, so move approvals into the system where they are tied to the job.

Templates and tools

If you are not ready for software, at least standardize your spreadsheets with a change order log template and a job cost report template so every job looks the same. When you are ready, Smart Business Automator brings change orders, invoicing, job costing and WIP views, retainage, and sub tracking into one place connected to your accounting. See job costing and WIP automation and how to build construction dashboards owners actually use.

Frequently asked questions

Can a construction company run on Excel?

Small companies with a few jobs often do. Problems grow with more jobs and more people, because the same numbers live in several files and drift apart.

Which spreadsheet should a contractor replace first?

The one that loses the most money. For many contractors that is the change order log, because approved changes that never reach the invoice are lost revenue.

Should we move historical jobs out of spreadsheets?

Usually not. Move active jobs, and keep closed jobs archived in a place you can still open for tax, warranty, and contract records.

How long should we run the old spreadsheet and new system in parallel?

One billing cycle or one month per workflow is usually enough to find differences. Longer parallel runs tend to become permanent.

Sources

  1. Cornell LII: 15 U.S.C. 7001, General rule of validity (ESIGN Act)
  2. IRS: How long should I keep records?
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment