Skip to content

Project management

Feedback to estimating from the finished job: what the estimate got right and wrong

By Review.LivePublished 3 min readHow we write

The job finished over its labour allowance. Estimating hears that the site was difficult, while the superintendent says the estimate was unrealistic. The next tender is approaching, but neither explanation identifies what assumption should change.

Three people's hands over printed house plans with a scale ruler, pencil and calculator on a shared table.
Photo: Pedro Miranda on Unsplash

Hold a focused finished-job review with estimating and the delivery team using checked quantities, hours, costs and scope. Plan a one-hour session around prepared information, with follow-up for unresolved checks. Compare the three largest meaningful differences with the assumptions made at tender, then record what future estimates should treat differently. Aim to meet within a month of completion while the conditions remain familiar. The purpose is a better estimating basis, not a contest over which department owns the result.

Translate the result into a future assumption

  1. Prepare a comparable scope. Bring the estimate basis, final scope and checked job-cost information. Separate approved additions and omissions so the team is not comparing an original allowance with a different finished package.
  2. Check quantities and hours before rates. Confirm the installed quantities, labour-record coverage and cost-code boundaries. A unit comparison is useful only when its numerator and denominator describe the same work.
  3. Choose the three differences worth investigating. Look for the largest supported departures in labour, material, subcontract prices or general conditions. State the evidence and uncertainty rather than selecting only the differences that favour one department.
  4. Trace the assumptions behind each difference. Ask what access, sequence, crew, scope or duration the estimate assumed and what actually happened. Distinguish an estimating omission from a changed requirement, a delivery decision or a coding error.
  5. Write the next estimating instruction. Record the condition that should trigger a different allowance, a clarified exclusion or an additional enquiry. Attach the supporting job reference so the lesson can be tested on the next comparable tender.
  6. Assign the update and return check. Name who changes the estimating notes or reference data and when. Ask the next tender reviewer to confirm the relevant lesson was considered rather than assuming a meeting automatically updated the system.

Common mistakes

  • Comparing original scope with final costs without separating changes.
  • Changing a reference rate before checking quantities and cost coding.
  • Ending with “communicate better” instead of a concrete estimating instruction.

Checklist

What estimating should receive

  • A reconciled scope and checked job reference.
  • Three supported differences and their causes.
  • Conditions that make the comparison relevant.
  • Specific estimating assumptions or enquiries to update.
  • An owner and a check on the next comparable tender.

Check your understanding

The finished job’s unit cost is higher, but its quantity basis includes work outside the estimate package. Should the estimating rate change now?

Show the answer
Reconcile the package boundaries and quantities first. The apparent difference may describe unlike scopes. Use a checked, comparable basis to decide what to update, and record any remaining uncertainty rather than converting an unexplained number into the next estimate’s default.