Compliance Document Management: What a System Does That a Shared Drive Cannot
A compliance document management system does 5 things a shared drive cannot. It knows when a document expires and tells someone. It keeps every superseded version, so you can prove which one was in force on a given day. It controls who sees what and logs who did what. It chases renewals without a person remembering to. And it produces the right document under pressure. It will not fix a requirement nobody agreed.
Nobody buys a document system because they want better filing. They buy one after a week where a certificate turned out to have lapsed in March, the safe work method statement on the server was not the one the crew was working to, and finding either took two people most of a day.
So the useful comparison is not a feature list. It is the shared drive, the spreadsheet, and the inbox, against what a system does on the same job. Here is that comparison, and then the three problems a system will not fix, because pretending otherwise is how these purchases disappoint.
The Duty Is to Manage the Risk. The Document Is the Evidence.
Start here, because it keeps the rest honest. Section 17 of the model Work Health and Safety Act requires a duty holder to eliminate risks to health and safety so far as is reasonably practicable and, where that is not reasonably practicable, to minimise them so far as is reasonably practicable.2 Nothing in that sentence is about paperwork.
Safe Work Australia’s code of practice on managing risks puts the document in its place: keeping records of the risk management process demonstrates what you have done to comply with the Act and the Regulations, lets you show how decisions about controlling risks were made, and demonstrates to regulators, investors, and customers that risks are being managed.1
That is the whole argument for a system, and its limit. The document is proof of the managing. A better filing cabinet does not make a workplace safer; it makes the proof retrievable, current, and attributable, which matters enormously on the day somebody asks for it.
The Shared Drive, the Spreadsheet, and the Inbox.
Almost every business doing this manually is running all three at once, and each one fails differently.
- The shared drive holds the file and knows nothing about it. It has no idea the certificate inside expired, no idea which of four similarly named files is current, and access is granted per folder, so anyone who can see one document can see all of them.
- The spreadsheet holds the dates but not the documents. It is only as current as the last person who updated it, it has no audit trail, and when two people edit it there are quietly two versions of the truth.
- The inbox holds the evidence that a document was requested and the chase that followed, in one person’s mailbox, unsearchable by anyone else, and gone when they leave.
Each of the next five sections is one thing that combination cannot do.
Expiry, Because a Folder Cannot Tell You a Certificate Lapsed.
A folder is passive. It waits to be opened. Every requirement with a date on it - insurance, a licence, a high risk work ticket, a plant inspection, a health monitoring review - fails silently between the day it expires and the day someone happens to look.
A system inverts that. The expiry date is captured when the document is approved rather than guessed at later: the reviewer checks the date the contractor entered, corrects it if it is wrong, or marks the category as having no expiry.7 From there the question “what expires in the next 30 days” is a filter, not an afternoon, and the same report shows what has been rejected, what has expired, and what is still awaiting upload.6
The behaviour that matters is the exception. A dashboard of totals tells you most documents are current, which nobody can act on. A useful one tells you which are not, and who is responsible for each.
Version, Because the Question Gets Asked After the Incident.
“Which safe work method statement was in force on the day” is not a filing question. It is asked by an inspector, an insurer, or a lawyer, months later, and a folder answers it badly because the file was overwritten.
The model WHS Regulations require a safe work method statement to be kept until the high risk construction work it relates to is completed, and for at least 2 years after a notifiable incident occurs in connection with that work. For the whole of that period a copy must be readily accessible to any worker engaged to carry out the work, and available for inspection.4 Safe Work Australia’s construction code adds the line that decides the argument: where a statement is revised, every version should be kept.5
The same shape applies well beyond construction. Records of tests, inspections, maintenance, commissioning, decommissioning, dismantling, and alterations of registered plant must be kept for the whole period the plant is used or until you relinquish control of it.4 That is a document with a decade of history in it, not a file that gets replaced.
Access, and the Trail of Who Did What.
Compliance documents are not all equally open, and folder-level permissions are too blunt an instrument for that.
Some documents must be pushed at people. The current safety data sheet for a hazardous chemical has to be readily accessible to any worker using, handling, or storing it and to an emergency service worker likely to be exposed. The asbestos register has to be readily accessible to workers, to health and safety representatives, and to any business that carries out or intends to carry out work at the workplace, with a copy given to anyone whose work risks exposure to airborne asbestos.4
Others must be held tightly. Health monitoring reports are confidential records that may not be disclosed without the worker’s written consent,4 and under Australian Privacy Principle 11.2 personal information you no longer need, and are not required by law to keep, must be destroyed or de-identified.8
Then there is the alteration rule. Fair Work records must be legible, in English, readily accessible to an inspector, and not changed except to correct an error.3 A spreadsheet cannot evidence that. A system that records who uploaded, who approved, who rejected and why, and keeps rejected documents in the history rather than deleting them,7 can.
Who Chases the Renewal Is the Real Cost.
Here is the part buyers underestimate. The expensive work in compliance documents is not storing them. It is asking a subcontractor for the sixth time for a current certificate of currency, and knowing which of 140 suppliers is up to which stage of that conversation.
Done manually, that lives in one coordinator’s head and their sent items. Done by a system, the request, the reminder, the upload, the review, and the rejection comment all sit against the document itself, where the next person can pick it up.7 That is the difference between a process and a person, and it is why workforce compliance work survives a resignation.
Retrieval Under Pressure Is the Only Real Test.
Every claim about a document system can be reduced to one question. Something has happened. A person who is not at a desk needs a specific document now. How long does it take.
Safe Work Australia is unusually practical about this. If a safe work method statement is not kept at the workplace, it should be stored where it can be delivered to the workplace quickly, and it can be kept electronically.5 The code on managing risks adds that everyone in the workplace should know which records are accessible and where they are kept.1
Apply that test to your current arrangement honestly. A document behind a corporate login, on a server, reachable only from the office network, fails it. So does a lever-arch folder in a site office nobody has a key to at 6am. Our post on site documents management works through what availability at the point of use actually requires.
What a System Does Not Fix.
Three things, and each one has sunk a rollout I have watched.
A requirement nobody agreed. Software will faithfully chase a document that no one ever decided was needed, and will not chase one everybody assumed was covered. The requirement set has to be a decision first: which document categories apply to which contractor type at which site. In ComplyFlow those requirements are assigned per site precisely because a working with children check or a high risk work licence may be required at one facility and not at another.9 Get that wrong and you have automated the wrong list.
A document nobody reads. A current, correctly versioned safe work method statement that a crew has never opened is a controlled document and an uncontrolled risk. The code of practice asks for workers to understand the hazards and implement the controls, which happens in a toolbox talk or an induction, not in a repository.5
A supplier who will not supply. No system produces an insurance certificate that does not exist. What it does is make the gap visible and dated, so the commercial decision about whether that supplier works this week is made by a person with the facts, rather than discovered afterwards. That is an operations decision, and it is the one place where making the problem undeniable is the whole contribution.
How to Tell Whether You Have Outgrown the Drive.
Four questions, answered honestly about this week rather than about a good week.
Can you name what expires in the next 30 days without anyone running a report. Can you produce the version of a document that was in force on a nominated date last year. Can one person see a document that another person must not. Can a supervisor at a gate open it on a phone.
If any of those is a no, the gap is not filing discipline, and more folders will not close it. Site documents and prequalification are the two places most businesses feel it first. If you want the underlying obligations rather than the tooling, what employee records you must keep and for how long sets out the periods, and none of them is the one you would guess.
Sources
- How to manage work health and safety risks: Code of Practice
- Model Work Health and Safety Bill
- Record-keeping
- Model Work Health and Safety Regulations
- Construction Work: Code of Practice
- Reporting on all documents in the system
- Approving or Transferring Documents
- Read the Australian Privacy Principles
- Compliance Requirements, Training Requirements and Site Contact
Written by
Mitchell BourneManaging Director, ComplyFlow
Mitch has run ComplyFlow since 2009 and has spent that time inside the contractor, site, and safety problems of Australian operators. He writes about where compliance actually fails, and what the people responsible for it can do about it.
Writes about: Contractor compliance, WHS duty and proof, Running a compliance program
Questions
Questions People Ask About This.
What is a compliance document management system?
A system that holds the documents a business is required to keep, with the requirement, the expiry date, the version history, and the access rules attached to each one. The difference from general document storage is that it knows what each document is for and when it stops being valid, so it can raise an exception rather than waiting to be asked.
Why is a shared drive not enough for compliance documents?
A folder stores a file. It does not know that the certificate inside it lapsed last Tuesday, it overwrites the previous version rather than keeping it, and it gives everyone with access to the folder access to everything in it. Those three gaps are exactly where compliance failures come from, and none of them is fixed by better folder names.
How long do I have to keep a safe work method statement?
Under the model WHS Regulations, until the high risk construction work it relates to is completed. If a notifiable incident occurs in connection with that work, the statement must be kept for at least 2 years after the incident. For the whole of that period a copy has to be readily accessible to any worker engaged to do the work and available for inspection.
Does a document management system make my business compliant?
No. The duty under Australian WHS law is to eliminate risk so far as is reasonably practicable and otherwise to minimise it. A document is evidence that you did that. A system makes the evidence retrievable, current, and attributable, which is worth a great deal when a regulator asks, but the work of managing the risk still has to happen.
What should I look for when comparing document systems?
Whether it can tell you what expires in the next 30 days without anyone running a report, whether it keeps superseded versions with the date each one was replaced, whether access can be set per document rather than per folder, and whether a person standing at a site gate can retrieve a document on a phone. If it cannot do those four, it is storage.
Keep Reading
More on Contractor Compliance.
See it against your own contractors, sites, and rules.
Book a 30-minute demo. We will show ComplyFlow working with your kind of sites, your kind of contractors, and your requirements. No slides, no hard sell.
- ISO 27001
- Hosted on AWS
- Microsoft & Okta SSO
- API & MCP
- Data in Australia
Compliance you can prove, instantly.