Poka-Yoke Knowledge & Mistake-Proofing Project App

Learn the principles of mistake-proofing, distinguish prevention from detection and warning, explore practical manufacturing and service examples, evaluate solution concepts, and create a structured Poka-Yoke project with portable JSON save/load and a professional printable report.

Prevent mistakes becoming defects Structured project builder Verify controls under real operating conditions
3
Core methods: contact, fixed-value and motion-step
4
Control strength levels: eliminate, prevent, detect, warn
0%
Current project completeness
JSON / PDF
Portable project data and report output

What Poka-Yoke Means

Design the process so the correct action is natural and errors cannot escape.
Poka-Yoke is a mistake-proofing methodology that prevents an unintended human action, process condition or component selection from becoming a defect. The strongest controls remove the error opportunity entirely. When prevention is not practical, the process should detect the error immediately and stop, isolate or correct the condition before defective output progresses.

Mistake versus defect

A mistake is an unintended action or omission. A defect is the nonconforming output produced when the process permits that mistake to continue.

Example: Forgetting a fastener is the mistake; releasing an incomplete assembly is the defect.

Design over vigilance

Training, signs and attention are useful, but they are weaker than a physical, electronic or logical control that makes the wrong action impossible.

Example: A keyed connector is stronger than a label telling the operator which way to insert it.

Immediate containment

Where the error cannot be eliminated, detection should occur at source before value is added, the condition becomes hidden or the product leaves the station.

Example: A torque-controlled tool locks the station until every required joint reaches the approved window.

Hierarchy of Mistake-Proofing Strength

LevelPurposeTypical mechanismExampleRelative strength
EliminateRemove the error opportunity or unnecessary task.Process redesign, part simplification, automatic completion.Use one common fastener instead of two easily confused types.Strongest
PreventMake the incorrect action physically or logically impossible.Keying, locating pins, interlocks, software rules.A fixture accepts the component only in the correct orientation.Very strong
Detect and stopIdentify the error at source and stop progression.Sensors, counters, barcode checks, vision, torque monitoring.The cycle cannot close until all six fasteners are confirmed.Strong
WarnAlert a person and rely on a response.Lights, alarms, labels, prompts and checklists.An alarm sounds when the wrong programme is selected.Weakest

Core Principles

Three Classical Methods

Contact method

Checks a physical characteristic such as shape, size, colour, position or presence.

Example: An asymmetrical locating pin prevents a bracket being loaded backwards.

Fixed-value method

Checks that a specified number of actions, parts or operations has been completed.

Example: A fastener counter prevents job release until twelve installation cycles are recorded.

Motion-step method

Checks that required actions occur in the approved sequence.

Example: A machine requires load, clamp, guard closure and identification verification before cycle start.

Industry Examples

Aerospace fastener installation

Risk: wrong fastener type or missed installation.

Poka-Yoke: kitted fasteners, barcode verification, tool recipe control, fastener count and station lock until completion.

Verification: challenge with wrong part, duplicate scan, missed cycle and tool disconnect.

Special process recipe selection

Risk: incorrect heat-treatment, plating or cure programme.

Poka-Yoke: scan part and route card; PLC loads only the approved locked recipe; unauthorised recipes are unavailable.

Verification: challenge with an incompatible part number and expired approval.

Paint mixing

Risk: wrong ratio or omitted activator.

Poka-Yoke: keyed dispensing connections, gravimetric recipe control and container release only when the required ratio is achieved.

Verification: simulate underweight and overweight additions.

NDT reporting

Risk: missing coverage, expired certification or incomplete records.

Poka-Yoke: mandatory technique selection, personnel authorisation check, coverage checklist and blocked report approval until required evidence is attached.

Verification: attempt approval with missing zones and expired certification.

Assembly orientation

Risk: component fitted 180 degrees out.

Poka-Yoke: asymmetric feature, unequal locating pins or fixture nest matching only the correct orientation.

Verification: attempt incorrect loading using representative variation and worn fixtures.

Administrative data entry

Risk: invalid serial number, wrong revision or missed approval.

Poka-Yoke: controlled dropdowns, format validation, cross-record checks, mandatory approvals and role-based permissions.

Verification: invalid formats, duplicate serials, obsolete revisions and unauthorised users.

Important: colour coding, labels, training and checklists are useful supporting controls but normally remain dependent on human attention. Do not describe a warning-only control as prevention. Consider foreseeable bypass, maintenance failure, sensor drift, workarounds and new failure modes introduced by the device.

Poka-Yoke Solution Evaluation Matrix

Score concepts from 1 (poor) to 5 (excellent). Higher risk reduction, prevention strength, reliability and ease of use are better; lower cost and complexity receive higher scores.
ConceptControl levelRisk reductionReliabilityEase of useLow costLow complexityTotal
Add and score solution concepts to identify the strongest candidate.

Poka-Yoke Project Builder

Define phase
0% complete

Poka-Yoke Project Report

Generated from the project builder and solution matrix.
Complete the project builder and select Generate Report.