INCIDENT REPORTING
Report the hazard while the work is happening — and keep the response tied to the task.
Workers should be able to report a hazard, changed condition, near miss or Stop Work issue directly from the active task. ONE records it against the work, alerts the responsible supervisor, line manager or authorised person, and keeps the response and closure in the same evidence trail.
REPORT HAZARD / CHANGE10:26
EVIDENCE ATTACHEDPhoto and report saved to the active task.Ready for supervisor review.
1Worker reports→2Supervisor notified→3Work reviewed
AFFECTED WORKOn hold until re-cleared
PAUSEDIN PLAIN ENGLISH
Incident reporting should start the learning process, not end with a form in a folder.
Hazard and incident reporting is the controlled way to capture what happened or changed while the work was being performed, together with the task context needed to respond.
A hazard found during a job can change the controls, permit conditions, Work Clearance or whether the work should continue. It should not disappear into a separate form or inbox.
From the active task, a worker can raise Report Hazard, Ask a Question or Stop Work. ONE links the report to the task and routes attention to the people who can act.
INCIDENT REPORTING IN PLAIN LANGUAGE
Record the event. Preserve the truth. Learn before the next task.
An incident record should capture what happened and connect it to the work, people, conditions, controls and evidence that existed at the time. Statutory notification duties vary by jurisdiction and industry, so ONE should distinguish internal reporting from any external notification requirement and surface verified local rules when they apply.
Preserve what was true at the time.
Keep the applicable task version, prerequisites, controls, evidence and decisions so the history is not rewritten by later edits.
Make corrective action visible.
Investigations, actions, owners, due dates and verification should remain connected to the event and the affected work.
Feed the learning back into controlled work.
Repeated failures, near misses and lessons should improve the task knowledge and checks used the next time similar work is planned.
REPORT FROM THE WORK
One tap from the active task should start the response loop.
The person doing the work should not have to know which reporting module to open. The task already gives ONE the context.
Report Hazard / Stop Work.
The worker raises the issue from the active task and can add the information or evidence needed to explain what they found.
Attach the task context.
The person, task, workplace, time and affected work stay connected to the report automatically.
Get it to the right person.
The responsible supervisor, line manager or authorised person receives a clear action. Urgent alerts are used for matters affecting immediate safety or work authorisation.
Action, evidence, closure.
The response, changed controls, review decision, restriction or stop-work outcome remains in the same task evidence trail until resolved.
CLOSE THE LOOPA report is not closed because somebody read the notification.
See the Task Lifecycle →ONE should keep the issue open until the required action and evidence are recorded, and reconnect any material change to the task, permit, induction or Work Clearance position it affects.
NOTIFICATION IS NOT RESOLUTION
ONE should not just tell somebody. It should keep the issue open until somebody acts.
A worker report creates an action state. The responsible supervisor, line manager or authorised person must be able to acknowledge it, investigate or assess it, take or assign action, record evidence and reconnect any material change to the current Work Clearance position.
Worker raises the issue.
The original words and evidence are preserved against the live task.
Continue, pause or stop.
ONE makes the current work position visible instead of treating the report as a passive form submission.
Send it to the right authority.
The responsible role is resolved from the task and workplace context, with escalation available where required.
Someone takes responsibility.
Seeing a push notification is not the same thing as accepting responsibility for the issue.
Assess and intervene.
Controls can be confirmed, work kept paused, corrective action assigned, a permit reviewed or another controlled pathway initiated.
Record what changed.
Actions, photos, decisions and verification remain tied to the event and task.
Re-evaluate readiness.
If the issue affects a prerequisite or control, ONE reconnects the changed condition to readiness and authorised review.
Tell the worker what happens next.
The worker sees Review underway, Continue task, Ready to resume or Authorised review required — not silence.
ONE EVIDENCE TRAIL
Notification sentAcknowledgedAction takenIssue resolvedWork authorised to resume
Each is a separate recorded event. A notification alone does not authorise work to resume.
Hazard reported
Your supervisor has been notified.
Work paused
Do not continue this work until the issue has been reviewed.
Ready to resume
The authorised outcome is recorded and the worker is told what to do next.
NO RECEPTION?Report Hazard and Stop Work should still work offline.
See the Evidence Trail →The device can preserve the event time, report, evidence and local work state, then synchronise the report and notifications when connectivity returns. A safety pause should not depend on a push notification getting through.
ONE INTELLIGENCE
Same work. Different context. Different answer.
ONE is designed to adapt the pathway to the task, industry, jurisdiction, workplace rules and verified requirements — rather than forcing every organisation into the same generic form.
Start with what the person is actually going to do.
Industry, jurisdiction, workplace, people, plant and client requirements can change the pathway.
Apply the right legal and workplace language only when the applicable source is known.
Choose the appropriate document, checks, prerequisites and evidence — without hiding uncertainty.
GLOBAL FRONT DOORSimple language first.
LOCAL LEGAL INTELLIGENCEJurisdiction-specific duties when known.
TRUST RULEIf ONE is not sure, it tells you.
CONNECTED APPROACH
The document or check is not the destination.
The practical value comes from keeping the work, prerequisites, controls and evidence connected.
Capture what happened.
Record the event in the controlled operational system with the relevant task and workplace context.
Keep supporting information connected.
Photos, statements, task versions and other evidence may need controlled handling and access.
Connect actions and change.
Corrective action or revised controls should feed back into the work rather than remain separate from future readiness.
Reconstruct less.
A connected evidence trail can reduce the need to rebuild the safety story after an event.
FROM INFORMATION TO READINESS
Connect the topic back to the work.
ONE is designed so task information can contribute to a broader Work Assurance picture rather than becoming another disconnected file.
What are you going to do?
Start from the work and the current context.
What applies?
Surface the people, workplace, control and evidence items that matter.
What is unresolved?
Show missing, expired, unknown or changed items in plain language.
Who decides?
Keep system findings separate from the authorised human decision.
TRY THE CONNECTED VIEWStart with the Gap Check.
Start the Gap Check See where your current task information, prerequisites and evidence may be fragmented across people, folders and systems.
COMMON QUESTIONS
Questions about this part of ONE.
Open only the question that matters to you.
Can a worker report a hazard while doing the task?
Yes. Report Hazard, Ask a Question and Stop Work should be available from the active worker experience so the event stays connected to the task, workplace, person and time.
Who gets notified?
ONE should route the event to the appropriate supervisor, manager or authorised person according to the configured rule and severity, while avoiding repeated duplicate notifications.
Does the original task record disappear if there is an incident?
No. ONE should preserve the released version and the event history. Material changes can create review and a new controlled version rather than rewriting what actually happened.
Is the issue resolved when the manager receives the notification?
No. Notification, acknowledgement, action, resolution and any authority to resume work are separate events. ONE should keep an action-required issue open until the required response and evidence are recorded.
What should the worker see after reporting a hazard?
The worker should see the current state clearly — for example Hazard reported, Review underway, Work paused, Continue task or Ready to resume — so they are not left wondering whether anybody acted.
What if the worker has no mobile reception?
Report Hazard and Stop Work should be capable of being recorded locally with the original event time and work state, then synchronised when connectivity returns. The local stop or pause state should not depend on successful notification delivery.
I still have another question. What should I do?
Use the green Ask ONE button or the full ONE FAQs first. Register Interest is for joining a ONE pathway, not routine product questions.