claused. vs Excel and spreadsheets
Most environmental registers in Australian construction start life as a spreadsheet. This page is an honest look at where Excel genuinely holds up, where it falls apart, and when it is time to move on.
Let's start with the truth: Excel is a great tool. It is free with the Office licence your company already pays for, everyone on site knows how to use it, and it will bend into whatever shape your project needs. If you have ever built an ESC inspection register with conditional formatting and a dropdown of condition numbers, you know exactly how far a determined environmental advisor can push a spreadsheet.
The problem is not that spreadsheets are bad. The problem is that environmental compliance on a construction site is not a spreadsheet shaped problem. It is a field problem, a timing problem and an evidence problem, and Excel was never designed for any of those three.
| Dimension | Excel / spreadsheets | claused. |
|---|---|---|
| Cost | Free with Office, which almost every contractor already has. | Free during early access while the product is built with the first sites. |
| 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 auto-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. |
The evidence never makes it into the spreadsheet
A spreadsheet lives at a desk. Compliance happens in the mud. That gap is where most registers quietly fail. The site engineer takes photos of the sediment fence on their phone, sends two of them to the WhatsApp group, and intends 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 the moment of capture. There is no transcription step, so there is nothing to lose between the site walk and the register. If you want to see what that evidence looks like when an auditor asks for it, read our guide to building a condition evidence pack for audits.
Excel cannot watch the weather
Many NSW approvals require ESC inspections 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 maths and remembering the clock, on top of everything else the role demands. Miss one event during a wet fortnight and there is a permanent hole in the record that no amount of tidy formatting can fill.
In claused., rainfall-triggered inspections are raised automatically and sit in the schedule until they are done. The trigger, the due window and the completed inspection are all part of the same record. Our 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 actually asks is per condition. Show me everything for condition B12. In a spreadsheet, answering 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 auto-tagged to the conditions it evidences, so the per-condition audit pack is generated rather than assembled. Weeks of audit prep become an export.
The single-owner problem
Every great compliance spreadsheet has an author, and that is its biggest weakness. The macros, the colour codes, the tab structure, they all live in one person's head. When that person goes on leave, changes projects or resigns, the register stalls or forks into competing copies. Version chaos follows: parallel files 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, on their phone or laptop, and the field app means the newest team member captures records the same way the most experienced one does.
The fairest test is to see both side by side. Open the live demo with your current spreadsheet next to it and walk through one real inspection, one corrective action and one condition. If the spreadsheet still feels faster, keep it. We think you will find the opposite.
See it on a real site
Early access is free while we build claused. with the first sites on board. Or open the live demo workspace right now, no sign up needed.