“The auditor opened the JSEA for the high-pressure flush and asked which MSMS section the controls came from. The supervisor pointed at the template and said ‘the contractor’s standard.’ The auditor closed the folder and wrote it up. The contract was extended by another 90 days — conditional on us fixing the system.”
— Perth drilling services supplier, post Tier 1 audit
MSMS-Aligned JSEAs and SWMS: What Perth Mining Suppliers Get Wrong
The single test every Tier 1 auditor will run
Pick a task that one of your crews is doing today. Ask for the JSEA. Now ask: which MSMS hazard control does each step trace back to? Who is the statutory holder accountable for that control? Are all sign-ons by workers currently competent for each control? When was the JSEA last reviewed, by whom, and what triggered the review?
If the answer is a folder of PDFs and a few binders, you have a finding waiting to happen. If the answer is a single screen with the JSEA, the MSMS reference, the statutory holder, the sign-on register, the competency check, and the review history visible at once — you pass.
Why generic templates fail
- Hazards listed are generic to the trade, not specific to the site or operator
- Controls listed are at a different level in the hierarchy than the operator's MSMS expects
- Statutory holder reference (SSE, ERM, etc) is missing entirely
- Sign-on register is on paper and not linked to current competency records
- Version control is “the latest one in the office cabinet”
- Review history is a date scribbled on the cover page, no trigger, no reviewer
None of this is a problem with the supervisor or the worker. It is a system problem. A folder of PDFs cannot enforce MSMS alignment, link to competency, or carry a review trigger. A structured procedure pack can.
What MSMS alignment looks like in practice
Every step traces to a hazard and a control
Each task step in the JSEA names the hazards it introduces and the controls applied. Controls reference the operator's MSMS section so the auditor can see the lineage immediately.
Statutory holder is named on every control
High-risk controls reference the statutory position accountable for them — SSE for site-wide controls, ERM (Electrical Risk Manager) for electrical isolation, etc. The auditor sees responsibility, not just a name on a cover page.
Sign-on checks competency at the moment of work
Worker scans the JSEA on the phone, signs on, and the system checks competency for each listed control. If the high-voltage isolation card has expired, the sign-on is blocked and the alternate is offered.
Reviews are triggered, not scheduled
When a control fails, an incident is reported, the equipment changes, or the operator updates the MSMS section, the affected JSEAs and SWMS are flagged for review with a clear trigger reason and a review owner.
Version control is the system, not the binder
Every JSEA, SWMS, and SOP carries a version number. The phone always shows the current version. Old versions are retained for audit but cannot be signed-on against in the field.
The DrilLedger Procedure Pack approach
The Procedure Pack agent generates JSEAs, SWMS, and SOPs from a structured task definition. You describe the task once — hazards, controls, MSMS section, statutory holder, required competencies. The agent produces the JSEA, the SWMS (where the work meets the high-risk-construction-work definition), and the SOP, all consistent with each other and traceable to the operator's MSMS. Workers sign on through the Training & Competency Matrix, which checks currency at sign-on. Reviews fire automatically when a trigger event occurs.
The result: when the Tier 1 auditor opens a JSEA, every control traces to an MSMS section, every statutory holder is named, every sign-on is competency-checked, and the review history is a clean log instead of a date on a cover page.
What this is worth
Audit response time
2 days of folder hunting and binder building per audit — eliminated. 4 audits/year = 8 days saved.
Avoided contract conditions and re-audits
Tier 1 audit findings frequently come with conditional contract extensions and a 90-day re-audit. Each cycle is days of management time and a real risk to the contract.
Statutory holder coverage
Every high-risk control names the accountable statutory holder — no more dispute about who owns what.
Real-time competency assurance
Sign-on blocked if a worker is not competent for a control. Risk goes down, supervisor cognitive load goes down.
Total: 8+ days of audit prep saved per year, materially reduced contract risk, and a system the SSE will trust.
Frequently asked questions
What is the difference between a JSEA, a SWMS, and a procedure?
A JSEA (Job Safety and Environment Analysis) breaks a task into steps and identifies the hazards, environmental risks, and controls for each step. A SWMS (Safe Work Method Statement) is the high-risk-construction-work cousin required under the WHS Regs for specific high-risk work types and is contractually mandated by every Tier 1 client for work like working at heights, confined spaces, hot work, and energised electrical. A procedure (SOP) describes the safe and correct way to perform a task in detail. In practice, a Perth supplier needs all three working together — the procedure is the long-form how-to, the JSEA/SWMS is the pre-task hazard analysis, and both must trace back to the controls in the MSMS.
What does MSMS alignment actually mean?
The Mine Safety Management System (MSMS) is the operator's system describing how they manage risk on the mine site. Under WHS (Mines) Regs 2022, every contractor on the site must operate within the MSMS — your JSEAs, SWMS, procedures, and training records have to be consistent with the operator's controls, hierarchy of risk, and reporting standards. Alignment means: when a Tier 1 auditor opens your JSEA for a task, the listed controls match the operator's MSMS controls; the controls reference the relevant statutory holder (SSE, ERM, etc.) where required; and the workers signed-on are competent for that task per the operator's training matrix. A generic JSEA pulled off a contractor template is the fastest way to fail this test.
Why do Tier 1 audits keep finding the same gaps?
The most common audit findings on Perth mining suppliers are: (1) JSEAs are generic and do not reference the specific site or task hazards, (2) controls listed do not match the operator's MSMS hierarchy, (3) SWMS for high-risk work has not been reviewed since the last contract change, (4) workers signed-on for the task do not have current competency for the listed controls, and (5) there is no version control — the JSEA in the field doesn't match the JSEA on the office system. Every one of these is fixable when JSEAs, training records, and the MSMS reference are in one structured system instead of a folder of PDFs.
How often do JSEAs and SWMS need to be reviewed?
There is no single statutory frequency — the WHS Regs require review when the work changes, when a control fails, after an incident, when new equipment or workers are introduced, or at intervals defined in the operator's MSMS. In practice, Tier 1 clients expect a documented review cycle (often quarterly for high-risk SWMS, annually for standard JSEAs) plus event-triggered reviews. The procedure system needs to track the last review date, the trigger, the reviewer, and the next due date for every document.
How does DrilLedger help suppliers stay MSMS-aligned?
The Procedure Pack agent generates JSEAs, SWMS, and SOPs from a structured task definition, references the operator's MSMS section and statutory holder, and pulls competency requirements from the Training & Competency Matrix. Workers sign-on through the same flow that checks competency. Every document carries a version, a review date, and a chain back to the hazards and controls it addresses. When a Tier 1 auditor asks “show me the JSEA for this task and prove the controls match your MSMS”, the answer is one click instead of a folder hunt.