Knowledge / AEC-native data
Change orders, variations and compensation events
Instructed or notified changes to scope, time or cost, and the notices, quotations and assessments that follow under the contract.
A variation is never one document. Under NEC4 a compensation event runs, sometimes from an early warning, through notification, a quotation with its programme and cost build-up, the Project Manager's assessment and implementation, with periods set in clauses 61 to 66 as amended by the Z clauses. Under JCT the Contract Administrator, or the Employer's Agent under design and build, instructs the variation and it is valued under the valuation rules. Either way the record is a chain spread across letters, email, the programme and the drawing register. Construction variation AI is useful when it holds that chain together, so a team can ask what an event changed, what was quoted and what has been agreed, with every answer traceable to its document.
What teams need to ask of it
Which events have been notified but not yet quoted, and which quotations are past the period in the contract as amended?
What was the actual scope of this event, and which drawings and specification clauses did it change?
Which events touch the same area of the works, and do their quotations overlap?
Was an early warning given before this event was notified, and when?
What is the accumulated time effect of the implemented events on the completion date?
Has the Project Manager's assessment been implemented, and does it differ from the quotation?
Which instructions have been issued that nobody has yet notified as an event?
Why generic AI gets it wrong
The chain is the meaning. A quotation is a proposal, an assessment is a decision, and an implementation is the point at which the prices and the completion date actually move. Read in isolation the three documents make similar statements about the same event, and a general-purpose tool has no way to tell which one is now the contractual position. Flatten the correspondence and the tool will find the contractor's quoted figure, report it as the value of the event, and be wrong, because the Project Manager assessed it lower a month later and the assessment is in a different folder. It cannot see that the quotation references programme revision 7 and the assessment revision 9, or which activities moved between them.
The periods and conditions are also not what the tool assumes. It may know a standard form, but the contract on this project has Z clauses that change the notification period, the quotation period and what counts as a compensation event, and the amendments live in the contract data and the schedule of amendments. A tool that quotes the standard form gives a commercial manager a deadline that is wrong on this project. Because the answer names a clause and a period, it looks authoritative, and a notification goes in late. In a process where time bars exist, a well-written wrong answer is worse than none.
One question, answered
QUESTION
ANSWER
SOURCES
We onboard a focused slice of your project data, configure the ingestion paths, extract a structured context graph, and build a workflow against the resulting structured knowledge layer.
Related to
Every change reads against the contract that governs it and the programme that shows its time effect, which is why construction contracts and construction programmes are the two documents an event cannot be assessed without. Meeting minutes are often where the change was first agreed, and site diaries are where its effect was recorded. Variation and change impact review traces a proposed change through the record, and contract obligation extraction finds the periods that apply.
Does it cover JCT variations as well as NEC compensation events?
Where does it read the change record from?
How do we see it on our own change register?
Related pages
Construction contracts (NEC, JCT, FIDIC)
The conditions of contract, particulars, amendments and schedules that define obligations, risk allocation, notices and payment between the parties.
Construction programmes
The logic-linked schedule of activities, durations, milestones and float, held in P6, Asta or MS Project and issued as baselines and updates.
Meeting minutes and decision records
Minutes of design team, progress and coordination meetings, holding the decisions, actions and agreed changes that rarely make it back into the drawings.
Variation and change impact review
Tracing a proposed change through the drawings, specification, programme and contract to identify what it touches and what it triggers.
Contract obligation extraction
Extracting obligations, notice periods, risk allocations and deliverables from the executed contract into a structured register the project team can act on.