Workflow

Flow 22 — Deviation, concession and waiver governance

Govern temporary permission against exact approved design, NCR and MRB sources with independent technical, configuration, conditional contract/safety and final QA authority, then verify every bounded use before closure.

Overview

Inventory meaning

Flow 22 records permission and verified application evidence only. It never approves or revises a baseline, dispositions or moves stock, replaces MRB or inspection authority, creates an audit, or sends a customer/regulatory message.

Responsible roles

Quality Engineer → different QA Head scope reviewer → different Product Engineer → different Configuration Manager plus conditional Project/Contract and Product Safety Managers → different QA final authoriser → Quality Engineer application recorder → separate QA verifier/closer → Auditor read-only

Process

1
Exact scope
Freeze approved design, NCR/MRB, validity, effectivity and controls.
Immutable permission draft
2
QA scope gate
Reject for replacement version or approve completeness independently.
No design or stock authority
3
Technical review
Product Engineering decides bounded technical acceptability.
Technical evidence only
4
Authority concurrence
Configuration plus declared contract and safety authorities decide.
Exact source snapshots
5
Final QA
A separate QA user activates only the fully approved version.
Permission active · custody unchanged
6
Use and closure
Record, verify and close every application independently.
Read-only permission history
READ ONLY

Role handoff

Detailed reference chapters

Deviation, concession and waiver governance Product configuration and released baselines Nonconformance and CAPA governance Controlled documents and evidence roles

Detailed steps

1
As Quality Engineer, open Quality → Deviations & concessions and create scope v1 against one exact approved item revision, released product baseline or active configuration item. A concession requires one exact same-site/classification NCR; any material effect requires a matching approved MRB; a waiver requires contract/customer review and cannot carry material disposition authority.
2
Submit v1. As a different QA Head, reject it and confirm it remains immutable. Create replacement v2, submit and independently approve scope completeness.
3
As a distinct Product Engineer, approve the technical basis. As separate Configuration Manager, approve the exact source. Add separate Project/Contract Manager and Product Safety Manager concurrence only when v2 declared those authorities required.
4
As a second QA Head distinct from the scope reviewer and all prior reviewers, record final authorisation. Confirm no role can skip an authority, self-review or authorise a rejected/incomplete version.
5
As Quality Engineer, record each bounded use within validity against its exact configuration, MRB execution, work order or inspection record and CLEAN evidence. As a separate QA Head, independently verify or reject each application.
6
Request closure only after at least one verified application and no pending verification. A separate QA Head may close acceptable/monitored residual risk but cannot approve unacceptable residual risk. Reconcile that configuration, inventory, ledger, audit and notification records did not change.

Field-by-field practice data

Use a disposable training tenant

Request a time-bounded training deviation against one exact released design source. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Authorised Quality or Engineering role

Create the deviation request

Open /quality/deviations

Select the exact source and bound dates/quantity before independent decisions.

Exact field name	Requirement	Sample value A	How to use it
Site	Select existing	`COM-01`	Select the governed site.
Case type	Required	`DEVIATION`	Use concession only for the approved use case.
Classification	Required	`RESTRICTED`	Match the design and evidence.
Title	Required	`TRAIN-A temporary bolt finish deviation`	Use a factual bounded title.
Request reason	Required	`Approved supplier finish unavailable; equivalent controlled finish proposed for training evaluation.`	State the operational need without presuming approval.
Exact design source type	Required	`ITEM_REVISION`	Select the applicable authoritative source type.
Approved/released source	Select existing	`TRAIN-A-BOLT-M8 rev A`	Select the exact source.
Valid from	Required	`2026-09-15`	Set the earliest allowed use.
Valid until	Required	`2026-10-15`	Use a bounded end date.
Quantity limit (optional)	Optional	`10`	Enter when the authority is quantity limited.

Expected result: Approval creates only the declared exception authority; application remains an exact attributable action.

End state

One closed temporary-permission case retains immutable source snapshots, rejected and authorised scope versions, separated technical/configuration/conditional authorities, independently verified applications and closure evidence without acquiring design-release, custody, MRB, inspection, audit or messaging authority.