Guide · How construction work moves
The Reconstruction Tax,
the cost no one puts on an invoice.
Every time a job moves from one desk to the next, someone rebuilds what the last person already knew. This guide explains why that happens, where it shows up in a building business, and what actually reduces it.
01 / The basics
In plain English
Every job carries two things. There is the data: the estimate, the purchase orders, the invoices, the schedule. And there is the understanding: what was actually quoted, what was assumed, what was promised to the client, why a price was set the way it was, what changed on site and what it means for the money. The data gets stored. The understanding usually does not. It lives in the head of whoever last touched the job.
So every time the job changes hands, the person receiving it rebuilds that understanding from scratch: reading back through emails, opening the estimate, ringing whoever priced it, working out what the last person meant before they can do their own part. We call that rebuild the Reconstruction Tax, and most builders pay it on every job without ever putting it on a cost report.
Why it happens
It is not a discipline problem, and it is rarely a people problem. It is an architecture problem. Estimating, procurement, cost control and accounts each have their own tool or their own tab, and each one stores its slice of the job. What none of them stores is the context that ties the slices together. So the context travels the only way it can, by someone explaining it again, and the job gets re-understood at every handover.
Where the job changes hands
- Estimator to procurement: the estimate is won, and someone now has to work out what it actually allowed for before they can order.
- Procurement to site: the purchase order lands on site, and something on it does not match the ground, so the phone comes out.
- Site to accounts: an invoice arrives with no PO number, and accounts loses time chasing whoever remembers the conversation.
- Accounts to management: the financial position gets reconstructed after the fact, from invoices that arrived out of context.
- Anyone to nobody: a person leaves, and the understanding of their live jobs walks out with them.
02 / The reality
Where builders get stuck
The handover that opens with a question
The tell is simple. When the receiving person’s first job is to work out what the last person meant, you are watching the tax being paid.
The unmatched invoice
A bill turns up with no order to match it to. It sits unpaid while someone reconstructs which job it belongs to and whether the price is right.
“What did we actually allow for here?”
The question every supervisor dreads, asked at the moment it is hardest to answer, because the allowance is in an estimate nobody has open.
Costs that arrive late
When the financial picture is reassembled monthly instead of carried forward, you find out a job is tight after the money is spent, not while you can still act.
Knowledge that leaves with the person
The most valuable thing a builder owns is the understanding of its live jobs. When it lives in heads, it is one resignation away from gone.
The same thing, entered twice
Data keyed into a job system and again into accounting is the visible symptom. Re-explaining the job underneath it is the part no one counts.
03 / The fix
A workflow that holds up
- 01
Map where the job changes hands
List the real handovers on a job: estimate to order, order to site, site to invoice, invoice to report. That is where the tax is charged.
- 02
Find the handovers that start with “what did they mean?”
Those are the expensive ones. The goal is to remove the question, not to answer it faster.
- 03
Make the estimate the source of truth
When later stages read the estimate instead of reinterpreting it, procurement and site stop guessing what was allowed for.
- 04
Tie commitments to invoices
Raise purchase orders so accounts has something to match against, and the unmatched invoice stops being a research project.
- 05
Keep costs current, not monthly
A cost picture that updates as commitments and invoices land does not need to be rebuilt at month end.
- 06
Put the understanding in the system, not the person
Anything the business only knows because one person remembers it is an unfunded liability. Get it out of heads and into the job.
04 / The tooling
How software helps
Here is the uncomfortable part: most construction software makes the Reconstruction Tax worse, not better. A tool that only stores its own slice of the job, estimating here, scheduling there, accounts somewhere else, adds another handover and another place the context has to be re-explained. More software, more rebuilding.
The distinction that matters is between a system of record and a system of understanding. A system of record stores what happened. It is a better filing cabinet, and storage was never the problem. A system of understanding carries the job’s context forward: it reads the invoice in the context of the order and the estimate, connects a commitment to the bill that settles it, and keeps cost tracking live so the picture is never reassembled. When the software holds the understanding, the next person does not have to.
05 / In practice
Where VIABUILD fits
VIABUILD is built to stop the tax being paid.
VIABUILD is a system of understanding, not another system of record. It holds a live understanding of every job, what was quoted, ordered, promised and spent, and hands it to whoever picks the job up next. Oryn™ reads your plans and invoices and connects every order to every cost, so the estimate flows into procurement, procurement into accounts, and the numbers stay current instead of being rebuilt.
The practical effect is that no one re-understands the job at the next desk, the unmatched invoice stops being a research project, and the knowledge stays in the business when a person leaves.
- A system of understanding, not a system of record
- Oryn reads and connects plans, invoices and orders
- The estimate flows into orders and invoices, entered once
- Costs stay live, not reassembled monthly
- The understanding stays when a person leaves
06 / FAQ
Common questions.
It is the name VIABUILD gives to the recurring cost of rebuilding the understanding of a job every time it moves between people or departments. The data (estimates, orders, invoices) is stored, but the understanding of the job usually is not, so it gets reassembled at each handover. It rarely appears as a line on a report, which is part of why it goes unmanaged.
Double entry is one symptom, but the tax is broader. Re-typing the same number into two systems is visible and annoying. Re-explaining what a job actually allowed for, why a price was set, or what changed on site is the larger, quieter cost, and no keyboard shortcut fixes it.
Most construction software is a system of record: it is very good at storing what happened, which was never the hard part. Storing data is not the same as preserving understanding. If each tool holds only its own slice of the job, the context that ties the slices together still has to travel by someone explaining it.
Listen for the handover that opens with a question, watch for invoices that sit unmatched while someone works out where they belong, and count how often the answer to “what did we allow for here?” takes a phone call. Those are the tax being charged.
Generally yes. More jobs and more people mean more handovers, and every handover is a point where the understanding can be rebuilt or lost. The cost tends to scale with headcount and job count, which is why it often bites hardest just as a builder is trying to grow.
07 / Keep reading
Related guides & features
See it on your own jobs.
Start with 7 days free: the full platform, your real data. $199 for your first month, then $435/mo. Month-to-month, no lock-in.