AI SWMS generators are marketed as a fast, low-cost route to a compliant Safe Work Method Statement for construction work. In a few minutes of form-filling, a small fixed fee, and a finished document. For a sole trader facing an early site start with no SWMS, the appeal is obvious. The concern is what sits behind the document and if it is likely to be compliant under regulator scrutiny. Safetysure examined a currently promoted platform that sends a single activity label to a large language model and returns a generic hazard list, with an absence of knowledge of the actual site, the proposed scope of works, the workers involved, or the specific high-risk construction work triggers that apply. That is not what the law requires, and the same structural limitation is likely to apply to any generator built on the same single-input pattern.
This article draws on a direct examination of how one such platform operates, together with the requirements of the work health and safety regulatory framework.
What the law actually requires for a compliant SWMS
A Safe Work Method Statement is a statutory instrument under the Work Health and Safety Regulations in each harmonised jurisdiction. Regulation 291 of the WHS Regulation 2011 (Qld), and its equivalents in New South Wales, the Commonwealth, and other adopting jurisdictions, defines high-risk construction work (HRCW) across 18 specific categories: work involving a risk of falling more than two metres, work in or near a confined space, demolition of a load-bearing element, work involving asbestos, work on or near energised electrical installations or services, and 13 others.
A SWMS is not a paperwork formality in that Regulation 299 requires the SWMS to be prepared before high-risk construction work commences, to identify the specific HRCW involved, to state the hazards and associated risks, to describe the control measures, and to be prepared taking into account all relevant matters including “circumstances at the workplace that may affect the way in which the high risk construction work is carried out.” That last clause is the site-specificity obligation. Sections 47 to 49 of the WHS Act 2011 (Qld) impose a separate duty to consult workers on matters affecting their health and safety. Regulation 300 requires the person conducting the business or undertaking (PCBU) to put in place arrangements for ensuring work is carried out in accordance with the SWMS. Regulation 302 requires the SWMS to be reviewed and revised whenever the relevant control measures are revised under reg 38.
A document generated from a single activity label, without any worker input and without reference to the actual site or scope of works, does not meet those requirements. It simply reproduces the form of a SWMS without the substance that really matters.
How these platforms work
The platform Safetysure examined in depth follows a straightforward pattern, and generators built on the same single-input model are likely to work in a similar way.
The user selects a work activity from a pre-built menu, enters basic details such as business name, supervisor name, site address and emergency contact, and clicks generate. The platform sends the activity label to a large language model. The response is a risk table listing hazards and control measures for that activity category. That content is inserted into a document template, combined with the form data, and rendered as a PDF.
The model has received, in effect, a single word: “carpentry,” or “electrical,” or “demolition.” It has no information about the actual site conditions, the specific task sequence, the experience level of the workers, the existing plant and equipment, the proximity of other trades, or the environmental conditions. The output is a generic hazard list for a generic version of that activity. It has the appearance of a SWMS. Measured against the site-specificity requirement in reg 299(3)(a)(i), it is not a compliant one.
On the platform examined, other document types offered richer input fields, while the SWMS generator itself accepted minimal input. The regulatory requirement is not minimal.
Five things that can go wrong
1. The AI-generated SWMS may not cover the applicable high-risk work triggers
A generator that categorises SWMS types by trade (carpentry, plumbing, electrical) rather than by the statutory HRCW triggers in reg 291 can produce a document that misses a trigger the job actually involves. A plumber selecting “plumbing” may receive a well-formatted document covering general plumbing activities. What that document may not contain is a confined space framework, even if the specific job involves entering a confined space. Confined space entry is a distinct HRCW trigger under reg 291(f), with its own obligations under AS/NZS 2865:2009: atmospheric testing protocols, entry permits, standby person requirements, and emergency rescue procedures. None of those elements will appear in a generic plumbing SWMS.
A further example illustrates the architecture problem. A generator that lists “silica” or “silica dust” as a selectable category, alongside the genuine high-risk construction work triggers, invites a related error. Silica dust is not a high-risk construction work trigger under reg 291. It is governed by a separate regime in Chapter 8A of the WHS Regulation 2011 (Qld), introduced in 2024. Under reg 529CB, a person carrying out high-risk processing of a crystalline silica substance must prepare a silica risk control plan before the processing starts. That plan has its own mandatory content: it must identify the high-risk processing, include the written assessment required under reg 529CA, and state how the control measures will be implemented, monitored and reviewed.
There is one point of intersection, and it matters. Under reg 529CB(3), the separate silica risk control plan is not required if the silica processing is also high-risk construction work, a SWMS has been prepared, and that SWMS satisfies the silica risk control plan content requirements. In other words, a sufficiently detailed SWMS can do double duty. A generic “silica” SWMS generated from a one-word label does not. It will not contain the written reg 529CA assessment, it will not address the specific crystalline silica substance being processed, and it will not satisfy the reg 529CB(2) content requirements. A business that generates such a document and treats its respirable crystalline silica obligations as discharged would be mistaken, because the obligations remain unmet.
Safety consequence A worker who enters a confined space under a plumbing SWMS that does not address confined space entry has no atmospheric testing protocol, no entry permit, no standby person, and no emergency rescue procedure. Those are not documentation gaps; they are the controls that prevent a confined space entry from becoming a fatality.
2. The consultation and site-specificity requirements are not satisfied
Regulation 299(3)(a)(i) requires the SWMS to be prepared taking into account “circumstances at the workplace that may affect the way in which the high risk construction work is carried out.” Sections 47 to 49 of the WHS Act impose a consultation duty: s 49 requires consultation when identifying hazards, when assessing risks, and when making decisions on the measures to control those risks, which are the activities a SWMS records. The Model Code of Practice: Construction Work states that a SWMS should be prepared in consultation with the workers who will carry out the work. An AI-generated document prepared by one person ahead of the job, with no worker input, satisfies neither requirement.
The consultation obligation is not procedural box-ticking. Workers who carry out high-risk tasks know things that no algorithm can access: which anchor points on this roof are compromised, why the concrete in this pour behaves differently from the plans, what happened the last time someone worked in that pit. A SWMS that emerges from genuine pre-task consultation with the workers doing the job is substantively different from one generated in isolation. It is also more likely to be followed, because the workers who will use it helped shape it.
When a regulator investigates a serious incident and examines the SWMS, the question is not whether a document exists. It is whether the document reflects a genuine risk assessment for that specific work on that specific site. A generic AI-generated SWMS cannot answer that question satisfactorily.
3. The controls may not reflect the hierarchy or the actual hazard profile
A SWMS for roofing work generated from the activity label “roofing” will list control measures appropriate to a generic roofing scenario: edge protection, fall arrest systems, safe access. These are appropriate in general. Whether they are appropriate for this roof, with these anchor points, for this task sequence, is a question the algorithm has not been asked and cannot answer.
The order of controls also matters. Under the WHS framework, a risk must first be eliminated so far as is reasonably practicable (reg 35). Where elimination is not reasonably practicable, reg 36 sets the order of minimisation: substitution, isolation and engineering controls first, then administrative controls, then personal protective equipment as the last resort. A risk table generated to look comprehensive may list PPE alongside engineering controls without distinguishing their order of priority. A SWMS that treats PPE as a co-equal control for a fall risk, rather than a measure of last resort, does not reflect the regulatory framework, even where it satisfies every formatting expectation.
There is also the problem of unknown unknowns. A demolition SWMS that does not mention asbestos, because the user selected “demolition” rather than “asbestos,” has a potentially fatal gap. The algorithm does not know the building was constructed in 1975. It does not know the wall being demolished contains bonded asbestos cement sheeting. Nobody asked.
4. The document is not the safety system
Regulation 300 of the WHS Regulation 2011 (Qld) requires the PCBU to put in place arrangements for ensuring work is carried out in accordance with the SWMS. A document that workers have never seen, never been briefed on, and had no part in preparing is unlikely to influence how work is actually done on site.
The gap between the paper safety system and actual site practice is one of the most consistent findings in serious incident investigations. The Mastermyne/Crinum matter is a recent illustration from an adjacent sector. In March 2026 Mastermyne Crinum Operations Pty Ltd, the company that employed and managed the underground production workforce at the Crinum mine, was convicted of industrial manslaughter under Queensland’s mining safety legislation, the first such conviction in the State’s mining sector since those laws commenced in 2020. On 1 May 2026 the company was fined $7 million, with a conviction recorded, and it has lodged an appeal against the penalty. Safetysure’s analysis of the publicly available material identifies inadequate strata control, a failure to act on precursor events, gaps in management information flow, and episodic rather than ongoing expert engagement as contributing factors, with documented procedure and actual practice not aligned. The sentencing judge described the death of Graham Dawson as avoidable.
The context is mining, not construction, and the case has nothing to do with SWMS or AI. The mechanism it illustrates, documented compliance that does not reflect what happens on site, is not sector-specific.
An AI-generated SWMS downloaded before the job and signed by workers who have not read it functions as liability documentation rather than a working safety system.
5. Worker signatures and personal information are a separate exposure
The first four points concern whether the document protects the people doing the work. This one concerns a different question: what happens to the information a business hands over in order to produce it.
Generating a SWMS, an incident report or a permit to work on an online platform means uploading a substantial amount of personal information. Depending on the product, that can include the business name, supervisor names, phone numbers, email addresses, site addresses, project details, site photographs, worker names, and worker signatures. That information is stored on the operator’s servers, and once it is uploaded the business has limited control over how it is held, how long it is retained, or what becomes of it if the operator is sold or ceases trading.
Worker signatures warrant particular attention. A signature is sensitive personal information, and unlike a password it cannot be reissued if it is ever compromised. It appears on employment contracts, statutory declarations, financial documents, and other legal instruments. A signature captured for a safety document and then stored indefinitely on a third-party server is a long-lived record that the worker, and often the employer, has little ability to retrieve or control.
Legal position Under the Privacy Act 1988 (Cth), Australian Privacy Principle (APP) 11 requires an entity that holds personal information to take reasonable steps to protect it from misuse, interference and loss, and from unauthorised access, modification or disclosure. Names, phone numbers, site addresses and worker signatures are all personal information. The obligation does not rest with the platform alone. A business that uploads its workers’ personal information to a third-party service takes on its own responsibility for choosing a service that handles that information appropriately, and the platform’s terms and conditions do not transfer that responsibility back. A disclaimer of liability protects the operator, not the workers whose data was uploaded, and it does not discharge the uploading business’s own privacy obligations. The practical response is due diligence before use, which is the subject of the questions set out further below.
Moral position Workers sign a SWMS as part of their job. They have not necessarily agreed to have their handwritten signature stored indefinitely on a server they know nothing about, linked to a record of every high-risk task they have been assigned. In most cases they will not know the arrangement exists. An employer who adopts one of these platforms makes that decision on its workers’ behalf. That is worth weighing on its own terms, independent of any legal obligation, and the fact that a set of terms and conditions permits it does not settle whether it is the right thing to do.
What does a compliant SWMS looks like?
A compliant SWMS reflects the actual conditions of a specific task on a specific site. It identifies which HRCW triggers apply. It applies the hierarchy of control in reg 36 to the actual hazards present, rather than to a statistical average of hazards for that activity category. It is prepared with input from the workers who will carry out the work. It is reviewed when conditions change, near misses occur, or the task scope is modified.
The pre-task conversation with workers is not procedural. It is the mechanism by which site-specific knowledge enters the document. An experienced concreter who worked on that formwork type last week knows things about its behaviour under load that no AI system knows. A plumber who sees that pit dimensions differ from the plans can adjust the confined space protocol before anyone enters. A scaffolder who finds unstable substrate can change the anchoring plan. That knowledge has to come from somewhere, and reg 299 and the WHS Act consultation duty are the mechanisms that require it to be sought.
The objection in this piece is not to artificial intelligence in safety work. It is to a single design pattern: a single activity label in, a generic document out, with no consultation and no review by a competent person. Templates, digital signing tools, document management systems, and structured hazard libraries all reduce administrative burden and improve consistency. The distinction is between technology that assists a competent person exercising genuine professional judgement and technology that replaces that judgement with a generic output.
The principal contractor’s position in accepting the SWMS
Principal contractors who accept AI-generated SWMS documents carry their own exposure. Regulation 312 of the WHS Regulation 2011 (Qld) requires the principal contractor to take all reasonable steps to obtain a copy of the SWMS before high-risk construction work commences. That is a duty to obtain the document. The principal contractor’s responsibility does not end there. Under reg 309(2)(e), the principal contractor’s WHS management plan must set out arrangements for the collection and any assessment, monitoring and review of safe work method statements at the workplace, and under the primary duty in s 19 of the WHS Act the work the principal contractor controls must be carried out safely so far as is reasonably practicable. A principal contractor whose arrangements amount to collecting whatever arrives, with no assessment, and that allows high-risk work to proceed on a SWMS that is plainly generic, is not giving effect to the assessment arrangements its own management plan is required to contain.
In practice, an AI-generated SWMS is often identifiable to an experienced reviewer: a generic hazard list with no site-specific detail, controls that list personal protective equipment ahead of engineering controls, toolbox-talk sections that read as boilerplate, and a document structurally identical to every other SWMS of that activity type submitted to the site. A principal contractor that identifies these features is entitled to reject the document and require a compliant one. The cost of producing a compliant replacement under time pressure, on the morning of the job, is higher than the cost of preparing it properly beforehand.
Questions worth asking before using any AI SWMS platform
Any business evaluating an online WHS documentation platform should ask the following before using it.
Does the platform’s output reflect the specific HRCW trigger categories under reg 291, or does it use trade categories that do not map to the regulatory framework? Does the platform require the user to document worker consultation, or does it generate a document that bypasses that step entirely? Does it identify when a task spans multiple HRCW triggers, such as demolition work that also involves confined space entry? Has the platform been independently reviewed by a qualified WHS professional? What personal information is stored on the platform’s servers, how long is it kept, and what happens to it if the operator ceases trading? What are the platform’s security certifications, and when were they last independently verified?
These questions do not require technical expertise to ask. They do require recognising that a convincing-looking PDF is not the same as a compliant SWMS, and that the gap between the two carries both legal and human consequences.
Conclusion
The convenience of AI SWMS generation is genuine and may assist with brainstorming ideas for your SWMS but the limitations are structural, and they follow from how these systems are typically built: a single activity label in, a generic hazard list out, no site context, no worker input, and no regulatory-architecture check.
The businesses most exposed are not the large contractors with WHS teams and legal counsel; they are the sole traders and small subcontractors working under time pressure, on sites where principal contractors expect documentation and regulators have enforcement powers. These businesses deserve tools that work, rather than tools that produce documents which look as though they work until something goes wrong.
Ultimately though, the workers who sign those documents deserve to know where their signatures go.
You might like to read or recent articles Paper to Practice Gaps in Work Safety or Regulating Psychosocial Safety at Work
References
Legislation: Queensland
- Work Health and Safety Act 2011 (Qld), s 19 (primary duty of care), ss 47 to 49 (duty to consult workers).legislation.qld.gov.au: WHS Act 2011 (Qld)
- Work Health and Safety Regulation 2011 (Qld), reg 35 (management of risk), reg 36 (hierarchy of control measures), reg 38 (review of control measures), reg 291 (meaning of high-risk construction work), reg 299 (SWMS required: preparation and content), reg 300 (compliance with SWMS), reg 301 (copy to principal contractor), reg 302 (review of SWMS), reg 309 (WHS management plan, including arrangements for assessment and review of SWMS), reg 312 (principal contractor to obtain SWMS), reg 529CA (identifying high-risk processing of crystalline silica), reg 529CB (silica risk control plan). legislation.qld.gov.au: WHS Regulation 2011 (Qld)
Legislation: New South Wales
- Work Health and Safety Regulation 2025 (NSW), the equivalent provisions at the same numbers (291, 299, 300, 302, 309, 312). The 2025 remake styles its provisions as “sections” but retains the model numbering.legislation.nsw.gov.au: WHS Regulation 2025 (NSW)
Legislation: Commonwealth
- Privacy Act 1988 (Cth), Australian Privacy Principle 11 (security of personal information). legislation.gov.au: Privacy Act 1988 (Cth)
Regulatory guidance
- Office of the Australian Information Commissioner, Australian Privacy Principles Guidelines, Chapter 11, APP 11: Security of Personal Information. oaic.gov.au: APP 11 guideline
- Safe Work Australia, Model Code of Practice: Construction Work (November 2024 edition).safeworkaustralia.gov.au: CoP Construction Work
Standards
- Standards Australia, AS/NZS 2865:2009 Safe working in a confined space (incorporating Amendment No. 1, October 2025). store.standards.org.au: AS/NZS 2865:2009
Case reference
- Mining and Energy Union, Justice served: Mastermyne guilty of industrial manslaughter in workplace death of miner, 30 March 2026 (guilty verdict). Mastermyne Crinum Operations Pty Ltd, District Court of Queensland at Emerald. meu.org.au: Mastermyne verdict
- Mining and Energy Union, Justice served by historic industrial manslaughter penalty, 1 May 2026 (sentencing: $7 million fine plus costs, conviction recorded). meu.org.au: Mastermyne sentencing
- An appeal against the penalty was lodged following sentencing (reported May 2026). miningmonthly.com: Mastermyne appeal
Safetysure is a national work health and safety consultancy based in South Brisbane, accredited to ISO 9001, 45001, and 14001. For guidance on SWMS preparation, high-risk construction work compliance, or occupational hygiene services, contact Safetysure at safetysure.com.au.