claused. vs manual registers and folders
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.
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 a folder system is only as good as its weakest filing day. 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 needs to be produced and nobody can find the middle link.
| Dimension | Manual registers / folders | claused. |
|---|---|---|
| Cost | Effectively zero. Word, paper forms and SharePoint are already there. | Free during early access while the product is built with the first sites. |
| 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. | Search and filter by condition, record type, date, location or status. |
| 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 owners, due dates and status, and stay visible until 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. |
Findability: the folder tree always 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 auto-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. Our 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 prep becomes a multi-week scavenger hunt across folders, inboxes and phone 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 is minutes, not weeks.
If you are weighing it up, run one honest drill: pick a condition from your current approval and time how long it takes to assemble every piece of evidence against it. Then open the live demo and run the same drill there. The difference is the argument.
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.