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.
What to enter
Use the identifier your organisation recognises: for example an SOP code, version, effective date or controlled work-instruction name.
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.
Approved instructions take precedence.
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.
Working steps.
- 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.
At a glance
A useful reference identifies the exact controlled instruction and makes it possible for a reviewer to find it.
| Item | Purpose | Review |
|---|---|---|
| Identifier | The recognised SOP or work-instruction code. | Use the organisation’s controlled naming scheme. |
| Version or date | The version or effective date relevant to the work. | Confirm currency through document control. |
| Review | The accountable check before use. | Typing a reference does not validate or approve the document. |
Worked example
Enter the controlled SOP code, version and effective date used by your organisation. Confirm that it applies to the area and task. If the source changes, review the saved draft against the current instruction before reuse.
Common questions
Only a document title is available.
Ask the responsible document owner for the recognised identifier and current version.
Two sources appear to disagree.
Route the conflict to the responsible reviewer before use. The tool does not decide which instruction is authoritative.