Commercial controls
Construction Variation Log from Site Event to Decision
Keep the site event, notice, estimate, instruction and forecast treatment traceable in a construction change register.
A variation log should explain how a field event became a decision. Keep the event, assessment, any notice and subsequent authorisation linked by one identifier. Otherwise the commercial team can end up pricing one version of the change while the supervisor is acting on another. Agree the contract's notice route, delegation and response requirements with the commercial lead at mobilisation. Software statuses should map to that procedure.
Record the facts while the work is visible
Capture an event date, location, work package, referenced drawings and factual evidence. Record what scope is affected and whether unaffected work can continue. Acknowledge dependencies on design, procurement and sequencing. Track cost and time as separate assessments; each has its own assumptions, exclusions, reviewer and decision. The party responsible for the contractual notice should use the agreed route and deadlines. Keep a copy or reference in the register.
Worked example — a revised layout after procurement
A layout change shifts four fixtures after their positions have been released to a specialist. The supervisor photographs the area, references both drawing revisions and asks the commercial lead to record the event. The estimator separates additional labour and material from omitted work and requests supplier evidence of abortive costs. The planner checks whether replacement work affects a completion milestone. Both assessments stay linked to one event. When an authorised instruction arrives, record its scope and date and update only the approved budget and commitments through the applicable controls.
Keep pending exposure visible
Show pending estimates, approved changes and transfers distinctly so the same value does not appear twice. The November Forma notes describe a cost due-date digest and expanded budget segment classifications. These can support ownership and consistent grouping. Check configuration in the project and maintain the evidence you would need if the export were reviewed outside the software.
Weekly change review
- Match events to instructions, notices and replies where applicable.
- Name the owner of each unresolved cost or time assessment.
- Use an agreed forecast treatment for pending changes and avoid double counting.
- Reconcile the register to procurement, programme and the commercial report.
Video walkthrough
Follow the path from the originating RFI to a potential change record. Identify where you would record the notice reference and the separate decision that authorises work under the contract.
Watch: Cost Management product tour with change-order workflow