A drawing arrives with a later revision. Someone saves it into the estimate folder, another estimator keeps working from the previous issue, and the model now contains two different versions of the same design. The problem is easy to describe after the event. During a tender, it can be surprisingly difficult to spot.
The useful control is not a rule that everyone must always use the newest file. Information can be newly uploaded without being suitable for the estimating task. Start by identifying the authorised source, revision and permitted use. Where a project uses an information management system, retain its status and suitability information rather than replacing it with a private label called final.
Keep a register that answers estimating questions
A source register can be modest. Record the document identifier, title, revision, status, date received, relevant package and the estimate issue that uses it. Add the location of the controlled source. For a specification or model extract, include enough detail to identify the exact information used. A filename on its own may be ambiguous once files have been copied or renamed.
| Record | Illustrative entry |
|---|---|
| Source and revision | Structural layout S-201, revision C |
| Suitability | Use confirmed for this estimate issue |
| Affected package | Foundations and ground beams |
| Estimate baseline | Cost plan issue 03 |
| Review action | Recheck pad volumes; owner assigned |
Illustrative fields, not a prescribed information standard. Use the identifiers and status conventions agreed for the project.
The UK BIM Framework describes a common data environment as a workflow supported by technical solutions. Its guidance distinguishes work in progress, shared, published and archived information. Those states should not be treated as a promise that every item is suitable for every estimating purpose. Read the accompanying status and project requirements. The register described here is a practical estimating control, not a replacement for the project's information protocol.
Make a revision trigger an impact check
When a new issue arrives, identify the affected packages before updating quantities. A revised plant arrangement may change bases, access requirements, electrical connections and maintenance clearances. If only the equipment quantity is revisited, the estimate can appear current while related allowances still describe the previous layout.
Give the impact check an owner. Record whether the revision changes scope, quantity, specification, sequence or price basis. Link each resulting action to the affected estimate rows or package. If the team decides that there is no cost effect, keep a brief reason. That conclusion may be entirely reasonable, but another reviewer should not have to infer it from the absence of a change.
Separate receipt from acceptance
A supplier return is another information issue. Log when it arrived, which enquiry it answers and what it excludes. A revised quotation may have a different validity period, lead time or supply boundary even when the headline price is unchanged. Preserve the earlier return when it explains a movement, and make clear which version is included in the comparison.
For spreadsheet imports, check the unit and the meaning of the quantity before matching a row. Gross area, net installed area and purchased area are different measures. Keep the imported file and a short mapping record so the process can be repeated. Where the source is extracted from a PDF, treat the extracted table as something to verify against the document, particularly at page breaks and repeated headings.
- Receive the controlled source
- Confirm suitability and scope
- Identify affected quantities and rates
- Review the movement
- Record the new estimate issue
The sequence links document control to estimating decisions. Receipt alone does not establish acceptance.
Freeze the issue, then keep working
An information cut-off creates a reproducible estimate position. It does not stop the project from changing. Record late information separately, assess its consequence and agree whether it enters the current issue or the next revision. The decision should be visible in the basis of estimate. Quietly including some late changes while leaving others out makes comparisons unreliable.
At issue, retain the source register alongside the model and review record. A future estimator should be able to identify what was known, what was assumed and what remained unresolved. That is the standard to aim for. An elaborate folder structure is of little value if it cannot answer those questions.