Problem guide
Spreadsheets became the system of record
A spreadsheet becomes the system of record when it holds something the official systems leave out: the WIP schedule, the orders waiting on stock, the referrals waiting on approval, the units turned this week. Every connector documents gaps. Procore's link to Spectrum does not sync timecards or owner invoices, and Jobber's QuickBooks sync runs one way. Name what each sheet holds that nothing else does, stop retyping its inputs, and give that information a proper home.

How it actually happens
Nobody decides to run part of the business on a spreadsheet. It happens one gap at a time.
The operating system holds jobs, orders, appointments or leases. The accounting system holds cost, billings and payroll. A project or practice system holds its own slice. Each connector between them carries some things and documents what it leaves out. Procore and Spectrum do not pass timecards, subcontractor invoices or owner invoices between them. Jobber sends to QuickBooks Online and nothing comes back, not even paid status. simPRO sends Xero the hours but not the labor cost. ServiceTitan sends a purchase order to QuickBooks Online as one line called Service Titan PO Item.
So someone needs a number that lives across two of those systems, and builds it. A contractor's controller pulls job cost and billings from the books, asks each project manager for percent complete, and calculates over and under billings in Excel. An operations lead keeps a sheet of every open job, order or case and what it is waiting on, because no system has a column for "waiting on the customer's approval." A roofing foreman's squares installed go into a sheet because the connector between Procore and Sage 300 CRE does not sync production quantities. A property manager's make-ready list and a clinic's referral tracker start the same way.
The sheet works. People trust it more than the systems, because it holds the one number they need in the shape they need it. More people open it. Copies appear. A steel estimator on r/estimators said the easy option for tracking cost against estimate was to build an Excel sheet, which is how most of these start.
Then the costs arrive quietly. Every typed column is a chance to mistype. Panko's compilation of spreadsheet audits found important errors in most of the operational spreadsheets examined. The sheet runs a step behind its sources: Procore does not see a Sage cost until it is posted in Job Cost, and the sheet is only as current as the last paste. The keeper's rules live in colors and comments only she understands. The template breaks when rows are added, as one r/ConstructionManagers poster found every month end.
The sheet also picks up obligations nobody planned for. If it is where percent complete is worked out for a long-term contract taxed on percentage of completion, it feeds the cost-to-cost ratio in 26 CFR 1.460-4. If it splits prevailing-wage hours by contract, it is part of the Davis-Bacon payroll record. If it is the only place a deduction or a payroll figure was worked out, the IRS retention rules reach it too.
What to keep from the sheet
The sheet is the best requirements document the business has. Its columns show what people actually need to see, and its calculated cells show the rules they use. A replacement that drops those columns is the reason the sheet comes back. Read it carefully before anyone retires it.
Signs you have this problem
- The owner decides from a spreadsheet, not from the systems the company pays for
- One person keeps the sheet and nobody else fully understands it
- Several copies exist and people argue about which is current
- Someone types numbers into the sheet from other systems every day or week
- The month-end template breaks when rows are added
What usually causes it
- Values are copied by hand from the operating and accounting systems into the sheetThe re-entry trap
- The sheet tracks work no system shows, such as jobs, orders or cases waiting on parts, approvals or peopleThe invisible queue
- The sheet holds the special cases, overrides and notes the official systems have no field forThe exception swamp
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Is there a number the owner decides on that exists only in a spreadsheet?If yes: the sheet is already a system of record. List it first.
- Does someone type or paste values into the sheet from another system every day or week?If yes: the sheet is a re-entry point. Check twenty rows against the source.
- Does the sheet hold something no system has a field for, such as what a job or order is waiting on?If yes: the sheet is filling a real gap. Write that gap down before anyone replaces the sheet.
- Do two people keep their own versions of the same sheet?If yes: the business has two truths. Pick one file and retire the copies.
- Would the sheet stop being updated if its keeper left tomorrow?If yes: the risk is one person. Get the one-page explanation written this week.
How it breaks in each industry
- Construction contractors running a WIP schedule
- Accounting holds cost and billings; the project manager holds percent complete; the WIP schedule that compares them lives in Excel. A poster on r/ConstructionManagers described pulling QuickBooks Online data into Excel every month end to calculate percent complete and over and under billings by job, on an accountant's template that breaks when the job count changes.
- HVAC, plumbing and electrical service
- The field system holds jobs and invoices. The sheet holds what the field system has no column for: jobs waiting on a part, a quote approval, a warranty claim or a return trip. The dispatcher, the parts lead and the owner each keep a version.
- Property management
- The property management system holds leases and rent. The make-ready tracker that shows which units are vacant, what each is waiting on and when it will be rent-ready lives in a sheet the maintenance lead updates from texts, and leasing reads it to decide what to show.
- Healthcare practices and clinics
- The practice system books visits and bills claims. Referrals and prior authorizations waiting on a payer or another office are tracked in a shared sheet, and a patient waits whenever the person who keeps it is out.
Where it breaks between systems
- Procore and Trimble Spectrum
- Timecards and timesheets, commitment invoices and payments, and prime contract invoices and payments do not sync. The integration takes one Spectrum cost code list, and projects already in progress when it is connected cannot be synced without paid Professional Services.[1]
- Procore and Sage 300 CRE
- Costs reach Procore only after they are posted in Sage's Job Cost module; costs posted only in Accounts Payable or Payroll do not sync until then. The project manager's cost view runs behind the controller's.[2]
- ServiceTitan and QuickBooks Online purchasing
- Purchase order materials export to QuickBooks Online as a single 'Service Titan PO Item' instead of the specific materials, classes are not tied to the PO's business unit, and inventory works from a single site. Anyone who needs cost by material or by truck rebuilds it elsewhere.[4]
- ServiceTitan job costing and payroll
- Job costing uses a labor burden rate typed into each technician's payroll profile, which ServiceTitan calls a managerial estimate, while payroll is the actual check, and the two will almost never match to the penny. Payroll leaves as a CSV or Excel export to the payroll provider.[5]
- Jobber and QuickBooks
- The sync runs one way, Jobber to QuickBooks Online, and paid status on invoices no longer syncs back. Jobber does not sync to QuickBooks Desktop at all; a Desktop client list comes across once by CSV.[6]
- Housecall Pro and QuickBooks Online
- Estimates do not push to QuickBooks, labor and materials are not separated when the price book syncs, edits to existing price book items do not carry across, and invoices deleted or canceled in Housecall Pro must be removed in QuickBooks by hand.[7]
- simPRO and Xero
- Labor cost is not posted to Xero, only hours against each pay rate. A payment larger than the invoice does not export, because Xero cannot process overpayments.[8]
- ServiceM8 and Xero
- Invoices created in Xero are not sent to ServiceM8, zero-dollar invoices are not sent to Xero, and suppliers are not imported. Items deleted or set inactive in Xero stay in ServiceM8.[9]
By the numbers
| Figure | What it measures |
|---|---|
| 91%[10] | Spreadsheets with important errors across the five core field audits in Raymond Panko's compilation (55 operational spreadsheets, studies from 1992 to 2008, not construction-specific). |
| 84%[10] | Spreadsheets with errors across nine audit studies covering 163 spreadsheets, same compilation. In one of them, Coopers and Lybrand in 1997 found 91% of 23 large accounting spreadsheets wrong by at least 5%. |
| About 1%[11] | Error rate for single data entry in Barchard and Pace's 2011 lab study of 195 undergraduates; checking entries by eye was no more accurate than not checking. Lab data entry, used here as an analogy for retyped columns. |
| 1,300 hours[12] | A year spent assembling usable reports by 88% of construction and engineering executives who use four or more data systems, 400% more than single-system users (TrackVia survey of 500 executives and managers, 2018, vendor survey). |
| 61%[12] | Executives in the same 2018 TrackVia survey who said they make decisions with outdated data; half of managers said their data passes through five steps to reach a system, and 65% said change orders get missed some to all of the time because of manual collection. |
Rules that apply
- 26 CFR 1.460-4(b)(1), percentage of completion[15]
- For long-term contracts taxed on percentage of completion, completion is measured by comparing allocable contract costs incurred with estimated total allocable contract costs. A WIP sheet built from stale job cost or a guessed estimate-to-complete feeds that ratio. A long-term contract is one not completed within the contracting year (26 CFR 1.460-1(b)(1)).
- 26 U.S.C. 460(e)(1), exemptions[16]
- Home construction contracts, and other construction contracts expected to finish within two years by a taxpayer who meets the gross receipts test of section 448(c), are exempt from the percentage of completion requirement. Know which of your contracts the sheet is actually computing for.
- 29 CFR 5.5(a)(3)(i)(B), Davis-Bacon payroll records[17]
- On covered federal and federally assisted work, payroll records must show each worker's classification, rates, deductions, wages paid, and daily and weekly hours worked in total and on each covered contract. If those hours are split out in a spreadsheet, that sheet is part of the record. Certified payroll does not apply to contracts of $2,000 or less (29 CFR 3.3(c)).
- IRS record retention[18]
- The IRS says to keep records for 3 years in the ordinary case, and employment tax records for at least 4 years. A spreadsheet that is the only place a deduction or a payroll figure was worked out has to be kept like any other record.
Measure it in your own shop
From: The spreadsheets themselves, their version history in your shared drive, and the source systems each copied column comes from (operating system, accounting, payroll, project system).
- List every spreadsheet opened by more than one person in a typical week, with its keeper and what is decided from it.
- For the top three, count the columns that are typed or pasted from another system.
- In the most important one, compare twenty rows of copied values to the source system and count the mismatches.
- Ask the keeper to log the minutes spent updating it each working day for one pay period.
Reading it: The mismatch rate is how far the sheet has drifted from the systems. The minutes per pay period is the labor it costs. The list of columns no system holds is what any replacement has to provide, or the sheet comes back.
What does not fix it
- Banning spreadsheets
- The sheet exists because a system has no place for something people need. A ban removes the coping tool and leaves the gap, so the sheet reappears on someone's desktop.
- Moving the sheet to a shared drive
- It ends the argument about which copy is current. It does not stop anyone retyping the inputs, so the errors and the hours stay.
- A better template
- The r/ConstructionManagers poster's template was built by an accountant and still broke when the job count changed. A template formats the copying; it does not remove it.
- Buying the connector and assuming the gap is closed
- Each connector publishes what it leaves out. Procore's own Spectrum page lists timecards and both kinds of invoices as not syncing. Read the list before retiring the sheet.
What to try this week
- List the sheets people would panic withoutAsk the controller, the operations lead, the scheduler and each manager which spreadsheets they open every week. Write down the keeper, what it tracks, who reads it and what gets decided from it.
- Mark every typed columnFor the sheets that drive money or schedule, mark each column as typed, pasted, or calculated. Typed and pasted columns are where the errors and the hours are.
- Write down what no system holdsSome columns exist because no system has a field for them: percent complete by a manager's judgment, what a job or order is waiting on, units completed. List them. That list is the actual requirement for a replacement.
- Check twenty rows against the sourcePick twenty rows of the most important sheet and compare each copied value to the system it came from. The mismatch rate tells you how much to trust the next decision made from it.
- Get the logic out of one headHave the keeper write one page on how the sheet works: what each column means, where it comes from, what the colors mean, what gets updated when. It protects you the week that person is out.
Put a number on it
- The cost of retyping calculator: Calculate the office hours and dollars your company spends each year retyping job information from the field into other systems.
Where do-it-yourself stops
These steps make the sheet safer and show what it costs to keep. They do not remove the copying that feeds it, and the requirement it fills is still met by one person's file. The lasting fix is a tool built around your own systems that gives what the sheet holds a real home and fills it from the systems without retyping. That is what a Workflow Spec designs.
Questions people ask
How often do business spreadsheets contain errors?
Raymond Panko's compilation of field audits found important errors in 91% of 55 operational spreadsheets, and errors in 84% of 163 across nine studies. The studies run from 1992 to 2008 and cover businesses in general, and no audit has found error-free spreadsheets to be the norm.
Is having someone double-check the sheet enough?
Visual checking alone is weak. In Barchard and Pace's 2011 lab study, checking entries by eye caught no more errors than not checking at all. Comparing copied values to the source system, row by row, is a better test.
Does a contractor's WIP spreadsheet affect taxes?
It can. For long-term contracts on percentage of completion, 26 CFR 1.460-4(b)(1) measures completion as costs incurred against estimated total costs. Home construction contracts and short contracts of businesses under the gross receipts test are exempt under 26 U.S.C. 460(e).
Why can't our project and accounting systems replace the sheet?
Sometimes they can, but read the connector's limits first. Procore's Spectrum page says timecards and owner and subcontractor invoices do not sync, and its Sage 300 CRE page says costs reach Procore only after posting in Job Cost. Every connector publishes a list like that.
Which spreadsheet should we replace first?
The one where money or schedule decisions are made, the most columns are retyped, and only one person can keep it current. Check twenty rows before deciding; a high mismatch rate settles the order.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
