Standard Work Template + Training & Verification Checklist

A complete, practical standard work template with clear fields, example phrasing, a built-in training session plan, competency verification steps, a weekly verification (audit) checklist, and a simple revision log. Includes guidance to keep standards current and owned at the team level.

Standard Work Template — Purpose & How to use this template

This template helps teams capture the best-known safe and efficient method for a task, teach it consistently, and verify competence over time. Use it as a living document: assign an owner, test the steps on the floor, run short training sessions, collect verification sign-offs, and schedule regular reviews to keep the standard up to date.

Header (document control)

  • Title: [Task Name]
  • Process/Area: [e.g., Packaging Line 2]
  • Document ID / Version: [e.g., SW-PL2-001 v01]
  • Owner: [Name / Role]
  • Created: [YYYY-MM-DD]
  • Next review: [YYYY-MM-DD]
  • Approved by: [Name / Role]

Purpose & Scope

Purpose: A short statement describing why this standard exists (safety, quality, throughput, repeatability). Example: "Ensure consistent, correct setup and operation of the shrink-wrap station to meet quality and safety requirements."

Scope: Which operators, shifts, equipment, and product variants the standard covers.

Prerequisites & Materials

  • Required tools and PPE (list specific items)
  • Required materials / consumables
  • Required training or certifications before performing this work
  • Key safety permits or LOTO steps (if applicable)

Step-by-step Standard Work

For each step include: Step number, Who, Action, Expected time (takt or standard time), Visual reference, Safety / quality checks, Acceptance criteria.

  1. Step 1 — [Short Title]
    Who: [Role]
    Action: [Concrete, observable verb-first description of what to do]
    Standard time: [e.g., 00:01:30]
    Visual reference: [Photo filename or link / sketch ID]
    Safety / Quality checks: [e.g., ensure guard closed; no visible damage]
    Acceptance criteria: [What must be true to consider the step correctly completed]
  2. Step 2 — [Short Title]
    ...
  3. Continue until task complete.

Tip: Keep steps short and observable. If a step takes more than 2–3 minutes, consider breaking it into sub-steps or noting decision points.

Safety & Quality Checks (required checks per cycle)

  • List mandatory inspections before, during, and after the task.
  • Include tolerances, torque values, sensor readings, or example defect photos when possible.

Visual References

Attach or link to clear, annotated photos, diagrams, or short video clips showing correct setup, common mistakes, and acceptance examples. Example filenames: "SW-PL2-001_Setup.jpg" and "SW-PL2-001_Defect01.jpg".

Skills Matrix

Use this to map roles to required skill levels and training status.

  • Role: [Operator A] — Required level: Competent / Qualified / Trainer
  • Role: [Operator B] — Training required: Basic machine operation

Training Session Plan

Short plan to teach the standard to a new operator or to retrain an existing operator.

  1. Introduction (5 min): Explain purpose, safety risks, and outcomes.
  2. Demonstration (10–15 min): Trainer performs the task at normal speed, narrating key points.
  3. Guided practice (15–30 min): Trainee performs steps with trainer coaching.
  4. Independent practice (10–20 min): Trainee performs task alone while being observed.
  5. Competency check & sign-off (see below).

Competency Check (Training & Verification)

Define pass/fail criteria tied to acceptance criteria in the steps. Require at least one supervised successful run plus a separate verification run where the trainee meets all acceptance criteria.

  • Trainee name: _____________________
  • Date: _____________________
  • Trainer: _____________________
  • Observed runs: [number]
  • Outcome: Pass / Needs coaching / Fail
  • Notes: [space for coach to record deviations or coaching points]
  • Signatures: Trainer ________ & Trainee ________

Quick Weekly Verification (Audit) Checklist

Purpose: Fast confirmation that the standard is being followed and remains accurate. Use a short checklist during a weekly walk.

  1. Is the latest version of the standard posted at the work area? (Yes / No)
  2. Are visual references (photos, labels) present and legible? (Yes / No)
  3. Observed operator follows the documented start-up steps? (Yes / No / N/A)
  4. Critical safety checks performed as documented? (Yes / No)
  5. Any deviations noted? If yes, describe and tag as potential improvement.
  6. Last competency verification date for operators on shift: [date]
  7. Weekly verifier name & signature: ____________________

Record any observed deviations with photos and route to the owner for rapid correction or improvement planning.

Metrics & Acceptance

List 2–3 measures that indicate the standard is delivering value (examples):

  • Process defect rate (defects per 1,000 units)
  • First-pass yield
  • Average setup time vs standard time

Define responsibility for tracking each metric and review cadence (e.g., shift daily board, weekly CI huddle).

Revision Log (example entries)

  1. v01 — 2025-02-01 — Initial release — Owner Name
  2. v02 — 2025-03-15 — Updated step 4 to add torque spec after field test — Owner Name

Keeping Standard Work Living (avoid common mal-hungers)

Standards fail when they are paperwork only. Keep this living by:

  • Assigning a named owner responsible for continuous improvements and reviews.
  • Scheduling quick weekly verifications and a monthly review cadence with frontline representation.
  • Encouraging frontline change proposals: small experiments should be trialed, documented, and if successful, incorporated into the standard.
  • Using photos and short video clips so the standard is easy to follow for new hires.
  • Making acceptance criteria objective and observable to reduce interpretation drift.

Quick Copy Checklist — Before publishing or using

  • Does each step have a clear owner and acceptance criteria?
  • Are safety & quality checks explicit and visible?
  • Are visual references attached and labeled?
  • Is there a training plan and competency sign-off section?
  • Is document control (owner, version, review date) present?

Example file & naming guidance

Store the file where teams look for work instructions. Use a consistent file name pattern: [Area]_[Task]_[DocID]_vXX (e.g., PL2_ShrinkWrap_SW-PL2-001_v02.pdf).

Notes for adopters

Tailor the template to local terminology and regulatory needs. Keep it short and focused on observable behavior. If digital tools are available, consider capturing training sign-offs and weekly verifications electronically to build searchable competency and audit history.


Discussion

Comments and conversation will live here.