Variation Claim Documentation Checklist for Construction Projects

Variation claims are one of the most common sources of commercial pressure on construction and infrastructure projects. A variation may start with a simple instruction, drawing change, site direction, access constraint, revised specification, or late client requirement. However, if the change is not documented properly, the project team may later struggle to prove what changed, who instructed it, when notice was required, what cost was incurred, whether time was affected, and whether the claim pathway under the contract was followed. This is why a variation claim documentation checklist is not just an administrative tool. It is a commercial risk control. It helps project teams move from informal project noise to a clear claim pathway supported by evidence. For construction teams, the issue is rarely only whether extra work occurred. The more difficult issue is usually whether the records prove the contractual pathway from instruction to entitlement. In practical terms, this means the team needs to capture the instruction, confirm authority, issue the required notice, define the scope change, record the cost impact, assess the programme impact, and keep the supporting evidence in a structured way. The importance of good variation documentation is clear from wider construction dispute data. HKA’s CRUX Insight Eighth Annual Report analysed more than 2,200 construction and engineering projects across 114 countries, with a combined capital expenditure value of US$2.433 trillion. HKA reported that total costs claimed stood at US$95.0 billion, disputed costs averaged 33.4% of contract budgets, and time extensions sought by contractors amounted to 65.8% of planned schedules. HKA also reported that change in scope remained the most common cause of conflict, affecting just over 28% of projects. For teams managing variation claims in construction, these numbers reinforce a simple point: poor documentation is not a small problem. It can become a major driver of claim exposure, dispute risk, delayed payment, and weakened negotiation position. For more background on the broader commercial risk behind variations, read Perfomir’s related article: Variation Claims in Construction Contract Risk.

What is variation claim documentation?

Variation claim documentation is the collection of records used to support a claim that the contract scope, method, timing, quantity, sequence, access, quality requirement, or performance obligation has changed. In construction, variation claim documentation may include:

Documentation category	Examples	Why it matters
Instruction records	Formal directions, superintendent instructions, engineer instructions, client emails, site directions, revised drawings	Shows what changed and who directed the change
Authority records	Delegations, contract roles, meeting minutes, approval workflows	Helps confirm whether the person giving the instruction had authority
Notice records	Variation notices, delay notices, early warnings, claim notices, email acknowledgements	Shows whether the required contractual pathway was followed
Scope records	Contract drawings, revised drawings, specifications, RFIs, design clarifications, marked-up documents	Shows the difference between original and changed work
Cost records	Labour, plant, materials, subcontractors, preliminaries, supervision, disruption, quotations, invoices	Supports valuation of the variation
Time records	Baseline programme, updates, delay analysis, lookaheads, critical path notes, access records	Supports any extension of time or delay-related impact
Site records	Photos, diaries, daily reports, timesheets, delivery dockets, inspection records	Provides contemporaneous evidence
Commercial records	Claim register, correspondence log, assessment notes, payment claim references	Keeps the claim pathway organised

The purpose of these records is not to create paperwork for its own sake. The purpose is to show cause, effect, entitlement, and value in a clear sequence. A good variation claim file should answer eight practical questions:

1. What changed?
2. Who instructed or caused the change?
3. When did the change occur?
4. Was notice required?
5. Was notice submitted on time?
6. What work was affected?
7. What cost and time impact resulted?
8. What contract clause or claim pathway supports the claim?

If the file cannot answer these questions, the team may still believe the variation is valid, but the evidence may not be strong enough to support negotiation, assessment, payment, or dispute avoidance.

Why documentation matters before a variation becomes a dispute

Many contract variation disputes do not start as hostile disagreements. They often start as small gaps in records. A site team receives a verbal instruction and proceeds to keep the project moving. A revised drawing is issued, but the commercial impact is not assessed immediately. A superintendent or client representative asks for additional work, but the authority is unclear. A delay notice is drafted late because everyone is focused on delivery. Costs are captured in general cost codes rather than against the specific variation event. By the time the claim is prepared, the team is trying to reconstruct the story from emails, diaries, meeting notes, and memory. This is where variation claims become vulnerable. A strong variation claim is built as the event develops, not months later when the project team is under pressure to recover cost. The earlier the documentation is captured, the easier it is to show the link between the instruction, the changed work, and the impact. Industry data supports the importance of early discipline. HKA’s CRUX data shows that scope change remains the most common cause of conflict on major projects. RICS also promotes early conflict avoidance processes that encourage parties to identify issues quickly and resolve disagreements before escalation. In practical project terms, this means variation claim documentation should not wait until a dispute has already formed. The documentation process should begin as soon as a possible change is identified.

1. Capture the instruction

The first step in any construction variation claim documentation checklist is to capture the instruction. A variation usually begins with one of the following:

Type of instruction	Example	Documentation required
Formal written instruction	Written direction under the contract	Save the instruction, date received, clause reference, and response
Email instruction	Client or superintendent requests extra work by email	Save the email chain and confirm the instruction in writing
Verbal direction	Site conversation or meeting instruction	Send a confirmation email or site instruction confirmation
Revised drawing	Drawing revision changes scope, quantity, detail, or specification	Save old and new drawings and revision history
RFI response	Clarification creates additional work	Save the RFI, response, date, and affected work package
Meeting direction	Instruction recorded in meeting minutes	Save minutes and confirm any action or cost/time reservation
Site condition	Unexpected condition requires changed method or additional work	Save photos, reports, inspection records, and notice

The most important rule is simple: do not rely on memory. A verbal instruction should be converted into a written record as soon as possible. A short confirmation email can be valuable:

Further to today’s site discussion, we understand that we have been directed to proceed with [description of changed work]. We are reviewing the cost and time impact and will submit the required notice/details in accordance with the contract.

This does not need to be aggressive. It simply creates a record. The instruction file should include:

1. Date and time of instruction
2. Person issuing the instruction
3. Role and organisation of the person issuing the instruction
4. Method of instruction
5. Description of the work directed
6. Location or work package affected
7. Contract drawing/specification reference
8. Immediate response from the contractor or project team
9. Any reservation of rights or notice that cost/time impact is being assessed

Common mistake: Teams proceed with the work but do not confirm the instruction. Later, the other party may say the work was already included, was not authorised, or was carried out voluntarily. Better approach: Capture the instruction immediately and link it to a variation register item.

2. Confirm authority under the contract

Not every person on a project has authority to instruct a variation. This is one of the most important and often overlooked parts of claims and variations management. A project team may receive directions from client representatives, design consultants, site supervisors, asset owners, operators, project managers, engineers, superintendents, or end users. Some may have technical influence. Some may have operational control. But the contract may only allow certain people to issue binding instructions. The variation claim documentation should therefore include evidence of authority.

Authority question	Why it matters	Evidence to keep
Who gave the instruction?	Identifies the source of the direction	Email, meeting minutes, site diary, instruction form
What role did they hold?	Shows whether they had contractual authority	Contract particulars, delegation matrix, organisation chart
Was the instruction issued under the contract?	Connects the direction to the formal claim pathway	Clause reference, formal instruction number
Was approval required before proceeding?	Avoids later arguments about unauthorised work	Approval email, workflow record, superintendent direction
Was the instruction later confirmed?	Strengthens the record if initial direction was informal	Confirmation email, revised instruction, minutes

If authority is unclear, the safest practical approach is to ask for confirmation from the authorised contract representative. This does not need to delay urgent work, but it should be recorded. Example wording:

We note the requested change to [scope item]. Please confirm whether this is to be treated as a direction/variation under the contract and whether we should proceed pending valuation of cost and time impact.

This type of record helps avoid a common contract variation dispute: the contractor says the work was directed; the other party says the person who requested it had no authority. Perfomir helps with this problem by identifying clauses related to authority, variation pathways, notice obligations, and claim exposure so project teams can see where the contract may require formal approval before a variation claim is progressed.

3. Check the notice requirement

Notice obligations are often the point where variation claims become commercially vulnerable. Many construction contracts require notice within a specific period after the contractor becomes aware, or should have become aware, of an event that may give rise to a claim. Some contracts require separate notices for variations, delay, extension of time, disruption, latent conditions, directions, or cost claims. Some require the notice to include specific information. Some require the notice to be sent to a specific person or through a specific system. For more detail on this topic, read: Notice Obligations in Construction Contracts. A variation claim documentation checklist should capture the following:

Notice item	What to check	Record to keep
Trigger event	What event started the notice period?	Instruction, drawing revision, site direction, RFI response
Notice deadline	How many days are allowed?	Contract clause extract, notice tracker
Notice recipient	Who must receive the notice?	Contract particulars, email distribution
Notice form	Is a specific form, portal, or wording required?	Submitted notice, portal confirmation
Notice content	What details must be included?	Description, cause, likely impact, reservation
Supporting details	Are further particulars required later?	Claim programme, cost build-up, attachments
Proof of submission	Can you prove it was sent on time?	Email receipt, transmittal, document control record

A practical notice should usually identify the event, explain that it may give rise to a claim, reserve the right to claim cost/time impact where appropriate, and state that further particulars will follow once assessed. The exact requirements depend on the contract. This article does not provide legal or contractual advice. The point is that project teams should not assume that one email is enough unless the contract pathway has been checked. Common mistake: The site team sends many emails about the issue, but none of them satisfy the notice requirement. Better approach: Maintain a notice register and link every potential variation to the relevant contract clause, due date, submitted notice, and supporting documents.

Australian project context

On Australian construction and infrastructure projects, the required variation records and procedures depend on the specific contract, project type, and applicable state or territory framework. A document prepared for a progress claim should not automatically be assumed to satisfy a separate contractual variation notice, delay notice, extension-of-time requirement, or time bar. The practical control is to track these pathways separately while linking them to the same underlying event. For each potential variation, record the contractual notice required, the recipient, the due date, proof of submission, any later particulars, and the related payment or assessment status. This keeps the evidence connected without treating different contractual steps as interchangeable.

4. Define the scope change

A variation claim must clearly show what is different from the original contract scope. This is where many claims become unclear. The claim says “additional work was required”, but it does not explain the baseline. To support a variation claim, the team needs to show the difference between the original obligation and the changed requirement. The simplest method is a “before and after” comparison.

Scope element	Original requirement	Changed requirement	Evidence
Drawing	Drawing A Rev 1	Drawing A Rev 3	Drawing register, revision cloud
Specification	Standard coating system	Upgraded coating system	Specification revision, instruction
Quantity	100 metres	145 metres	Measurement sheet, take-off
Method	Install during normal access	Install in restricted access window	Access notice, programme update
Sequence	Work after Area A handover	Work resequenced before Area A completion	Programme, site instruction
Quality/testing	Standard inspection	Additional hold point/testing	ITP revision, inspection request

A good scope change record should include:

1. Original contract requirement
2. Changed requirement
3. Date the change was introduced
4. Document that introduced the change
5. Work package affected
6. Drawings/specifications affected
7. Quantity or method impact
8. Interface with other trades or disciplines
9. Whether the work has started, is ongoing, or is complete

The scope definition should be specific. Avoid broad wording such as “additional works due to design changes” unless it is supported by a detailed breakdown. Better wording:

The revised IFC drawing C-410 Rev 4 changed the pipe route between Grid B4 and C6, increasing the installed length by approximately 38 metres and requiring two additional bends, revised supports, and night-shift access due to the interface with live operations.

This gives the claim assessor something concrete to assess.

5. Record cost impact

A variation claim normally requires a clear valuation. The cost record should be detailed enough to show how the claimed amount was built up and why it relates to the variation event. Cost records may include:

Cost category	Examples of records
Labour	Timesheets, labour allocation sheets, supervisor sign-off, daywork sheets
Plant	Plant dockets, hire invoices, utilisation logs, standby records
Materials	Purchase orders, delivery dockets, invoices, wastage records
Subcontractors	Quotations, subcontract variation claims, invoices, assessment notes
Supervision	Site management time, additional supervision records
Preliminaries	Site facilities, temporary works, extended project overhead records
Disruption	Productivity records, workface access constraints, resequencing records
Design/engineering	Consultant instructions, design invoices, review hours
Testing/commissioning	Additional inspection, testing, commissioning records

A good cost record should answer:

1. What cost was incurred?
2. When was it incurred?
3. Who incurred it?
4. Why was it necessary?
5. How does it link to the variation instruction?
6. Is it actual cost, quoted cost, schedule of rates, lump sum valuation, or assessed estimate?
7. Has any part already been paid or included elsewhere?

Common mistake: Costs are captured in general project cost codes and later allocated to the variation based on estimate or memory. Better approach: Create a variation-specific cost code as soon as the change is identified. Even if the final entitlement is not yet agreed, the team can capture labour, plant, materials, and subcontractor costs against the potential variation event. A simple cost build-up table may look like this:

Cost item	Quantity	Rate	Amount	Evidence
Electrician labour	48 hours	$X/hr	$X	Timesheets, daywork sheets
EWP hire	3 days	$X/day	$X	Hire invoice
Additional cable	220 metres	$X/m	$X	Supplier invoice, delivery docket
Subcontractor testing	1 visit	$X	$X	Subcontractor invoice
Supervisor time	12 hours	$X/hr	$X	Allocation record

This article does not provide financial advice. The table is a practical documentation example only. The valuation method should be checked against the relevant contract.

6. Record time and programme impact

Not every variation causes delay. However, many variations affect time, sequence, access, productivity, or critical path risk. If the team does not record the time impact as the event develops, it may be difficult to support an extension of time or delay-related claim later. Time records may include:

Time record	Purpose
Baseline programme	Shows original planned sequence
Accepted/revised programme	Shows current approved plan
Lookahead programmes	Shows short-term workface impact
Delay notices	Records potential delay event
Progress updates	Shows actual progress before and after the event
Site diaries	Records daily work status and constraints
Access records	Shows restricted areas, permits, shutdowns, possessions
Photos	Shows physical status and workface availability
Meeting minutes	Records discussions about delay, resequencing, mitigation
Critical path analysis	Shows whether completion or milestones were affected

The programme impact should explain more than “the variation caused delay”. It should identify the activity affected, the planned dates, the actual dates, the sequence impact, and whether the affected activity was on or near the critical path. A practical programme impact table may include:

Programme issue	Detail
Affected activity	Install cable tray in Area 3
Planned date	3–7 August
Actual/revised date	10–17 August
Cause of impact	Revised drawing increased route and required new supports
Dependency	Work could not proceed until design clarification was issued
Mitigation	Additional crew added for two shifts
Residual impact	4 working days to downstream testing activity
Evidence	Programme update, site diary, RFI, photos, meeting minutes

HKA’s 2026 article on proactive dispute management notes that time-related disputes often involve delay events, insufficient float, unrealistic programmes, failure to comply with notice provisions, and lack of contemporaneous records. This is exactly why variation documentation must include both cost and time records.

7. Link the variation to entitlement

A variation claim is stronger when it links the facts to the contract pathway. This does not mean giving legal advice inside the claim file. It means organising the claim so the assessor can understand the contractual basis being relied on, subject to proper review. The claim pathway should identify:

1. Relevant variation clause
2. Relevant notice clause
3. Any valuation clause or schedule of rates
4. Any delay or extension of time clause
5. Any time-bar or condition precedent risk
6. Required claim particulars
7. Required assessment process
8. Required approval or determination process

For broader context, read: Contract Claims in Construction. A practical entitlement matrix may look like this:

Claim element	Project record	Contract pathway check
Instruction	Superintendent direction SI-014	Variation instruction clause
Notice	Variation notice VN-014 submitted 2 May	Notice clause and time period
Scope change	Drawing C-410 Rev 4	Scope/specification change
Cost impact	Labour/material/subcontractor records	Valuation clause or rate basis
Time impact	Programme update and delay notice	EOT/delay clause
Supporting evidence	Photos, diaries, RFIs, minutes	Claim particulars requirement
Claim submission	Claim package submitted 18 May	Assessment/payment process

The strongest variation claim files are easy to follow. They do not force the reviewer to search through hundreds of emails to understand the story. Common mistake: The claim includes cost records but does not clearly explain entitlement. Better approach: Use a claim pathway summary at the front of the claim package.

8. Keep evidence in one clear claim pathway

Variation claim documentation fails when evidence is scattered. One email is in the project manager’s inbox. The revised drawing is in the design folder. Photos are on a phone. Timesheets are in payroll. Subcontractor costs are in procurement. Notices are in document control. The programme impact is in a planner’s update. Nobody can see the whole pathway. This creates avoidable commercial risk. A practical variation claim folder structure should look like this:

Folder	Contents
01 Instruction	Original instruction, email, site direction, drawing revision
02 Authority	Contract role, delegation, confirmation of authority
03 Notices	Notice, proof of issue, acknowledgement, follow-up particulars
04 Scope Change	Original vs revised drawings/specifications, RFIs, sketches
05 Cost Records	Labour, plant, materials, subcontractors, quotes, invoices
06 Time Records	Programmes, delay analysis, lookaheads, diaries
07 Site Evidence	Photos, reports, inspection records, delivery dockets
08 Correspondence	Relevant emails, meeting minutes, commercial correspondence
09 Claim Submission	Claim narrative, valuation, attachments, assessment history
10 Outcome	Approval, rejection, negotiation notes, payment status

The goal is not to make the file complicated. The goal is to make it reviewable. A senior commercial manager, project director, superintendent, client representative, or independent reviewer should be able to open the file and understand:

1. The event
2. The contractual pathway
3. The evidence
4. The value
5. The time impact
6. The current status

This is where technology can help.

How AI can help identify variation claim exposure earlier

Variation claim risk often appears before a formal claim is submitted. The early warning signs may be hidden in contract clauses, notice periods, project correspondence, design revisions, site events, meeting actions, or repeated informal instructions. Perfomir’s contract risk intelligence platform, Contriqo by Perfomir, helps construction and infrastructure teams identify contract risk, notice obligations, claim exposure, and claim pathways earlier. Instead of waiting until a claim becomes a dispute, Perfomir helps project teams see where risk is forming. For example, Perfomir can assist by:

Project problem	How Perfomir helps
Teams miss notice obligations	Identifies notice-related clauses and highlights obligation pathways
Variation instructions are informal	Helps flag events that may create claim exposure
Claim evidence is scattered	Supports structured thinking around claim pathways and required records
Teams do not know which clause applies	Surfaces relevant contract clauses and risk categories
Commercial risk is identified too late	Helps teams detect early warning signs of claim exposure
Project leaders lack visibility	Provides a dashboard view of contract risk, claim exposure and obligations

Perfomir does not replace contract administration judgement, professional advice, or project-specific review. Its value is in giving construction teams earlier visibility of the contractual and commercial risk signals that are often missed during busy project delivery. To learn more about the software category, see: Contract Risk Management Software. For related risk management guidance, read: Construction Contract Risk Management. For claim risk forecasting context, read: Claim Exposure Prediction. Teams that want to explore how Contriqo by Perfomir may support their contract and claim risk workflows can review the Perfomir plans or contact Perfomir.

Variation claim documentation checklist summary

Below is a practical checklist that construction teams can use when a possible variation arises.

Step	Checklist question	Key record
1	Has the instruction been captured?	Direction, email, drawing revision, site instruction
2	Has authority been confirmed?	Contract role, delegation, confirmation email
3	Has the notice requirement been checked?	Notice clause, due date, notice register
4	Has notice been submitted on time?	Notice, transmittal, acknowledgement
5	Is the scope change clearly defined?	Original vs revised drawings/specifications
6	Has cost impact been recorded?	Labour, plant, materials, subcontractor records
7	Has time impact been assessed?	Programme update, delay notice, site diary
8	Is entitlement linked to the contract pathway?	Clause matrix, claim narrative
9	Is evidence stored in one place?	Structured claim folder
10	Has the claim status been tracked?	Register, assessment notes, payment outcome

A variation claim documentation checklist should be used early, not after the claim has already become difficult. The best time to document a variation is when the instruction, event, or change first appears. The second-best time is now. Strong documentation does not guarantee that a variation claim will be accepted. It does, however, give the project team a clearer pathway, better evidence, stronger internal visibility, and a more disciplined basis for commercial discussion. In construction and infrastructure projects, variation claims are rarely just about extra work. They are about the ability to prove the changed work through records, notices, scope definition, cost impact, time impact, and contractual pathway. That is why the most effective teams treat variation documentation as a live commercial control, not a month-end recovery exercise.

References

• HKA, CRUX Insight Eighth Annual Report: From Insight to Foresight
• HKA, Proactively Managing Construction Disputes: Strategies for Early Resolution
• Arcadis, 2024 Construction Disputes Report findings
• RICS, Conflict Avoidance Process

This article is for general information only. It does not provide contractual, legal, financial, or project-specific advice. Always review the relevant contract and seek appropriate professional advice before making decisions on a specific project or claim.