Control BOQ revisions before comparing estimates

Record the tender or project, issuing party, document number, revision, issue date, received date and any associated addendum. Keep the original files and identify the version used for each estimate. A filename ending final does not establish that it is the controlling issue.

Link the BOQ to relevant drawings, specifications and clarifications. A line description can remain unchanged while a referenced specification changes. The comparison therefore needs a route for technical review, not only a spreadsheet difference report.

Assign an owner to confirm the tender basis before pricing continues. The existing tender checklist guide explains how addenda affect completeness. Here, the key is to preserve which evidence each estimate actually used, including unresolved clarifications.

In this fictional example, Revision A contains 120 metres of pipe at an illustrative rate of ₹1,000 per metre. Its line value is ₹120,000. Revision B retains that pipe line and adds eight fittings at ₹2,000 each. The revised subtotal for these lines is ₹136,000, before any other charges or taxes.

The ₹16,000 increase is new separately priced scope. The pipe quantity and rate have not changed. Dividing ₹136,000 by 120 metres would produce about ₹1,133.33 per metre, but that blended figure would conceal the fittings and should not be described as a pipe-rate increase.

The estimator should confirm whether the original pipe rate already included fittings under the tender description. If it did, the new lines may introduce a clarification or potential overlap rather than automatically justify an extra ₹16,000. The arithmetic is simple; the scope interpretation still needs review.

Use stable item codes where the issuer provides them, together with description, unit and specification references. Row position is a weak key: inserting one line can make every later row appear changed. Retain the original line numbers for traceability while using a reviewed cross-reference for comparison.

Classify each relationship as unchanged, modified, new, removed, split, merged or unresolved. A line split into two may need a one-to-many mapping. Do not select the most similar description automatically and call it the same item when the unit or technical requirement differs.

For unmatched rows, show the full value and the reason for uncertainty. Excluding them from the comparison total produces a neat but incomplete reconciliation. The estimator and technical owner should resolve the relationship or retain it explicitly as an open pricing issue.

For comparable lines, show old and new quantity, unit and rate. Separate quantity effects from rate effects using a stated calculation basis. When both change, define the order of calculation or show the combined difference without pretending that a unique decomposition exists independently of the chosen method.

Keep new and removed scope outside that comparable-line bridge. Show allowances, discounts and other adjustments separately with their basis. If currency or tax treatment differs, finance and commercial owners need to establish a consistent comparison before totals are presented as like-for-like.

Reconcile from the original total to the revised total using all classified differences and unresolved values. The bridge should explain the entire change, not only the lines that matched successfully. Save the calculation version alongside the comparison report.

A BOQ revision may affect vendor enquiries, long-lead requirements, subcontract packages and labour assumptions. Assign the relevant follow-through after the scope is understood. A revised total in the estimating file does not automatically update an issued purchase enquiry.

For each material change, identify the affected quotation or assumption and whether it remains valid. A supplier may have quoted the earlier specification or excluded a newly separated item. Keep the old quote as evidence, but mark the gap before using it in the revised estimate.

ERPNext's Supplier Quotation documentation illustrates structured quotation records and comparison. It does not determine whether two tender lines are commercially equivalent. Use a reviewed scope mapping before feeding revised quantities into any procurement comparison.

A controlled spreadsheet can be effective for a modest BOQ if versions, mappings and formulas are protected and reviewed. A document comparison tool helps identify candidate differences. An estimating platform may provide stronger version history and package links. None removes the need to decide whether the underlying scope is comparable.

Test the method with an inserted row, a changed unit, a specification-only change and a split item. Ask it to preserve unresolved matches rather than forcing a result. The output should let a reviewer navigate from the summary difference to both source lines and the mapping decision.

Measure completeness of the value bridge and the time needed to resolve ambiguities. A fast report with many incorrect matches can create more work than a slower, transparent comparison. Keep the review responsibility with estimating and the relevant technical owners.

The approved comparison should state which revision the estimate now uses, what changed, what remains unresolved and which dependent enquiries or budgets need updating. Preserve the previous estimate so the team can explain the commercial decision later.

The practical result is a change explanation that distinguishes added fittings from a changed pipe rate and carries that distinction into the bid. That is more useful than a single percentage increase.

1. Freeze the two BOQ versions and their linked tender evidence.
2. Review item identities, units and scope before accepting automated matches.
3. Reconcile every value difference, including unmatched and split lines.
4. Update affected quotations and assumptions before issuing the revised estimate.