Most document packs are finished the day they are handed over. This one was not — and that is the whole point. What it takes to turn a folder of mismatched documents into a controlled system, and to keep it true after the review is passed. No deadline forced it; they chose to do it before anyone made them.
This did not start with a rejection, a portal deadline or a mobilisation date. No client had sent anything back. They simply knew what needed doing, and knew they had neither the capability in-house nor the hours to do it.
Worth saying plainly, because most work of this kind starts in a panic. This one started with a decision — and it is a materially cheaper way to arrive at the same place.
They were not starting from nothing, either. They had procedures, forms and registers already. Real ones, written by people who knew the work.
But those had been written at different times, by different people, for different reasons. Different styles. Different fonts. Different layouts. No shared numbering. Nothing recording which version was current or when anything was last looked at. And in among them, gaps — documents that should have existed and simply did not.
Each document, taken on its own, was defensible. Taken together, they were not a system. And a document review does not assess documents one at a time.
Every document was rebuilt into a single structure and issued as a first controlled release. One numbering pattern across twelve categories. One document-control table on page one of everything. One revision history. One master register listing every document with its version, its issue date and the date it next falls due.
Where a document existed and was sound, it was kept and brought into the scheme rather than replaced for the sake of it. The goal was a system they recognised as theirs, not a new pack with their logo on it. Where a document was missing, it was written.
Five gaps mattered. The first one explains the other four.
| Missing document | Why it mattered |
|---|---|
| Master document register | There was no list of the documents. Nothing recorded what existed, what version it was at, who owned it, or when it was next due for review. The set could not be audited because nobody could state what the set was. |
| Mental health & psychosocial hazards | Managing psychosocial risk is now an explicit duty under Australian WHS regulation. Document sets assembled before that change routinely have nothing covering it, and reviewers have started asking. |
| Environmental management system | The E in HSE. Present in how the business described itself, absent as a controlled document. |
| Return to work policy | What happens after someone is hurt. Reviewers look for it because it evidences the obligations that continue long after the incident report is closed. |
| Subcontractor management | How the contractor controls the people it brings onto someone else’s site. On a client-controlled site, this is one of the first things a principal asks to see. |
None of the gaps were in the daily hazard work. That was well covered — it is what the crew does every day and what supervisors already think about.
The gaps were in the obligations around the work: the register that indexes it, the newer duties, the non-safety limb, what happens after an incident, and responsibility for other people’s crews.
Teams document the work in front of them. Reviewers ask about everything else.
A legislation and standards currency review was run the month after the first release. It resulted in 26 of the 47 documents being revised and reissued.
More than half the system changed within weeks of being delivered. Not because the first release was wrong, but because compliant is a statement about a date, and legislation, standards and client requirements do not hold still.
A template pack is finished when it is handed over. It looks compliant on the day and quietly stops being true from the day after — and nobody notices until a reviewer does.
A controlled system carries a review date on every document, a register that shows what is due, and someone who actually runs the review. That is the only reason audit-ready means anything twelve months on.
| Release | What happened | Scope |
|---|---|---|
| First issue | Initial controlled release — 47 documents into one numbering scheme and register | All 47 |
| Currency review | Legislation and standards currency review; documents updated and reissued | 26 revised |
| Capability added | New specialist welding procedure plus five associated record forms; one existing procedure revised | 6 added |
The client took on a specialist welding process that was not part of the original scope. In a folder of loose documents that means a new file appearing with no number, no owner and no relationship to anything else — the exact drift that made the original set unreviewable.
Here it went in as a numbered procedure in the existing category, with five associated record forms numbered against it, added to the master register, and a related procedure revised where the two overlapped.
The procedure took the next sequential number in its category — not a new prefix, not a standalone file.
Five forms — joint logs, a machine pre-start check and a task-specific SWMS — numbered as associated forms of the parent procedure.
An existing procedure that touched the same work was revised at the same time, so the two do not contradict each other.
The master register moved up a version, recording what was added, what was revised, and who signed it off.
Send one register that shows every document, its version, its issue date and its next review date. Answer “is this current?” without opening a single file. Add a capability without the system drifting. And show a reviewer a revision history that proves the system is maintained rather than merely written.
That last point is the one that carries weight. Reviewers use revision history to test whether a management system is live. A document at version 1.0 with no history is indistinguishable from a template bought last week. A document at version 1.1, revised at a documented currency review, is evidence of a system somebody is actually running.
This case file is published with the client’s identity, personnel, contact details and document prefix removed. Document counts and revision scope are accurate and taken from the delivered master register. No client data, site data or commercial terms are reproduced.
If your documents were written at different times by different people, a reviewer will see that before they see the content. Tell us what you have and what has been asked for, and we will come back with a fixed scope, a price and a delivery date.
Get my document suite quote →Check if your docs would pass →Site-Ready pack delivered in 10 business days · Revised free for 90 days from delivery, until they pass review · T&Cs apply
Send us what you are working with. We will tell you what holds up, what does not, and what a fixed-price rebuild looks like — usually within two business days.
Fixed price · No obligation · Scope confirmed within 2 business days