Template

Standard Work Template + Rapid Test Plan

A practical, fill-ready standard work template with a simple rapid test plan, training & skill-check checklist, and governance guidance to turn observed best practice into a verified, trainable, and maintainable standard.

Purpose

This template helps teams capture a repeatable, tested standard work sequence and run a short rapid test to validate, train, and iterate the standard on the shop floor. Use it to reduce variation, speed onboarding, and create clear visual signals while preserving frontline input.

How to use this template

  1. Observe and document current best practice using the fields below.
  2. Run the Rapid Test Plan with a small team, capture feedback, and record iterations.
  3. Complete quick skill checks and sign-off before publishing the standard to your control board or knowledge base.
  4. Set review cadence and triggers to keep the standard current and relevant.

Template fields (copy these into your document or digital form)

Process name — Short, consistent name used in workflows and visual boards. (Example: "Box Sealing — Line 2")

Purpose — Why this process exists and the outcome it must deliver. (Example: "Seal cartons to prevent damage during transport and ensure weight remains within spec.")

Takt time / Target cycle time — Customer-driven rhythm or cycle time target (if applicable). (Example: "45 seconds / unit")

Scope / Start & End — Where the standard starts and stops; boundaries and handoffs. (Example: "Start: operator places empty carton on conveyor. End: sealed carton exits inspection station.")

Sequence of steps — Numbered step-by-step actions. For each step include: operator action, observable criteria (what correct looks like), time expectation, and photo or short video link. Example format:

  1. Step 1 — Inspect carton for damage. Observable: no tears; action time: <5s; photo: link.
  2. Step 2 — Insert product and align to center. Observable: product centered within 5mm; tool: alignment jig.
  3. Step 3 — Apply adhesive tape twice across seam. Observable: tape fully covers seam with no gaps.

Key quality checks — Critical inspections, measurement points, and defect thresholds (include frequency). (Example: "Visual seal check every 10th unit; failure = visible gap >2mm.")

Required tools, PPE, and materials — List model numbers, settings, and any consumables.

Safety notes / hazards — Known hazards, lockout/tagout needs, ergonomics tips.

Training checklist / Skill checks — Short observable tests the operator must pass (see Training section below).

Visual controls & job aids — Location of shadow boards, labels, process map, floor markings, and images used at the point of work.

Revision history — Date, author, change summary, and approval initials.

Standard owner — Role or person responsible for updates and reviews.

Storage / Reference — Where the master file, videos, and change log are stored (intranet path, document ID, or system link).

Rapid Test Plan (use for quick PDCA)

Run a short, focused test to validate the draft standard before wider rollout.

Objective — What the test must demonstrate. (Example: "Operators can complete the sealed-carton process within takt time with no more than 2% defects over 50 units.")

Hypothesis — A concise testable statement. (Example: "If operators follow the new alignment jig step, center alignment defects will drop by 75%.")

Test steps — Who will run the test, when, and how many units or cycles to run. Include data collection method (paper log, tablet, or video timestamp).

Success criteria — Quantitative and qualitative pass/fail rules. Examples:

  • Quantitative: ≤2% defect rate over 50 consecutive units.
  • Qualitative: Operators report the steps are clear and have no safety concerns.
  • Time: Average cycle time ≤ takt + 10%.

Feedback capture — A simple form or notes area for operator comments, observed obstacles, and improvement ideas. Include timestamps or video clips linked to specific steps.

Iteration log — Record each change, why it was made, who approved it, and results of the next mini-test. Example entry format: Date | Change | Rationale | Tester | Result | Approval.

Sign-off — Operator representative, supervisor, quality, and process owner signatures (or initials) to publish the standard.

Training & Skill-check checklist (practical, observable)

  1. Explain: Trainer demonstrates the full sequence, calls out key quality checks (trainer demonstrates twice).
  2. Observe: Trainee performs each step while trainer observes, with trainer prompting if safety risk exists.
  3. Skill-check: Trainee completes full cycle without prompting for N consecutive units (N = 3–5 depending on risk).
  4. Quality verification: At least one measured sample meets key quality checks (e.g., no visible gap, torque within spec).
  5. Sign-off: Trainer initials the training checklist and records date and employee ID.

Practical tips for video & visual evidence

  • Record short clips (10–30s) that show the operator’s hands and the work outcome; avoid long unedited footage.
  • Use timestamps and short captions to link video to specific step numbers in the standard.
  • Keep videos under a shared path or embed thumbnails in the standard for quick access at the workstation.

Visual management examples

  • Use a one-page job card posted at the workstation with step photos and the top 3 quality checks.
  • Color-code tools and fixture locations with shadow boards and labeled outlines.
  • Place a simple red/green cue (or a yes/no puck) at the end of the line to quickly show pass/fail status of the last inspected unit.

Governance: keep standards alive (avoid the Mal Hunger)

Standardization can become stale or heavy. Use these rules to keep standards useful and current:

  • Local ownership: Assign a clear standard owner with the mandate and time to keep the document current.
  • Review cadence: Quick review every 90 days for active processes; immediate review after a quality, safety, or performance incident.
  • Frontline feedback channel: Provide an easy, recognized mechanism for operators to propose improvements (e.g., a simple feedback box, digital form, or brief huddle entry).
  • Keep it lean: Prefer short job cards and photos over lengthy manuals. Reserve detailed procedures for high-risk tasks.
  • Version control: Always record change date, author, reason, and quick summary in the revision history field.

Acceptance criteria for publishing a standard

  • Rapid Test met the success criteria (quantitative and qualitative).
  • At least one operator has passed the skill-check and signed the training checklist.
  • Standard owner and quality or safety representative have signed off.
  • Visual job aid is posted at the workstation and linked to the master file (video/photos available).

Example quick filled summary (for illustration)

Process: Box Sealing — Line 2

Purpose: Prevent damage during transport; target defect rate <2%.

Takt: 45s

Key steps: Inspect carton → Insert and center product → Apply tape twice → Visual seal check.

Skill-check: Operator completes 3 consecutive units within takt and passes visual seal check.

Owner: Line 2 Supervisor — review every 90 days.

When to adapt rather than standardize

If frontline operators repeatedly propose improvements that improve quality or safety, treat the standard as a living hypothesis: test the change with the same Rapid Test Plan and update the standard if results are favorable. Avoid enforcing a document that demonstrably reduces performance or morale.

Links & attachments

Attach or link to:

  • Short videos or annotated photos for each critical step
  • Tool specifications and settings
  • Quality inspection templates and defect examples

Template: Revision log (copy into your record)

Please record entries as: Date | Change summary | Author | Tester | Result | Approval initials

If you’d like, this template can be converted into an interactive form that collects test results, stores revision history, and saves training sign-offs to the organizational record. See Capability Enhancements below for recommendations.

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.