29 Sep Deviation Request
A capsule house supplier deviation request register records a proposed departure from an approved requirement before the supplier implements it. The register keeps the source requirement, proposed alternative, evidence, impact review and authorized disposition connected.
Submitting or receiving a request does not approve it. The governing agreement, approved specifications and named technical and commercial authorities determine whether a deviation may proceed.
Reference the Exact Requirement
Record the drawing, specification, schedule or purchase-order clause and its revision. Quote or summarize the affected requirement accurately. Identify the unit, quantity or batch in scope rather than applying the request to the entire project by assumption.
Structure the Request
| Field | Record | Review question |
|---|---|---|
| Requirement | Controlled source and revision | Is the baseline unambiguous? |
| Departure | Proposed difference and affected scope | Is the change stated factually? |
| Reason | Supplier explanation and assumptions | Are claims supported? |
| Impact | Technical, commercial, schedule and document effects | Were qualified reviewers assigned? |
| Disposition | Open, returned, rejected or authorized | Is authority recorded? |
Keep Work on the Approved Baseline
Unless the authorized project process says otherwise, a pending request should not be treated as permission to manufacture, substitute or ship. Record any hold point and notify affected teams through the controlled channel.
Close the Decision Trail
Preserve reviewer comments, conditions, evidence and final decision. If authorized, update the affected controlled documents. If rejected, confirm that the approved baseline remains in force and that obsolete proposal copies are identifiable.
Use the design change log for approved baseline changes and the corrective action response log for documented findings. To discuss configuration and supplier records, contact Rovellc.