All resourcesPractical guide

Training after a procedure change: evidence and rollout

Sending a revised procedure does not show who understood the change, what was checked or which document version applied. Connecting the change decision with each completion confirmation in a concise, repeatable record gives leaders a clearer starting point for explaining the new step and helping people apply it.

Author: Piotr Adamski · Updated:

A procedure change needs a controlled handover

A revised procedure changes work only when the people who perform that work know what changed and can apply it. A circulation email proves that a message was sent.

It does not establish that a substitute operator received the right version, that a night shift understood a new stop condition, or that a supervisor checked the result. The training record should connect those decisions so the supervisor can see who needs an explanation or a practical check without first chasing names across messages.

Identify the action that changed

ISO 10015 provides guidance on competence management and people development. It offers a useful foundation for treating training as a response to a defined need, followed by evaluation, rather than as an isolated event [1]. For workplace safety, the EU framework directive separately addresses appropriate training, including training connected with changed work or equipment [3]. These are different sources with different scopes. Neither means that a completion click automatically proves competence or satisfies every applicable obligation. Public APG competence guidance also distinguishes training participation from evidence of competence [2].

Start with one practical question: what must a person do differently after this release? If the owner cannot answer that question, a broad training assignment will probably produce activity without resolving the actual change. Identify the new decision, sequence, limit, responsibility or escalation route first. Then choose how to communicate and check it.

Define the affected population before sending invitations

Build the assignment list from tasks and exposure. Job titles can help, but they rarely describe the entire population. A person may cover another line, inspect the output, clean the equipment, authorise a restart or support production during a breakdown. Each of those duties can create a training need even when the person's usual title appears unrelated. Use the current roster and planned work as inputs. Include agency workers and contractors where the procedure applies to their work. Decide who is responsible for reaching them and checking completion. Do not assume that the contracting company has trained people on a site-specific change. Equally, do not collect training records for unrelated activities merely because a person entered the building.

Consider an illustrative example: a packaging instruction changes the response to an unreadable batch code. The affected population includes packaging operators, relief operators, quality inspectors and the people authorised to release held product. The warehouse team might need only the changed identification rule for held pallets. These are distinct learning objectives, so one identical course for everyone may be unnecessary. Record the selection rule and the date of the roster snapshot. If someone later asks why a person was included or excluded, the owner can explain the decision without reconstructing an old mailing list.

Turn the revision into observable learning objectives

A version comparison should identify operational differences, not just changed paragraphs. For each material difference, write the expected behaviour in plain language. For example: stop the line when the code cannot be verified; identify the affected batch; notify the named role; do not release product until the authorised decision is recorded. These objectives can be assessed directly. Choose evidence proportionate to the task. An administrative contact update may need acknowledgement. A changed inspection decision may need a scenario question. A new equipment setup can require supervised practice and observation. The document owner should explain the choice, particularly where a knowledge test is being used for a practical activity.

Avoid questions that reward memorising a heading while ignoring the changed action. Asking which department owns the instruction tells little about whether an operator will isolate affected product. A better question presents a realistic condition and asks what happens next. Include the important exception as well as the normal case. Training should also explain why the step exists. People faced with an unfamiliar condition need enough context to recognise that the standard instruction may not apply. They must know when to stop and ask, rather than improvise. Keep the explanation within the approved procedure; training is not an opportunity to create an unofficial second method.

Approve the source, material and questions as a connected release

Give the procedure a stable identifier and a release number. Give the training material and question set their own identifiable versions. Link them explicitly. A test result is meaningful only if the organisation can identify the instruction and assessment that produced it. Before publication, the accountable content owner should compare the material with the approved source. Check removed steps, changed limits, pictures, exceptional conditions and escalation contacts. If a summary omits a warning, a concise presentation has become a different instruction. If AI assists with drafting, a competent owner still needs to check each operational statement and question. A fluent explanation can contain a precise error.

Record who approved publication and when. Approval of the source does not automatically approve a later slide deck, translation or question set. Decide which material needs separate review and keep that decision visible. Reviewers should examine the languages employees will actually use, including units and technical terms. Once a release has completions against it, preserve it. A later correction should create a new material release rather than silently change what earlier participants supposedly read. Distinguish a correction that changes meaning from a minor presentation correction, and retain enough history to explain both.

Schedule training around the effective date

The procedure's effective date and the training deadline should support the same operational decision. If people must apply a new critical step from Monday, allowing them to finish training on Friday of that week leaves an avoidable gap. The process owner should determine whether training and any practical assessment must happen before independent work begins. Plan access during the actual working pattern. Night shifts, part-time employees, planned leave and workers without individual computers need an explicit arrangement. Provide a usable device and time where required. Moving the course to a browser removes one access barrier; it does not allocate time or replace supervisory responsibility.

Create a rule for late arrivals and people returning from absence. They should receive the current applicable requirement before performing affected work. If a person leaves before the change takes effect, keep the record of that scope decision instead of treating every incomplete assignment as an unexplained failure. Where a transition period is acceptable, define its boundaries: which activities may continue, under which instruction, with what supervision, and until when. An exception should have an owner and end condition. A list of overdue people is informative, but the operational control is the decision about what those people may do.

Check understanding and respond to unsuccessful attempts

Set the acceptance criterion before assignments begin. Explain what the assessment checks and what happens if the criterion is not met. Avoid adjusting a threshold after seeing inconvenient results unless the owner identifies and records a genuine flaw in the assessment. Otherwise the report becomes an exercise in making the numbers look comfortable. Keep attempt history. A failed first attempt followed by explanation and a successful repeat shows that a gap was detected and addressed. Replacing every attempt with the latest score removes that information. At the same time, access to detailed individual results should be limited to people who need them for the stated purpose.

Investigate patterns in wrong answers. If several experienced employees choose the same incorrect response, the problem might be an ambiguous question, a conflicting local instruction or an unclear change explanation. Use those patterns to guide a conversation with the team before attributing the result to carelessness. Inspect the source, material and working conditions together before deciding on another course. For practical work, record the additional observation separately. Identify the task, conditions, assessor, criterion and decision. A knowledge score can support that decision, but it should not be relabelled as observed skill. Where formal task authorisation is needed, preserve the authorisation decision and its scope.

Build a report that exposes the remaining work

A useful report starts with everyone who was required to complete the change response. It then shows assignments, completion, results, practical checks where applicable, overdue items and agreed exceptions. The denominator matters. A system can report full completion if the missing workers were never assigned in the first place. Make the material version and effective date visible. Show the report generation time and applied filters. A historical export represents a point in time; it should not be confused with today's operational view. Retain the underlying records so the export can be explained later.

Assign an owner to every unresolved item so the shift leader can act on a defined gap instead of asking everyone for a status update. The next action might be arranging access, correcting the roster, clarifying the material, performing a supervised check or deciding a task restriction. A reminder does not close the item. Closure requires the appropriate evidence or a documented change to the requirement. Review by shift and task as well as by overall percentage. An illustrative report with ninety-eight completions out of one hundred can look strong. If the two incomplete people are the only operators scheduled for the changed task tonight, the risk remains concentrated. Percentages need the context of planned work.

Verify the change at work and improve the next release

After implementation, inspect a small, relevant sample of work. Choose observations that test the changed action, especially stop conditions and exceptions. Record what was checked and the result. The purpose is to discover whether the handover worked, not to repeat the entire course without reason.

If problems remain, determine their cause. The instruction may be wrong, the equipment may make the intended action difficult, a local supervisor may still teach the old method, or the training may have missed an important scenario. More reminders will not repair a conflicting process. Correct the source of the gap and decide whether another targeted assignment is necessary.

Evaluate the evidence workflow

CrewShift can support procedure assignments, completion records, scores, history and exports. Create an account and evaluate those capabilities with one representative procedure change and the actual people responsible for the process. Check whether the record preserves the source, population, result and unresolved actions you need, and whether leaders can move from checking status to helping the people who need it. Do not infer practical competence, certification or legal compliance from a completed status.

The final handover should be easy to reconstruct: a defined change affected a defined population; approved material explained it; people completed the relevant checks; exceptions were resolved; and the owner verified implementation. That chain gives the next reviewer something concrete to assess and leaves the leader better prepared to discuss the work itself with the team.

Questions worth asking

Is a signed attendance sheet enough?

It confirms attendance but usually not the source version or understanding. Add the material version, result and assignment history.

Does every revision require complete retraining?

Not necessarily. Use the change impact to decide. A minor clarification may need a short acknowledgement; changed duties may require full material and a check.

What should happen when several people fail the same question?

Check the question, source and training explanation before repeating the course. A common wrong response can reveal ambiguous wording or conflicting local instructions.

Does the training deadline have to match the effective date?

The owner should decide what evidence is needed before the changed task is performed. Where a transition is acceptable, record its scope and controls rather than leaving an unexplained gap.

Sources and scope

  1. ISO 10015:2019 — competence management and people development
  2. ISO / IAF Auditing Practices Group — guidance on auditing competence (2015 edition context)
  3. EU-OSHA — OSH Framework Directive 89/391/EEC

This informational material does not replace licensed standards or individual legal advice.