Standard Procedures, Checklists and Deviations for Supervisors
A premium course for supervisors and team leaders on making procedures work at the point of work: why procedures are ignored, writing usable procedures and standardized work, designing and using checklists (with the WHO Surgical Safety Checklist as a model), handling planned and unplanned deviations under ISO 9001 and FDA rules, and keeping procedures current through review and change control. Not an accredited qualification.
What you will learn
- Explain why procedures are not followed and what supervisors can do about it.
- Write or improve a usable procedure or standardized work sheet.
- Design and use a checklist correctly.
- Handle planned and unplanned deviations and nonconforming output.
- Keep procedures current through review, change control and workplace checks.
Modules
- Why procedures are not followed
- Writing usable procedures
- Checklists that work
- Deviations and nonconforming output
- Keeping procedures alive
Course facts
- Estimated study time
- about 1.5 hours
- Final assessment
- 10 questions · Pass mark 80%
- Available in
- English, Français, العربية
- Price
- Free. Optional verifiable certificate: $12
- Last updated
- Published by
- AMAADOR ACADEMY
Who this course is for
Supervisors and team leaders in production, laboratories, healthcare, IT operations, finance operations and services who own or enforce procedures.
Prerequisites
No formal prerequisite.
Course content
1. Why procedures are not followed
Every organisation has procedures that are not followed. The UK HSE’s human factors guidance gives the usual reasons: procedures that are inaccurate or out of date, too long or too complicated, written for auditors rather than users, not available where the work is done, or impossible to follow in real conditions (wrong tools, not enough time, steps in the wrong order). People then develop their own way of working, often sensible, sometimes dangerous, and always invisible to management.
Researchers describe this as the gap between ‘work as imagined’ — what the procedure says — and ‘work as done’. The supervisor is the person best placed to see that gap. When you find people not following a procedure, start with curiosity, not discipline: watch the job, ask why they do it that way, and check whether the procedure is actually correct and usable. Often the procedure is wrong; sometimes the workaround is risky and must stop; usually both need attention.
HSE advises that procedures should be developed with the people who use them, should match how the task is actually performed, and should be reserved for tasks where they add value — critical, infrequent or complex tasks. Not every task needs a detailed written procedure; competent people doing simple, frequent tasks may need only a short standard or job aid. Over-proceduralising simple work makes people less likely to read the procedures that matter.
Key point: When a procedure is not followed, first check whether it is right and usable; involve users and keep procedures for tasks where they add value.
2. Writing usable procedures
A usable procedure is written for the person doing the job, in the order the job is done. Start each step with a verb (‘Close valve V-12’, ‘Check the total matches the bank statement’). Keep one action per step, put warnings and cautions before the step they apply to, mark critical steps clearly, and use pictures, tables or flowcharts where they are clearer than text. Say what ‘good’ looks like at checkpoints. Test the draft by having someone who did not write it perform the task with it.
The Lean Enterprise Institute describes standardized work as having three elements: takt time (the rate at which work must be completed to meet demand), the work sequence, and the standard inventory or work-in-process needed to keep the process running smoothly. Standardized work is owned by the people who do the work and their supervisor, is displayed at the workplace, and is the baseline for improvement — when someone finds a better way, the standard is updated so the improvement sticks.
ISO 9001 (clause 7.5) requires documented information to be controlled: identified (title, number), in a suitable format, reviewed and approved, available where needed, protected, with changes controlled and obsolete versions prevented from unintended use. In practice, the supervisor must make sure that the version at the workstation, on the shared drive or in the app is the current approved one, and that printed copies are removed when a new version is issued. Uncontrolled copies are a frequent audit finding and a frequent cause of error.
Key point: One verb-led action per step, warnings before the step, critical steps marked, tested by a real user — and only the current approved version at the workplace.
3. Checklists that work
A checklist is not a procedure. It is a short list of the critical items that even experts sometimes forget under pressure, used at a defined moment — a ‘pause point’. Two types are common: ‘read-do’, where the user reads each item and then does it (good for infrequent tasks), and ‘do-confirm’, where people do the work from memory and then stop to confirm that every item was done (good for frequent tasks done by experienced teams). Most good checklists have five to nine items and fit on one page or screen.
The WHO Surgical Safety Checklist is the best-known example. It has three pause points — before induction of anaesthesia (‘sign in’), before skin incision (‘time out’) and before the patient leaves the operating room (‘sign out’) — and is read aloud by one team member while the team confirms each item. The checklist checks things that matter and are easily missed: the right patient, site and procedure; allergies; expected blood loss; antibiotic given; instruments and swabs counted; and the team introducing themselves by name and role.
Checklists fail when they are too long, include trivial items, are completed after the event or ticked by one person alone, or when the team sees them as paperwork. A supervisor can make them work: involve users in designing and testing them, explain why each item is there, make the pause point a real pause, and check from time to time that the checklist is being used as intended — out loud, at the right moment — not just that the boxes are ticked.
Key point: A checklist is a short list of critical, easily missed items used at a real pause point — read-do or do-confirm, ideally out loud.
Case study: the WHO Surgical Safety Checklist pilot (2007–2008). WHO’s ‘Safe Surgery Saves Lives’ programme tested the checklist in eight hospitals in eight countries, from high- to low-income settings. In the published evaluation (Haynes et al., New England Journal of Medicine, 2009), the rate of major complications fell from 11.0% to 7.0% and inpatient deaths from 1.5% to 0.8% after the checklist was introduced. The lesson for supervisors: a short, well-designed checklist used as a team routine can change outcomes — when it is actually used as intended.
4. Deviations and nonconforming output
A deviation is any departure from an approved procedure or specification. A planned deviation is decided in advance — for example a temporary change of supplier or method — and must be assessed for risk and approved before it happens, for a limited time or quantity. An unplanned deviation is discovered during or after the work: a step was missed, a parameter went out of range, the wrong version of a document was used. Both must be recorded. In pharmaceutical manufacturing, U.S. rules (21 CFR 211.100) require written procedures to be followed and documented, and any deviation to be recorded and justified.
When a procedure cannot be followed safely, the default is: stop, make the situation safe, and ask. Do not improvise on critical steps. If output may be affected — a product, a data set, a payment run, a patient sample — contain it. ISO 9001 (clause 8.7) requires nonconforming outputs to be identified and controlled to prevent unintended use or delivery, and dealt with by correction, segregation, containment, return or suspension, informing the customer, or obtaining authorised concession — with records of the nonconformity, actions taken, concessions and the authority who decided.
The supervisor’s job is to make it easy and safe to report deviations. People hide deviations when reporting leads to blame; then the same problem repeats and the record is wrong. Record facts quickly, take immediate containment action, notify the people who must decide (quality, the process owner, the customer where required), and feed the deviation into root-cause analysis and corrective action if it is significant or recurring. A pattern of small deviations usually means the procedure, the equipment or the planning needs to change.
Key point: Planned deviations are approved before; unplanned ones are recorded at once. Stop, make safe, contain affected output, report without blame.
5. Keeping procedures alive
Procedures decay. Equipment, software, materials, people and regulations change, and a procedure that was right two years ago may now be wrong. Set a review period appropriate to risk (often one to three years) and also review a procedure whenever something relevant changes, after an incident or deviation, and when users report a problem. A review should involve at least one experienced user and should check the procedure against the job as actually done, not only against the previous version.
Change control means no informal edits. A proposed change is written down with the reason, assessed for its effect (on safety, quality, other procedures, training, validation, data), approved by the right people, issued with a new version number and date, and communicated — with training where the change affects how people work. ISO 9001 requires that changes to documented information be controlled and that obsolete documents be prevented from unintended use. Marking what changed (‘revision bars’ or a change summary) helps users see what is new.
Finally, check at the workplace. A short regular observation — the supervisor watching a task with the procedure in hand, asking the person to talk through critical steps — finds gaps much earlier than an annual audit. Lean organisations call this going to the ‘gemba’, the place where work is done. Treat what you find as information: praise good practice, fix the procedure where it is wrong, coach where a person needs it, and escalate where resources or equipment prevent people from working to standard.
Key point: Review on a schedule and after changes or incidents, change only through change control, and check procedures in use at the workplace.
The full lesson, case studies, scenarios and templates continue in the interactive course on this page.
Sources and references
- Human factors: procedures
- ISO 9001:2015 Quality management systems — Requirements (catalogue) — clauses 7.5, 8.5.1 and 8.7
- Safe surgery: WHO Surgical Safety Checklist — tools and resources
- 21 CFR 211.100 — Written procedures; deviations
- Lean lexicon: standardized work
Professional education only, not an accredited qualification. Regulated sectors (pharmaceuticals, medical devices, aviation, nuclear, finance) have specific documentation and deviation rules; follow them and your quality system. ISO content is paraphrased from public catalogue pages.