Deviations and concessions
Govern a time- and scope-bounded deviation, concession or waiver against one exact approved design/configuration source and verify each authorised application.
Screen orientation
Deviation permissions, site and clearance apply. Quality authors scope; QA, Product Engineering, Configuration, conditional Contract/Product Safety and final QA authorities decide independently.
The editor freezes source, validity, risk and evidence. The record then displays ordered authority reviews, active applications, independent verification and closure history.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Site · Case type · Classification | Selects | Required. | Choose the owning site, DEVIATION/CONCESSION/WAIVER type and handling level. | Sets authority, source and visibility rules. |
| Title · Request reason | Text | Required. | State the bounded request and technical reason. | Freezes the attributable request. |
| Exact design source type · Approved/released source | Selects | Required. | Pin one approved item revision, released baseline or active configuration item. | Creates the immutable design-source snapshot. |
| Exact approved MRB | Select | Required for material-effect deviation/concession. | Choose only the matching approved same-site/classification MRB. | Pins material authority without executing it. |
| Valid from · Valid until · Quantity limit (optional) | Validity controls | Dates required; quantity only when the authorisation is quantity-bounded. | Set the exact permitted window and ceiling. | Constrains later applications. |
| Immutable scope evidence | Controlled evidence | Required. | Select CLEAN evidence for the current immutable version. | Pins scope evidence. |
| Decision · Residual risk · Follow-up reference · Decision evidence | Review controls | Required according to authority stage and decision. | Record the exact decision, remaining risk and follow-up. | Creates attributable authority evidence. |
| Affected object type · Affected object UUID (optional) · Affected reference | Application identity | Required according to authoritative route. | Identify the exact use without inventing a source UUID for a manual route. | Scopes one application fact. |
| Authoritative route · Exact source UUID · Source reference | Application source | Required according to route. | Select a matching authoritative record or retain an explicit external reference. | Pins the application evidence source. |
| Applied on · Application result · Application evidence | Application outcome | Required. | Record when and how the authorised use was applied with CLEAN evidence. | Creates the immutable application fact. |
Actions and effects
When to use: When one exact design source needs bounded permission.
What it does: Creates an immutable draft/successor and preserves rejected history.
When to use: In the required QA, technical, configuration and conditional authority order.
What it does: Records concurrence; it does not modify the source or MRB.
When to use: By a different QA actor after all required authorities approve.
What it does: Activates only the frozen scope.
When to use: During validity, then by a separate QA verifier.
What it does: Retains one exact use and verification without executing its source-domain work.
Lists and states
- Deviation/concession register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
The case governs permission evidence only. It cannot release a baseline, execute MRB, disposition inspection, create maintenance work, move custody, change stock or send a message.