Practical guide · Educational reading
Learn to distinguish requirements from recommendations, map statements to existing processes and check evidence before deciding that another procedure is needed.
Audience / jurisdiction: International; educational guidance for management system coordinators, process owners and small-business managers, without jurisdiction-specific legal advice.
Start with interpretation, not a procedure template
Before writing procedures, read the selected standard closely enough to distinguish what it requires from what it recommends or permits. Then connect the relevant requirements to the way your organization already works. The immediate output should be a traceable interpretation and a set of questions to investigate—not automatically a new procedure for every statement.
ISO’s drafting guidance distinguishes “shall” as a requirement, “should” as a recommendation and “may” as permission. These distinctions give readers a useful starting point for deciding which statements belong in an implementation task list and which need different treatment.
The workflow below is an editorial suggestion for management system coordinators and process owners. ISO’s drafting guidance explains language; it is not an organizational implementation standard. Decisions about conformity must be checked against the applicable standard itself.
Sources: [1]
Step 1: Establish the document and reading context
First establish your reading baseline. Record the document identifier, edition, publication status, amendments being used and location of the controlled copy. Confirm those details against an authoritative publication record rather than relying on a filename or an inherited checklist. Keep any draft under discussion visibly separate.
Next, read the introduction, scope, references and definitions before extracting tasks. Note unfamiliar terms and questions about applicability. Do not settle those questions simply because an existing template offers a convenient answer.
Choose a manageable starting area: one process and a small group of relevant statements. As a suggested working format, record the source reference, statement classification, interpretation, existing process, owner, evidence to examine, unresolved question and next action. This is a proposed reading aid, not a prescribed ISO record.
Sources: [1]
Step 2: Classify statements without losing their meaning
Use ISO’s verbal-form distinctions to classify each relevant statement. Mark a “shall” statement as a requirement, a “should” statement as a recommendation and a “may” statement as permission. Keep explanatory material distinguishable from actions you intend to assign.
Do not use keyword searching as the whole reading method. For each statement, identify who must act, what the statement addresses and any conditions attached to it. Read the surrounding text and relevant definitions before recording your interpretation.
Keep the source reference alongside your plain-language explanation. A colleague should be able to retrace your reasoning without guessing which passage you meant. If two readers disagree, record the question instead of quietly turning one interpretation into an assigned obligation. Recommendations can inform improvement decisions, but should not be relabelled as requirements.
Sources: [1]
Step 3: Map the requirement to practice and evidence
For each requirement, ask: What must our organization achieve or control? Then identify the business process that could address it. Delay the documentation decision until you have examined the activity.
Identify the process owner and ask them to describe current practice. Record evidence to examine, not just evidence you hope exists. A proposed record, an untested assumption and an inspected record should have visibly different statuses in your working notes.
As an editorial diagnostic method, distinguish four possible findings: no process exists; a process exists but is inconsistently followed; practice appears adequate but supporting evidence is unclear; or the original interpretation needs reconsideration. Each finding points toward a different next step. Agree the next action with the process owner and retain unresolved interpretation questions separately from confirmed gaps.
Sources: [1]
Worked example: Investigate before commissioning a training procedure
Hypothetical example: a small service business is examining employee competence. Its coordinator initially proposes a new training procedure and an attendance spreadsheet. This example demonstrates the suggested reading method; it does not interpret a particular standard’s clause.
The coordinator instead maps the activity to recruitment, induction and assignment of work. Supervisors explain that they demonstrate tasks and observe new employees. The coordinator identifies role expectations, observed-task assessments and authorization records as possible evidence to examine.
The open question becomes more specific: do supervisors consistently assess readiness before allowing independent work? The suggested next action is to sample several recent starters and compare the available evidence with supervisors’ descriptions.
That check could reveal inconsistent practice, unclear evidence or a mistaken initial assumption. The team would then select a response based on what it found. The exercise does not establish conformity; it shows how to avoid choosing a documentation solution before understanding the issue.
Sources: [1]
Common mistakes to avoid
The following are editorial cautions, not findings about named organizations. Avoid treating every recommendation as mandatory: that loses the distinction ISO’s drafting guidance makes between “should” and “shall”. Equally, do not treat permission expressed through “may” as an instruction to adopt that option.
Avoid reading isolated sentences without checking their context. Also avoid creating one procedure per extracted statement before identifying whether an existing process already addresses the issue.
Finally, do not mistake a completed interpretation spreadsheet for checked implementation. A row saying “evidence available” is a prompt to inspect that evidence, not a substitute for doing so. Review a small sample with process owners before extending the method across the document.
Sources: [1]
A short action checklist
Suggested action checklist: confirm the selected document and publication status; separate requirements, recommendations and permissions; retain source references; map requirements to processes and owners; inspect evidence before declaring a gap; and review uncertain interpretations before assigning corrective work.
Start with one process, test the method and refine your working notes before expanding the exercise. Keep the eventual implementation checklist focused on verified requirements and clearly identified actions.
Sources: [1]
Sources
Your experience
Which requirement in your current implementation checklist would benefit from checking an existing process before commissioning a new procedure?
Originally published by AdviseISO, a knowledge-sharing initiative of W3 Solutionz.
