Conformance is demonstrated at the point of work through observation, records and credible handling of deviations.
Training attendance proves that an event occurred; it does not show that a person can carry out an approved method under actual operating conditions. Likewise, a signed procedure may be poorly understood, inaccessible or contradicted by production targets. A sound check connects the current authorized method, competence, observed work, records and exception management. The approach should be respectful and representative, helping leaders distinguish knowledge gaps from impractical process design.
A practical assessment begins by separating what the organization claims should happen from what a relevant employee or transaction can demonstrate. Decision rights, acceptance criteria, exceptions and retained evidence form the bridge between management system language and dependable operations. The approaches below are editorial recommendations for implementation; the applicable published standards and binding obligations remain the governing references.
Define the exact method and critical step
Before observing employees, identify the currently approved instruction and the actions that actually protect the outcome. Some steps are administrative preferences while others are essential acceptance or safety gates.
Assurance checkpoint. Check the method revision, its owner and whether operators can retrieve it at the workplace without informal copies. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
The auditor and process owner need agreement on which steps protect the outcome. A trivial formatting difference should not receive the same attention as a missing release gate. A sample taken from routine work can establish what happened in that context; it should not automatically be generalized to every product, shift or location. Record what remains unknown before changing the risk classification.
Choose representative work and conditions
A planned audit visit can create rehearsed behaviour. Select transactions across shifts, product variants, workload peaks and handoff interfaces without compromising safety or disrupting critical operations.
Sampling cannot cover every transaction. Acknowledge limitations and focus on combinations of shifts and conditions most likely to reveal material weaknesses. Where practice and written expectation differ, examine whether the deviation was an authorized adaptation or evidence that resources, design or competence are inadequate. These two explanations require different management decisions.
Source record test. Document sampling rationale, observed task and the circumstances that might affect whether findings generalize. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
Observe without coaching or changing the process
Observation is most useful when the worker performs the normal sequence. Ask clarifying questions after the step and distinguish a harmless ordering difference from an omitted protective barrier.
Decision evidence. Record what occurred, where a deviation began and the applicable instruction, rather than relying on a tick box assessment alone. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
Non punitive observation increases information quality. If workers fear blame, the audit may record a performance staged for inspectors rather than actual practice. Set a measurable acceptance condition before approving a solution. Otherwise completion will be reported when an action is entered in the tracker rather than when reliable operational control is demonstrated.
| Sampling perspective | Key question | Evidence |
|---|---|---|
| Method availability | Can the worker reach current instructions? | Current displayed revision |
| Observed performance | Are key controls actually performed? | Direct observation and time stamped outcome |
| Exception response | What happens when a step cannot be done? | Deviation authorization and follow up |
Compare the action with its retained record
A completed record can be backfilled, cloned or generated automatically without the underlying control occurring. Compare timestamps, equipment logs, IDs, approvals and physical outcomes where independent evidence is available.
Data integrity checks should be proportional and specific. Cross checking all records manually creates effort but not necessarily stronger assurance. Evaluate the actual handoff between roles and systems. Interfaces are where responsibilities become ambiguous, information is lost and an apparently satisfactory local decision can create downstream exposure.
Field verification. Trace the chosen transaction from work activity to the record and investigate contradictory or implausible timestamps. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
Explore competence and practicality together
If staff misunderstand a requirement, targeted coaching may be justified; if the method cannot be followed with available tools or staffing, rewriting the training slide will not fix the design.
Operational challenge. Ask the worker to explain the purpose of the control and ask the owner how deviations are raised and resourced. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
Some “training failures” are actually designs that conflict with production reality. Examine whether resources and authority support the instruction before requiring retraining. Evidence needs provenance as well as content: A retained document, log or observation must identify the relevant operating period, object and accountable person. Contradictions deserve examination rather than quiet reconciliation.
Test the escalation and exception path
The approved method should describe what to do when data, equipment or authority are unavailable. A process that works only during normal conditions may need an accepted temporary control mechanism.
A well defined exception route prevents improvisation. Make deviations visible and let staff stop or contain output without needing to conceal delays. A representative exception should inform the response, with its limits disclosed. The objective is a proportionate conclusion that a second independent reviewer could test, not a compelling anecdote selected after the fact.
Exception sample. Sample a relevant abnormal event and verify stop work, containment, approval and subsequent reconciliation decisions. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
Verify sustained adoption, not a single demonstration
An auditor observed successful transaction proves limited conformance at that moment. Repeat sampling under independent conditions and review trends to decide whether corrective work was effective.
Effectiveness review. Schedule an ordinary later sample after supervision returns to normal, then record acceptance and remaining uncertainties. The line supervisor should be able to relate the evidence to a specific work instruction, its decision authority and the original acceptance criteria.
A later verification should be performed without special preparation. Its value lies in discovering whether the method has become routine across responsible staff. Follow up must address whether the controlled process changed after the decision. If later samples do not support the intended benefit, review the treatment and remaining exposure rather than simply extending the closure date.
From Assessed Practice to Reliable Control
The next management decision should identify one materially significant control described in this article, the responsible process owner, its current operating evidence and the conditions under which the conclusion would be reconsidered. A plan to improve documentation is useful when it enables consistent work; it is not a substitute for the actual work, decision or result.
Treat the resulting assessment as a starting point for responsible verification. Select representative normal and exceptional transactions, compare their outcomes with the intended criteria, agree proportionate action and review later evidence. Strong management systems preserve this chain even when personnel, sites, technology or business priorities change.