Getting Started with OH Consultant SWMS

Before stepping through the platform, it helps to understand what a compliant SWMS must contain under WHS Regulation 2025 section 299. The regulation requires four mandatory elements: identification of the high-risk construction work, specification of the hazards and the risks associated with the hazards, description of the control measures to be implemented, and description of how the controls will be implemented, monitored, and reviewed. These four elements are the regulatory floor, and any document that omits one of them does not satisfy section 299 regardless of how detailed the other sections are.

The SWMS must also be prepared taking into account the circumstances at the workplace where the HRCW will be carried out, and must be set out in a way that is readily accessible and understandable to the workers who will use it. This means a SWMS is not a generic template that can be reused unchanged across different sites — it must be customised for each project with site-specific hazards and controls. It also means the document cannot be written in dense legal language that workers cannot follow; the test is whether the workers performing the HRCW can read and understand it.

The HRCW categories that trigger the SWMS requirement are listed in WHS Regulation 2025 Schedule 1 and cover 18 categories of high-risk construction work. These 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, and the remaining Schedule 1 categories. The SWMS must identify which of these categories apply to the specific work, because the regulator uses this identification as the starting point for assessing adequacy.

Victoria operates under OHS Regulation 2017 Part 5.1 with similar requirements but uses employer and employee terminology rather than PCBU and worker. The fall threshold in Victoria is 2 metres, and the HRCW categories are broadly aligned with the model jurisdictions. A contractor working in Victoria should build the SWMS using Victorian terminology and reference WorkSafe Victoria Compliance Codes rather than Safe Work Australia Codes of Practice.

Understanding these requirements before opening the builder helps the user make better choices during the build process. A contractor who knows why the hierarchy of controls matters will think harder about elimination and engineering controls rather than defaulting to PPE. A contractor who knows why site-specific detail matters will complete the project details section with actual information rather than placeholders. The time invested in understanding the regulatory framework is paid back several times over during the build itself.

Navigate to the platform homepage and click the button to start building. The account creation form asks for a small number of details that appear on the SWMS documents the user will produce. The required fields are the user's name (which appears as the author of the SWMS), the email address (used for account access and document notifications), the business name (which appears on the SWMS header as the PCBU preparing the document), and optionally the ABN.

The ABN is optional but recommended because it appears on the SWMS header and demonstrates to principal contractors that the user is a legitimate registered business. Principal contractors reviewing submitted SWMS routinely check ABN validity against the Australian Business Register, and a SWMS with no ABN can attract scrutiny even if the content is adequate. Adding the ABN at account creation means it is automatically embedded in every document the user produces and does not need to be entered manually each time.

No credit card is required for account creation. The first SWMS is free, and the user can build, download, and distribute the document without paying anything. The builder only prompts for a paid plan when the user starts their second document, at which point the user can choose One-Off, Solo, or Business depending on how many SWMS they expect to produce. This approach avoids the credit-card-required trial pattern that causes so much friction in software evaluation, and allows the contractor to evaluate the tool with real work before committing.

After email verification, the user is taken to the dashboard. The dashboard is empty at this stage — there are no SWMS, no sign-on records, and no amendments — but it will populate as the user builds documents and runs sign-on at the pre-start meeting. The navigation is designed around the common workflow: build a SWMS, distribute it to workers, monitor sign-on, amend as needed, retain for the regulatory retention period. New users can ignore the more advanced features (multi-site dashboard, bulk sign-on, tender export) until they actually need them.

The account is the user's permanent record of their SWMS history. Records created under the account remain accessible indefinitely, regardless of whether the user continues with a paid subscription. This matters because WHS Regulation 2025 requires retention for at least 2 years after a notifiable incident, and best practice is 7 years. An account that is downgraded to free or cancelled entirely still provides access to the historic documents, so the retention obligation is met automatically without requiring ongoing payment.

From the dashboard, click the button to start a new SWMS. The guided builder walks through each section in sequence, asking specific questions and pre-populating responses based on the trade and HRCW selections. The builder is designed so that a user who has never produced a SWMS before can still complete a compliant document in under ten minutes by answering the prompts in order.

The first section is project details: the site address, the project name, the principal contractor name, and the planned start date. These fields make the SWMS site-specific, which is the first test the document must pass under section 299. Generic SWMS with no site address or with a placeholder address fail the site-specific requirement on their face, and regulators routinely reject them as non-compliant templates. Spending 30 seconds entering accurate project details is the single most important thing a user can do to make their SWMS credible.

The second section is HRCW category selection. The builder displays the 18 categories from WHS Regulation 2025 Schedule 1 with plain-English descriptions, and the user ticks the ones that apply to the work. Most trade SWMS trigger one to three categories. An electrician working on a switchboard ticks Category 12 (work on or near energised electrical installations) and potentially Category 1 (work at height) if the switchboard is above 2 metres. A roofer ticks Category 1 and potentially Category 17 (extremes of temperature) for summer work. The builder provides guidance if the user is unsure which categories apply.

The third section is trade selection. The builder offers pre-loaded content libraries for more than 20 construction trades, and selecting the user's trade automatically populates the subsequent sections with relevant hazards, controls, PPE requirements, training references, and Australian Standards citations. Electrical, plumbing, carpentry, concreting, roofing, waterproofing, tiling, plastering, HVAC, welding, scaffolding, rigging, demolition, excavation, and the other major trades each have their own library. The user reviews the pre-loaded content and adjusts it for the specific job rather than building from a blank template.

The fourth section is the risk assessment. Each hazard from the pre-loaded library is displayed with a 5x5 risk matrix showing consequence and likelihood. The builder calculates the inherent risk (before controls) and the residual risk (after controls) automatically based on the user's selections, producing two ratings that demonstrate the effect of the control measures. The inherent rating shows how dangerous the work would be without controls; the residual rating shows the actual operational risk when the SWMS is followed. The gap between the two numbers is the measure of how much protection the controls provide, and it is a key audit question when regulators review SWMS adequacy.

The fifth section is the control measures. Each pre-loaded control is tagged to a level of the hierarchy of controls — elimination, substitution, isolation, engineering, administrative, or PPE — and the builder enforces the hierarchy by prompting for higher-order controls before accepting PPE-only responses. A user who tries to submit a SWMS that addresses fall hazards with only harness and lanyard PPE will be prompted to consider guardrails, scaffolding, or other engineering controls first. This is not pedantry — it is the regulator's expectation under section 36 of the WHS Regulation, which requires risks to be minimised in the order of the hierarchy.

The sixth section covers plant and equipment, PPE requirements, training and licensing, emergency procedures, and the consultation record. Each of these sections is pre-populated based on the trade and HRCW selections and can be customised for the specific job. The PPE section uses current Australian Standards references, and the training section uses current units of competency (CPCCWHS1001 for the construction induction white card, with the older CPCCOHS1001A flagged as superseded if it appears in user input).

The final step is review and publish. The user reads through the complete SWMS, makes any final adjustments, and publishes the document. Publishing generates the PDF, creates a unique QR code for worker sign-on, and activates the document in the user's register. The SWMS is now ready for worker sign-on and site use.

Once the SWMS is published, the platform generates a unique QR code that is printed on the cover page of the document and is also accessible from the user's dashboard for direct display on a phone or tablet. Worker sign-on uses the QR code as the entry point to a mobile-friendly view of the SWMS content. The workflow is designed to take under 30 seconds per worker and to work on any smartphone without app installation.

At the pre-start meeting, the supervisor displays the QR code — either on the printed SWMS cover page, on their phone, or on a tablet positioned at the sign-on station. Each worker opens their phone camera, points it at the QR code, and taps the notification that appears. This opens a mobile-optimised page showing the SWMS summary, the key hazards for the work, the main controls, and the sign-on form. The worker reads through the summary, enters their name, and confirms acknowledgement by tapping the sign-on button.

The platform records the sign-on with a timestamp, the device identifier, and the specific version of the SWMS the worker acknowledged. The record is tamper-evident — it cannot be modified after creation, and any attempt to retroactively add a worker to an earlier sign-on is visible in the audit trail. This evidentiary integrity is the main reason digital sign-on has replaced paper sign-on sheets on managed construction sites: the digital record is reliable in ways that paper cannot match.

Workers do not need to install an app, create an account, or log in. The sign-on page is a standard web page served by the platform, and the worker's interaction with it is a simple tap-to-acknowledge. This approach removes the friction that undermines other digital sign-on platforms — the friction that causes supervisors to fall back to paper sheets when workers cannot or will not install apps on their phones. The QR-to-browser workflow works for every smartphone without configuration.

When the SWMS is amended (discussed in step 5), the existing sign-ons are invalidated and workers must re-acknowledge the updated version before continuing the affected HRCW. The platform issues a notification to the previously signed-on workers and prompts them to scan the updated QR code. The supervisor sees the re-sign count on the dashboard in real time and can confirm that the full crew has acknowledged the amendment before releasing them back to work. This workflow is essential for compliance with WHS Regulation 2025 section 300, which requires workers to be made aware of the amended SWMS before continuing the HRCW.

Digital signatures are legally accepted under Australian WHS law. The Electronic Transactions Act 1999 (Cth) and equivalent state legislation confirm that electronic signatures are valid if the method identifies the person signing, indicates their intention, and is reliable under the circumstances. QR-code-to-browser sign-on meets all three criteria and produces stronger evidence of acknowledgement than handwritten signatures on a paper sheet.

A published SWMS needs to be accessible on site throughout the duration of the HRCW, not just at the pre-start meeting. The platform supports several access modes that together cover the full range of on-site scenarios the user will encounter.

On the supervisor's phone or tablet, the SWMS is available through the dashboard at any time. The user logs in, selects the active project and the relevant SWMS, and the document is displayed with the full hazard register, control measures, and sign-on history. This is the primary mode for daily use — the supervisor can show the SWMS to an inspector, to the principal contractor, or to any worker who wants to review it, without needing a printed copy or a physical folder.

For sites that require a printed copy in the site office, the PDF can be downloaded and printed on standard A4 paper. The PDF is formatted for professional presentation, with the user's business logo (if configured), the trade, the HRCW categories, the hazard register with risk matrix, the control measures in hierarchy order, and the sign-on history. The printed copy is suitable for the PCBU's file, for the principal contractor's SWMS register, or for any regulator request. On managed sites, the principal contractor typically wants both the digital version (for the shared platform) and a printed copy (for the site office file).

For direct sharing with the principal contractor, the platform supports email delivery and shared links. The user can email the PDF directly to the principal contractor's WHS coordinator or share a link that allows the principal contractor to view the current version without needing their own account. On platforms with multi-site dashboards, the principal contractor sees the user's SWMS in their own project register automatically, which eliminates the email step entirely.

Inspector mode is a specific feature for regulator visits. When a SafeWork inspector arrives on site and asks to see the SWMS, the user opens the platform and switches to inspector mode, which shows a read-only view of the current SWMS, the sign-on list, and the amendment log. Other documents, business data, and unrelated projects are hidden from this view so the inspector sees only what they need to review the specific SWMS. The inspection typically takes 3 to 5 minutes on this workflow, compared to 20 to 30 minutes on a paper-based system with lost documents and illegible sign-on sheets.

The key point is that the SWMS is a working document, not a filing exercise. Workers should be able to refer to it during the job, the supervisor should use it during pre-start briefings, and the inspector should be able to see it within minutes. Documents that are filed and never consulted do not satisfy the section 299 accessibility requirement even if they technically exist. The platform is designed to keep the SWMS in active use throughout the life of the HRCW.

A SWMS is not a set-and-forget document. WHS Regulation 2025 section 300 requires the SWMS to be reviewed, and if necessary revised, whenever site conditions change, a new hazard is identified, a control measure is found to be inadequate, after any incident or near-miss, at the request of an HSR, or at regular intervals during the work. The platform makes amendments simple enough that users will actually perform them in the field rather than deferring them until the next office visit.

The quick-amend workflow allows the supervisor to modify the SWMS from a phone or tablet in under two minutes. The user opens the document, navigates to the section that needs updating, edits the relevant field (adding a hazard, modifying a control, updating a risk rating), and saves the change as a new version. The platform automatically creates an amendment log entry with a timestamp, the identity of the person making the change, and the reason for the change. The new version becomes the active document, and the previous version is retained in the history for audit purposes.

After the amendment is saved, the platform issues a notification to all previously signed-on workers prompting them to re-acknowledge the updated version. Workers scan the updated QR code on their phones and confirm sign-on to the new version. The sign-on count is visible to the supervisor in real time, and the work cannot proceed until the required workers have acknowledged the amendment. This is the operational implementation of the section 300 review obligation — the workers are made aware of the changes before the HRCW continues.

Common triggers for amendments include a new hazard identified during a pre-start briefing, a near-miss that reveals a gap in the control measures, a change in weather that requires additional precautions, the arrival of a different piece of plant than was specified in the original document, the discovery of a previously unknown service during excavation, and a change in the scope of the work. Each of these triggers should produce an amendment if the existing SWMS does not already address the new circumstances.

The amendment log is the audit trail for the SWMS history. An investigator examining an incident several weeks later needs to see what the SWMS said at the time of the incident, not just the current version. The log shows every version of the document, every amendment, every reason for change, and every sign-on record associated with each version. This level of historical traceability is impossible with paper-based SWMS and is one of the main reasons digital platforms have become standard on managed construction sites.

Regular review is also important even without specific triggers. Most well-managed projects review SWMS every 28 to 30 days as a minimum, to catch drift between the document and the site practice. The platform supports scheduled reviews by reminding the user when the next review date approaches, and by tracking the review date in the SWMS register for auditors to see. A SWMS that has not been reviewed in 60 days is flagged for attention, and the supervisor can choose to confirm the document is still current or to trigger a revision.

New users frequently make several mistakes during their first SWMS build, and knowing about them in advance helps avoid them. The most common mistake is skipping the site-specific details and leaving the project address, principal contractor name, or start date blank or set to placeholder values. This produces a SWMS that is technically complete but fails the site-specific requirement of section 299. Always enter the actual project details at the start of the build.

The second common mistake is selecting too few HRCW categories. Users focus on the most obvious category (typically fall hazards or electrical work) and miss secondary categories that also apply. An electrician working in a confined switchroom may trigger both Category 12 (energised electrical installations) and Category 6 (confined space), and a scaffolder erecting a facade scaffold may trigger both Category 1 (fall hazards) and Category 15 (work adjacent to a road or footpath). Review the full Schedule 1 list and tick every category that applies, even if it feels like overkill — the regulator reviews against the actual work, not the user's selections.

The third common mistake is accepting the pre-loaded hazards without adding site-specific ones. The content library contains the common hazards for each trade, but every site has unique features that the library cannot anticipate. Adjacent occupied buildings, overhead powerlines at unusual heights, contaminated ground, archaeological constraints, weather exposures, and conflicts with other trades all produce site-specific hazards that must be added to the SWMS by the user. Spend a few minutes walking through the site mentally and adding anything the library missed.

The fourth common mistake is accepting PPE-only controls without considering higher-order alternatives. The builder prompts for hierarchy consideration, but users can still select PPE controls without thinking about whether elimination, substitution, isolation, or engineering controls might work better. The test is whether a regulator reviewing the SWMS would be satisfied that the PCBU considered the full hierarchy, not just whether PPE is listed. If the only control for a fall hazard is a fall-arrest harness, the SWMS is likely to be criticised and may be returned for revision by the principal contractor.

The fifth common mistake is not running the worker sign-on properly. Users publish the SWMS, print it out, and then forget the QR sign-on step at the pre-start briefing. This defeats the purpose of the digital workflow and reverts the user to paper-equivalent evidence quality. Always run the sign-on at the pre-start meeting, confirm every worker has acknowledged the document before releasing them to HRCW, and check the dashboard to verify the sign-on count matches the crew list.

The sixth common mistake is forgetting to amend the SWMS when conditions change. New users tend to treat the SWMS as a one-off document produced at the start of the project and never updated. The quick-amend workflow is designed to be fast enough to use in the field, and the amendment log is the audit trail that auditors expect to see. Get into the habit of amending the SWMS whenever something changes, even if the change seems minor — the log builds up evidence of active management, and the habit ensures nothing falls through the cracks when a significant change occurs.