Assemble at the front gate on Harbour Street. Morgan Example coordinates the site response.
Prepared by Morgan Example
The version the site is working to
The approved version is in effect. Later edits belong to a new version.
Fictional dataTry the controls
03SWMS
Approved version assigned
Prepare the SWMS against the site’s in-effect WHS plan, record consultation, review the controls, assign the approved version and keep acknowledgements and changes tied to that version.
Responsible role
Site manager, then assigned people
What this stage does not prove
Consultation entries are manager-recorded assertions. Acknowledgement is not statutory approval, proof of understanding, proof controls were implemented or authority to start work.
The assembly point for this example site is the front gate on Harbour Street.
Read, answer, review
Try a sample question. This example does not create a signed induction or demonstrate competency.
Fictional dataTry the controls
05Attendance
Check-in recorded
Workers check in to an assigned site and check out against the same attendance record. Supervisors see the current roster and a separate queue for old sessions that need review.
Responsible role
Worker, contractor or supervisor
What this stage does not prove
Open sessions older than 14 hours are excluded from current headcount. Manual attendance does not create GPS, selfie or device evidence that was not captured.
The decision remains linked to this plan version when a later draft is prepared.
Fictional dataTry the controls
Take a closer look at the work.
Explore six stages in the actual SafeSite interface, with fictional records and clear context for every preview.
The workflow in 23 seconds.
23 second overview, silent
Actual interface · Example draft
A silent, illustrated overview using example interface captures. The film includes an earlier unsaved SWMS builder at step 3 of 6; the still above shows a saved draft. Neither is an approved version.
Read the complete film sequence
01Site setOperating context recorded
02Approved plan in effectDecision and effective date retained
03Approved version assignedReview and acknowledgement stay distinct
04Completion recordedCompletion tied to the published version
05Check-in recordedCurrent roster and old sessions separated
06Ready for operational reviewPoint-in-time evidence remains reviewable
See where preparation, oversight and completion change hands.