A contractor finishes a drainage package on a remeasured contract. It knows it imported more bedding sand than the bill allowed, that the trench ran deeper than the long section over a 60-metre stretch, and that it stood down twice waiting for the water authority. None of that is seriously disputed by anyone who was there.

Six weeks later the superintendent measures the work from the drawings, pays the bill quantities, and rejects the extra on the basis that there is no agreed record of the actual depths and no signed dockets for the sand. The contractor is right about what happened and cannot be paid for it, which is a different thing from being wrong.

This guide is about the records that close that gap. It is not about how work is priced — that is schedule of rates versus lump sum and bills of quantities, provisional and PC sums — nor about the statutory payment regime, which is security of payment in Australia. It is about the paper that makes a claim under any of them stand up.

The gap between work done and money received

On a lump sum job with no variations, records barely matter commercially. On everything else they are the mechanism of payment, and civil work is almost never the first case.

• Remeasured work is paid on measured quantity, and measurement is an agreement between two parties about a number. Your record is half of that agreement.
• Variations are paid on what was instructed and what it cost, both of which are historical facts that decay fast.
• Delay is paid on what was actually affected, which cannot be reconstructed from a programme alone.
• Latent conditions are assessed against what was encountered, and the condition is usually buried again within a day.
• Defects allegations are defended with evidence of conformance, often years later, by people who have left.

The common feature is that the evidence has to exist before you know you need it. Nobody keeps records for the claim they can see coming; the records that matter are the routine ones kept on a day that seemed unremarkable.

Three records, three different jobs

Contractors routinely treat site records and dockets as one thing. They are three, with different authors, different audiences and different failure modes.

Record	Answers	Typical author	How it fails
Daily diary	What happened, who was here, what stopped	Supervisor or foreman	Written up weekly from memory, or reduced to “continued works”
Dockets	What was delivered, used, carted or hired	Driver, operator, supplier	Unsigned, illegible, or never matched to an invoice
Survey and measurement records	What was built, to what line and level, in what quantity	Surveyor or engineer	Taken too late, after the work is covered

A fourth category sits across all three: correspondence. Notices, instructions, emails and responses are records too, and they are the ones that establish that the other party knew. The discipline for those is covered in our guide to contract administration for civil SMEs.

The daily diary that survives a dispute

The site diary is the single most valuable document a civil contractor produces and the one most often reduced to a formality. Its value comes entirely from being contemporaneous, specific and dull.

What a useful entry contains, every day, including the days nothing happened:

• Labour actually on site, by name or at least by trade and number, with start and finish times.
• Plant on site, and critically whether it worked or stood. A machine on site and idle is the whole evidence of a standby claim.
• Work performed, by location. “Pipe laying Ch. 120–185, 12 lengths DN300” is evidence. “Drainage works” is not.
• Weather, with substance. Not “wet” — rainfall if you have a gauge, the condition of the ground, and what specifically could not proceed because of it.
• Who attended. Superintendent, client representative, authority inspector, subcontractor supervisor, and what was discussed.
• Instructions received, verbal or written, with who gave them and when.
• Delays and disruptions, with the cause and the activity affected.
• Anything unexpected — a service found, ground different from the drawings, damage, an incident.

Three rules make the difference between a diary that helps and one that hurts.

• Write it the same day. A diary written up on Friday for the whole week is worth a fraction of one written daily, and an opponent will say so.
• Record facts, not conclusions. “Superintendent directed the crew to stand down at 10:15 pending a decision on the alignment” is a fact. “Superintendent caused another pointless delay” is an opinion that makes the whole document look partisan.
• Do not leave gaps. A diary with twelve missing days invites the inference that the records were made selectively. Record the quiet days.

A caution worth stating plainly: everything in the diary is discoverable. Frustration, blame, speculation about the client’s motives and jokes about the design all read very differently in a hearing room. Train supervisors to write as though a stranger will read it in two years, because one might.

Dockets: the ones you issue and the ones you accept

Dockets are the transaction record of civil work. They prove what arrived, what left, what was used and what was hired, and they flow in both directions.

Docket type	What it must show	The common failure
Material delivery	Product, quantity, source, date, time, vehicle, and who received it	Nobody signs it, or it is signed by whoever was nearest the gate
Concrete	Mix, batch time, slump, water added on site, and discharge time	Water added on site is not recorded, which matters later when a cylinder fails — see concrete supply and testing
Cartage and spoil	Loads, destination, tonnage or volume, and the weighbridge ticket where there is one	Volume assumed from truck size rather than recorded
Plant hire	Machine, hours worked, hours stood, operator, and what it was doing	Hours recorded without the standing time, which is the claimable part — see plant hire agreements
Labour	Names, hours, and the activity against a cost code	Hours captured for payroll but never coded to the work, so job costing cannot see the job
Subcontractor	What was done, where, and by how many people	Accepted on the subcontractor’s say-so at claim time

Two disciplines matter more than the format. Someone with authority signs, and their name is legible. An unsigned docket is an assertion; a signed one is an agreement. And the docket is matched to the invoice before the invoice is paid, not after. Dockets that are never reconciled are the standard route to paying for material that never arrived, and they are equally the reason a genuine delivery cannot be claimed.

On the receiving side, be careful what your people sign. A docket that says “received in good order” signed without inspection is a problem when the product is later rejected, and a docket with pre-printed terms on the back can carry contract conditions you did not negotiate.

Proving quantities on remeasured work

Remeasurement is where good records pay for themselves most obviously, because the quantity in the bill is a forecast and the quantity you are paid for is a measurement.

• Pick up before you cover up. Trench depths, subgrade levels, rock surfaces, bedding thickness and over-excavation are all invisible the next day. A survey pickup taken before backfill is the only evidence that will ever exist.
• Agree the method of measurement before you measure. Whether a quantity is paid by theoretical profile or actual excavation changes the number enormously, and that argument is much easier before the work than after.
• Do joint measurement where you can. A survey the superintendent attended, or at least was invited to in writing, is worth several times one you did alone.
• Keep the raw data, not just the calculation. The point file and the field notes are the evidence; the spreadsheet is your interpretation of it.
• Note the reason for any departure. If you dug deeper than designed, the record must say why — instructed, unsuitable material found, or a survey error — because that reason decides who pays.

Where machine control is in use, a large part of this record is generated automatically and most contractors never extract it — a point covered in our guide to machine control and GNSS in civil delivery. The as-built surface a machine produces is a measurement record you have already paid for.

Dayworks: the record that must be signed on the day

Daywork is work paid on actual resources rather than a rate, and it is the single most record-dependent payment mechanism in civil contracting. The mechanism itself is covered in our guide to bills of quantities, provisional and PC sums; this is the paperwork that makes it payable.

• Raise the sheet the day the work is done, not at the end of the week and certainly not at the end of the month.
• Get it signed by the superintendent’s representative on site. Signature for the resources, even where entitlement is disputed, is the usual and workable compromise — it separates “how many hours” from “who pays”.
• Record resources, not a dollar figure. People, hours, plant, hours, materials, quantities. Pricing comes later from the contract rates.
• Describe the work and the instruction. What was done, where, and under whose direction.
• Where signature is refused, send it anyway with a note recording the refusal and the reason given. An unsigned sheet transmitted the same day is far stronger than one produced months later.

The failure mode here is uniform across the industry: the crew does the work, everyone agrees it was extra, and the sheets are written up weeks later from a foreman’s notebook. At that point the hours are an estimate and the other side knows it.

Photographs, and why most of them are useless

Every phone on site takes photographs and almost none of them survive as evidence, for reasons that are easy to fix.

• No scale. A photograph of a rock face with nothing in frame for scale proves nothing about the volume. Put a staff, a shovel or a tape in the shot.
• No location. A close-up of a trench could be any trench. Take a wide shot that includes a recognisable feature, then the detail.
• No date you can rely on. File metadata is generally the date, but it is easily doubted; a board with the date and chainage in frame removes the argument entirely.
• Stored on a personal phone. When that person leaves, so does the evidence. Photographs need to land somewhere the business controls, the same day.
• Never captioned. Four hundred unnamed images in a folder are not a record. A caption of ten words at the time is worth an hour of guessing later.
• Only taken when something is wrong. The pre-start condition of the site, the neighbouring buildings and the existing pavement are the shots that defend you, and nobody takes them because nothing has happened yet.

The highest-value photographic habit in civil work is the pre-condition record before you mobilise — the existing cracks, the kerb damage, the state of the verge. Our guide to noise, vibration and dust management covers the formal pre-condition survey where vibration is involved, and making an insurance claim covers what an insurer will want to see.

The records a delay claim actually needs

Extension of time claims fail on evidence far more often than on entitlement. The mechanism is covered in our guide to extension of time and delay claims; these are the records that feed it.

To prove	You need
The event happened, on this date	The diary entry, correspondence, and a photograph
It affected this activity	The diary showing what that crew was doing and what it stopped doing
The activity was on the critical path	An updated programme as at the time, not one reconstructed afterwards
You mitigated	Records of what you redeployed the crew and plant to instead
It cost you this much	Timesheets, plant records showing standing time, and the cost report
You gave notice	The notice itself, sent in the contractual form and within the time bar

The row most often missing is the third. A programme updated monthly during the works is evidence; a programme built after the event to demonstrate a claim is advocacy, and it is treated as such. Updating the programme is a records discipline as much as a planning one, and our guide to writing a construction program covers how it is built in the first place.

Records that turn an instruction into a payment

Most disputed variations in civil work are not disputes about whether the work was done. They are disputes about whether it was instructed, and by someone with authority.

• Confirm verbal instructions in writing the same day. “Further to your direction on site this morning, we will…” costs two minutes and converts a conversation into a record.
• Know who can actually instruct you. A client’s engineer, a consultant and a site inspector may have very different authority under the contract, and work done on the wrong person’s say-so is work done for free.
• Keep the original scope. You cannot show that something is additional without the document that shows what was included.
• Record the cost separately from the moment it starts. A variation cost reconstructed from a general cost code is an allocation, not a cost.
• Do not let the work get ahead of the paperwork for long. Carrying unapproved variations is a cash-flow exposure as well as an evidentiary one — see variations in civil construction contracts.

Paper, phones and the system that gets used

The best record system is the one a tired supervisor will complete at four o’clock in the rain. That constraint rules out most of what gets sold.

• One place, not five. A diary in a notebook, photographs on a phone, dockets in a ute and timesheets in a spreadsheet is four systems and no record.
• Capture at the point of work. Anything that requires going back to the office to enter will be done late or not at all.
• Structured fields beat free text for the things you will need to search — date, location, activity, plant — with free text for the narrative.
• Photographs attached to the entry, not stored separately. The link between image and context is most of the value.
• Exportable. If your records cannot leave the app in a readable form, they are not much use in a dispute or a sale of the business.
• Backed up off the device. A phone in a creek should not cost you a claim.

Paper still works, and a signed carbon docket book remains excellent evidence. The failure of paper is not the medium, it is that the top copy ends up in a glovebox. Whatever the system, the test is whether a complete week’s records exist for every job, every week, without anyone chasing them.

Records down the chain, and back up it

A head contractor’s records are only as good as what comes up from its subcontractors, and its obligations upward depend on both.

• Require daily records as a subcontract obligation, in a stated form and by a stated time. Asking for them at claim time produces a reconstruction.
• Keep your own record of their resources. If a subcontract delay claim arrives, your diary entry recording how many of their people were on site is the only independent evidence you will have.
• Do not simply pass claims up. A subcontractor’s claim becomes your claim, with your evidentiary burden attached — see engaging and managing subcontractors.
• Reconcile their dockets against your own. Cartage loads and plant hours are the two that most often differ.

What to keep, and for how long

Retention periods come from several directions at once, and the practical answer is to keep project records for the longest of them rather than trying to apply each separately.

• The contract usually requires records to be kept and made available for a stated period, and sometimes gives the principal an audit right over them.
• Tax and employment law set their own minimum periods for financial and employee records.
• Limitation periods for contract claims run for years after completion, and longer where a deed is used — which is why “we finished that job in 2023” is not a reason to delete anything.
• Safety and health records have their own, much longer requirements where exposure monitoring or health surveillance is involved.
• Insurance may require you to be able to substantiate a claim long after the event.

Two practical rules. Close each job out deliberately, assembling the records into one place while people still remember what they are — the same discipline as the final claim covered in practical completion, defects liability and the final claim. And do not rely on an individual’s email account as the project archive, because it leaves when they do.

What tenders and audits ask for

Records appear in tenders more often than contractors expect, usually inside a quality, contract administration or management criterion, and they are easy marks for a business that has the system.

• Name the system and who maintains it. Not “comprehensive records are maintained” — the actual tool, the actual role, the actual daily deadline.
• Show a redacted example. One real diary page and one daywork sheet tell an evaluator more than a page of description.
• Connect records to the ITP. Conformance records, hold point releases and test results are a records question as much as a quality one — see quality management plans and ITPs.
• Describe the as-constructed deliverable and when it is produced, because on many contracts it is a condition of completion.
• Say how subcontractor records are obtained, which almost nobody addresses.

The same material supports an ISO 9001 audit, and reusing it across both is exactly the kind of leverage our guide to building a tender content library describes.

Checklist

• Is a diary completed every working day on every job, including quiet days?
• Does it record plant standing as well as plant working?
• Does it record work by location and quantity rather than by trade?
• Are verbal instructions confirmed in writing the same day?
• Do you know who, under the contract, can actually instruct you?
• Are delivery dockets signed by someone with authority, and legibly?
• Are dockets reconciled to invoices before payment?
• Is water added on site recorded on concrete dockets?
• Are daywork sheets raised and submitted the same day, in resources rather than dollars?
• Where signature is refused, is the sheet still transmitted with a note?
• Is survey pickup taken before work is covered?
• Is the method of measurement agreed before measuring?
• Are photographs captioned, located, scaled and stored off the phone the same day?
• Do you have pre-start condition photographs for every site?
• Is the programme updated during the works, not after?
• Do subcontracts require daily records in a stated form and time?
• Is there one place a complete week’s records can be produced from?
• Are records archived at job close-out rather than left in an inbox?

The short version

• Records convert work performed into work paid. On remeasured, varied or delayed work they are the mechanism of payment, not administration.
• The evidence has to exist before you know you need it, which means the routine days matter most.
• A diary written the same day, in facts rather than opinions, with no gaps, is the most valuable document a civil contractor produces.
• Record plant standing, not just plant working. Standing time is the claimable part.
• Everything in the diary is discoverable. Train supervisors to write for a stranger reading it in two years.
• An unsigned docket is an assertion. A signed one, reconciled to the invoice before payment, is an agreement.
• Pick up quantities before you cover them up, agree the method of measurement first, and keep the raw survey data.
• Daywork sheets must be raised and signed the same day, in resources rather than dollars. Signature for resources is the workable compromise where entitlement is disputed.
• Most site photographs are useless: no scale, no location, no caption, stored on a phone that leaves.
• Delay claims fail on the programme updated during the works, which almost nobody keeps.
• Confirm verbal instructions the same day, and know who actually has authority to give them.
• The best system is the one a tired supervisor completes in the rain. One place, at the point of work, exportable and backed up.
• Require daily records from subcontractors as a subcontract obligation, not a favour at claim time.
• Keep project records for the longest applicable period and archive at close-out, not in somebody’s inbox.

Sources and further reading

This guide is general information for Australian civil construction businesses and is not legal, accounting or contractual advice. What records a contract requires, who may issue an instruction, how work is measured and valued, what notices must be given and within what time, and what rights a principal has to audit records are all set by the particular contract, and differ between standard forms and amended conditions. Record retention periods are set separately by contract, by tax and employment law, by work health and safety legislation in each state and territory, and by limitation periods that differ by jurisdiction and by whether the contract is executed as a deed. Always work from the executed contract and current advice. Information is current as at October 2026.

• Australian standard-form construction contracts and their provisions on records, measurement, dayworks, instructions and the superintendent’s authority, which establish the patterns described in §05, §06 and §09. The forms in general use in Australian civil work are sourced in full in our guides to AS 4000 and AS 2124 and contract forms beyond construct-only. Amended conditions frequently alter who may instruct and how work is measured, and the executed contract governs.
• State and territory security of payment legislation, under which a payment claim must identify the work to which it relates and a payment schedule must state reasons for withholding — both of which depend on the records described here. Sourced in full in our guide to security of payment in Australia.
• Record-keeping obligations arising outside the contract and referenced in §12: Commonwealth tax record requirements, employee record requirements under workplace relations law, and the much longer retention periods that apply to health monitoring and exposure records under work health and safety legislation in each state and territory. Limitation periods for contract claims are set by state and territory limitation legislation and differ by jurisdiction.
• Related TenderBuilt guides carrying the primary-source detail referenced above: contract administration for civil SMEs, extension of time and delay claims, variations, bills of quantities, provisional and PC sums, schedule of rates versus lump sum, and latent conditions.