Start here
Understand the workflow before changing the inputs.
Sector tools use source references to keep operational drafts connected to the approved rule that governs the work. The sections below explain what the tool is doing, where local rules still control the task, and which steps are worth checking first.
Use support content to clarify the workflow, then return to the live task with the relevant source, inputs and local controls still in view.
01 · Support note
Why the reference matters
A named SOP, work instruction, label or technical document makes it clear which approved source the operational draft is based on.
02 · Support note
What to enter
Use the identifier your organisation recognises: for example an SOP code, version, effective date or controlled work-instruction name.
03 · Support note
What the tool does not do
Typing a source reference does not validate that the document is current. The responsible organisation still owns document control and approval.
Operational boundary
Use the support article to navigate the tool — not to replace the controlled source.
Approved labels, SDS, SOPs, contracts, site procedures and accountable decisions remain authoritative where applicable. If the workflow conflicts with a controlled source, stop and resolve the source issue first.
Quick workflow
Use the shortest reliable path.
Work through only the checks that matter to the issue you are trying to resolve.
- 01
Identify the controlled source used for the task.
- 02
Enter its recognised name or code.
- 03
Confirm the version through your document-control process.
- 04
Escalate uncertainty instead of guessing from an outdated copy.