A manual compliance register vs a system of record.
Word registers, paper forms and SharePoint folder trees run more Australian sites than any software does. They are familiar and free. This is an honest look at where they hold up and where they quietly fail.
| What matters | Manual registers and folders | claused. |
|---|---|---|
| Cost | Effectively zero. Word, paper forms and SharePoint are already there. | One price per project with every user included. Founding sites are onboarded by invitation during early access. |
| Familiarity | Everyone knows a folder. No training, no rollout, no logins. | A short learning curve, then records file themselves where they belong. |
| Findability | Depends on the naming convention and the memory of whoever filed it. | Filter by condition, record type, date or status and get the records, not the file names. |
| Evidence linkage | Photos in one folder, forms in another, lab results in email. Linked by folklore. | Photos, results and sign-offs live on the record, and the record links to its conditions. |
| Trigger discipline | Post-rain inspections rely on someone remembering the clock is running. | Rainfall-triggered ESC inspections are raised automatically and tracked to closure. |
| Corrective actions | A note in a Word register that no one is chased on. Closure is optional in practice. | Actions have an assignee, a due date and a status, and stay visible until verified closed. |
| Handover | A folder tree only its creator understands, explained in a one-hour walkthrough if you are lucky. | A structured workspace any new team member can read from day one. |
| Audit velocity | Days or weeks to gather, print and cross-reference scattered documents. | Per-condition audit packs generated on demand from tagged records. |
A folder system is only as good as its weakest filing day.
The manual system deserves respect before it gets critiqued. A Word register, a drawer of signed paper forms and a carefully tended SharePoint tree have carried thousands of projects through audits. They cost nothing, need no rollout, and everyone from the graduate to the superintendent understands a folder. When one diligent person maintains them, they can look immaculate.
The trouble is that records go in, but the relationships between them, this photo proves that inspection, which discharges that condition, exist only in someone's head. The system does not fail loudly. It fails two years later, in an audit room, when a specific chain of evidence has to be produced and nobody can find the middle link.
Findability: the folder tree wins until it loses
Every folder system starts tidy. Then the project gets busy, a second person starts filing, and the convention bends. Is the March discharge monitoring in 04_Monitoring, in 07_Water, or attached to an email with the subject FW: FW: results? The person who knows is on another job now. Searching a folder tree finds file names. It cannot find meaning.
In claused. you do not search for a file, you ask for the records: every ESC inspection on the eastern catchment since May, every open corrective action, everything tagged to one condition. The answer is a filtered list, not an archaeology dig.
Evidence that is linked, not just stored
Storage was never the problem. SharePoint stores everything. Linkage is the problem. An auditor does not ask whether you have photos. They ask which photos prove that this inspection, on this date, satisfied this condition. In a folder world that chain is reassembled by hand, every time.
In claused. the chain is the data model. Photos and results attach to the record at capture, the record carries its signature and timestamp, and the record is tagged to the conditions it evidences. That is what makes a condition evidence pack something you generate, not something you build over a lost weekend.
Trigger discipline cannot live in a folder
A register records what happened. It has no opinion about what should happen next. Rainfall-triggered ESC inspections are the sharpest example. The obligation arrives with the weather, the completion window is short, and a folder cannot tell you the clock has started. The same applies to corrective actions that need chasing and permits that must not be approved before their tests pass.
claused. raises the inspection when the trigger is met and keeps the action open until it is closed. The guide to ESC inspections after rainfall in NSW shows how quickly that window closes on a busy site.
Handover and the speed of an audit
Two moments expose a manual system: the day its owner leaves, and the day an audit is announced. Handover of a folder tree is an oral tradition, and whatever is not explained is effectively lost. Audit preparation becomes a multi-week scavenger hunt across folders, inboxes and camera rolls, done by the most senior environmental person on the project, which is the most expensive possible use of their time.
A system of record changes both moments. The structure is the same for every user, records are captured once in the field app and filed automatically, and the audit pack for any condition takes minutes, not weeks.
When manual registers are enough.
A short project with a small set of conditions, one environmental contact, no rainfall triggers and a stable team can run on a disciplined Word register and a tidy folder. If audits are rare and the record set is small enough to hold in one head, the manual system's zero cost is a real advantage. The complete guide to compliance tracking covers what that register has to hold.
Move to a system of record when the project is long enough for staff to change, when conditions number in the dozens or hundreds, or when an EPL and triggered inspections raise the price of a missing link. Folders do not scale with obligations. The plans are priced per project so the crew is never the cost.
Three questions teams ask before they switch.
What is a system of record for environmental compliance?
One place where every condition of an approval sits beside the field records that discharge it, with each record dated, attributed and signed. The register is the source the audit pack is generated from, not a summary typed up from folders after the fact.
Do we lose the paper forms and folders we already have?
No. Existing documents can be uploaded and filed against the conditions they evidence, and an existing register can be imported by CSV so the numbering and status carry across. The folder tree stays where it is as an archive.
How long does it take to set up?
Upload the approval, licence or plan and claused. reads it into a register of conditions, held for review before anything is published to the crew. During early access founding sites are set up with us: the approval read in, the gauge linked, the first forms live and the crew invited.
The guides and pages behind this comparison.
- 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.
- The complete guide to compliance tracking for constructionGuides · 12 min read. How to set up and maintain a compliance tracking system for Australian construction and infrastructure projects.
- 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.
Run one honest drill.
Pick a condition from the current approval and time how long it takes to assemble every piece of evidence against it. Then request early access, open the live demo and run the same drill there. The difference is the argument.