Pre-Start Checklist Template for Construction Sites

The WHS Act 2011 and WHS Regulation 2025 do not use the phrase pre-start meeting anywhere in their text, but several duties combine to make a daily briefing effectively mandatory on most construction sites. Section 19 of the Act imposes the primary duty of care on the PCBU to ensure the health and safety of workers so far as is reasonably practicable, which includes providing information, instruction, training, and supervision. Section 47 of the Act requires consultation with workers on matters that affect their health and safety, which on a construction site includes the identification of hazards, the implementation of controls, and the review of work methods.

Regulation 299 requires that the SWMS be prepared in a way that workers can access and understand it, and that workers be made aware of the content before commencing HRCW. A document that sits in the site office filing cabinet and is never discussed with the crew does not satisfy this requirement. The daily pre-start meeting is the operational vehicle for SWMS awareness — the mechanism by which the supervisor confirms that every worker on today's HRCW knows the hazards and the controls that apply.

Regulation 309 places specific duties on the principal contractor for construction projects above $250,000, including the duty to ensure compliance with the SWMS for each HRCW activity on site. Compliance cannot be ensured if the workers do not know what the SWMS says, and the pre-start meeting is the point at which the principal contractor's WHS representative verifies that knowledge. On OFSC-accredited projects, the Federal Safety Officer routinely reviews pre-start records during audits, and a pattern of missed or undocumented meetings generates non-conformance findings.

Victoria operates under the OHS Act 2004 and OHS Regulation 2017, which use employer and employee terminology instead of PCBU and worker but impose equivalent consultation duties through sections 35 to 39 of the OHS Act. WorkSafe Victoria Compliance Codes on construction work reference pre-start briefings as part of the employer's duty to provide a safe system of work. The content of the briefing and the documentation requirements are essentially the same as in the model jurisdictions; only the terminology differs.

An effective pre-start meeting follows the same sequence every morning, so the crew knows what to expect and the supervisor does not have to remember what to cover. The sequence should take five to ten minutes. Briefings that routinely run beyond fifteen minutes are either too detailed for the daily format and should be split into a separate toolbox talk, or are too unfocused and need to be tightened.

Start with the date, time, location, and attendees. Record every worker present, note anyone absent who was expected, and note any new workers, visitors, or late arrivals who will need to be inducted separately. The attendee list is the starting point for the sign-on record and is essential evidence if the principal contractor needs to demonstrate who was briefed on what.

Move to the weather check. Wind speed and direction are critical for crane work, work at heights, scaffolding, and roof access. Temperature drives heat stress risk above 35 degrees and cold stress risk below 5 degrees. Rain creates slip hazards, electrical risks, and excavation stability problems. Lightning within 10 kilometres of the site requires all outdoor work to stop under AS/NZS 1768, and the supervisor should be monitoring the forecast before the briefing starts. Record the weather conditions on the pre-start sheet so that the decision to proceed or stand down is traceable.

Review the SWMS for today's work. Which SWMS apply to today's activities? Have all workers signed on to the current version? Are there amendments since yesterday that require re-acknowledgement? Is there any new HRCW starting today that requires a new SWMS not previously submitted? Pull up the SWMS on a phone or tablet and walk through the key hazards and controls with the crew. This is the part of the briefing that satisfies the section 299 awareness requirement.

Identify new hazards. Anything that has changed since yesterday — new excavations, new scaffolding, changed access routes, new plant arrivals, scheduled deliveries, adjacent work creating new risks — needs to be flagged and added to the relevant SWMS if necessary. Ask the crew directly: what is different this morning compared to yesterday? Workers often notice changes that the supervisor has not registered.

Confirm PPE, plant, exclusion zones, and emergency arrangements. PPE check covers availability and condition — hard hats, safety boots, high-visibility clothing, gloves, eye protection, hearing protection, harnesses. Plant pre-use inspections confirm that every piece of powered mobile plant has been inspected before use today, with the logbooks and pre-use tags available for review. Exclusion zones cover crane swing radius, excavation edges, overhead work zones, and live services. Emergency arrangements cover muster point, first aid officer, first aid kit location, defibrillator location, and the evacuation route. Any change to these from yesterday must be communicated clearly.

The regulatory basis for the pre-start meeting is consultation, which by definition is two-way. A supervisor reading from a script while the crew stares at their boots is not consultation — it is a monologue, and both the crew and an inspector will recognise it as such. Effective pre-start meetings are structured as guided conversations where the supervisor prompts input from the crew and actually listens to the answers.

Ask open questions. What hazards do you see today that were not here yesterday? Has anyone got concerns about today's lift plan? Is there anything stopping you from doing this work safely? What equipment do you need that is not here yet? These questions prompt workers to think about the upcoming work rather than passively receive information. The answers often reveal issues the supervisor has not seen, and the supervisor's response to those issues is where the real consultation happens.

Use the SWMS as the agenda. Pull up the document on a phone or tablet and walk through the hazard register, the controls, and the implementation arrangements for today's specific activities. A platform that stores the SWMS in the cloud means the current version is always available on the supervisor's device, without needing to remember which USB stick has the latest revision. Walking through the SWMS at the pre-start makes the document a live reference rather than a filing cabinet artefact, which is both a consultation improvement and an auditor-visible sign of an active safety system.

Address new workers immediately. Anyone who was not present at yesterday's pre-start needs an individual catch-up before joining the crew on HRCW. This is not optional — section 299 requires every worker on HRCW to be aware of the SWMS content, and a worker who missed the briefing cannot participate in the work until they have been briefed. The catch-up should cover the SWMS, the site-specific hazards, the PPE requirements, and the emergency arrangements. A new worker who is told to shadow someone else without a formal induction is a non-compliance finding waiting to happen.

Follow up on yesterday's actions. If a worker raised a concern yesterday — a scaffolding defect, a missing spotter, a plant pre-use check that found a fault — the supervisor should report on the action taken. Nothing kills safety culture faster than workers raising issues that disappear into a void. Even if the action is not yet complete, acknowledging the issue and explaining the plan keeps the consultation loop alive. A supervisor who responds to every concern with we will look into it and then never mentions it again is training the crew to stop raising concerns, which is the opposite of what the regulation intends.

A structured pre-start checklist gives the supervisor a consistent format to work through every morning and produces a documented record for the audit trail. The template below contains the essential fields and can be adapted to specific project requirements. It should be printed on a single page (or displayed on a device) so the briefing does not become a paperwork exercise.

Header: date, time, location, site supervisor, project name, and project number. These fields establish the context for the briefing and link it to the broader project records.

Attendees: a list of every worker present at the briefing, recorded by name and trade. Space for notes on absentees, new arrivals, and visitors. This section produces the sign-on evidence that the supervisor can cross-reference against the SWMS acknowledgement records.

Weather: current conditions including temperature, wind speed, rain, and lightning activity. Space to note any weather-related decisions such as stand-downs, modified work methods, or exclusion zones adjusted for wind loading.

SWMS in effect today: a list of every SWMS that applies to today's activities, with version numbers and amendment flags. A tick box for each document confirming that the crew has acknowledged the current version. Space to note any new SWMS starting today and any amendments since yesterday.

Hazard review: new hazards identified since yesterday, changes to the work area, adjacent work, service discoveries, and plant movements. Space to note how each hazard will be controlled and whether a SWMS amendment is required.

PPE check: confirmation that all required PPE is available and in serviceable condition. Specific items checked should match the SWMS requirements for the day's work.

Plant check: confirmation that pre-use inspections have been completed for all powered mobile plant in use today. Logbook references and any defects noted.

Exclusion zones: confirmation that exclusion zones are established and marked. Crane swing radius, excavation edges, overhead work zones, and live service corridors.

Emergency arrangements: muster point, first aid officer on duty, first aid kit location, defibrillator location, evacuation route, and contact numbers for emergency services.

Actions from previous pre-starts: any open items from earlier briefings, with updates on status.

Supervisor signature and worker acknowledgement: the supervisor signs to confirm the briefing was conducted and the record is accurate. Workers acknowledge either through individual signature, group acknowledgement, or digital sign-on. On platforms with QR-code sign-on, the supervisor scans the crew onto the briefing record in seconds.

The single most common weakness in pre-start meetings is that the content is disconnected from the SWMS. The supervisor covers generic safety reminders — watch your step, wear your PPE, stay hydrated — while the actual document that describes the hazards and controls for today's specific work sits unopened in the site office. An inspector who observes this disconnect will find it within seconds, because the crew cannot articulate the controls that are supposed to be in place, and the SWMS is not being used as the communication tool it is intended to be.

The pre-start content should come directly from the SWMS. The hazard register in the SWMS becomes the list of hazards reviewed at the briefing. The control measures in the SWMS become the items the supervisor confirms are in place. The monitoring arrangements in the SWMS become the responsibilities assigned for the day. The worker sign-on record for the SWMS is updated at the briefing, either through paper sign-on or digital QR-code acknowledgement. The SWMS is not a separate document that workers read once and forget — it is the script for the daily conversation.

This direct connection is the reason cloud-based SWMS platforms have become standard on managed sites. When the SWMS is on the supervisor's phone, the document is available at the pre-start, at the work area, during inspections, and during incident investigations. When the SWMS is a printed document in the site office, the supervisor has to remember which version is current, whether any amendments have been added, and whether the document matches what the crew actually acknowledged. The printed workflow breaks down under pressure, and the breakdown shows up in audit findings and investigation reports.

The pre-start meeting is also the moment when workers sign on to the SWMS. Before QR-code sign-on became widely available, this was a paper process where the worker wrote their name on a sheet at the back of the printed SWMS. Paper sign-on is prone to illegible signatures, missed entries, and retrospective completion, and it is one of the most common sources of audit findings. Digital sign-on produces a timestamped, tamper-evident record that the worker acknowledged the specific version of the SWMS at the pre-start, which is exactly the evidence that an inspector or investigator needs.

Amendments triggered during the pre-start follow the same workflow. If the crew identifies a new hazard that is not addressed in the current SWMS, the supervisor amends the document on the spot, saves the new version, and the crew re-signs the amended version before work commences. The whole workflow takes under two minutes on a well-designed platform and produces a complete audit trail of the change, the reason for it, and the workers who acknowledged it. Compare that to the paper workflow: the supervisor has to return to the site office, re-print the SWMS, circulate the new sheet, collect new signatures, and file the updated version. The paper workflow takes hours and is almost never completed in the field.

A pre-start meeting that is not documented did not happen, from the perspective of a regulator or an OFSC Federal Safety Officer. The documentation requirements are modest but essential: date, time, location, attendees, topics covered, and any actions arising. These fields produce the evidence that the supervisor can point to when asked to demonstrate that the consultation duty under section 47 of the WHS Act is being discharged.

The paper version of this documentation is a signed pre-start sheet that lives in the site office and is filed at the end of the project. Paper works but has three weaknesses. The first is retrieval: finding a specific pre-start sheet from three weeks ago requires physical access to the filing system, which is often no longer accessible after the project ends. The second is integrity: paper sheets can be modified or created retrospectively, and a supervisor who forgets to run a briefing can easily backdate a sheet, which is exactly the kind of practice that undermines the audit value of the record. The third is integration: the paper sheet is disconnected from the SWMS sign-on record, so the supervisor has to maintain two separate records and reconcile them when questioned.

Digital pre-start documentation solves all three weaknesses. Retrieval is a matter of searching by date and project in a dashboard. Integrity is supported by server-side timestamps that cannot be modified after the fact, so the record shows exactly when the briefing was captured. Integration is automatic because the SWMS sign-on and the pre-start record share the same platform, and the same QR-code scan that acknowledges the SWMS also records the pre-start attendance. The supervisor maintains one workflow rather than two, and the audit trail is consistent across the whole project.

On OFSC-accredited projects, the consistency of pre-start documentation is one of the areas that Federal Safety Officers examine closely. A project with daily pre-start records for every shift, every crew, and every HRCW activity, showing clear attendee lists and traceable action items, is evidence of a mature safety management system. A project with intermittent pre-start records, missing weeks, and unexplained gaps is evidence of a system that exists on paper but not in practice. The second pattern attracts non-conformance findings and can contribute to suspension of accreditation in serious cases.

The documentation also matters in incident investigation. When SafeWork investigates a serious injury or fatality, one of the first questions is what the worker was briefed on before starting the work. A documented pre-start record that shows the worker acknowledged the SWMS, understood the hazards, and confirmed the controls was in place is a significant defence for the principal contractor and the subcontractor. Absent or inconsistent documentation is treated as an absence of the briefing itself, and the investigator proceeds on the assumption that consultation was not performed.

The pre-start meeting is often where the decision to proceed or stand down is made. Weather, plant availability, worker numbers, and site conditions all feed into the go or no-go call, and the supervisor's decision should be documented on the pre-start sheet with the reasoning. A stand-down that is not documented looks like an unexplained loss of productive hours; a documented stand-down with specific reasoning (wind speed, lightning proximity, missing plant) is evidence of active risk management.

Wind thresholds for work at heights, crane work, and scaffolding are typically set by the equipment manufacturer's specifications, the relevant Australian Standard, or the principal contractor's WHS Management Plan. A common default is 40 km/h for general work at heights and lower thresholds for specific activities. The pre-start check should include actual wind measurement (or a reliable forecast) and a decision on whether the day's work is safe to proceed. Documenting the measurement, the threshold, and the decision creates the audit trail that supports the call.

Lightning stand-downs are mandatory under AS/NZS 1768 when lightning is detected within 10 kilometres of the site, or when the time between a visible flash and audible thunder is 30 seconds or less. All outdoor work stops, workers move to a safe indoor area or enclosed vehicle, and work does not resume until 30 minutes have passed with no further lightning activity. The pre-start sheet should note the lightning check at the start of the shift and any stand-downs during the day, with the resumption time recorded.

Temperature-based stand-downs are driven by the heat stress risk assessment. Above 35 degrees (or lower with high humidity), work-rest cycles should be adjusted, cool drinks should be available, and workers should be monitored for heat stress symptoms. Below 5 degrees, cold stress risk applies. The pre-start is where the supervisor confirms the day's temperature expectation and applies the relevant controls. These decisions should be documented along with the temperature measurement.

Plant unavailability is another common stand-down trigger. If a critical piece of plant — the crane, the EWP, the concrete pump — is unavailable, the affected work may need to be postponed. The pre-start sheet should note the plant availability check and any work postponement decisions. This protects the supervisor from later claims that the work was stood down for arbitrary reasons and connects the commercial decision to the safety justification.

The integration of the pre-start meeting, the SWMS, and the worker sign-on record is the place where digital platforms provide the largest benefit. In a manual workflow, the supervisor runs the briefing, circulates a paper sign-on sheet for the pre-start, circulates a separate paper sign-on sheet for the SWMS, and files both sheets at the end of the day. These sheets are then reconciled weekly or monthly (or not at all) against the attendance records, the SWMS register, and the audit trail. The work is tedious, error-prone, and routinely skipped.

On a connected platform, the same QR-code scan that acknowledges the SWMS also records pre-start attendance. The worker scans the code on their phone, reads the SWMS content, confirms acknowledgement, and the platform writes three records simultaneously: SWMS sign-on for the specific version, pre-start attendance for today's briefing, and an update to the project's aggregate attendance log. The supervisor sees the sign-on count on their dashboard in real time and can confirm the crew is fully inducted before releasing them to work.

The connection also supports amendment workflows. When a new hazard is identified during the briefing and added to the SWMS, the existing sign-ons are invalidated and the workers are prompted to re-acknowledge the amended version. The amendment, the re-acknowledgement, and the pre-start record all share the same timestamp and can be traced through the audit trail. A regulator investigating an incident three weeks later can reconstruct exactly what the SWMS said at the time of the briefing and who had acknowledged it.

On platforms with multi-site visibility, the pre-start records also flow into the principal contractor's dashboard. The WHS manager running three concurrent projects can see at a glance which sites ran their pre-start meeting this morning, which sign-on counts match the expected crew size, and where the gaps are. This replaces the weekly reconciliation meeting where the WHS manager tries to piece together the previous week's activity from scraps of paper. The dashboard shows a live view of the project's safety system activity, which is also the evidence base for OFSC audits.

The pre-start meeting is the operational heartbeat of a construction site's safety system. It is where the SWMS moves from document to daily practice, where consultation happens in real time, and where the crew is prepared for the day. Treating it as a paper exercise disconnects it from the safety outcomes it is supposed to produce. Connecting it to the SWMS through a platform that supports integrated documentation and sign-on turns the pre-start into a five-minute workflow that satisfies three statutory duties at once and produces the audit trail that a well-managed site depends on.