A contractor working on client-controlled sites asked for one controlled system in place of a folder of documents written by different people at different times. This is what the build found, what the first currency review found a month later, and why the second matters more than the first.
This did not start with a rejection, a portal deadline or a mobilisation date. The contractor knew the documents needed doing and knew they had neither the capability in-house nor the hours to do it. Most work of this kind starts in a panic. This one started with a decision, which is a cheaper way to arrive at the same place.
They were not starting from nothing. They had procedures, forms and registers, written by people who knew the work. But they had been written at different times, in different styles, with no shared numbering, no record of which version was current and no date on which anything was last looked at. In among them were gaps: documents that should have existed and did not.
Each document on its own was defensible. Together they were not a system. A reviewer opening a set like this cannot answer the three questions they are there to answer: is this current, is this complete, is this controlled. Not because the answer is no, but because the documents give no way to tell.
Every document was brought into a single structure and issued as a first controlled release on 12 July 2026: 41 documents across twelve categories, one document-control table on page one of everything, one revision history, and 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 aim was a system the contractor recognised as theirs, not a new pack with their logo on it. Where a document was missing, it was written.
| Missing document | Why it mattered |
|---|---|
| Master document register | Nothing recorded what existed, what version it was at, who owned it or when it was next due. The set could not be audited because nobody could state what the set was. |
| Mental health and psychosocial hazards | Managing psychosocial risk is an explicit duty under Australian WHS regulation. Sets assembled before that change routinely have nothing covering it, and reviewers now ask. |
| 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 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, one of the first things a principal asks to see. |
None of the gaps were in the daily hazard work. That was well covered, because it is what the crew does every day. The gaps were in the obligations around the work. Teams document the work in front of them. Reviewers ask about everything else.
On 11 August 2026, every Act, Regulation, code of practice and Australian Standard cited anywhere in the 41 documents was extracted and checked against the primary source: the NSW legislation register, SafeWork NSW, the NSW Resources Regulator and the Standards Australia catalogue. Then a second, independent pass tried to disprove each finding before anything was changed.
| What the review found | Why it mattered | Documents |
|---|---|---|
| WHS Regulation 2017 (NSW) cited as current | Repealed on 22 August 2025 and replaced by the WHS Regulation 2025. Citing a dead instrument is the first thing a prequalification reviewer notices. | 22 |
| No code of practice named anywhere | From 1 July 2026 a new section 26A of the WHS Act makes compliance with approved codes a duty, not just evidence. A generic “applicable codes” line no longer holds. | 41 |
| Industrial manslaughter not mentioned | Part 2A of the WHS Act has been in force since September 2024. Officer due diligence had to be stated in the policy and in every procedure’s responsibilities block. | 41 |
| Four standards out of date | Fall arrest, hard hats, test and tag and confined spaces were all cited at superseded editions, one of them retitled and split into new parts. | 6 |
| Welder competency cited the wrong standard | The training manual referenced a pipe product standard for PE welding competency. It says nothing about operators. Replaced with the correct competency units and installation standard. | 1 |
| Psychosocial controls behind the regulation | The 2025 Regulation removed the carve-out that kept psychosocial risk outside the hierarchy of controls. The procedure had to apply the hierarchy, not go straight to support programs. | 1 |
| Workers compensation thresholds changed | Amendments commencing 1 July 2026 changed the return to work position. The policy was updated and a second tranche diarised for October. | 2 |
Twenty-six documents were revised, reissued at version 1.1 and signed off by the Managing Director on 11 August 2026. The master register was updated to match. Fifteen documents needed no change, and the register records that too.
Most of the procedures were the contractor’s own, brought into the scheme rather than rewritten, and their citations came with them. Some were already out of date on the day of the first release. That is the point of a currency review: nothing flags a repealed regulation until someone checks. Legislation, standards and client requirements do not hold still, and a document that was right in July is not automatically right in August.
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. A controlled system carries a review date on every document, a register that shows what is due, and someone who runs the review. That is the only reason “audit-ready” means anything twelve months on.
Twenty days later, on 31 August 2026, the whole suite was re-checked. The law had not moved. But the re-check found that the August review had wrongly dropped an approved code of practice for elevating work platforms, gazetted that July. The code was added to four procedures and the August report was corrected in place, with the error struck through rather than quietly rewritten.
It also found that the procedures manual still listed 41 documents while the register listed 47, because a new welding procedure and its five forms had been added between reviews. Two controlling documents giving different answers to “what is in the system” is a document-control finding in its own right, whatever the content says. The manual was brought into line, and the rule that adding a document touches three files, not one, was written into the build method.
A review that never finds anything wrong with itself is not a review.
| Issue | Date | What happened | Scope |
|---|---|---|---|
| First issue | 12 Jul 2026 | Initial controlled release: 41 documents into one numbering scheme and one register | 41 issued |
| Currency review | 11 Aug 2026 | Every citation checked against current law and standards; documents updated and reissued at v1.1 | 26 revised |
| Capability added | 12 Aug 2026 | New polyethylene welding procedure with five record forms; Hot Works revised where the two overlapped | 6 added |
| Re-check | 31 Aug 2026 | Suite re-checked; an error in the August review corrected; manual aligned with the register; dates and versions standardised | 10 revised |
| Issue passes | Sep 2026 | Pre-issue correction pass, branded first-page header across the suite, approval blocks aligned. No control measure changed | 47 reissued |
The contractor 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 with no number, no owner and no relationship to anything else, which is exactly the drift that made the original set unreviewable. Here it went in differently.
The procedure took the next sequential number in its category. Not a new prefix, not a standalone file.
Five forms, including joint logs, a machine pre-start check and a task-specific SWMS, numbered as associated forms of the parent procedure.
An existing hot works 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. The manual followed at the next review.
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. Show a reviewer a revision history that proves the system is maintained rather than merely written.
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.4, revised at two documented currency reviews and signed off each time, 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, dates and revision scope are taken from the delivered master register and the two currency review reports. No client data, site data or commercial terms are reproduced.
If your documents were written at different times by different people, or have not been checked against the law since they were issued, a reviewer will see that before they see the content. Start with the free check, or tell us the contract and get a monthly price.
Check if your current documents would pass →Get my monthly price →Site-Ready pack in 10 business days · Revised free for 90 days from delivery · 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