How to keep a construction variation log before approval
Separate a proposed change from an approved instruction, budget revision and paid cost.
By ENRO team
Keep proposed construction changes in a variation log with their scope, evidence and approval status. A requested change is not automatically permission to proceed or an approved increase to the budget.
Follow one proposed change
Illustrative example: a design revision adds a partition. The site estimates ₹80,000 and two working days. Record the drawing revision, affected location, quantity basis, requested decision date and work that may be blocked. Label the cost as an estimate until the appropriate review is complete.
If the authorized decision approves a different material for ₹65,000, retain the original proposal and record the approved scope separately. Do not silently replace the estimate and erase the discussion.
Suggested log fields
- Change ID, project, location and date raised.
- Origin: revised drawing, client request, site condition or other reason.
- Original scope and proposed scope, including exclusions.
- Estimated cost and time effect, with the person who prepared each.
- Supporting drawing, instruction, quotation and correspondence references.
- Current status, decision owner, required date and decision record.
- Approved amount, implementation record and later actual cost.
Use clear statuses such as proposed, under review, approved, rejected and withdrawn. Add a separate execution status if needed. Approval and completion describe different things.
Avoid two common reporting mistakes
Do not put every proposed variation into the approved budget. Show potential exposure separately so managers can see risk without presenting it as authorized spend. Likewise, do not hide a known change simply because a price is unresolved.
An approval to change scope may not settle price or time entitlement. Follow the actual contract and authorization process, with professional advice for disputed terms. This operational checklist does not decide contractual rights.
At each review, focus on changes with imminent site consequences and assign a next action. A log full of entries marked pending is only useful if someone owns the decision.