An estimating manager can have a busy team and very little confidence in the next issue. Quantities are being measured, enquiries are going out and the headline number changes each afternoon. Yet nobody can say which assumptions have been agreed or whether two packages carry the same temporary works. Activity is visible; readiness is harder to judge.
The first job is to define the decision the estimate must support. A feasibility comparison needs a different level of detail from a subcontract enquiry. Record the scope boundary, price basis, information cut-off, required outputs and intended review date before assigning packages. If the client changes the decision, revisit the brief rather than quietly asking everyone for more detail.
Give packages a boundary as well as an owner
A package plan should name the estimator, checker and person who can resolve scope questions. It should also describe the interfaces. For a building envelope package, who carries access, secondary steelwork, fire stopping, testing and protection after installation? A list of trade headings is not enough to answer that.
- Agree the estimating brief
- Allocate packages and interfaces
- Build and record the evidence
- Challenge and reconcile
- Issue, hand over and learn
Scope, ownership, evidence, review and handover form a continuous estimating process.
Keep the plan small enough to use during the week. Package, owner, source information, next decision, due date and review status are usually a workable start. A package described as nearly complete may still depend on a supplier clarification that changes its whole basis. Ask what prevents issue and record the answer. That is more useful than debating whether progress is 80 or 90 per cent.
Plan the checking before the deadline
Reserve review time when you allocate the work. The checker needs the quantity basis, source rates, supplier qualifications and significant assumptions, not just a total. If the first review happens an hour before issue, the team can correct arithmetic but may have no practical opportunity to reconsider the work method.
Use two distinct conversations. First, check the package: scope, quantities, units, rate build-ups and exclusions. Then review the assembled estimate: interfaces, preliminaries, escalation, risk allowances and reconciliation to the previous issue. A collection of individually reasonable packages can still be an incomplete project estimate. The lead estimator owns that reconciliation, even when specialists own the individual calculations.
Make meetings resolve something
A short coordination meeting can focus on decisions that affect another person: a revised drawing, an unresolved exclusion or a changed construction sequence. Detailed measurement queries are often better handled by the people involved. Capture the decision, its owner and the affected estimate revision. Otherwise the same question returns at the next meeting with slightly different wording.
When workload becomes difficult, reallocate a defined package or task. Asking everyone to help often creates duplicate effort and unclear ownership. Distinguish preparation from approval. A senior estimator can support a junior colleague with a difficult rate without becoming the only person who understands the package. Ask the colleague to explain the resulting basis at review; this exposes gaps and develops judgement at the same time.
| Question | Evidence to bring |
|---|---|
| Is the scope complete? | Package boundary and interface notes |
| Can the quantity be repeated? | Source reference, revision and measurement basis |
| What changes the rate? | Resource build-up and production assumption |
| What remains unresolved? | Named action owner and issue consequence |
Use this as a conversation guide. The project and estimating purpose determine the depth of review.
Issue a position the team can reproduce
An issued estimate needs a stable snapshot. Keep the agreed model, source register, basis of estimate and outstanding qualifications together under an issue reference. The next revision should explain the movement from that position. If the team cannot recover the previous assumptions, a cost movement becomes a discussion about memory rather than evidence.
Do not judge team performance by how many rows were priced. Look at avoidable rework, repeated scope gaps, unresolved review actions and whether the estimate supported the decision on time. These measures need context. A difficult package with poor source information can consume more effort than a much larger routine package. Discuss the reasons before drawing conclusions about an individual's performance.
Close the loop after award
Arrange a handover with the delivery or commercial team while the estimating basis is still familiar. Identify the production assumptions worth testing and the costs that should be captured separately. A short follow-up after procurement or early delivery can then compare like with like. Feed a supported lesson into the library, template or review checklist with an owner and a date. A lesson that changes no future action remains an observation.
This framework is deliberately adaptable. A two-person team may combine several roles; a larger team may have dedicated information and commercial leads. The requirement is to make ownership and review explicit, including the limits of independence when the same person has to perform more than one role.