CONTEXT(CLONE)
Sign in

Trace failure modes through control plan to work instructions

For: Quality engineer or process engineer preparing for a customer or certification audit

Pattern: Hierarchical decompositionNeeds live modelsDesigned for 12 to 300 agents
Get early accessSign in to use

The pain today

The process failure analysis lists controls, the control plan should carry them, and the work instructions should tell the operator how. After years of changes the chain breaks in places, and auditors find the breaks first.

The ask

“I attached our process failure mode analyses, control plans and work instructions for these lines. For each failure mode, follow its prevention and detection controls into the control plan and then into the work instruction for that step. List every control that is missing, worded differently or has a different frequency downstream.”

Plain words, as you would say it to a colleague. Edit it to fit your case before you send it.

What you attach or connect

  • Process failure mode and effects analyses as text
  • Control plans
  • Work instructions per process step
  • Process flow with step identifiers

The unit of work

One worker task per one control traced across three documents.

Why a swarm fits

The structure is a tree: line, process step, failure mode, control. A leaf needs three short excerpts. Steps are independent, so leaves run in parallel and roll up per line.

Not for

Judging whether the risk ranking or the chosen control is adequate. One line with a handful of steps is quicker by hand.

The decision tree

6 typed decisions, each with an action for every answer

At fixed moments in a run, the engine puts one narrow question to a decision model. The decision model never writes text: it answers yes or no with a probability, picks from listed options, or gives a score, about a small slice of the material. The engine then does exactly what this tree says, which is what makes the run auditable. The thresholds are the template's design values, not measured results.

  1. Planner, while planning

    Split or keep serialYes or no, with a probability

    While planning

    Do the three document sets for this line use step identifiers that can be aligned one to one?

    Sees only: The step lists of the analysis, control plan and instruction index for one line

    Why: Tracing starts only where steps align; unaligned steps are reported first.

    • Yes: 0.60 or higherthenSplit the work
    • Unsure: 0.40 up to 0.60thenKeep serial
    • No: below 0.40thenKeep serial

  2. Split or keep serialYes or no, with a probability

    While planning

    Does this process step list more than one prevention or detection control in the failure analysis?

    Sees only: The failure analysis rows for one process step

    Why: Splits a step into per-control leaves only when there is more than one control to follow.

    • Yes: 0.60 or higherthenSplit the work
    • Unsure: 0.40 up to 0.60thenKeep serial
    • No: below 0.40thenKeep serial

  3. After workers, the judge checks

    Evidence checkA choice among options

    After a worker answers

    Does the control plan row for this step contain the control named in the failure analysis?

    Sees only: One control from the analysis and the control plan rows for that step

    Why: Shows where a control promised in the analysis never reached the plan.

    • Same control, same methodthenAccept
    • Same characteristic, different method or gaugethenMark unresolved
    • Not in the control planthenMark unresolved

  4. Evidence checkYes or no, with a probability

    After a worker answers

    Does the work instruction state the same check frequency and sample quantity as the quoted control plan row?

    Sees only: One control plan row and the matching instruction passage

    Why: Finds controls whose frequency was loosened on the way to the operator.

    • Yes: 0.85 or higherthenAccept
    • Unsure: 0.50 up to 0.85thenEscalate to a strong model
    • No: below 0.50thenReject and retry

  5. Evidence checkYes or no, with a probability

    After a worker answers

    Does the work instruction passage tell the operator what to do on a failed check, as the control plan's reaction plan column requires?

    Sees only: The reaction plan cell and the instruction passage for one control

    Why: A control without a stated reaction is a common audit finding and is easy to miss.

    • Yes: 0.85 or higherthenAccept
    • Unsure: 0.50 up to 0.85thenEscalate to a strong model
    • No: below 0.50thenReject and retry

  6. Accountable person, before anything is settled

    Person decidesYes or no, with a probability

    Before anything is reported as settled

    Is the broken or weakened control tied to a characteristic marked special, safety or regulatory in the failure analysis?

    Sees only: One trace break with the analysis row's classification column

    Why: The process owner and quality engineer decide every change to a control.

    Accountable: The process owner and the quality engineer own every change to a control and the release of revised documents.

    • Yes: 0.40 or higherthenAsk a person
    • Unsure: 0.15 up to 0.40thenAsk a person
    • No: below 0.15thenAccept

The fleet: who does what

Model tiers by role, not brands: you choose the models. Strong reasoning models plan and reconcile, small fast models do the wide work, and the judge is a decision model from a different family, so it does not share the workers' blind spots.

  1. Planner

    A strong reasoning model aligns step identifiers across the three document sets and builds the tree of controls.

    Decisions here:1. Split or keep serial2. Split or keep serial

  2. Workers

    Small fast workers from an open-weight family trace one control from the analysis to the control plan to the instruction.

    Designed for 12 to 300 agents, one worker task per one control traced across three documents. Each worker receives only its own unit.

  3. Judge, from a different model family

    A decision model from a different family decides whether downstream wording is the same control or a weaker one.

    Decisions here:3. Evidence check4. Evidence check5. Evidence check

  4. Reconciler

    A strong reasoning model rolls breaks up per step and line and keeps cases where equivalence is arguable.

  5. Accountable person

    The process owner and the quality engineer own every change to a control and the release of revised documents.

    Decisions here:6. Person decides

Checked before anything is accepted

  • Each break quotes the control in all documents where it appears
  • Frequencies, sample sizes and reaction plans are compared as stated
  • Steps that cannot be aligned across documents are reported before tracing

What comes back

  • Trace table of controls across the three documents
  • Missing or weakened controls per process step
  • Steps with unaligned identifiers
  • Line-level status map

What to measure

  • Breaks confirmed by the process engineer
  • Audit findings on lines already traced
  • Engineer hours per line
  • Cost per control traced

Names of measures only. No result is claimed for this template.

Templates open in the workspace chat with the ask filled in. Nothing runs until you send it.

Get early accessSign in to use

More in Manufacturing and quality

Find recurring causes across non-conformance reports

For: Quality manager or continuous improvement lead across several plants or lines

Non-conformance reports are written by many people in free text.

Pattern: Map, verify, reduceNeeds scale6 decisionsDesigned for 40 to 500 agents