Key takeaways
- A site record only protects you if it was made at the time, by the person who saw the thing, and stored where it can be found later.
- Photographs, diary entries and signed variations are the three records that decide most residential disputes, because they fix what was agreed and what was actually built.
- The NSW dispute resolution process expects a documented attempt to resolve a matter before it escalates, which means your site records are effectively your first submission.
- Records have two audiences with different rules: the tax system wants the transaction trail, and a dispute wants the decision trail, and a good site system produces both from one habit.
- Delegating records to an apprentice without checking them is worse than keeping none, because a wrong record is harder to explain than a missing one.
Ask a builder what went wrong on a job that ended in a fight and the answer is rarely that the work was defective. It is usually that nobody could prove what had been agreed, what had been built, or when either of those things happened. The trade knowledge was there. The evidence was not.
Site administration is the part of the job that produces that evidence. It is not the same thing as your accounting system, and it is not the same thing as how you run the business day to day. It sits between them: the habit of capturing what happened on site, in a form that survives being read by someone who was not there and does not want to agree with you.
This article is about the records themselves — what to capture, when, where it goes, and which ones actually get used when a matter escalates. Business system design and cash flow forecasting are separate problems, and there are other articles on this site that deal with those.
Why a record made late is worth almost nothing
The value of a site record comes from three things: it was made at the time, it was made by someone who saw the thing, and it can still be found. Miss any one of those and the record degrades. A diary reconstructed on a Friday afternoon from memory is not contemporaneous. A photograph taken by a supervisor who was told about a defect by a subbie is not first-hand. A folder of images on a phone that was replaced two years ago is not findable.
This matters because of how building disputes actually resolve. The NSW Government guidance on resolving building disputes sets out a process that expects the parties to have attempted resolution, and that process runs on documents. When a matter gets to a point where a third party is assessing it, they are not assessing your workmanship from scratch. They are reading two competing accounts and deciding which one is better supported. A builder with dated photographs and a complete diary usually wins that contest without the merits being tested at all.
The commercial consequence is blunt. A dispute that resolves at the letter stage costs you a few hours and some goodwill. The same dispute that escalates costs you time off the tools, legal fees, and in the worst case a defect claim you cannot rebut because the wall was rendered over before anyone photographed it.
The three records that decide most residential disputes
Not all records carry equal weight. In residential work, three categories do most of the work.
Photographs, taken at the right moment
A photograph is only useful if it shows the thing before it was concealed. Frame, bracing, waterproofing membrane, flashing, slab reinforcement, service penetrations — all of these are invisible a day after the trade moves on. The habit that protects you is photographing each element at the point where the next trade would cover it, and keeping the images with the job address and a date.
Variations, signed before the work proceeds
A variation that exists only as a text message is a variation you will argue about. The record needs to identify what changed, what it costs, and who agreed to it. If the client will not sign before work starts, record in writing that you are proceeding on instruction and that the cost will follow. That single sentence, sent the same day, changes the shape of the argument later.
The site diary
The diary is where you record the things that are nobody’s fault but still cost money: rain days, delayed deliveries, a client who could not decide on tile selection, an inspector who needed a detail clarified. These entries look trivial when written. They become the basis of an extension of time claim, or the reason a delay is not yours.
Building a defensible site diary
- 1Record the day’s conditionsWeather, access, deliveries, who was on site, and anything that stopped work proceeding as programmed.
- 2Note instructions as they arriveWho gave the instruction, when, in what form, and what it changed about the scope or sequence.
- 3Log delays with a causeRecord the event and its consequence separately, so the effect on the programme can be argued later.
- 4Attach the evidence the same dayPhotographs, delivery dockets, emails and inspection records go in while the context is still obvious.
- 5Sign off and date itAn undated entry is worth very little when someone else’s version of events is dated.
What a site diary entry actually needs to contain
A diary is not a journal. It is a structured record, and the structure is what makes it credible. Each entry should be able to answer the same set of questions, whether it is written by you or by a supervisor.
- Date and day of the week. Sounds obvious; it is the first thing missing from a retro-fitted diary.
- Weather and site conditions. Relevant to concreting, rendering, painting, waterproofing and earthworks, and to any claim about lost time.
- Labour on site. Who was there, which trade, and how many. Useful for progress claims and for questions about whether a delay was a resourcing problem.
- Work completed and work not completed. Both halves matter. What did not get done, and why, is where the money is.
- Instructions received. Verbal instructions should be written down the same day and confirmed by email, even when the relationship is good.
- Deliveries, inspections and visitors. Who attended, what they inspected, what they said.
- Incidents and near misses. Kept for safety reasons, and occasionally relevant to a later claim.
The point of the structure is that it forces the writer to record the unfavourable things as well as the favourable ones. A diary that only ever records good progress reads as fabricated, and it will be treated that way.
Records have two audiences, and they want different things
Most builders understand that records are needed for tax. The ATO guidance on record keeping for business is clear that records must be kept, that they must be able to be produced, and that they need to support what you have reported. That is one audience: the tax system wants a complete transaction trail, and it wants it retained for the period the law sets.
A dispute is a different audience. It does not care about your BAS. It wants to know what was agreed, what was built, when, and by whom. A builder can have flawless financial records and still lose a defect argument, because the invoice proves money moved and proves nothing about the work.
The efficient answer is not two systems. It is one habit that produces both. A photograph taken for the job file is also evidence the work was done as claimed. A signed variation is both a document supporting the invoice and the record of what changed. The trick is filing everything against the job address rather than against a person or a month, because that is how it will need to be retrieved.
Two audiences for the same records
| Records the tax system wants | Records a dispute wants |
|---|---|
| Invoices and receipts for every purchase | Instructions and who gave them |
| Bank and payment records | Dated photographs of work before it is covered |
| Wages and subcontractor payment records | Signed variations and the reason for each |
| Records of assets and their disposal | Diary entries on weather, access and delays |
| Records kept for the period the Act sets | Records kept until the defects liability period ends |
Where records go, and why the folder structure matters more than the format
Whether you keep records in a cloud folder, a project management app or a filing cabinet is a secondary question. The primary question is whether someone who is not you can find a specific document from a specific date on a specific job without ringing you.
A workable structure is one folder per job, containing subfolders for the contract and approved plans, variations, the site diary, photographs by stage, inspection and certification documents, subcontractor and supplier records, and defects and handover documents. The names should include dates in a consistent order so they sort correctly.
Two rules make the difference. First, records go in on the day they are created, not at the end of the project. Second, nothing is stored only on a personal phone. If the only copy of the waterproofing photographs is on a supervisor’s device, then when that supervisor leaves, so does your evidence. Sync it or lose it.
Delegation, and the trap of the unchecked record
On larger jobs, the site diary and photo record will be kept by a supervisor or leading hand. That is fine, and often better, because they are closer to the work. What is not fine is delegation without a check.
An apprentice who records that a slab was poured on the wrong day, or a supervisor who writes “client instructed” without naming the client, has created a document that will be used against you. A wrong record is harder to explain than a missing one, because it suggests either carelessness or something worse.
The check is simple and takes minutes. Once a week, read the diary entries and look at the photographs. Do they match what you know happened? Are there gaps on days when something went wrong? Gaps are the tell, and they are much easier to fix a week later than a year later.
The mistake that costs the most. Leaving a variation undocumented because the relationship is good and the client is reasonable. The client who never disputes a variation is the same client who, six months after handover, cannot remember agreeing to it — and by then the wall is tiled and the cost has already been carried by you.
Records and the pointy end: insolvency and non-payment
There is a harder reason to keep site records than disputes over defects. If a client or a head contractor becomes insolvent, your ability to establish what you are owed depends entirely on documents. ASIC’s guidance on voluntary administration for creditors sets out the process creditors go through to establish and pursue a claim, and it runs on written evidence of the debt and the work that gave rise to it.
In that situation, a builder with signed variations, progress claims, delivery dockets and a diary showing what was done has a claim that can be quantified. A builder with a verbal arrangement and a phone full of photos has a much weaker position, and may be treated as an unsecured creditor with a disputed amount. The records you keep on site are the same records that determine what you recover.
Worked example: a renovation in western Sydney
A builder in western Sydney is running a ground-floor renovation with a first-floor addition. The contract is straightforward, the client is engaged, and the job is going well until week nine, when the client asks for the kitchen window to be moved and a wall removed.
The builder does the right thing in the moment: he tells the client it is a variation, gives a verbal figure, and the client says to go ahead. Work proceeds. The window is framed in the new position and the wall comes out. Nothing is written down, because the client is on site every day and the relationship is pleasant.
At practical completion, the builder issues the final claim including the variation. The client disputes it, saying the window move was discussed but never agreed at that price, and that the wall was always going to come out. There is no signed variation, no email, and no diary entry naming the conversation.
The builder’s position now depends on what else exists. If his diary for week nine records the instruction, who gave it, the date, and the figure quoted, he has something. If there are photographs showing the wall intact at the start of the week and removed at the end, he has corroboration. If the subsequent invoices to the frame carpenter and the plasterer reference the change, the trail is stronger again.
If none of that exists, the matter turns into a credibility contest about a conversation in a kitchen. Even if the builder is believed, he has spent unpaid time establishing something that a single signed page would have settled. The cost of the dispute exceeds the value of the variation.
The lesson is not that the client was dishonest. It is that memory is unreliable and goodwill is not a record. The builder who writes the variation up the same day, sends it, and keeps a copy has removed the dispute from the realm of recollection entirely.
Before you close out a job
- Every variation is signed by the person with authority to sign it.
- Photographs exist for each stage before it was covered up.
- The site diary runs without gaps from start to practical completion.
- Inspection and certification documents are filed against the address, not a person’s inbox.
- Subcontractor and supplier records are complete enough to answer a claim.
- Defect reports and the responses to them are stored together.
- Handover documents and the final claim sit in the same job file.
Building the habit without building a bureaucracy
The failure mode for site administration is over-engineering. A system that takes an hour a day will be abandoned within a month, and an abandoned system is worse than a simple one because it creates gaps that look deliberate.
Start with the three records that carry the most weight: a daily diary entry, photographs at each concealment point, and a written variation for every change. Everything else can be layered on later. If you want the wider context of how these habits sit inside a builder’s systems, the article on business systems for a small builder covers how the pieces fit together, and the piece on supplier accounts and credit terms deals with the money side rather than the evidence side.
Two practical rules make the habit stick. First, attach the record to the moment it is created — the photo at the point of concealment, the diary entry at the end of the day, the variation email before the trade is booked. Second, keep everything against the job address, so retrieval does not depend on remembering who was involved.
What good site administration is actually for
Builders tend to think of paperwork as a compliance cost, something imposed by the tax office or the certifier. That framing is why it gets done badly. The records that matter on site are not there to satisfy anyone external. They are there so that when a client, a subbie or an insurer disputes something, the answer takes an hour rather than a year.
The measure of a good site record system is not how comprehensive it is. It is whether a stranger could pick up the file for a finished job and reconstruct what was agreed, what was built, when, and what changed. If they can, you are protected. If they cannot, you are relying on everyone else’s memory being as good as yours, and it will not be.
If you want to go further into how these obligations sit alongside your licensing requirements, the guide to how NSW builder CPD works sets out the framework, and the PointCPD course catalogue covers the business and contract units that deal with records and disputes in more depth.
Questions builders ask
How long do I need to keep site records for a residential job?
There are two different retention questions and they have different answers. Tax records must be kept for the period set out in the tax law, and that period runs from when the record was prepared or the transaction completed. Site records kept for dispute purposes need to survive the defects liability period and any subsequent claim, which is usually longer. Keep job files intact until well after the last possible claim on that job has expired.
Is a text message from a client enough to prove a variation?
It can help, but it is usually incomplete. A message that says 'go ahead with the window move' establishes agreement to the change but often not the price, the scope or the effect on the programme. The better practice is to follow the message with a written variation setting out what changes, what it costs, and when it will be done, and to ask for confirmation in writing.
Who should keep the site diary on a job with a supervisor?
The person closest to the work should write it, which usually means the supervisor or leading hand. What matters is that the builder reviews it. A weekly check that the entries are complete, dated and consistent with what you know happened catches problems while they can still be fixed, rather than discovering a gap when a dispute starts.
What should I photograph on site, and when?
Photograph each element at the point where the next trade would conceal it. That means frame and bracing before lining, waterproofing before tiling, flashing and sarking before cladding, slab reinforcement before the pour, and service penetrations before they are closed up. Keep the images filed against the job address with a date, not on a personal device.
Do I need to give the client copies of my site records?
Not the working diary, but clients are entitled to records that relate to their job, including variation documentation, inspection certificates and handover material. The practical approach is to send anything that changes the scope or the price as a matter of course, and to keep the internal working record for your own use. If a dispute escalates, you may be asked to produce the rest.
What is the difference between records for tax and records for a dispute?
Tax records prove that money moved and that what you reported is supported: invoices, receipts, payment records and wages. Dispute records prove what was agreed and what was built: instructions, variations, dated photographs, diary entries and inspection documents. A well-run job file produces both from the same daily habits, filed against the job address.
Sources
- Record keeping for business · Australian Taxation Office
- Voluntary administration · ASIC
- Passive design · Your Home (Australian Government)
- Resolving building disputes · NSW Government
Published 1 September 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
