In the ideal manufacturing world, designs are frozen, tooling is perfect, and production runs exactly as planned. The reality is far messier. Customer requirements evolve. Engineering discovers a better solution. Raw material becomes unavailable. A tolerance proves impossible to hold. Errors in the original drawing surface. These realities drive one of the most common and potentially disruptive events in any custom manufacturing project: the revision and change order.
Handled poorly, change orders create chaos—missed deadlines, cost overruns, finger-pointing, and damaged relationships. Handled well, they become an opportunity to improve the product, strengthen the partnership, and demonstrate professionalism. This article provides a comprehensive framework for managing revisions and change orders smoothly, from initial request through implementation and documentation.
Why Change Orders Are Inevitable – And Why They Matter
Change orders are not a sign of failure. They are a normal part of product development and production. Common triggers include:
- Customer-driven changes: End-user feedback, new market requirements, regulatory updates.
- Design improvements: Engineering identifies a lighter, stronger, or more cost-effective geometry.
- Material substitutions: A specified alloy is on long lead time; an equivalent grade is proposed.
- Tolerance adjustments: A dimension that is unnecessarily tight is relaxed to improve yield and reduce cost.
- Error correction: Mistakes in the original drawing (e.g., missing threads, incorrect surface finish callout) are discovered.
- Process optimization: The supplier proposes a manufacturing change that reduces cost or lead time.
The goal is not to eliminate change orders—that is impossible. The goal is to manage them systematically so that all parties understand the impact on cost, schedule, and quality, and agree on the path forward before any work is done.
The Hidden Cost of Poor Change Management
When change orders are handled informally—via email, verbal conversations, or “we’ll figure it out later”—the consequences can be severe:
| Consequence | Typical Cost |
|---|---|
| Rejected parts due to miscommunication | Scrap cost + replacement production + expedited freight |
| Delayed production because the supplier was not informed | Idle labor + missed customer delivery + penalty fees |
| Disputes over cost with no documented agreement | Legal costs + damaged relationship |
| Duplicate or conflicting revisions causing rework | Engineering hours + machining time + material waste |
| Traceability gaps for regulated industries (medical, aerospace) | Regulatory finding + remediation + potential product recall |
A documented, disciplined change management process is not bureaucracy—it is risk management.
The Core Principle: No Work Without Written Authorization
The single most important rule of change management is:
No changes shall be implemented without a written, agreed-upon change order signed by both parties.
Verbal instructions, instant messages, or “I told the shipping guy” are not authorization. If it is not documented, it did not happen. This protects both the buyer and the supplier.
Step‑by‑Step Change Order Process
A robust change management process has five distinct phases.
Phase 1: Initiation – Requesting the Change
The process begins when a need for a change is identified. This can come from the buyer (customer) or the supplier.
For customer‑initiated changes: The buyer submits a formal Engineering Change Request (ECR) or Change Order (CO) document. At a minimum, it should include:
- A unique change order number (sequential, easy to reference).
- The original part number and drawing revision.
- A clear description of the proposed change (text and/or marked-up drawing).
- The reason for the change.
- Required effective date (when the change must be implemented).
For supplier‑initiated changes: The supplier submits a Deviation Request or Process Change Notice. This might propose:
- An alternative material (e.g., 4140 instead of 4340).
- A different manufacturing process (e.g., casting instead of machining).
- A change to inspection or testing method.
The supplier should not implement the change without customer approval.
Best practice: Use a standard template for change requests. This reduces ambiguity and ensures all necessary information is captured.
Phase 2: Impact Assessment – Understanding the Consequences
Once a change request is received, both parties must evaluate its impact on:
- Cost: Will the change increase or decrease per‑part price? Will there be one‑time charges (tooling, programming, requalification testing)?
- Schedule: How much additional lead time is required? Will the change cause a production gap or require re‑sequencing of orders?
- Quality: Does the change affect critical characteristics? Will it require new inspection methods, additional testing, or re‑validation (e.g., PPAP resubmission)?
- Tooling: Does the change require new fixtures, dies, or molds? Can existing tooling be modified?
- Inventory: What happens to work‑in‑process and finished goods that do not yet incorporate the change?
- Regulatory: For medical or aerospace parts, does the change trigger regulatory notification or re‑certification?
The supplier provides a formal Impact Statement or Quotation for Change, including revised unit price, tooling charges, and new lead time. The buyer reviews the impact against their own constraints (customer deadlines, budget, inventory levels).
Example – Simple Change: Adding a chamfer to a drilled hole.
- Cost impact: Minimal (additional deburring step).
- Schedule impact: None (can be done within existing cycle time).
- Tooling: No new tooling.
- Inventory: Parts already machined without chamfer can be used as‑is (if chamfer is not critical).
Example – Major Change: Changing material from 6061 aluminum to 7075.
- Cost impact: Material cost increase of ~40%.
- Schedule impact: New material must be sourced (2‑week delay).
- Tooling: Same tools may work, but speeds/feeds need re‑optimization.
- Inventory: All existing 6061 parts become obsolete if the change is retroactive.
Phase 3: Approval – Formal Authorization
After impact assessment, the change request is either approved, rejected, or conditionally approved.
- Approved as proposed: Both parties sign the change order. The supplier proceeds.
- Rejected: The request is denied. Reasons are documented. The original specification stands.
- Conditionally approved: Approval with modifications (e.g., “approved but with lower quantity” or “approved only for future orders, not current WIP”).
Critical document: The Change Order Authorization (COA) is a signed agreement that references the original contract/purchase order and explicitly states the changes to cost, schedule, and specifications. It should include a line: “All other terms and conditions remain unchanged.”
Both parties should retain a signed copy. For electronic signatures, use a system that provides audit trails (e.g., DocuSign, Adobe Sign).
Phase 4: Implementation – Executing the Change
Once authorized, the change is implemented according to the agreed timeline.
Key implementation actions:
- Update engineering documents: Revise the drawing (increase revision letter), update the CAD model, and modify any technical specifications.
- Communicate to production: The supplier’s manufacturing team receives updated work instructions, tooling, and inspection plans. Obsolete documentation is removed from the floor.
- Manage inventory: Determine disposition of existing WIP and finished goods:
- Rework to meet new spec (if feasible).
- Use‑as‑is with customer waiver.
- Scrap or sell as spare parts.
- Update quality documentation: Revise control plans, inspection checklists, and FAI reports.
- Notify sub‑tier suppliers: If the change affects raw material or outsourced processes (plating, heat treat), pass the change down with appropriate flow‑down requirements.
Traceability: For safety‑critical components, it is essential to mark which parts conform to which revision. This can be done via batch numbers, date codes, or physical marking on the part.
Phase 5: Verification and Closure – Closing the Loop
After the first production run with the change, verify that the change was implemented correctly:
- Inspect the first articles against the new drawing.
- Document any discrepancies and resolve them with the supplier.
- Update the baseline for future orders (revision level becomes the new standard).
- Close the change order in your system, marking it as “Completed.”
If the change required requalification (e.g., new PPAP submission), ensure those documents are received and approved.
Best Practices for Smooth Change Management
1. Use a Change Management System (CMS)
Spreadsheets and email threads are error‑prone. Implement a simple CMS (even within your ERP or a dedicated tool like Arena PLM, Siemens Teamcenter, or a cloud‑based platform like Zoho or Monday.com) to:
- Assign unique change order numbers.
- Track status (draft, impact assessment, approved, implemented, closed).
- Store supporting documents (drawings, quotes, emails).
- Provide audit trail for compliance.
2. Establish a Change Control Board (CCB)
For large or complex projects, create a CCB with representatives from engineering, quality, procurement, and production. The CCB reviews change requests, assesses cross‑functional impact, and approves or rejects changes. This prevents unilateral decisions that ignore downstream effects.
3. Define Tiered Approval Levels
Not every change requires the same level of scrutiny. Define thresholds:
| Change Type | Example | Approval Authority |
|---|---|---|
| Minor (no cost/schedule impact) | Clarifying a note on drawing | Supplier quality engineer |
| Moderate (<5% cost or <1 week schedule) | Adding a surface finish callout | Buyer’s engineer + supplier PM |
| Major (>5% cost or >1 week schedule) | Material substitution, tolerance change | CCB or senior management |
4. Communicate Proactively, Not Retroactively
If you anticipate a change, alert the supplier as early as possible—even before the formal change order is drafted. They may be able to pause work or adjust material orders, saving waste. Surprise change orders create friction; early communication builds goodwill.
5. Build Contingency into Contracts
In your master supply agreement, include a clause governing change orders. Specify:
- That no change is binding unless in writing.
- How cost and schedule impacts will be calculated.
- A maximum response time for impact assessment (e.g., 5 business days).
- That both parties will act in good faith to minimize disruption.
6. Train Your Team and Your Supplier’s Team
Change management fails when people do not follow the process. Provide training to:
- Your buyers, engineers, and quality staff on how to submit and approve changes.
- Your supplier’s sales, engineering, and production staff on how to process and implement changes.
Consistent training reduces errors and speeds up the change cycle.
Handling Revisions in Different Scenarios
Scenario 1: Early in Development (Prototype to Pilot)
Revisions are frequent and expected. Manage them with:
- Version control of CAD files (v1, v2, v3) rather than formal change orders for every tweak.
- Change logs that document what changed and why.
- Batch control: Limit pilot runs to small quantities so that changes can be absorbed without large scrap.
Scenario 2: During Ongoing Production
Revisions are disruptive and costly. To minimize impact:
- Accumulate minor changes: Instead of issuing a change order every week, batch non‑urgent changes and release them quarterly.
- Use “cut‑in” dates: Specify that the change applies to all parts produced after a certain date, while existing stock can be used.
- Implement rolling change: For very long production runs, the change can be phased in gradually.
Scenario 3: Supplier‑Initiated Changes
Suppliers may propose changes to improve yield, reduce cost, or address material availability. Treat these as collaborative opportunities:
- Request a trial run to validate the change before full implementation.
- Share savings through a gainsharing arrangement (e.g., 50% of documented cost reduction returned to the supplier).
- Update the quality agreement to reflect the new process.
Scenario 4: Emergencies (Stop‑Ship, Safety Issue)
If a change is required immediately due to a safety or regulatory issue:
- Verbal approval may be necessary to stop production, but follow up with a written change order within 24 hours.
- Isolate affected parts and conduct root cause analysis.
- Document the emergency change in your system with full traceability.
Documentation and Traceability
In regulated industries (aerospace, medical, automotive safety), change orders are auditable records. Maintain:
- Complete change history for each part number, including all approved and rejected changes.
- Reason for the change clearly stated (e.g., “improve fatigue life,” “obsolete material”).
- Approval signatures with dates.
- Disposition of affected material (rework, scrap, use‑as‑is).
Use a Revision Table on your engineering drawing to list each revision, date, description, and approver. This provides a quick reference for anyone reviewing the drawing.
Real‑World Example: A Change Order Gone Right
Situation: A manufacturer of hydraulic cylinders discovered that the specified O‑ring groove dimensions, while theoretically correct, caused assembly difficulty and occasional seal damage. The supplier proposed a change to the groove depth (0.2mm deeper) based on their experience.
Process:
- Supplier submitted a Deviation Request with a marked‑up drawing.
- Buyer’s engineering team assessed impact: Cost increase negligible; schedule: no impact; quality: improved seal life.
- Buyer approved a trial run of 100 parts with the new groove.
- Trial parts assembled easily; no leaks in pressure test.
- Formal Change Order signed to update the drawing revision.
- All existing inventory of the old groove was reworked using a modified tool.
- Documentation updated in the quality system.
Outcome: Assembly time reduced 15%, field seal failures dropped to zero. The supplier’s proactive suggestion strengthened the relationship.
Common Pitfalls and How to Avoid Them
| Pitfall | Why It Happens | Solution |
|---|---|---|
| Verbal change orders | Urgency or casual communication | “No work without written CO” policy; follow‑up email confirming any verbal instruction |
| Incomplete impact assessment | Rushing to approve | Use a standard impact checklist; require supplier to quote all affected costs |
| Disconnected documentation | Different teams use different systems | Centralized change log; integration between PLM, ERP, and supplier portal |
| No approval authority defined | Confusion over who can approve | Document approval matrix in the supply agreement |
| Failure to update sub‑suppliers | Supplier forgets to flow down change | Make subcontractor approval part of the change order checklist |
| Lost revision history | Poor record keeping | Use PLM or a shared cloud folder with read‑only archive |
Conclusion: Change Is Inevitable – Chaos Is Optional
Revisions and change orders will always be part of custom manufacturing. They are not a sign of failure but a reflection of real‑world product evolution. The difference between a smooth, professional process and a painful, costly one lies entirely in the systems and disciplines you put in place.
By establishing clear written processes, using structured documentation, communicating proactively, and respecting the impact on both parties, you can turn change orders from a source of friction into a routine, manageable, and even value‑adding activity.
Remember the golden rule: No work without written authorization. Protect your project, your budget, and your relationships by making change management a core competency, not an afterthought.
