WHS Management Plan Template for Construction Projects

A WHS Management Plan is a project-level document that describes the systems, procedures, and arrangements the principal contractor will put in place to manage safety across the project. It is not a substitute for individual SWMS, and it does not contain the trade-specific hazard and control detail that belongs in a SWMS. Instead, the plan sets out the framework within which the SWMS are collected, reviewed, monitored, and updated, and the broader arrangements for consultation, induction, incident management, and emergency response.

The legal basis for the WHS Management Plan is WHS Regulation 2025 section 309A in the model jurisdictions. The regulation requires the principal contractor to prepare a plan for any construction project where the contract price is $250,000 or more, and to maintain the plan so that it remains current throughout the life of the project. The $250,000 threshold includes GST and applies to the total contract price, not the principal contractor's margin. For staged or multi-package projects, the threshold applies to the aggregate value of the construction work under the principal contractor's control.

The plan must be prepared before construction work commences on site, which in practice means before the first subcontractor arrives for mobilisation. A principal contractor who starts work before the plan is in place has breached the regulation regardless of whether the subsequent work is performed safely. The plan must be available to any person at the workplace who requests it, which means it is not an internal management document but a site-accessible reference that workers, subcontractors, HSRs, and inspectors can consult.

Victoria operates under OHS Regulation 2017 Part 5.1, which establishes an equivalent construction safety coordination plan requirement for projects involving construction work over $350,000 or involving high-risk work. The Victorian provisions use employer rather than PCBU terminology and reference WorkSafe Victoria Compliance Codes. The substantive requirements are aligned with the model jurisdictions, but the dollar threshold and the precise content requirements differ, and a contractor operating in Victoria should work from the OHS Regulation text directly rather than assuming the model provisions apply.

The principal contractor is the PCBU who has been engaged by the client to have overall management and control of the construction workplace. On most projects this is the head builder or civil contractor, but on some projects the client themselves may hold the principal contractor duty. The duty cannot be delegated — whoever holds it is accountable for the WHS Management Plan, and any subcontractor is obliged to cooperate with the plan under the general cooperation duty in WHS Act section 46.

WHS Regulation 2025 section 309A prescribes specific content elements that must be addressed in a WHS Management Plan. These are the minimum requirements, and a mature plan typically covers additional content to address project-specific circumstances and principal contractor internal standards. The mandatory elements are set out in sub-regulations (2) and (3) and include the following.

Names, positions, and health and safety responsibilities of all persons at the workplace whose roles involve specific health and safety responsibilities. This includes the principal contractor's project manager, site supervisor, WHS manager or coordinator, first aid officers, emergency wardens, and any designated permit authorities. The plan should identify each person by name (updated as personnel change), by position, and by the specific WHS duties they hold on the project. Vague statements such as the WHS Manager will ensure compliance do not satisfy the requirement; the plan must be specific enough that an inspector can identify who is accountable for each area.

Arrangements for consultation, cooperation, and coordination between the principal contractor and all persons involved in the construction work. This covers toolbox talks, safety committee meetings, pre-start briefings, and the processes for workers to raise safety concerns. The plan should describe the frequency of these activities, who attends, how issues are recorded, and how they are followed up. On multi-subcontractor projects, the plan should also describe how the principal contractor coordinates activities between subcontractors to avoid conflicts that would create new hazards.

Arrangements for managing incidents, including investigation, notification, and record-keeping. The plan should describe who investigates incidents, how notifiable incidents are escalated to the regulator under WHS Act section 38, how investigations are conducted, and where records are kept. Incident management arrangements should align with the jurisdiction's notifiable incident requirements and the principal contractor's internal incident management process.

Any site-specific health and safety rules and the arrangements for communicating them to all persons at the workplace. Common elements include PPE requirements, speed limits for site vehicles, exclusion zones around plant and excavations, hot work restrictions, permit-to-work requirements, alcohol and drug policies, and mobile phone policies. The communication arrangements typically include a site induction program that covers the rules at entry and toolbox talks that reinforce them during the project.

Arrangements for the collection, assessment, monitoring, and review of SWMS for the HRCW carried out on the project. This is the element that links the WHS Management Plan directly to the SWMS system and is the most frequently audited part of the plan. The plan must describe how SWMS will be obtained from subcontractors, who reviews them, the criteria for acceptance, how compliance is monitored on site, the triggers for review, and the arrangements for retention.

Arrangements for ensuring compliance with Part 6.4 of the WHS Regulation, which covers general construction induction training (white cards) and high-risk work licences. The plan must describe how the principal contractor verifies that workers hold the current CPCCWHS1001 white card (the older CPCCOHS1001A unit is superseded and should not be accepted on current projects) and any required high-risk work licences such as RIIWHS204E, TLILIC0005, and the relevant load-shifting unit.

Arrangements for the storage, movement, and disposal of construction materials and waste at the workplace. This includes hazardous materials management, asbestos controls if applicable, fuel and chemical storage, and waste streams. Since the national engineered stone ban took effect on 1 July 2024, the plan must not include engineered stone as a selectable material for benchtops, panels, or slabs.

The SWMS section of the WHS Management Plan is the operational interface between the principal contractor and the subcontractors. Every subcontractor performing HRCW on the project will submit a SWMS, and the plan describes how those documents are handled from submission through to retention. A well-drafted SWMS section eliminates ambiguity about what the principal contractor expects and makes enforcement straightforward when subcontractors fall short.

Collection arrangements specify how and when SWMS are submitted. A typical clause reads: All subcontractors performing high-risk construction work on this project must submit their SWMS to the site WHS Manager at least 48 hours before commencing HRCW. SWMS may be submitted digitally through the project SWMS platform or in hard copy. Late submissions will result in work being stood down until the submission is reviewed and accepted. The 48-hour lead time gives the WHS team time to review the document before work starts and prevents last-minute submissions that force either a rushed review or a stand-down.

Review and acceptance arrangements specify who reviews the SWMS and the criteria applied. A typical clause reads: The Site WHS Manager will review each submitted SWMS within 24 hours of receipt. Reviews assess the document against the minimum requirements in this plan and against WHS Regulation 2025 section 299. SWMS that do not meet the minimum requirements will be returned to the subcontractor with specific feedback and a revised submission deadline. HRCW may not commence until the SWMS is accepted. The review service level protects the principal contractor from accusations of slow review holding up the project and gives the subcontractor certainty about when feedback will be available.

Minimum content requirements specify what a SWMS must contain to be accepted. The requirements should reference WHS Regulation 2025 section 299 and enumerate the elements the principal contractor expects to see. A typical list includes identification of the HRCW categories under Schedule 1, site-specific hazard identification (not generic boilerplate), a risk assessment using a defined matrix with inherent and residual ratings, control measures arranged in hierarchy order, named responsibility for each control, implementation and monitoring arrangements, review triggers, training and licensing requirements, PPE requirements with Australian Standard references, plant and equipment lists, emergency procedures, consultation records, and worker sign-on.

Monitoring arrangements describe how compliance with the accepted SWMS is verified during the work. A typical clause reads: Site supervisors will verify at each pre-start meeting that all workers performing HRCW have signed on to the current version of the relevant SWMS. The Site WHS Manager will conduct random site inspections at least twice per week and document observations against the SWMS controls. Deviations from the SWMS will trigger immediate stop-work and the SWMS will be reviewed before work resumes. Active monitoring is the difference between a SWMS that exists as paper and a SWMS that operates as a control.

Review triggers describe when a SWMS must be revised. Triggers include any change to the HRCW, identification of a new hazard, discovery that a control is inadequate, the occurrence of an incident or near-miss, a request from an HSR, a change in site conditions, and a scheduled periodic review. The periodic review interval on most projects is 28 or 30 days, with earlier reviews triggered by the event-based items. The trigger list should be explicit in the plan so subcontractors understand their ongoing obligations.

Retention and record-keeping arrangements describe how SWMS and sign-on records are preserved. A typical clause reads: All SWMS, amendment logs, and sign-on records will be retained on the project SWMS platform for the duration of the project and for a minimum of 7 years after project completion. SWMS relating to notifiable incidents will be retained permanently. Retention responsibility rests with the principal contractor, and the platform provides permanent access regardless of subscription status. The retention clause closes the loop on the SWMS lifecycle and meets the regulatory obligations under Regulation 299 and section 36.

Confusion between the WHS Management Plan and the SWMS is common on construction projects and produces documentation that is either too broad (SWMS that repeat the WHS Management Plan content) or too narrow (WHS Management Plans that omit project-wide arrangements and treat each activity as a separate SWMS). The distinction is straightforward once the purpose of each document is clear.

The WHS Management Plan is a project-level document prepared by the principal contractor. It covers the entire project from mobilisation to demobilisation, across all trades, all subcontractors, and all activities. It describes systems and arrangements — the WHO does WHAT and HOW in a procedural sense — and is not concerned with the specific hazards and controls for individual activities. The plan is required for projects where the contract price is $250,000 or more and a principal contractor has been appointed.

A SWMS is a task-level document prepared by the subcontractor or PCBU performing the HRCW. It covers a specific HRCW activity — installation of the mechanical services in Building C, erection of scaffold for the facade work, demolition of the existing concrete slab — and describes the specific hazards, controls, and work method for that activity. The SWMS is required for any HRCW regardless of project value, so it applies on small residential jobs as well as large commercial projects.

The two documents can exist independently in principle. A sole trader roofer working on a $30,000 residential re-roof is performing HRCW (work at height above 2 metres) and must prepare a SWMS, but the project is below the $250,000 threshold and has no appointed principal contractor, so no WHS Management Plan is required. Conversely, a large construction project with no HRCW — a rare case, but possible for some fit-out or finishes scopes — would require a WHS Management Plan under the dollar threshold but not individual SWMS, since the HRCW trigger is not met.

On typical commercial construction projects, both documents exist and operate together. The WHS Management Plan describes the overall safety framework, and the SWMS from each subcontractor fit into the framework through the submission, review, and monitoring arrangements set out in the plan. A principal contractor who drafts a thorough WHS Management Plan and then accepts poor-quality subcontractor SWMS has defeated the purpose of the plan. A principal contractor who demands high-quality SWMS but has no coherent plan for collecting, reviewing, and monitoring them has no framework within which the SWMS actually operate.

The most common failure mode on Australian construction sites is that the WHS Management Plan is prepared as a template document for tender purposes, accepted by the client, filed, and then ignored. The actual operational safety management runs through ad-hoc processes that do not match the plan. When an inspector or Federal Safety Officer compares the plan to the actual site practice, the gaps are visible immediately and generate non-conformance findings. The fix is to treat the plan as a living document that describes how safety is actually managed, and to update it as the project evolves.

The following outline sets out the structure of a comprehensive WHS Management Plan and should be adapted to the specific project, site, and principal contractor. The plan should be written in clear language and should be no longer than is necessary to address the regulatory content requirements — a plan that runs to 80 pages is typically less effective than one that runs to 30 pages, because the longer document is less likely to be read or followed.

Section 1 — Project Details. Project name, address, client, principal contractor details including ABN and licence numbers, project duration, estimated value, construction type (commercial, civil, residential, infrastructure), and scope summary. This section establishes the context and identifies the project to which the plan applies.

Section 2 — Key Personnel and Responsibilities. Project manager, site supervisor, WHS manager or coordinator, first aid officers, emergency wardens, permit authorities, and any specialist roles (confined space entry supervisor, fire warden, rescue team). Include names, phone numbers, and a specific description of the WHS duties each person holds. Update as personnel change and maintain the current version in the plan.

Section 3 — Consultation Arrangements. Toolbox talk schedule (weekly is typical), safety committee structure if any, pre-start meeting process, HSR election arrangements if applicable, and the process by which workers raise safety concerns and receive responses. Describe how issues are escalated and how the response loop is closed.

Section 4 — SWMS Management. Collection arrangements with the 48-hour lead time, review and acceptance process with the 24-hour service level, minimum content requirements referencing WHS Regulation 2025 section 299, monitoring arrangements describing daily pre-start checks and weekly site inspections, review triggers for amendments, and retention arrangements. This section is the operational core of the plan and deserves the most attention.

Section 5 — Site Safety Rules. PPE requirements, site speed limits, exclusion zones around plant and excavations, hot work restrictions and permit requirements, confined space entry procedures, electrical isolation and LOTO, roof access rules, alcohol and drug policy, mobile phone policy, smoking restrictions, and any project-specific rules such as traffic management plans or environmental controls.

Section 6 — Incident Management. Incident reporting process, investigation methodology, notifiable incident procedures under WHS Act section 38, first aid arrangements including kit locations and trained first aiders, emergency evacuation plan with muster points, fire safety arrangements, and rescue plans for specific activities (confined space, working at heights, trenching).

Section 7 — Induction and Licensing. White card verification process (confirming CPCCWHS1001 current unit, not the superseded CPCCOHS1001A), HRCW licence checks, site-specific induction content and delivery method, visitor management procedures, and the arrangements for inducting new subcontractors and workers who arrive after the initial project mobilisation.

Section 8 — Materials, Plant and Waste. Hazardous materials register with SDS availability, asbestos management plan if applicable, fuel and chemical storage, waste management plan including disposal routes for construction waste, plant pre-use inspection requirements, and the arrangements for mobile plant operation and coordination. The engineered stone ban must be reflected — engineered stone is not permitted as a material on any project.

Section 9 — Training and Competency. General induction requirements, HRCW licensing, trade-specific training (working at heights, confined space, rigging, dogging, crane operation), refresher training intervals, and the arrangements for recording and verifying training records.

Section 10 — Review and Revision. The schedule for reviewing the WHS Management Plan itself (typically every 6 months, or sooner after a significant incident or major scope change), the process for issuing new versions, the distribution list, and the version control arrangements.

Several failure patterns recur in WHS Management Plans across Australian construction projects, and avoiding them is the difference between a plan that passes audit and one that generates non-conformance findings. The most common failure is the template plan: the principal contractor uses a generic template downloaded from the internet or copied from a previous project, changes the project name and address, and files it without adapting the content to the specific site. Template plans are visible to any experienced auditor within minutes — the personnel names do not match the actual team, the rules reference site features that do not exist, and the arrangements are described in language that no one on site recognises.

The fix for the template failure is to write the plan for the actual project. Start with the template structure, but fill in the content based on the actual team, the actual site conditions, and the actual arrangements the principal contractor intends to operate. If the arrangements are not yet decided at the time of plan preparation, defer those sections and update them as the project mobilises, but do not fill them with placeholder content that will remain in the plan throughout the project.

The second common failure is the static plan: the plan is prepared before the project starts and never updated, even as personnel change, conditions evolve, and incidents occur. An inspector reviewing the plan six months into the project sees contact details for people who left the business three months ago, references to controls that were superseded, and a review date that has already passed. The plan has become evidence of inattention rather than a control.

The fix for the static plan failure is to treat the plan as a living document and update it systematically. Personnel changes should trigger an immediate update to Section 2. Incidents should trigger a review of the relevant sections (typically 4, 5, and 6). Periodic reviews should happen on the schedule described in Section 10. The updated version should be distributed to all persons covered by the plan and the old version should be archived with a date of supersession.

The third common failure is the vague SWMS section: the plan describes the SWMS arrangements in general terms without specific service levels, minimum requirements, or enforcement mechanisms. When a subcontractor submits a deficient SWMS, the WHS team has no documented standard to point to, and the subcontractor can argue that their document meets the plan because the plan doesn't specify otherwise. The review process becomes a negotiation rather than an enforcement of standards.

The fix for the vague SWMS section is to write it with specific, measurable requirements. The 48-hour submission lead time, the 24-hour review service level, the enumerated minimum content requirements, the monitoring schedule, and the retention period should all be stated in specific terms. A SWMS that does not meet the specific requirements can be returned with specific feedback, and the subcontractor has a clear path to remediation rather than an open-ended debate about adequacy.

The fourth common failure is the absent retention arrangement: the plan describes how SWMS are collected and reviewed but says nothing about how they are retained after the project completes. When a regulator or investigator asks for a SWMS from two years ago, the principal contractor cannot produce it because the paper documents were discarded at project close and no digital archive was maintained. The retention gap is a direct breach of WHS Regulation 299 and the general duty to maintain safety records. The fix is to specify permanent retention on a digital platform that preserves records after the project ends and the subscription terminates.

Principal contractors operating on federally-funded projects under the Australian Government Building and Construction WHS Accreditation Scheme are subject to additional requirements imposed by the Office of the Federal Safety Commissioner. The OFSC Scheme Criteria include specific content and process expectations for the WHS Management Plan that exceed the baseline regulatory requirements, and non-compliance with the criteria can result in non-conformance findings that affect accreditation status.

The OFSC criteria expect the WHS Management Plan to demonstrate a working system rather than simply a documentation of intent. The plan should describe auditable processes for each of the required elements, with evidence that the processes are actually operating on site. During an OFSC audit, the Federal Safety Officer reviews the plan, samples the associated records (SWMS register, sign-on records, incident reports, toolbox talk minutes, site inspection logs), and cross-checks them against the observed site practice. Gaps between the plan and the reality generate non-conformance findings.

The SWMS section is one of the most heavily audited parts of the plan. The FSO expects to see a documented submission process, a defined review standard, active monitoring, triggered amendments, and auditable retention. The expectation on OFSC-accredited projects is higher than the minimum regulatory standard, because the principal contractor has chosen to operate in a scheme that requires continuous demonstration of system effectiveness. A plan that meets Regulation 309A but falls short of the OFSC criteria can still generate findings that affect accreditation.

Consultation arrangements are another frequently audited area. The FSO checks the toolbox talk records, the pre-start briefing logs, the HSR election arrangements if any, and the process for workers to raise safety concerns. A plan that describes weekly toolbox talks but produces records showing sporadic or missing briefings is evidence of a gap between the plan and the practice. The fix is either to bring the practice up to the plan's description or to revise the plan to match what is actually happening on site — but not both at once, since revising the plan to describe a weaker standard is itself a non-conformance in a scheme that expects continuous improvement.

Notifiable incident management is audited both in the plan and through the actual incident records. The FSO checks whether the plan describes the notification process accurately, whether notifiable incidents that have occurred on the project were actually notified to the regulator within the required timeframe, whether investigations were conducted and documented, and whether corrective actions were implemented and verified. A plan that describes a good process but an incident record that shows the process was not followed is a serious finding and can result in conditional accreditation or suspension.

Retention and record-keeping are audited at the conclusion of projects and at accreditation renewal. The FSO may request records from prior projects to verify that the principal contractor is maintaining the audit trail across the accreditation period. A principal contractor who cannot produce records from a project that completed 18 months earlier is in breach of the retention obligations and may see accreditation conditions imposed at renewal. The practical answer is permanent digital retention on a platform that preserves records regardless of subscription status, which closes the retention gap without adding physical storage burden.