The estimate to budget handover,
where the price becomes the baseline.

On a residential job the estimate and the budget are largely the same numbers doing two different jobs. The estimate is the internal forecast that won the work, built through the process covered in the estimating reference. The budget is that priced scope locked in as the baseline the rest of the job measures against. Procurement lets packages and raises orders against it, cost tracking compares actuals to it, and progress claims draw their structure from it. The handover is the moment one becomes the other.

Defined precisely, the estimate to budget handover is the conversion of the winning estimate into the job cost baseline, together with the transfer of everything the numbers alone do not say. That second half is where handovers fail. The figures almost always make it across in some form; the assumptions, the exclusions, the intent behind allowances and the reasoning behind rates very often do not. This node sits on the boundary between the estimating and procurement clusters because the budget it produces is the document the entire commitment workflow runs on.

Why it matters

A job can only be controlled against a baseline, and the handover decides what quality of baseline the job gets. A budget converted line by line lets the PM see which package is drifting while there is still time to act. A budget re-keyed as trade totals can report that the job is over without ever being able to say where, why, or what to do about it. The handover also decides who carries the estimator's knowledge for the next eight months, the system or the estimator's phone.

In the estimate, win, build, claim, know lifecycle, this seam is the border crossing between winning the work and delivering it. Upstream sits everything estimating produced; downstream sit the disciplines that consume the baseline, letting trade packages, raising purchase orders, tracking cost against estimate and claiming progress. What binds the two sides together is structure. When estimate items, budget lines and invoice coding share one set of cost codes, comparison across the job is mechanical; when they do not, every report passes through a translation step that costs time and invites error.

The handover is also where cost control either starts on time or starts late. From the first purchase order, the job's real position is budget against committed costs, not budget against invoices received, and commitments can only be measured against a baseline that exists at line level. The wider discipline this feeds is covered in the builder cost tracking guide; this node is about the seam that determines whether that discipline has anything solid to stand on.

Experienced operators tend to hold a view that surprises newer builders. Most of the margin lost on jobs is not lost inside the estimate, it is lost at the two seams on either side of it, the handover from designer to estimator and the handover from estimate to budget. Inside the estimate, errors are arithmetic, visible and bounded; a wrong rate misprices one line. At the seams the loss is structural, because what disappears is the understanding that lets everyone downstream make good decisions, and that shows up as scope gaps, badly bought packages, allowances defended from memory and variations argued without evidence. The estimate gets the attention because it produces a number; the seams get none because they produce nothing visible at all.

The test experienced builders apply to a handover is deliberately concrete. Three months into the build, can the site supervisor find out why a number is what it is without ringing the estimator? If the answer lives in the budget line, its build-up and its attached qualifications, the handover worked. If the answer is a phone call, the business is paying the Reconstruction Tax on that job, and it will pay it again on the next one, and the day the estimator resigns the price of every live job becomes partly unexplainable.

The handover meeting

On larger jobs, where the estimator and the PM are different people, the common professional practice is a structured handover meeting. The estimator walks the PM through the job package by package, covering what was priced tight and why, where the contingency sits and against which risks, which numbers rest on real quotes and which on allowances, what was excluded, and what the client was told along the way. The meeting matters, and the written record of it matters more, because the PM's memory of the meeting decays at roughly the same rate as the estimator's memory of the job. On smaller jobs the same content still needs capturing, even when both roles are the same person, because the seam being crossed is time rather than people.

Where software fits the workflow

Traditionally the estimate lives in one tool and the budget in another, and the seam between them is a re-keying session. In VIABUILD the handover is a change of state rather than a transfer. On a win the estimate becomes the budget line by line, keeping quantities, rates, cost codes and allowance status, and cost tracking measures commitments and actuals against those same lines from the first order. Oryn™ reads incoming invoices in the context of the order and the budget line behind them, so the estimate-to-invoice trail stays connected as a by-product of paying the bills. The PM still owns every number; the system's job is to stop the understanding being rebuilt.

The handover itself is internal practice, not a regulated act, but several Australian realities decide what it must preserve. The points below are labelled by evidence class; requirements differ by state and change over time, so confirm the current source before relying on any of them.

• Legislation. Each state and territory's domestic building contract legislation regulates how prime cost items and provisional sums are disclosed and adjusted in residential contracts. Those adjustments are made against what the contract disclosed, so the budget must preserve each allowance's identity and intent, not just its amount. An allowance flattened into an ordinary budget line leaves the builder adjusting from memory, which is a weak position in any dispute. Confirm the rules for your jurisdiction with your state regulator.
• Common practice. Many Australian builders estimate in one tool and account in another (commonly a spreadsheet or estimating package feeding a small-business accounting system), which makes the handover a re-keying exercise by default. The two systems also usually differ in structure, job cost lines on one side, a chart of accounts on the other, so alignment has to be designed rather than assumed.
• Common practice. Estimates are typically built at cost excluding GST, while client-facing contract sums include it. The conversion needs to keep the budget, quotes, orders and invoices comparable like for like; a budget that silently mixes GST-inclusive and exclusive figures manufactures phantom overruns. Confirm the treatment for your structure with your accountant.
• Professional recommendation. On larger jobs, a formal handover meeting from estimator to PM with a written record is widely recommended practice in Australian building companies, and the record is the part that survives staff turnover.

Illustrative only, not a benchmark. An estimate carries a $15,000 provisional sum for site works, priced on the assumption of no rock, with rock breaking expressly excluded in the tender letter. The job is won, and the budget is keyed into the accounting package as a single line, site works, $15,000. Three months later the excavator hits rock. The supervisor needs to know whether rock was allowed for, and the budget line cannot say. The tender letter is in an email thread, the estimator is pricing another job, and the conversation with the client starts a week late from a defensive position.

Now run the same event through a converted budget. The line is flagged as a provisional sum, carries its scope note (site works to natural ground, rock excluded), and points at the tender letter clause. The supervisor reads it on site, the variation is raised the same day with the exclusion as evidence, and the client conversation is about the price of rock, not about whether the builder should wear it. The difference between the two outcomes was decided months earlier, in how one line crossed the seam.

Baseline (the locked reference the job is measured against), conversion (an estimate line changing state into a budget line, keeping its detail), re-keying (typing numbers from one system into another), allowance intent (what a PC or PS item was assumed to cover and exclude), line-level traceability (the unbroken chain from estimate item to budget line to purchase order to invoice), committed cost (money promised by orders and subcontracts before invoices arrive), handover meeting (the estimator's structured walkthrough of the job for the PM). Definitions for the wider vocabulary live in the construction glossary. From here, the natural next article crosses into the procurement cluster, purchase orders, the instrument that turns budget lines into commitments.

• Your state or territory's building regulator and fair trading body, for the domestic building contract rules governing prime cost and provisional sum disclosure and adjustment in your jurisdiction.
• Australian Institute of Quantity Surveyors , professional guidance on cost planning and cost management practice, including the relationship between estimates and cost control budgets.
• Your own signed contract and tender documents on each job, the primary record of what the budget's allowances, assumptions and exclusions actually promised.