SOP Template — Standard Operating Procedures for Trades

A SOP describes the correct procedure for performing a routine task in a way that produces a consistent outcome. The word standard in the name is load-bearing: the SOP sets the standard way of doing the task, so that variation between workers is minimised and the outcome is predictable. Variation in procedure is the enemy of both safety and quality, and SOPs exist to reduce variation where the task is routine enough to warrant a written procedure.

SOPs are used in almost every regulated industry in Australia. Manufacturing operations use SOPs for production line procedures. Healthcare providers use SOPs for clinical procedures. Food processing facilities use SOPs for hygiene and quality control. Mining operations use SOPs for plant operation, maintenance, and emergency response. Construction trades use SOPs for workshop equipment operation, quality assurance, and routine maintenance activities. The common thread is that the task is repeated frequently enough to benefit from a written procedure, and the consequences of variation are significant enough to justify the effort of documenting the procedure.

Typical trade SOPs cover activities such as how to operate a table saw safely, how to perform a pressure test on a newly installed plumbing system, how to mix and apply an epoxy flooring system, how to calibrate a laser level, how to perform daily pre-start maintenance on an excavator, and how to conduct a quality inspection on a completed installation. Each of these tasks has a correct method, a set of required tools and PPE, a pre-task check routine, and an emergency response if something goes wrong. Capturing this in a SOP means new workers can be trained consistently, experienced workers can refer back when performing an infrequent task, and the business has evidence of the procedure if a regulator or insurer asks.

The legal basis for SOPs is the primary duty of care under WHS Act 2011 section 19, which requires the PCBU to provide information, instruction, training, and supervision as necessary to ensure the health and safety of workers. SOPs are a primary mechanism for discharging the instruction and training components of this duty. A PCBU who directs a worker to operate a piece of equipment without providing adequate procedural guidance has failed the duty, and the absence of a SOP is evidence of that failure. Unlike SWMS, however, there is no specific regulation that prescribes the content or format of an SOP, so the PCBU has discretion about how to document the procedure.

The single most common confusion in trade safety documentation is treating a SOP as if it were a SWMS, or believing that a detailed SOP satisfies the SWMS obligation. It does not. A SWMS is a specific document type mandated by WHS Regulation 2025 section 299 for high-risk construction work, and no amount of SOP detail substitutes for a SWMS when HRCW is involved. The distinction is worth understanding clearly because it determines which document the contractor needs to prepare and what the regulator will accept in an audit.

A SWMS is required when the work falls into one of the 18 categories of high-risk construction work listed in Schedule 1 of WHS Regulation 2025. These categories include work where a person could fall more than 2 metres, work in excavations deeper than 1.5 metres, work on or near energised electrical installations, demolition of load-bearing structural elements, work involving asbestos disturbance, confined space entry, tilt-up and precast concrete work, work near powered mobile plant, work near pressurised gas or fuel lines, work in areas with flammable atmospheres, and the remaining Schedule 1 categories. If the work fits any of these, a SWMS is legally required before the work commences. No SOP, no matter how detailed, satisfies this requirement.

A SOP is not legally required in the same way. The obligation to document routine procedures arises from the general duty of care under section 19 of the WHS Act rather than from a specific regulation mandating SOPs. The PCBU has discretion about how to discharge the duty, and a well-run training system with demonstrable induction records can sometimes meet the obligation without formal SOPs. However, most mature trade businesses maintain SOPs because they provide a reliable, auditable basis for training and a reference point for workers performing less frequent tasks.

The site specificity is also different. A SWMS must be prepared taking into account the circumstances at the workplace where the HRCW will be carried out, including site-specific hazards, adjacent work, and environmental conditions. A SOP is generally written for a task rather than a site and applies wherever the task is performed. An SOP for operating an elevating work platform describes the controls, the pre-use inspection, and the safe operating envelope; it does not describe the specific overhead powerlines at a specific site. That site-specific content belongs in the SWMS.

The practical rule is that SOPs and SWMS work together on HRCW activities. The SOP describes how to operate the equipment or perform the routine task; the SWMS describes how that task will be performed safely on the specific site, taking into account site conditions that the SOP cannot anticipate. A worker who has been trained on the SOP for EWP operation arrives on site already competent; the SWMS adds the site-specific controls — proximity to overhead powerlines, exclusion zones for plant-pedestrian interaction, wind thresholds for the specific boom configuration — that the SOP does not cover.

The decision of which document to prepare is driven by whether the work involves HRCW and whether the task is routine enough to benefit from standardisation. The matrix is simple: HRCW always requires a SWMS, regardless of whether a SOP also exists; routine tasks benefit from a SOP whether or not they involve HRCW. Many tasks require both documents, with each addressing a different aspect of the work.

HRCW that is also a routine task in the business is the clearest case for both documents. An electrical contractor who installs switchboards frequently can write a SOP covering the standard installation procedure — circuit testing, isolation verification, busbar torquing, commissioning checks — and a site-specific SWMS for each job that identifies the particular installation and the specific hazards it presents. The SOP saves time because the contractor is not rewriting the installation procedure for every job; the SWMS satisfies the regulatory requirement to identify site-specific hazards and controls for the HRCW.

HRCW that is a one-off task on a specific site is a case for a SWMS without a SOP. A demolition contractor performing an unusual structural alteration on a heritage building is not going to write a SOP for a task they will never perform again. The SWMS covers the method, the hazards, and the controls for the one-off task, and the procedural detail lives inside the SWMS rather than in a separate SOP. This is acceptable regulatory practice because the SWMS content requirements of section 299 can absorb the procedural content.

Routine work that does not involve HRCW is a case for a SOP without a SWMS. A plumbing contractor who performs routine residential maintenance — tap replacements, drain clearing, hot water service servicing — is not triggering the HRCW categories in most cases. A SOP that standardises the procedure for each task type provides the training basis and the quality control, and no SWMS is required because the HRCW threshold is not met. The contractor still has a general duty of care, and the SOP is the evidence that the duty is being discharged.

One-off low-risk tasks generally require neither document. A contractor who is asked to perform an unusual non-HRCW task is expected to apply general trade competence and reasonable care, not to generate safety paperwork for every variation. The proportionality rule in WHS law is that documentation scales with risk, and low-risk one-off tasks do not trigger the formal documentation obligations. Judgment is required, and a contractor who is uncertain whether HRCW applies should check the Schedule 1 categories rather than assume.

An effective SOP is short, clear, and actionable. A good SOP is rarely longer than three pages, because workers will not read a longer document, and anything that is not read is not a training aid. The template below sets out the structure of a well-written SOP and should be adapted to the specific task being documented.

Header section: the SOP title, a unique document number (SOP-001, SOP-002 and so on), the version number, the date of issue, the author, and the name of the person who approved the document. Numbering matters because SWMS and other documents will reference SOPs by number (must be trained on SOP-007 before operating the cherry picker) and a reliable numbering system makes cross-references traceable.

Purpose: a single sentence describing what the SOP covers. Keep it tight — this SOP describes the safe operating procedure for the Makita 2712 table saw in the workshop at 14 Industrial Drive, Dandenong. Vague or broad purpose statements make the SOP harder to apply.

Scope: the tasks and equipment covered by the SOP, and anything related that is explicitly not covered. A SOP for workshop table saw operation should state that it does not cover portable circular saws or site-based table saw work, so workers do not misapply the procedure.

Responsibilities: who must follow the SOP (all workers using the equipment), who is responsible for training (the supervisor or the nominated competent person), and who reviews and updates the document (the WHS manager or business owner). Named responsibility makes the SOP enforceable — if a worker is not following the procedure, there is a clear accountability chain for re-training.

Required PPE: specific PPE for the task, listed individually. Safety glasses, hearing protection to AS/NZS 1270 Class 5, dust mask to AS/NZS 1716, close-fitting clothing with no loose sleeves, steel-cap boots to AS/NZS 2210.3. Do not list PPE that is not relevant to the specific task — generic PPE lists dilute the specific requirements and make the document harder to follow.

Pre-task checks: what must be verified before starting. Equipment inspection with reference to the manufacturer's pre-use checklist, guard function test, blade condition check, dust extraction confirmed connected, work area clear of obstructions, emergency stop tested. Pre-task checks are often the difference between a safe workflow and an incident, and they deserve explicit documentation.

Step-by-step procedure: numbered steps written in clear imperative language. Turn on dust extraction system. Inspect blade guard and confirm it moves freely and returns to the closed position. Adjust fence to required dimension. Turn on saw and allow blade to reach full speed before cutting. Feed material steadily using a push stick for any cut within 150 millimetres of the blade. Each step should be a single action, and the sequence should match the actual workflow.

Emergency procedures: what to do if something goes wrong. Equipment malfunction, worker injury, fire, or electrical fault. Location of the first aid kit, the fire extinguisher, and the emergency stop. Phone numbers for emergency services and the site supervisor. These details should be specific to the workshop or location rather than generic.

References: Australian Standards that apply to the task or equipment (AS/NZS 4024.3611 for woodworking machinery, for example), manufacturer's manuals, related SOPs, and any relevant Codes of Practice. References make the SOP traceable to authoritative sources and support training and audit.

Review schedule: the date the SOP will next be reviewed, typically annually at a minimum, and the triggers for an earlier review. Common triggers include any incident involving the equipment or task, equipment modification, supplier change, regulatory change, or worker feedback. The review schedule should be visible in the document header so that workers can see when the current version was issued and when it will expire.

On managed construction sites, SOPs and SWMS are designed to work together. The SOP provides the baseline procedure for the task, and the SWMS adds the site-specific safety overlay. Neither document replaces the other, and a well-structured safety system uses both. Understanding how they link helps contractors produce SWMS that are both shorter (because procedural detail lives in the SOP) and more site-specific (because the SWMS can concentrate on the hazards unique to the site).

A SWMS that references relevant SOPs is typically shorter than one that tries to embed all the procedural detail inline. The SWMS can state that workers operating the excavator must be trained on SOP-012 (Excavator Operation) and must have a current high-risk work licence, without reproducing the full SOP content. This reduces the length of the SWMS, keeps the site-specific content visible, and creates a clear link to the training system. An auditor who wants to check the procedural detail can pull up the referenced SOP; the SWMS itself stays focused on the site context.

The link also supports worker induction. A new worker arriving on a site is inducted on the SWMS for the HRCW they will perform, and the SWMS references the SOPs they must have been trained on before commencing work. The induction record captures both the SWMS acknowledgement and the SOP training, giving the supervisor a complete picture of whether the worker is ready to proceed. A worker who has signed on to the SWMS but has not been trained on a referenced SOP is not yet ready, and the supervisor can intervene before the work commences.

On multi-site operations, the SOP library becomes a central training resource that the SWMS for each site draws from. The business maintains a single set of SOPs for the equipment and routine tasks it performs, and every site-specific SWMS references the relevant entries from that library. When the SOP is updated — for example, when a new piece of equipment is introduced or a regulatory change affects the procedure — the change flows through to every SWMS that references the SOP without requiring each SWMS to be rewritten individually.

The inverse is also true. When a SWMS review identifies a gap — a missing pre-task check, an inadequate control for a specific hazard, a step that was performed incorrectly — the finding should flow back to the SOP library so that the procedure is updated for future use. A mature safety system treats SOPs and SWMS as a feedback loop where findings from site-specific SWMS reviews improve the baseline SOPs, and improvements to the baseline SOPs flow back out to every site using the referenced procedures.

A mature trade business operates with a layered safety document system that uses different document types for different purposes. SOPs form the foundation layer, SWMS form the site-specific high-risk layer, JSAs (Job Safety Analyses) or JHAs (Job Hazard Analyses) cover non-HRCW task-based assessments, permits to work authorise specific activities on managed sites, and the WHS Management Plan coordinates the whole system at the project level. Each layer has a distinct purpose and together they provide comprehensive coverage.

SOPs are the training backbone. Every piece of equipment in the workshop and on site, and every routine task that benefits from standardisation, should have a SOP. New workers are trained on the relevant SOPs during induction, experienced workers refer to the SOPs when performing unfamiliar tasks, and the business maintains the library as a living resource. Annual review, post-incident review, and review on equipment change keep the SOPs current.

SWMS are the site-specific high-risk layer. Every job that involves any of the 18 HRCW categories under WHS Regulation 2025 Schedule 1 gets a SWMS. The SWMS identifies the specific HRCW categories that apply, the site-specific hazards, the control measures, and the implementation arrangements. It references the relevant SOPs for baseline procedural content and concentrates on the site-specific safety overlay. Workers sign on to the SWMS before commencing HRCW, and the SWMS is amended as site conditions change.

JSAs or JHAs cover non-HRCW task-based risk assessments. Manual handling assessments, general construction activities, and workshop tasks that do not trigger HRCW can be documented with a JSA. Some principal contractors require a JSA for every task regardless of HRCW status; others require them only for higher-risk non-HRCW activities. JSAs are not legally mandated in the same way as SWMS, but they are widely used as evidence of risk assessment for non-HRCW work.

Permits to work are the operational authorisation layer for specific high-risk activities on managed sites. Hot work, confined space entry, excavation, electrical isolation, and roof access all commonly require permits in addition to the underlying SWMS. The permit authorises the specific activity on the specific day; the SWMS describes the method and the controls for the full duration of the work. Both documents are needed on most managed sites.

The WHS Management Plan sits above all of these on construction projects above $250,000. It describes how the principal contractor will manage WHS on the project, including the arrangements for collecting, reviewing, and monitoring subcontractor SWMS. The plan is a project-level document rather than a task-level document, and it ties the whole safety system together.

Several patterns recur in poorly written SOPs and should be avoided when developing the document library. The first is excessive length. A SOP that runs to five or ten pages will not be read by the workers who need to follow it, and an unread procedure provides no training value. Good SOPs are three pages or fewer and concentrate on the critical steps and safety checks. Procedural detail that does not change the outcome can be omitted or delegated to the manufacturer's manual.

The second is vague language. Instructions such as operate the equipment safely or follow all safety procedures provide no actionable guidance and cannot be audited. Specific language — use a push stick for cuts within 150 millimetres of the blade — is the standard that SOPs must meet. Vague procedures are often a sign that the author did not fully understand the task and has papered over the uncertainty with generic phrases.

The third is outdated content. SOPs that reference superseded Australian Standards, old equipment models, or withdrawn regulations are worse than no SOP because they train workers on incorrect information. The review schedule must be enforced, and triggers for early review (incidents, equipment changes, regulatory changes) must be acted on immediately. A SOP library that has not been reviewed in several years is a liability rather than an asset.

The fourth is missing PPE specificity. Generic PPE lists — wear appropriate PPE — do not tell the worker which items are actually required for the task. The SOP should list each item with the relevant Australian Standard reference, so the worker knows exactly what to use and the supervisor knows what to check before releasing the task. Hearing protection class, respirator type, glove material, and eyewear impact rating all matter for different tasks and should be specified.

The fifth is failure to integrate with the SWMS system. A SOP that exists in isolation, with no cross-reference to any SWMS and no link to the training records, is disconnected from the operational safety system. Workers may be trained on the SOP but the site supervisor has no way to verify the training before releasing them to HRCW. The SOP library should be built with cross-references to SWMS templates and to the induction records, so the whole system produces a coherent audit trail.