Variation Narrative Walkthrough
This walkthrough shows how a change event can be turned into a structured commercial narrative with evidence and entitlement logic.
Illustrative worked example
Six stages, one change event.
Each stage below opens the document it produced on Crestfield Distribution Centre Phase 2, a fictional NEC4 M&E package. The project, the parties and every figure in the pack are invented for the example, and each file carries an ILLUSTRATIVE mark on the page, so nothing here is a real client’s commercial position.
The Radar™Change Capture & Contractual Classification
Fourteen compensation events detected and classified against the NEC4 clause that gives rise to each one — a project-manager instruction changing the Scope, the employer failing to provide something by the date on the accepted programme, and physical conditions an experienced contractor would not have foreseen. The log records the clause, the source, the date of detection, the estimated effect and the status, and it is the feed the later stages read from.
Why it mattersCommercial control starts when the change happens, not at final account.
The Clock™Notice & Acknowledgement Tracking
The four NEC4 notice windows tracked at once for all fourteen events: the eight-week notification window whose expiry time-bars the entitlement outright, the project manager's one-week response, the three-week quotation window and the two-week deemed-acceptance trigger. Each row carries every date and acknowledgement; one near-miss is highlighted in the table, notified late and caught with three days to spare.
Why it mattersA notice window that closes takes the entitlement with it regardless of the merits, so the deadline is tracked as a fact rather than remembered.
The Case™Cause, Effect & Entitlement Narrative
The entitlement chain, shown twice on the same event: a weak version that says only that the work costs more, and the structured version that names the instruction, the clause relied on, the components of the cost effect, the programme consequence and the evidence behind each. The full narrative follows in four sections — cause, effect, entitlement and programme impact — and closes on a six-point gate before the event moves to evidence assembly.
Why it mattersA clear cause helps link the variation to an instruction, delay, access issue or scope change.
The File™Evidence Assembly
Ten evidence items indexed for the same event — the instruction itself, the third-party agreement behind it, the contract extract being departed from, supplier and civil estimates, the accepted and revised programme extracts, the early-warning and notification trail and site photographs of the existing installation — each typed, dated, cross-referenced to the narrative section it supports and given a filed status.
Why it mattersEvidence discipline strengthens the submission and reduces reliance on memory or retrospective reconstruction.
The Count™Valuation Build-Up
The Defined Cost build-up set out under the Schedule of Cost Components — plant and materials, subcontractor, people, equipment and charges — with the original allowance deducted line by line so only the change is claimed, and the contract Fee percentage applied at the end. Every line names the evidence item, timesheet or contract rate it traces to.
Why it mattersA valuation whose every line traces to a document in the evidence bundle can be checked by the assessor rather than argued about.
The Drop™Submission Pack Assembly
This section brings the narrative, evidence and valuation basis together for review. The pack that went to the project manager runs to seven documents — cover letter, entitlement narrative, Defined Cost build-up, assessed programme, evidence index, the attached evidence and the notice audit trail — each attributed to the stage that produced it, alongside the four-week monthly submission cycle and an audit log recording every submission, its recipient, its response deadline and its status.
Why it mattersFinal submissions remain subject to QS, commercial and contract-specific review.
What the six stages produced.
The client-facing deliverables from the same illustrative project: two period registers covering every change event on the job, then the six documents one compensation event travels through — narrative, evidence, entitlement, valuation, monthly submission and the forecast final-account position.
- Change Event LogPDF of the Change Event Log
- Notice TrackerPDF of the Notice Tracker
- Variation NarrativePDF of the Variation Narrative
- Evidence Bundle IndexPDF of the Evidence Bundle Index
- Entitlement StatementPDF of the Entitlement Statement
- Valuation Build-UpPDF of the Valuation Build-Up
- Monthly Commercial SubmissionPDF of the Monthly Commercial Submission
- Final Account PositionPDF of the Final Account Position
This is the type of structured output BuiltAI workflows help produce.
Every document linked here is an illustrative worked example on a fictional project. Final submissions remain subject to contract-specific review, commercial validation and approval before issue.