Managing Revision Chaos on Custom Orders

Every shop knows the drill: a customer sends an RFQ, you quote it, they approve, then the revisions start. A hole moves 2 mm. The material changes from 6061 to 7075. A chamfer becomes a countersink. By the time the job hits the floor, nobody is sure which drawing is current, the quote no longer matches the part, and the schedule has slipped.

Revision chaos is one of the biggest silent margin killers in digital manufacturing. It doesn’t show up as a line item on a P&L, but it eats capacity, creates scrap, and frustrates customers who expected faster turnaround. The good news? It’s solvable with a lightweight process — not more bureaucracy, but clear rules of engagement.

Why Revisions Spiral Out of Control

Most shops don’t have a revision problem because they lack discipline. They have one because the handoff between sales, estimating, and production is informal. Common failure points:

• No single source of truth. The quote references Rev A, the customer emailed Rev B, and the programmer is looking at a STEP file from last week.
• Verbal or email-only changes. A quick Slack message or phone call updates the spec but never hits the quote or the traveler.
• No change freeze point. Customers assume they can tweak until parts ship. Shops assume the quote locks the spec. Neither is written down.
• Version control lives in the CAD system, not the quote. Engineering sees Rev C; the shop floor sees the PDF attached to the PO.

These gaps let small changes compound into big problems: wrong material ordered, incorrect tool paths cut, inspection failures, and expedite fees that wipe out profit.

Establish a Revision Protocol

You don’t need PLM software to fix this. You need a protocol that everyone — sales, estimating, programming, quality, and the customer — follows. Three pillars:

1. Quote Locks the Baseline

When a quote is sent, it references a specific revision (drawing, STEP, PDF, BOM). That revision becomes the baseline. Any change after quote delivery is a revision request, not a clarification. Make this explicit in your quote terms: “Quote is based on Rev X dated Y. Changes after quote issuance may affect price and lead time.”

2. Single Change Channel

Route all revision requests through one channel — a form, a portal, or a dedicated email alias. No verbal changes, no side emails to the estimator. Every request gets a ticket number, a description, the affected revision, and the requested new revision. This creates an audit trail and forces the customer to articulate the change clearly.

3. Impact Assessment Before Commitment

Before you say “yes” to a revision, assess: Does it change material, machining time, fixturing, inspection, or outsourcing? Update the quote (or issue a change order) and get written approval before the job moves to programming or production. No exceptions for “small” changes — a 2 mm hole move can scrap a $5,000 part if the fixture is already cut.

Version Control That Works on the Shop Floor

The protocol only works if the right revision reaches the machine. Practical steps:

• Attach the approved revision to the work order/traveler. Not a link — the actual PDF or STEP file. Programmers and operators shouldn’t hunt for files.
• Stamp the revision on every document. Setup sheets, inspection plans, router cards — all show the same rev letter/number.
• Use a revision table in the quote. List each revision, date, description, and price/lead-time impact. Share this with the customer so they see the accumulating cost of changes.
• Archive superseded revisions. Keep them accessible (customers ask for old versions), but mark them clearly so nobody runs an old program by mistake.

If your MES or shop management system can enforce revision attachment at each workflow step, use it. If not, a disciplined manual check at programming and first-article inspection catches 90% of mismatches.

Communicate the Cost of Change

Customers don’t revise maliciously — they revise because they can, and they don’t see the downstream impact. Make it visible:

• Show the revised quote side-by-side with the original. Highlight delta in price and days.
• Explain the why: “Moving this hole requires a new fixture ($800) and adds 2 days to lead time.”
• Offer alternatives: “If the hole location is flexible, we can hold the original fixture and save you $800 and 2 days.”

When customers see the trade-off, they often withdraw or simplify the request. You protect margin; they get parts faster. Win-win.

Handle the “Urgent” Revision

Sometimes a revision truly is urgent — a field failure, a regulatory change, a customer’s customer moved a deadline. Have an expedited path:

1. Customer submits via the change channel with “URGENT” flag.
2. Estimator/production lead does a 30-minute impact assessment (not a full re-quote).
3. You communicate: “We can do this. Price impact: $X. Lead time impact: Y days. Need approval by [time] to keep schedule.”
4. Written approval (email reply is fine) before work starts.

The key: same process, compressed timeline. No skipping the impact assessment or the approval.

Measure Revision Health

Track a few metrics to know if your protocol is working:

• Revisions per job. Target: < 1.5 for standard work.
• Quote-to-production revision delta. How often does the production revision differ from the quoted revision? Target: zero.
• Revision cycle time. Average time from request to approved change order. Shrink this.
• Revenue from change orders. Should be positive — you’re getting paid for the extra work.

Review monthly. If revisions per job creep up, your quote process may be accepting incomplete specs. Tighten the intake checklist.

Conclusion

Revision chaos isn’t inevitable — it’s a process gap. Quote a locked baseline, route changes through one channel, assess impact before committing, and make the current revision unmissable on the shop floor. Your programmers stop guessing, your inspectors stop failing parts on old specs, and your customers get predictable lead times.

Solvi’s quoting engine attaches the exact revision to every quote and work order, so the spec that won the job is the spec that runs on the machine. See how it works.