Manufacturing Decision Record: Capture Rationale and Review Triggers

A manufacturing decision record preserves the problem, alternatives, evidence, chosen option, rationale and conditions that would reopen the decision. Attach it to the affected work so an informal agreement can be understood and reviewed by the next person.

A production lead and quality lead settle a priority outside a meeting. By the next shift, the chosen action is known but its limits are missing. Someone treats a one-day arrangement as a permanent rule.

The conversation may have been useful. Preserve enough of the reasoning for another person to act within the same conditions.

Choose the decisions that need a record

Start when a choice changes another team’s work, consumes constrained capacity or relies on an assumption likely to change. Routine actions already governed by an approved instruction do not need a second essay. Link the instruction or approval instead.

NASA’s decision-analysis guidance documents alternatives, criteria, assumptions and the final rationale. The short factory record below applies those basic documentation principles to an operational choice. It is our own worksheet, not a NASA compliance process.

Keep the choice and its reason together

The person coordinating the decision drafts the note. The decision owner confirms the rationale; affected teams acknowledge the action. If a technical approval is required, link that separate approval. A well-written note does not grant someone authority they do not hold.

Work through an inspection-capacity choice

Illustrative scenario: orders A and B need 90 and 60 minutes of final inspection. The available qualified inspection slot has 120 minutes. Both cannot fit: 90 + 60 = 150 minutes, leaving a 30-minute capacity gap.

The team considers A first, B first, or an additional approved inspection slot. Customer A has confirmed a collection time; customer B has agreed to the following morning. The authorised planner selects A first and reserves B for the next qualified slot. Quality retains the full inspection requirements for both orders.

The note records the two customer confirmations, capacity source and next slot. It also states when to reopen the choice: A is not ready at the agreed cut-off, the inspector becomes unavailable, or B’s accepted delivery arrangement changes. The owner must then reassess the options. Splitting or shortening a required inspection is not an implied fourth option.

Preserve disagreements and changed assumptions

If maintenance disputes the available time, record the disputed assumption and assign a person to resolve it. Mark a provisional choice as provisional. When the uncertainty blocks safe or authorised execution, keep the affected action on hold under the applicable procedure.

When a later decision supersedes the first, retain both versions and link them. The earlier note explains why the team acted as it did with the information available. Editing it to look prescient destroys that explanation. Keep confidential commercial detail available only to the roles that need it; the execution team still needs a clear permitted action.

Check that the next shift can use it

Before closing the note, ask the receiving supervisor to identify the chosen option, affected orders, expiry or review trigger and escalation owner. All four should be answerable from the record. At the review date, compare the observed result with the intended outcome and resolve outstanding actions.

Useful review measures include decisions awaiting acknowledgement, decisions past their review time and superseded instructions still in use. Count these consistently before trying to reduce them. The aim is a traceable decision, not a longer meeting.

Attach the rationale to work in Optiwise

Our no-code modules support configurable forms, related records and role-based form access. Configure a decision note that links to its orders, evidence and follow-up work. Keep the normal approval rules alongside it so rationale and permission remain clear.

Decision-record questions

Does every conversation need a decision note?

No. Record consequential choices that affect execution or need later review. Link existing instructions for routine actions and avoid duplicating their content.

What if the decision changes before everyone acknowledges it?

Mark the earlier instruction as superseded, issue the new version and identify anyone who may have acted on the first. Reconcile their work before closing the change.

Bring one recurring cross-team decision to an Optiwise demo and we can map its evidence, owner and review trigger.