The environmental compliance register: Excel vs software.
Most environmental registers in Australian construction start life as a spreadsheet. This is an honest look at where Excel holds up, where it falls apart, and when it is time to move on.
| What matters | Excel and spreadsheets | claused. |
|---|---|---|
| Cost | Free with Office, which almost every contractor already has. | One price per project with every user included. Founding sites are onboarded by invitation during early access. |
| Field capture | None. Photos live on phones and in WhatsApp threads, typed up later at a desk. | Inspections, observations and incidents captured on site, photos attached to the record at the moment it happens. |
| Rainfall triggers | Someone has to watch the gauge and remember the 24-hour clock themselves. | Rainfall-triggered ESC inspections are raised automatically when the trigger is met. |
| Condition linkage | A condition number typed in a cell, if anyone remembers to type it. | Every record is tagged to the approval conditions it evidences, across EPL, consent and CEMP. |
| Version control | Register_FINAL_v7_JT.xlsx. Parallel copies drift and nobody is sure which one is current. | One shared workspace. Everyone sees the same live register. |
| Signatures and timestamps | A typed initial and a date cell anyone can edit after the fact. | Records carry who did what and when, and permits are gated on the checks actually passing. |
| Audit prep | Days to weeks assembling photos, emails and rows into something an auditor can follow. | Per-condition audit packs generated from the records you already captured. |
| Key-person risk | The register lives in one person's head and one person's file. Leave, and it stalls. | A system of record the whole team works in, so nothing depends on one owner. |
Compliance is not a spreadsheet-shaped problem.
Excel is a good tool. It is free with the Office licence the company already pays for, everyone on site knows how to use it, and it bends into whatever shape the project needs. Anyone who has built an ESC inspection register with conditional formatting and a dropdown of condition numbers knows how far a determined environmental advisor can push a spreadsheet.
The problem is not that spreadsheets are bad. Environmental compliance on a construction site is a field problem, a timing problem and an evidence problem, and Excel was designed for none of the three.
The evidence never makes it into the spreadsheet
A spreadsheet lives at a desk. Compliance happens in the mud. The site engineer photographs the sediment fence on a phone, sends two shots to the WhatsApp group and means to file the rest later. The inspection row gets typed up on Thursday from memory. By audit time the photos are three phone upgrades away and the row says completed, no issues, with nothing behind it.
claused. is built the other way around. The record is created in the field, at the fence, with the photos attached at capture. There is no transcription step, so there is nothing to lose between the site walk and the register. The guide to the condition evidence pack shows what that evidence looks like when an auditor asks for it.
Excel cannot watch the weather
Many NSW approvals require an ESC inspection within a set window after a rainfall trigger. A spreadsheet has no idea it rained. The trigger discipline lives entirely in one person's habit of checking the gauge, doing the sum and remembering the clock, on top of everything else the role demands. Miss one event in a wet fortnight and there is a permanent hole in the record that no amount of tidy formatting can fill.
In claused. the site gauge feeds the register. Rainfall past the trigger raises the inspection with a deadline, and the trigger, the due window and the completed inspection are one record. The walkthrough of ESC inspections after rainfall in NSW covers how those windows work in practice.
Rows do not connect to conditions
An approval is not one obligation, it is hundreds: EPL conditions, consent conditions, CEMP commitments. The question an auditor or regulator asks is per condition. Show me everything for condition B12. In a spreadsheet that means filtering, cross-referencing folder paths and hoping the condition column was filled in consistently for three years.
In claused. every inspection, observation, corrective action and permit is tagged to the conditions it evidences at capture, so the per-condition audit pack is generated rather than assembled. Weeks of audit preparation become an export.
The single-owner problem
Every good compliance spreadsheet has an author, and that is its biggest weakness. The macros, the colour codes and the tab structure live in one person's head. When that person goes on leave, changes projects or resigns, the register stalls or forks into competing copies on email, on SharePoint and on a desktop, each slightly different, none obviously current.
A system of record removes that fragility. Everyone works in the same live workspace, and the field app means the newest team member captures records the same way the most experienced one does.
When Excel is enough.
A small site with a handful of conditions, one person responsible for compliance, no rainfall-triggered obligations and a low audit risk can run on a well-kept spreadsheet. Plenty of subdivisions and small commercial jobs are managed this way without drama, and the free conditions of consent register template is built for exactly that case.
The tipping point comes when conditions run into the dozens, more than one person touches the register, or an EPL and rainfall triggers enter the picture. That is when the hidden cost of Excel, the transcription time, the audit scrambles and the key-person risk, outweighs the fact that it is free. Plans for that point are on the pricing page.
Three questions teams ask before they switch.
Is an Excel register acceptable to a regulator or an auditor?
Yes. No NSW or Commonwealth instrument prescribes software. What an auditor checks is whether each condition has evidence behind it, dated and attributable. A spreadsheet can hold that for a small site. It struggles once the evidence lives on phones and in inboxes rather than in the register.
Can we keep a spreadsheet alongside claused.?
Yes. The register exports to a spreadsheet at any time and audit packs export to PDF, so a client report or a monthly return can still be a spreadsheet. The field work and the evidence live in claused. and the export is generated from them.
What does moving off the spreadsheet involve?
Upload the approval, licence or plan and claused. reads it into a register of conditions, held for review before anything is published. An existing spreadsheet register can be imported by CSV so the condition numbering and status carry across.
The guides and pages behind this comparison.
- Conditions of consent register template (Excel)Guides · 6 min read. A free Excel register for consent, EPL, EPBC and CEMP conditions, with twelve worked NSW example rows. What a register must hold, and an honest note on when a spreadsheet is enough.
- The condition evidence pack: what auditors actually ask forGuides · 7 min read. Environmental audits come down to one question per condition: show me the evidence. What a per-condition pack looks like and why spreadsheets fail it.
- PricingOne price per project with every user included, and what a project team pays for the alternatives.
- The field appInspections, observations, incidents and permits captured offline on site and filed against the condition they evidence.
See both side by side.
Request early access and we will set the project up with you. Open the live demo with your current spreadsheet beside it and walk through one inspection, one corrective action and one condition. If the spreadsheet still feels faster, keep it.