Quoting Setup Changes Mid-Run

Mid-run setup changes are a silent margin killer. A customer calls at 2 PM requesting a tolerance tweak on the next 50 parts. The machine stops, the operator re-fixtures, the programmer adjusts the CAM, and the inspector re-checks first articles. Meanwhile, the clock keeps running on a job quoted for a single setup.

Most shops absorb this cost because they don’t have a clean way to quote it after the fact. The result? Erosion that compounds across every disrupted run. Here’s how to build a quoting process that captures mid-run setup changes — before they hit the shop floor or after they’ve already happened.

Why Mid-Run Changes Break Standard Quotes

Standard quotes assume one setup, one program, one inspection plan per operation. A mid-run change violates all three:

• Machine downtime — stopping, re-fixtureing, re-zeroing, tool changes
• Programming time — CAM edits, post-processor updates, verification
• Inspection reset — new first-article, updated CMM routines, revised documentation
• Material risk — scrapped parts from transition, potential mix-ups
• Scheduling ripple — downstream jobs delayed, capacity shifted

None of these appear in a typical per-part or per-hour quote. They’re treated as “part of the job” — which is exactly why they disappear into overhead.

Classify the Change Before You Price It

Not all mid-run changes are equal. Build a simple classification so your team (and the customer) knows what they’re buying:

Attach a minimum charge to each class. Class 1 might be 30 minutes engineering time. Class 3 starts at 4 hours including fixture rebuild and FAI. Publish this schedule so customers see it upfront — not on an invoice surprise.

Track Actuals Against the Quote

You can’t improve what you don’t measure. Every mid-run change should generate a discrete work order or task code linked to the original job. Capture:

• Machine idle time (spindle stopped, operator active)
• Programming/engineering hours
• Fixture/modification labor and materials
• Inspection time (CMM, hand tools, documentation)
• Scrap/transition parts
• Schedule impact (hours/days pushed to next job)

Review these monthly. If Class 2 changes average 2.3 hours but you’re charging for 1, adjust the minimum. If Class 4 changes always pull in outside processing, bake that markup into the base rate.

Quote the Change in Real Time

The best time to quote a mid-run change is before the machine stops. Equip your floor leads with a tablet or phone linked to your quoting system. When a change request comes in:

1. Identify the change class
2. Pull the standard minimum for that class
3. Add any unique material/tooling/fixture costs
4. Send the change order to the customer for digital approval
5. Log the approval timestamp — work resumes only after sign-off

This turns a disruptive “can you just…” into a billable change order with a paper trail. No more “I thought that was included” conversations at month-end.

Build Mid-Run Change Logic Into Your Quote Engine

If your quoting software treats every job as a clean sheet, you’ll keep manually patching change orders. Look for (or build) a quote engine that lets you:

• Define setup change classes with default time/markup values
• Apply change-order templates to active jobs
• Track cumulative change impact on job margin in real time
• Generate customer-facing change orders with one click

Solvi’s instant quoting engine supports customizable change-order workflows tied to your process definitions — so mid-run disruptions get priced consistently, whether you’re quoting a new RFQ or managing an active job. See how it works at solvi.io.

Communicate the Policy Before the First Part Ships

No pricing structure survives a customer who doesn’t know it exists. Include a “Mid-Run Changes” clause in your terms or quote cover page:

• Definition of change classes and minimums
• Approval process (email, portal, verbal with written confirmation)
• Payment terms for change orders (net-15, prepaid, added to job invoice)
• Schedule impact disclaimer

Review it at kickoff. When the first “quick tweak” request arrives at 2 PM, you’re not negotiating — you’re executing a defined process.

Conclusion

Mid-run setup changes aren’t going away. Customers will always find something to adjust after seeing first articles or getting field feedback. The shops that protect margin aren’t the ones saying “no” — they’re the ones with a priced, tracked, and communicated process for saying “yes, here’s what that costs.” Start by classifying your last 10 mid-run disruptions. Assign actual hours. Build the minimums. Then bake the logic into your next quote.

Want a quoting engine that handles change orders as cleanly as first-run jobs? Solvi builds customizable change-order workflows into every quote.