Ask a civil contractor why a claim failed and you will usually get an answer about the other side — the superintendent was difficult, the council was slow, the principal never intended to pay. Ask what evidence supported the claim and the answer gets shorter.
The uncomfortable pattern across failed claims is that the merits were often fine. What was missing was proof, and the proof had to be created months earlier, on ordinary days, by people who were busy doing something else.
The only preventative discipline in post-award
The document control that underpins all of it is covered in our guide to document control on a bid and a job. Our other post-award guides are reactive by nature. Variations, extensions of time, latent conditions and completion and final claims all describe what to do once something has happened.
This one is different. It is the system that determines whether any of those claims can be made at all — and it has to be running before the event, because every one of those claims depends on records that cannot be created retrospectively without looking exactly like what they would be: reconstruction.
Two things make this achievable for a small business. First, the volume of genuinely necessary record-keeping is far smaller than a Tier 1 document control regime — most of what large contractors do exists to coordinate hundreds of people, not to prove entitlement. Second, almost all of it is the same handful of artefacts feeding every claim type, so the marginal cost of the second claim is near zero once the system exists.
What follows is that system. It assumes one person part-time, no document controller, and a business that would rather be building.
Step one: the one-page contract summary
Nobody on site is going to read a 180-page contract, and nobody should have to. What they need is one page, printed, in the site office, that extracts the operative facts.
This is the single highest-return hour of work in the entire post-award phase, and it is done once, at award.
| What goes on the page | Why it is there |
|---|---|
| Contract form and edition — AS 4000-1997, AS 2124-1992, GC21, minor works, or bespoke | Determines every clause number below. See AS 4000 vs AS 2124 and contract forms beyond construct-only |
| Superintendent’s name, and who holds delegated authority | An instruction from someone without authority is not a direction |
| Delegation limits, if any | A representative may be able to direct up to a value and no further |
| Date for practical completion | The date every time claim is measured against |
| Liquidated damages rate and cap | The exposure. Everyone making programme decisions should know this number |
| Variation notice period — and whether notice is a condition precedent | The most expensive line on the page |
| EOT notice and claim periods — and whether they are conditions precedent | As above |
| Latent conditions notice requirement | Usually “promptly and before disturbance” — the instruction that has to reach the operator |
| Payment claim date each month, and the payment schedule and payment due dates | Drives the monthly cycle and the security of payment position |
| Retention percentage, cap, and the two release points | So somebody chases it |
| Defects liability period length | Diarised from practical completion |
| Insurances required and their expiry dates | A lapsed policy mid-contract is a breach. See insurance requirements |
| Where notices must be served, and on whom | Notice to the wrong address or the wrong person can be no notice at all |
Where a term on that page is unfamiliar to whoever is reading it, our civil construction tendering glossary defines every term in this list in a sentence.
Print it. Put it on the site office wall and in the ute. Email it to everyone with a role on the job. When a supervisor knows the variation notice period is 14 days and a condition precedent, they behave differently — not because they have become contract administrators, but because they now know that a phone call on Tuesday is worth more than a good memory in September.
Step two: the notice calendar
Every date on the summary that has a clock attached goes into a calendar with a reminder. Not a mental note; a calendar entry with an owner.
- Monthly payment claim date — recurring, with a two-day warning.
- Payment schedule due date each month, so you notice when one does not arrive. A missing payment schedule has consequences that are worth knowing about on the day rather than a fortnight later.
- Payment due date each month.
- Every live notice deadline, entered when the triggering event occurs, set at half the contractual period.
- Superintendent response dates — the 14-day practical completion response, the 28-day EOT assessment. Under an unamended AS 4000 a Superintendent who does not assess an extension of time within 28 days is deemed to have directed the full extension claimed,[2] which is worth money and only to contractors who track it.
- Insurance renewals falling within the contract period.
- Programme update date — monthly.
- At practical completion: end of defects period, final claim date, both retention release dates.
The half-period rule deserves emphasis. If the contract gives you 14 days, your reminder is at 7. The buffer exists because the person who knew was on annual leave, the email went to a spam folder, or the significance only became clear after a site conversation. Contractors who set reminders at the contractual deadline miss notices; contractors who set them at half never do.
Who can actually direct you
An instruction from a person without authority to give it is not a direction under the contract, and it is one of the standard grounds on which a variation claim is refused. On council work in particular, the site is full of people who sound authoritative — a project engineer, a works supervisor, a consultant’s site representative, an asset owner’s inspector — and only some of them can direct a variation.
Settle it at the kick-off meeting, in writing, in one paragraph:
“We understand the Superintendent under the contract is [name]. We understand directions under clauses [variations] and [EOT] will be issued by [name] or their delegate [name], and that [name]’s delegation is limited to $[amount]. Could you please confirm, and advise if any other person is authorised to give directions.”
Five minutes, and it removes an entire category of dispute. It also does something subtler: it signals early that you administer contracts properly, which changes how the other side handles the file for the rest of the job.
Where an instruction later comes from someone outside that list, you do not refuse it and you do not ignore it. You act on it if it is sensible and you write the same day: “We received an instruction from [name] on [date] to [scope]. We understand [name] may not hold a delegation to direct variations. Please confirm the direction.” That converts an unenforceable instruction into a documented one.
The site diary
The site diary is the evidentiary spine of every claim in the post-award cluster. Australian agencies assessing delay and disruption claims expect contemporaneous cost records, wage sheets, hire documentation and evidence of mitigation, and they note that principals should maintain their own detailed site records to verify claims independently.[1] Where the principal has records and you do not, the contest is over before it starts. The same records feed the monthly cost forecast described in our guide to job costing and cost control.
A diary that works is completed daily, on the day, by the person on site. Not weekly. Not from memory on Friday. The evidentiary weight of a diary comes precisely from its being a contemporaneous business record, and a diary visibly written in blocks loses most of that weight.
| Field | What good looks like |
|---|---|
| Date and weather | Conditions and any rainfall, plus the effect — “18mm overnight, site unworkable until 11am”. Weather claims live or die here |
| Labour on site | Names and classifications, and hours. Not “4 men” |
| Plant on site | Each item, and whether working, standing or broken down. Standing plant is only claimable if recorded as standing |
| Subcontractors | Who, how many, what activity |
| Work performed | By location and quantity — “pipe laid ch. 180–246, 66m DN450” |
| Visitors and what was said | The field that most often decides a variation claim. “D. Nguyen (Superintendent’s rep) attended 9:15am, instructed undercut ch. 335–360” |
| Delays and disruptions | What stopped, for how long, and why. Even a two-hour delay, recorded, becomes part of a pattern later |
| Instructions received | Cross-referenced to the register entry and the confirming email |
| Safety and environmental events | Incidents, inductions, inspections, spills, controls installed |
| Testing and hold points | What was tested, witnessed, passed or failed — cross-referenced to the ITP |
Two rules make diaries defensible. Never backfill. If a day was missed, note it as completed late and say when. A diary with an honest gap is credible; one that has been quietly filled in afterwards, and is later shown to have been, contaminates everything else. Never editorialise. “Superintendent being unreasonable again” is worthless as evidence and damaging when read aloud. “Superintendent declined to inspect; advised he would attend Thursday” is a fact.
Photographs, and why most of them are useless
Every civil contractor takes hundreds of photographs. Very few of them prove anything, for three reasons that are easy to fix.
- No location reference. A trench photograph with no chainage marker, survey peg or recognisable feature could be anywhere on a two-kilometre job.
- No scale. Depth, thickness and extent are the disputed facts, and a photograph without a staff, a shovel or a marked stake cannot establish any of them.
- No sequence. A photograph of a finished pavement proves nothing about the subgrade under it. Value comes from before / during / after triples of the same location.
The fix is a standing instruction that costs nobody any time: wide shot showing where you are, then a close shot with something for scale, and a note of the chainage in the diary. Keep the originals with their metadata — a photograph exported and resized loses the embedded date, and a date you cannot prove is a date the other side can question.
Store them by date and location in a structure someone else could navigate. Photographs on a supervisor’s phone are not records; they are photographs on a phone that will eventually be lost, replaced or wiped.
Daily production records
This is the record almost nobody keeps and the one that unlocks the hardest claim type.
Disruption — loss of productivity caused by the principal’s actions, which may not delay completion at all — is a recognised category of claim, and it requires a comparison between planned and actual output attributable to a specific cause.[1] That comparison is impossible without production data.
The record is one line per activity per day: activity, location, quantity achieved, crew size, plant deployed, hours worked. Two minutes for a supervisor who already knows all six numbers.
What it buys you:
- The measured mile. Comparing an undisrupted stretch of the same activity on the same job against the disrupted stretch is the most persuasive disruption evidence available — and it only exists if you measured both.
- Rate substantiation. When you argue that a tendered rate does not fit varied circumstances, actual production data is what shows why.
- Programme evidence. Actual progress against planned, recorded as it happens, is what makes a programme update credible.
- Better estimating. A year of production records is the most valuable input your next tender has. Our guide to civil cost estimating covers how to use it.
That last benefit is the one that makes the habit stick. Contractors adopt production records to support claims and keep them because they price better.
The five registers
Five spreadsheets, one workbook, one tab each. Not software, unless you already have it.
| Register | Key columns | What it prevents |
|---|---|---|
| 1 · Instructions and directions | Ref, date, from whom, oral or written, scope, confirmation email sent (date), variation ref if any | Instructions disappearing between the site and the office |
| 2 · Variations | Ref, event date, source, description, notice sent, notice due, EOT claimed Y/N, valuation basis, claimed $, assessed $, paid $, status | The whole of §16 of the variations guide — missed notices, forgotten time claims, unreconciled amounts |
| 3 · Delays and EOT | Ref, event date, cause, qualifying/compensable, notice sent, claim sent, claim due, days claimed, days granted, Superintendent response due, delay costs claimed | Missed 28-day windows and unnoticed deemed assessments |
| 4 · RFIs and clarifications | Ref, date raised, question, date answered, days outstanding, impact | Late responses being invisible. The “days outstanding” column is the causation evidence for a whole class of delay claim |
| 5 · Drawing and document revisions | Drawing no., revision, date received, date reviewed, scope change Y/N, variation ref if any | Constructive variations arriving inside routine revisions and never being identified |
Register 5 is the one that most often surprises contractors with what it finds. The discipline is a fifteen-minute review each time a revised drawing lands, answering one question: does this change what we have to build, or how we have to build it? On a job with forty drawing revisions, that habit typically finds three or four claimable changes that would otherwise have been built silently.
Register 4’s “days outstanding” column is similarly underrated. A single late RFI response is an irritation. Fourteen RFIs averaging nineteen days against a contractual seven is a documented pattern of principal delay, and it is the kind of evidence that supports both an extension of time and a disruption claim.
Writing correspondence that helps you later
Every email on a construction project is a potential exhibit. That is not a reason to write defensively — defensive correspondence damages relationships and rarely helps — but it is a reason to write with a few habits.
- One subject per email. A message covering a variation, a programme question and a request for a pit lid cannot be filed against anything and cannot be produced cleanly later.
- Reference the register number in the subject line. “VO-07 — undercut ch. 335–360 — request for direction”. Six months on, the file organises itself.
- Facts, dates, and what you are asking for. Then stop. Adjectives about the other party’s conduct are the parts you will regret.
- Confirm conversations the same day. “To confirm our discussion this morning…” is the most useful sentence in contract administration.
- Ask for correction rather than asserting agreement. “If our understanding is incorrect, please advise before we proceed” invites a response and makes silence meaningful.
- Never describe your own position more weakly than the facts require. “We were probably running behind anyway” written casually in an email becomes the principal’s concurrency defence — and concurrency is what removes delay costs while leaving the extension intact.[1]
- Serve formal notices the way the contract requires. If the contract specifies an address, a portal or a named recipient, an email to the site engineer may not be service at all.
On tone: the objective is a file that reads, to a stranger eighteen months later, as the work of a competent contractor doing its job. That file is worth more in an assessment than any individual clever argument, and it is built one ordinary email at a time.
Keeping the programme alive
A programme submitted at tender and never touched again is a document that cannot support a time claim, because critical delay can only be demonstrated against a baseline that reflects reality.[1]
The minimum viable discipline:
- Get the baseline accepted and keep the acceptance correspondence.
- Update monthly with actual start and finish dates against each activity.
- Keep every revision as a separate, dated file. Superseded programmes are evidence.
- Note what changed and why in a short covering note with each issue — three lines is enough, and it is what turns a series of files into a narrative.
- Do not silently absorb principal-caused delay into your float. Re-sequencing to keep working is good practice, but do it visibly and record that you have done it, or the eventual claim looks invented.
The programme’s tender-stage role — as a scored document — is covered in our guide to writing a construction program for tenders. Its post-award role is entirely different and considerably more valuable.
Capturing cost against events
Claims are reimbursement claims. Agencies expect to see that costs were actually incurred, supported by cost records, wage sheets, invoices, hire documentation and subcontract agreements.[1] A claim priced from a rate card rather than from actual cost will be challenged.
The mechanism is simple and has to be set up before the event, not after: open a cost code the day you notify a variation, a latent condition or a delay, and code everything to it from that moment. Labour hours, plant hours, materials, subcontract, disposal, testing.
Two supporting decisions worth making once and holding across the business:
- Decide your plant rate basis and use it consistently. Internal rates, a published hire schedule, or the rates embedded in your tendered items — pick one, state it in every claim, and do not vary it between claims on the same job. Inconsistency invites a review of everything.
- Decide your overhead and margin basis and check it against what the contract allows. Some contracts fix the percentage applicable to variations, which particularly hurts on small, disruptive changes.
Remember what is not recoverable: claim preparation costs, loss of profit on a delay itself, and formula-based overhead calculations such as Hudson or Eichleay.[1] Including them signals a claim assembled from a template.
The monthly claim cycle
The monthly payment claim is the heartbeat of contract administration, and it is where all the registers converge.
- Measure the work — quantities completed this period, agreed with the Superintendent’s representative where possible before the claim goes in.
- Add every live variation, assessed or not. A disputed variation left out of the claim forfeits the statutory route for that cycle.
- Add delay damages for approved extensions attributable to compensable causes.
- Check the claim is endorsed and served as the legislation and the contract require — the mechanics differ by state and are set out in our guide to security of payment in Australia.
- Diarise the payment schedule date and the payment due date.
- When the schedule arrives, read the reasons. A respondent is generally confined to the reasons stated in the payment schedule, so those reasons define the shape of any adjudication that follows.
- Update the registers with assessed and paid amounts. The gap between claimed and paid, tracked monthly, is your live commercial position on the job.
Step 7 is the one that gets skipped, and skipping it is how a contractor arrives at practical completion without knowing that $61,000 of variations were never assessed.
The other direction: administering your subcontractors
Everything above treats you as the party making claims. On most civil jobs you are simultaneously the party receiving them, and the administration running downward is what determines whether a claim from above passes cleanly through you or lands on your margin.
Three exposures matter for a civil SME.
Back-to-back notice timing. If your subcontract gives a subcontractor 14 days to notify you of a delay, and your head contract gives you 14 days to notify the Superintendent, the two windows expire together and you have no time to assess anything. Subcontract notice periods should be materially shorter than the head contract periods they feed — commonly half. Where you have inherited a subcontract that does not do this, the practical fix is a standing instruction that subcontractors notify immediately and confirm in writing within seven days.
You are a respondent under security of payment, not only a claimant. When a subcontractor serves a payment claim on you, the same statutory machinery that protects you against the principal now runs against you — including the consequence of failing to serve a payment schedule within the statutory period. A missed payment schedule on a subcontractor’s claim is one of the more expensive administrative errors available to a civil SME, because it can remove your ability to raise reasons for withholding at all. The timeframes differ by jurisdiction and are set out in our guide to security of payment in Australia.
Subcontractor delay costs need verification before they are passed up. Where you claim a subcontractor’s delay costs as part of your own prolongation claim, expect the subcontract itself to be requested and the amounts to be verified.[1] Passing through a subcontractor’s number without checking it is how a contractor ends up defending someone else’s arithmetic.
The registers extend downward without much extra effort: add a column to the variations and delays registers recording whether the item originated with a subcontractor, and whether the corresponding notice was given both ways. On a job with three subcontractors that single column prevents most of the pass-through failures.
A filing structure that survives staff turnover
Records that exist but cannot be found are records you do not have. The test is simple and worth applying honestly: if the person who ran this job left tomorrow, could someone else assemble a variation claim from the files?
A structure that passes that test, per job:
- 01 Contract — executed contract, special conditions, annexure, the one-page summary, insurance certificates, security documents.
- 02 Drawings — by revision, with the superseded set retained rather than overwritten.
- 03 Correspondence — chronological, or by register reference where a matter has one.
- 04 Site records — diaries, production sheets, dockets, subfolders by month.
- 05 Photographs — by date, then location.
- 06 Programme — every revision, dated, with covering notes.
- 07 Quality — ITPs, test results, nonconformances, conformance survey.
- 08 Claims — payment claims, payment schedules, variation claims, EOT claims, assessments.
- 09 Registers — the single workbook.
- 10 Completion — notices, punch lists, handover documentation, final claim, certificates.
Two rules do most of the work. Never overwrite a superseded document — save the new revision alongside the old, because the comparison between them is frequently the evidence. And file by the register reference wherever one exists, so that VO-07 has a single home containing the instruction, the confirmation, the pricing, the claim and the assessment.
Whatever the storage — a shared drive, a cloud folder, project software — the requirement is the same: it is accessible to more than one person, it is backed up, and it is not on a phone.
When the relationship goes bad
Most civil contracts run on goodwill and are administered lightly by both sides. That works until it does not, and the transition is usually abrupt — a refused claim, a levied set-off, a superintendent replaced mid-contract by someone taking a harder line.
The contractors who come through that transition well are the ones whose administration did not change, because it was already correct. The ones who suffer are those who administered informally for eight months and then attempt to construct a record retrospectively — which is visible, and which damages the credibility of the genuine claims alongside the reconstructed ones.
Practical guidance for the point at which things turn:
- Do not escalate the tone. Correspondence that becomes adversarial reads badly to every subsequent reader, including an adjudicator. Keep writing the same neutral, factual letters you were writing before.
- Do not stop work over a payment dispute. Under AS 4000 clause 42.1 performance continues notwithstanding a dispute about payment,[2] and suspension outside the statutory rights is likely to put you in the wrong.
- Use the statutory route rather than the contractual one where you can. Adjudication is faster and cheaper than a contractual dispute process, and it runs on statutory timeframes.
- Get every outstanding item into the next payment claim. Leaving a disputed variation out to avoid provoking anyone forfeits the statutory route for that cycle.
- Take advice early rather than late. The cheapest legal advice is the advice that tells you which notice to send this week; the most expensive is the advice sought after a time bar has expired.
It is also worth naming the opposite failure mode. Some contractors respond to a deteriorating relationship by administering aggressively — claiming everything, writing at length, treating every exchange as a position. That produces a worse outcome than under-administration, because it converts a recoverable relationship into a file that has to be resolved formally. The target is neither passive nor combative: it is a job that is documented well enough that nothing needs to be argued about twice.
Who does this in a small business
The honest problem is that in a fifteen-person civil contractor there is no contracts administrator. The work falls to the owner, an estimator, or an office manager who is also doing payroll.
Three arrangements work, and one does not.
| Arrangement | How it works | Watch for |
|---|---|---|
| Split site / office | Supervisor owns the diary, photographs and production records. Office owns the registers, notices, correspondence and claims | The handover. It needs a fixed weekly time, not “when I get a chance” |
| Owner-administered | The owner does the contractual work personally, one hour a week per job | It is the first thing to go when the business gets busy — which is exactly when claims arise |
| Outsourced | An external contracts person runs the registers, notices and claims, working from the site records you supply | They can only work from what site actually records. The diary discipline is still yours |
| Nobody | Everyone assumes someone else is tracking it | The default state, and the reason most of these claims are never made |
Whichever applies, name the person. A system without an owner is not a system. If you would rather the contractual layer sat outside the business — the contract summary extracted, the notice calendar built, and the registers and claims run from your site records — that is what our post-award and mobilisation support exists to do.
The weekly and monthly rhythm
Daily — on site, ten minutes
- Site diary completed, on the day.
- Production line recorded per activity.
- Photographs taken with location and scale where anything unusual occurred.
- Any instruction received phoned or emailed to the office the same day.
Weekly — office, thirty minutes
- Update all five registers.
- Check notice-due dates for the coming fortnight; send anything outstanding.
- Send confirmation emails for any unconfirmed instruction.
- Review drawing revisions received this week for scope change.
- Check RFI days-outstanding and follow up anything overdue.
Monthly — office, two hours
- Update the programme with actual dates; issue with a short covering note.
- Prepare and serve the payment claim, including every live variation and delay claim.
- Reconcile claimed vs assessed vs paid, and chase the gaps.
- Check upcoming contractual dates for the month ahead.
Roughly fifty minutes a day across a business running three jobs, most of it by people already on site. Set against a single $40,000 variation that would otherwise fail for want of a same-day email, the return is not a close call.
A ninety-second self-audit
Pick your largest current job and answer these. Each “no” is a claim you probably cannot make.
- Can you state the variation notice period, without looking it up, and say whether it is a condition precedent?
- Is there a site diary for yesterday, written yesterday?
- Can you produce, in under two minutes, every instruction received on the job and whether each was confirmed in writing?
- Do you know how many days each outstanding RFI has been outstanding?
- Has the programme been updated with actual dates in the last month?
- For the last three drawing revisions, is there a record of whether they changed scope?
- Do you know the gap between what you have claimed and what has been paid?
- Is there a diary entry for the next contractual deadline on the job?
- If the Superintendent’s rep instructed something on site this morning, would an email have gone out today?
Most civil SMEs answer no to five or more of these on their busiest job — which is the same job carrying the most variations, the most delay and the most money at risk. The correlation is not coincidental: administration degrades exactly when the events that require it are happening.
That is the argument for building the system before it is needed. None of it is difficult. It is a page on the wall, a calendar with owners, a diary written daily, a photograph with a scale in it, and thirty minutes on a Friday.
References
This guide is general information for Australian civil construction businesses and is not legal advice. Notice requirements, service provisions and record-keeping obligations depend on the executed contract and differ between jurisdictions. All examples are illustrative. Always work from your contract documents and obtain advice on any claim of significance.
- NSW Government (buy.nsw) — Construction procurement guide: handling prolongation and disruption claims. Substantiation expectations including cost records, wage sheets, invoices, hire documentation, subcontract agreements and proof of mitigation efforts, and the expectation that the principal maintain detailed site records to verify claims independently. Definition of disruption claims as claims for loss of productivity arising from the principal’s actions which may not result in delay to completion, and of prolongation claims as claims for reimbursement of time-related costs caused by delays the principal caused. Requirement that the contractor demonstrate a delay occurred affecting the critical path or a completion milestone, that all claimed costs were actually incurred, and that every effort has been taken to minimise those costs. The position that a contractor is not entitled to delay costs where there is a concurrent delay within the contractor’s control. Non-recoverable items including claim preparation costs, loss of profit on the delay itself, and costs calculated under the Hudson or Eichleay formulas. The position that valuing the delay component of each claim when it is first submitted significantly reduces the opportunity to exaggerate quantum, and that aggregate end-of-contract claims obscure causation. ↩ ↩ ↩ ↩ ↩ ↩ ↩
- AS 4000-1997 General conditions of contract, clauses 20, 25, 34, 36 and 42, and AS 2124-1992 General conditions of contract, clauses 12, 35.5 and 40 — notice, direction, latent condition, extension of time, variation and dispute mechanisms, as described in Turtons Lawyers, How to claim a variation under AS 4000, How to claim an EOT under AS 4000, How to claim for a latent condition under AS 4000 and Practical completion under AS 4000, and sourced in full in the companion guides in this series. Clause 20 permitting the contractor to request written confirmation of an oral direction; clause 34.3 requiring an extension of time claim within 28 calendar days of becoming aware of the causation; clause 34.5 requiring the Superintendent’s written assessment within 28 calendar days, failing which a deemed assessment and direction for the full extension of time claimed arises; clause 25.3 excluding costs incurred more than 28 days before notice of a latent condition; clause 34.6 requiring notice of anticipated practical completion at least 14 calendar days before the anticipated date, with the Superintendent to respond within 14 calendar days; and clause 42.1 requiring the contractor to continue performing the work under the contract notwithstanding the existence of a dispute about payment. ↩ ↩