BOQ Revisions and Approvals: Handling Scope Changes Without Version Chaos
No construction project finishes with the BOQ it started with. Designs change, the client adds or drops items, and site conditions force substitutions. The question is not whether the BOQ will be revised, but whether anyone can tell which version is the approved one.
Why BOQ Revisions Cause Trouble
- Several copies of the file circulate, and the purchase team works from an old one.
- A change is agreed on a call but never written into the BOQ.
- The BOM is not updated, so materials are bought for the old scope.
- Nobody can say later who approved a change, or when.
A Simple Revision Process
- Raise the change. Record what is changing and why: the item, the old and new quantity or rate, and the reason.
- Review the impact. Check the effect on cost, schedule and materials before approval.
- Approve. The person with authority approves in writing. Until then, the previous version stays in force.
- Issue the new version. Number it (Rev 1, Rev 2) and make it the only version in use.
- Cascade. Update the BOM, budget and purchase plans that depend on the changed items.
One approved version, a visible history of every change, and nothing downstream left on the old numbers.
What to Record for Each Revision
| Field | Why it matters |
|---|---|
| Revision number and date | Shows which version is current |
| Items changed | Lets reviewers see exactly what moved |
| Reason for change | Supports client discussions and later disputes |
| Approved by | Gives a clear audit trail |
| Cost impact | Keeps the budget honest |
Keeping Downstream Documents in Step
A revised BOQ line changes the materials needed, and so the purchase requirement. The cleaner approach is a system where the BOM follows the BOQ automatically, as covered in our BOQ vs BOM guide, rather than relying on someone to remember.
Doing This in Software
VISWOX ERP includes BOQ approvals and revision history, so changes are logged, approvals are recorded, and earlier versions remain available for reference.
Summary
- Expect the BOQ to change, and plan for it.
- Use a raise, review, approve, issue, cascade process.
- Keep one approved version and a full history.
Control BOQ Revisions in One Place
VISWOX ERP supports BOQ approvals and revision history, so every change is recorded and the approved version is clear to everyone.