1.0 Why changes get missed
The change is controlled. The consequences usually are not.
Engineering change control is normally solid at the point of receipt: the revision is logged, effectivity is set, the drawing is updated in the system. What is rarely resourced is the second question — which of our documents just became wrong?
That question takes an hour of engineering time that nobody has during a change, so it gets deferred. The Control Plan still calls out the old tolerance. The PFMEA still analyzes an operation that moved. The work instruction still shows the previous fixture. None of it surfaces until an audit, a customer review, or a part built to superseded documentation.
A small, recurring service by design
This is deliberately scoped as a low-cost review you can run on every significant change rather than a project you commission after something goes wrong. Manufacturers with frequent change activity usually fold it into a monthly agreement.
- Deliverable
- Impact assessment listing affected documents and sections, with a prioritized revision plan
- Typical inputs
- The change notice and both drawing revisions, current documentation set, effectivity and disposition information
- Formats
- Standalone assessment, or written into your change-control or engineering-change form
- Starting price
- $500 per review
- Scales with
- Extent of the change, number of parts affected, size of the documentation set
- Optional
- Execution of the resulting revisions, quoted separately or covered by a monthly agreement
- Cadence
- Per change, or standing coverage of all changes under a monthly agreement
2.0 Impact
What a change can reach
| Document | How the change reaches it |
|---|---|
| Process Flow | Operations added, removed, resequenced, combined or moved to an outside processor; new interfaces created. |
| PFMEA | New failure modes introduced, existing ones invalidated, severity changed by a new effect, controls no longer applicable. |
| Control Plan | Characteristics added or removed, tolerances changed, methods no longer capable, frequencies no longer justified. |
| Inspection Plans | New characteristics to verify, changed acceptance criteria, methods that no longer resolve the tolerance, altered datum schemes. |
| Work Instructions | Changed sequence, tooling, parameters or acceptance; photographs that now show the wrong configuration. |
| Special Characteristics | Designations added or removed, or a feature becoming critical because its function changed. |
| Measurement requirements | Gauges no longer adequate, new fixturing needed, calibration or capability implications. |
| Reaction plans | Containment boundaries change when the affected feature or its effect changes. |
| Production-readiness documentation | Readiness status reopened for the affected area; open actions created or invalidated. |
3.0 Method
How the review runs
Intake
The change notice, both revisions and the effectivity are established, along with what is already in production or in stock.
Delta analysis
What actually changed — feature, tolerance, material, process, note, specification reference — stated precisely rather than as “drawing updated”.
Document impact mapping
Each delta is mapped to the documents and sections it affects, with the specific rows or steps identified.
Risk delta
Whether the change introduces new risk, removes existing risk, or invalidates a control the PFMEA relied on.
Revision plan
Priority and sequence, since some revisions depend on others, plus what must be complete before the next production run.
Execution
AiroQue revises the documents you assign, or your team does and AiroQue verifies the result.
Processed through your change control
The assessment is meant to enter your existing change process, not sit beside it. AiroQue writes it into the form your process already uses wherever one exists.
Your change forms
Findings written into your engineering-change, deviation or document-change form so the record lives where your auditors expect to find it.
Effectivity handling
Assessment states what applies to product in process, in stock, at outside processing and already shipped, using your effectivity conventions.
Notification requirements
Where a contract requires customer notification or approval before the change is implemented, the assessment flags it explicitly.
Standing coverage
For manufacturers with high change volume, a standing arrangement where every change notice is reviewed on receipt under a monthly agreement.
4.0 Adjacent services
What usually follows
Send a change notice and both revisions
AiroQue will return the affected-document list and a revision plan, then quote only the revisions you want executed.