SOPs and Work Instructions explain how routine or controlled work should be performed, including the steps, hazards, controls and practical requirements that matter.
SOP & WORK INSTRUCTIONS
Turn controlled task knowledge into usable instructions at the point of work.
SOPs and Work Instructions can describe the expected method, controls and sequence for a task. ONE is designed to connect that controlled instruction to the people, workplace and evidence that make it usable.
WORKER VIEWReleased
01
Isolate the supplyLock and verify before opening line.
02
Confirm zero energyUse approved verification method.
03
Replace valveFollow task controls and permit conditions.
IN PLAIN ENGLISH
A procedure only helps if the person doing the job can understand and use it at the point of work.
Long documents can become shelfware when the worker needs a short, clear instruction while supervisors need the controlled source and evidence behind it.
ONE can use one controlled task source to support both the fuller organisational record and a simpler worker-facing view without creating two disconnected truths.
SOPs & WORK INSTRUCTIONS IN PLAIN LANGUAGE
The repeatable way to do the work — without pretending every task needs a SWMS.
An SOP usually describes a standard, repeatable process. A Work Instruction can go deeper into the steps for a particular task, machine or activity. The right choice depends on the organisation, the work and the applicable requirements. ONE is designed to reuse controlled knowledge while adapting what is different this time.
Keep the stable method stable.
Where the task is repeatable, ONE can preserve the approved steps, controls and knowledge rather than rebuilding them every time.
Then ask: what's different here?
A different workplace, person, plant, material, condition or client rule can change what must be checked before the work proceeds.
Turn the controlled source into usable worker language.
Workers should receive the released information and actions they need — not be expected to interpret the entire safety management system.
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.
Reduce competing versions.
Keep a controlled task source so downstream instructions and related outputs do not drift apart.
Make the instruction practical.
The point-of-work view should be clear enough for the people doing the task and connected to the released version.
Connect the surrounding workflow.
Training, toolbox activity and pre-start checks can sit around the controlled instruction rather than in unrelated folders.
Reuse what remains current.
For recurring tasks, keep stable information and ask what is different in the current workplace or task context.
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.
When would ONE use an SOP or Work Instruction?
Where that is the appropriate task-control pathway for the work and applicable requirements, rather than using a SWMS simply because the software has one available.
Can the same work instruction feed the worker app?
Yes. The worker-facing view should derive from the same controlled task source so steps, hazards and controls do not drift between documents and the app.
What happens when the method changes?
ONE should identify the affected parts, route review where needed and preserve the previous controlled version rather than silently overwriting history.
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.