Standard Work Changes: Trial, Approve and Train Before Rollout

An approved instruction can still leave two methods on the floor

The day shift receives a revised work instruction. The night shift still uses a laminated copy from the previous month. Both teams believe they are following the standard, and both can point to a document with an approval signature.

This is a release problem. The improved method has reached the master file but has not reached every place where work happens. A short trial may have shown that the change can work. It has not shown that both shifts are ready to use it.

Standard work change control connects a new method with its use on the factory floor. Trial evidence, the approved instruction and training should all describe the same work. A long procedure cannot make that happen by itself. A clear one-page method with sound records may serve the team better than ten pages that nobody can find or apply.

The fictional example below concerns bundle identity at the handover from cutting to sewing. It follows a change from revision B to revision C across two shifts. Its counts, release rules and review periods are examples to adapt, not universal factory requirements.

Separate the work standard from the record of its use

A work standard describes the current agreed method and the conditions in which it applies. A completed record shows what happened when someone used that method. These serve different purposes.

The instruction might tell the receiving handler to check the bundle identity before signing for receipt. The handover record names the actual bundle, receiver and result. Editing the instruction does not alter those past events. Nor does a signature prove that the method itself is suitable for the task.

Lean uses “standardized work” in a more specific sense. The Lean Enterprise Institute links it to takt time, work sequence and the standard inventory needed for the process. It also describes work standards and job instruction sheets as related aids. A factory should not use these terms as if every form were the same thing.

The handover example needs three linked items: a work instruction, a revised handover form and a short training breakdown. The team must also check for changes to staffing, work sequence or allowed work in process. All these parts need to agree before the method is released.

ISO 10013:2021 gives guidance on developing and maintaining documented information. Its public scope says this should suit the organisation's needs. That supports a package sized to the task. The fields below are an original factory example; ISO does not prescribe this form.

Describe the failure before proposing the new method

In the fictional factory, the sending team checks bundle tickets under revision B. The receiving team then signs the delivery sheet. Yet B leaves a key point unclear: when must the receiver compare the ticket with the planned order? One person signs to confirm that a trolley arrived. Another thinks the signature confirms a bundle identity check.

Name the gap in the problem statement. “Improve bundle control” gives the team little direction. A clearer statement would be: “The receiver can sign for receipt before checking the required bundle identifiers.” This says which decision needs to change and where it occurs.

Revision C proposes a defined receiving check before the acknowledgment. It names the relevant order, style revision, size, bundle number and shade-group record where applicable. It also tells the handler what to do when the information does not agree.

The sender's check remains part of the route. The team is clarifying the receiving decision, not treating the new signature as a substitute for every earlier control. If shade identity is involved, the method must remain consistent with the factory's approved shade process. ApparelDiary's fabric shade segregation guide explains that wider material-control context.

Talk through the proposed change with the people who send and receive bundles. They may reveal that the receiving desk cannot see the full ticket or that the order list is not available at night. Those are design inputs, not excuses to be dismissed after rollout.

Define the scope of the trial and the release

A change record should make clear where revision C will apply. It may cover one product family, one handover route or a named group of workstations. A successful test at one desk does not automatically establish suitability for every site.

Record the current revision, proposed revision, reason and method owner. Then name the affected documents, people, equipment and records. A form change may also require a change in an electronic field or a printed ticket.

For the example, the trial covers the cutting-to-sewing handover on both shifts. It uses the existing ticket identifiers and an agreed receiving-check field. It does not introduce a new product specification or authorise staff to change a shade grouping.

The owner should also state what would stop the trial. Unclear bundle identity, a missing required record or a conflict with an approved quality rule needs a defined response. A trial label does not permit work to bypass an existing release hold.

ASQ's PDCA guide describes a small test, a review of the results and wider use of what was learned. These are separate decisions. First, the factory needs evidence that people can use the proposed method. It can then plan training and withdrawal of the old instruction.

Review the work with the people who perform it

The trial should expose the ordinary conditions of use. Watch how the handler finds the correct order, compares the ticket, records the result and deals with a mismatch. Ask the person to explain the reason for each decision.

The HSE's guidance on procedures supports walking through tasks with users and choosing a format suited to the task. It also warns that procedures do not replace competence or act as the sole defence against hazards. A signed sheet cannot repair a poorly designed task.

If a ticket is difficult to read, simply adding “read carefully” leaves the problem in place. The team may need to change its position, print quality or access to the reference record. That change should be tested with actual users, including the night shift.

The trial report should state which conditions made the method work. It may need a certain ticket layout, a working terminal or a trained support person. Keep those conditions in the release plan unless further evidence shows that the method works without them.

This review also looks for unwanted effects. An extra check could create a queue at the receiving point. A new field could invite workers to copy a result without making the check. Observe the actual sequence rather than judging the method only from a neat completed form.

Turn the trial result into a clear instruction

The revised instruction needs enough detail to reproduce the decision. Use the names and identifiers workers see at the workplace. “Verify traceability compliance” gives less help than naming the records to compare and the response to a mismatch.

For the bundle example, start by saying when the task begins and which identities must match. Then explain when the receiver may sign for receipt. Give a clear route for a mismatch, and state what evidence marks a completed check.

Keep the action and its reason close together. Explain how the check keeps a wrong size or shade group out of the line. That gives the worker a reason to question an unusual case. The reason should be concrete, not a slogan about quality.

The table is a content guide, not the complete operating instruction. Exact identifiers and hold arrangements must match the factory's system. Avoid making up a universal colour code or assuming that every site uses the same ticket fields.

Translations and visual aids belong to the same revision. If the English text changes but a translated copy does not, the factory has released two methods under one label. Have someone who understands both the task and the language check the changed meaning.

Approve the whole change package

An approval should name the items reviewed and the people responsible. Production might confirm the work sequence while quality checks the identity controls. The training lead could check that the method can be taught. Assign these roles through the factory's own authority structure.

The decision should cover the linked form and any system field as well as the instruction. Otherwise, workers may learn a new method but find that the old form has no place to record it.

Where the method changes work content, review its time basis too. An extra receiving check may require more work than the previous task. Adding a step can change the time needed for the job. Review that effect before keeping the old time allowance. ApparelDiary's SMV calculation guide explains why a time standard needs a defined method and basis.

For a quality system tied to a named standard, record the applicable edition. ISO now identifies ISO 9001:2026 as its current edition. An older implementation guide should not be presented as proof of meeting a new requirement. Check the factory's applicable obligations and transition arrangements when making a compliance decision.

Approval of revision C means the method is accepted for its stated scope. It does not mean every shift has received it, every person has practised it or every old copy has been withdrawn. Those are release conditions that still need evidence.

Teach the changed decision, then observe its use

Reading the new text aloud is not enough to establish readiness. The trainer should show the revised sequence, explain the key points and let the worker try it. Include the mismatch route as well as a normal handover.

NIST's Training Within Industry guide sets out four steps. The trainer prepares, shows the work, lets the learner try and follows up. Here, the check is whether a person can use revision C in the planned setting. Attendance alone cannot answer that question.

The trainer can use one valid bundle record and one deliberately prepared training mismatch. Training examples must be clearly separated from live goods and records. A learner should not create a false live receipt just to complete a practice exercise.

Ask the worker to explain when receipt can be acknowledged and what prevents it. Observe the action in the order it will happen on the floor. If the person needs more support, record that need and arrange another attempt.

The extent of the check should match the change and its consequences. A wording correction may need a different response from a new quality decision. Do not make every revision a full retraining course, but do not treat a meaningful method change as a notice-board update.

Read the rollout counts without hiding the gaps

Suppose twenty-four people are assigned to the affected work, twelve on each shift. The day shift has briefed all twelve, and eleven have demonstrated the changed method. The night shift has briefed ten, and seven have demonstrated it.

Briefing coverage is 22 ÷ 24 × 100 = 91.7%, rounded to one decimal place. Confirmed demonstration coverage is 18 ÷ 24 × 100 = 75.0%. Six assigned people still lack confirmed readiness: four need follow-up and two have not been briefed.

The overall figure also hides the shift difference. Day-shift demonstration coverage is 11 ÷ 12 = 91.7%; night-shift coverage is 7 ÷ 12 = 58.3%. A single 75% badge would not tell the release owner where support is needed.

These are rollout counts, not a statistical measure of everyone's future performance. The factory must either finish the missing preparation or narrow the release to work covered by ready staff. Any staffing change must still cover the actual tasks, breaks and handovers. A high attendance percentage does not fill a specific gap on the night shift.

Make the point of use ready for the same revision

List the places where the old method can still direct work. In the example, there are six workstation holders, two dispatch desks and one training board: nine controlled locations. A master-file update does not automatically update those locations.

Suppose eight now display revision C but the training board still shows B. Copy replacement is 8 ÷ 9 × 100 = 88.9%. The missing location matters even though it does not handle production directly. A trainer could use it to teach the old sequence again.

The release check should confirm the content as well as the revision label. A page marked C with an old translated step is not a complete replacement. Check that workers can read the current copy from their normal position and can reach the supporting records.

Digital instructions need the same care. Test the link using the access available at the workstation. A correct document in a manager's account is of little use if the operator sees an old download or cannot open the page.

Retain an approved fallback where offline work is needed. Identify its revision, owner and conditions of use. Workers need a valid route when the system is down. They should not have to rebuild the method from memory or choose between old files.

Choose a cutover rule for work already in process

Set a release boundary that people can apply to the goods as well as the documents. “From tomorrow” may leave a night shift unsure which rule to use. It also says little about bundles already moving between departments.

Assume revision C applies to receipts acknowledged after the stated cutover time. At that point, the example has eighty-four bundles in the affected flow. Fifty-two have already been received under the valid revision B method. Twenty are in transit, while twelve are ready at the sending point.

The count reconciles: 52 + 20 + 12 = 84 bundles. The twenty in transit still need a receipt check, as do the twelve awaiting dispatch. Those 32 bundles will use revision C when they reach the receiving point.

Do not rewrite the fifty-two completed records to make them appear to have used C. Their history belongs to the method valid when the work occurred. The reason for the change may also raise concerns about earlier receipts. If so, the owner must assess those goods and records separately.

Identify the thirty-two bundles that will cross the boundary. Their receipt status, ticket version and receiving instruction must agree. A bundle count does not establish a garment count unless its actual quantities are known, so keep the unit explicit.

Both shifts need the same cutover rule. Tell the sender which receipt evidence the new method needs. Show the receiver how to handle a bundle prepared under the earlier method. Walking through that case can reveal a gap that the written rule did not make clear.

Withdraw old working copies without erasing history

Remove revision B from places where it could still be used as the current method. That includes loose photocopies, saved local files, training folders and old links. Keep the approved historical version in an archive with its period of validity.

The archive serves a different purpose from a workstation copy. It lets the factory understand which method applied to a past record. Access and labels should make that purpose clear so that a search result does not send an old instruction back into use.

The withdrawal check should name who confirmed each location. “Email sent to all supervisors” proves that a message was sent. It does not prove that nine physical locations now contain the right method.

New employees and returning workers also need the current route. An old lesson in the training system can teach revision B again, even after the floor copies have changed. Update the training source and its links before closing the change.

Follow the released method across both shifts

After release, observe whether the agreed sequence is being used and whether it produces the intended evidence. Separate method use from product acceptance. A correctly completed handover check can still find a bundle that must be held.

Suppose the owner makes thirty scheduled observations on each shift. The day shift follows the changed sequence in twenty-nine observations; the night shift does so in twenty-three. Across both shifts, 52 of 60 observations follow the method, or 86.7%.

That leaves eight observed departures: one on days and seven on nights. Look into those cases. The 86.7% result describes the sixty observations made here. The checks were not designed as a sample that represents the whole factory, so they cannot establish its overall rate of compliance.

Look at what caused the departures. The night shift may lack access to the order list, or the wording may leave a decision unclear. A person may need coaching. These causes call for different actions, so do not label all eight cases “operator error” before checking the conditions.

Also watch for new queues, repeated record corrections or duplicate acknowledgments. A change that fixes one ambiguity may reveal another. Retain the evidence and decide whether the method needs adjustment, the resources need support or the rollout needs more time.

Keep a controlled route back when the change cannot work

The release owner should know what happens if revision C cannot be used. A hold may be needed. In other cases, an approved temporary method or a previously tested method may be suitable. The reason for the failure should guide that choice.

Returning to revision B is not automatically safe or acceptable. If B was withdrawn because it failed an essential control, reusing it could restore the same risk. The decision needs the relevant technical authority and an assessment of affected goods.

A temporary instruction needs a scope, owner, expiry or review point, and a clear link to the permanent method. Otherwise, a short exception can become an unrecorded third version of the job.

Close the change once the release conditions are met and someone owns each follow-up action. Keep the trial result, approval, training evidence, copy checks and cutover record together. The next team can then see which method applies and why it changed. It should not have to settle competing memories of how the job used to work.

References

• Lean Enterprise Institute: standardized work and related work standards and instruction sheets.

• ISO 10013:2021: public scope for guidance on documented information.

• ASQ: Plan-Do-Check-Act and the move from a small test to wider change.

• HSE: procedure design, user involvement and competence.

• NIST MEP: Training Within Industry and job instruction.

• ISO: current ISO 9001:2026 edition and public transition information.