- Home
- Blog
- Quoting & Promising
- Deleting a Quote Scenario You No Longer Need in ED…
Deleting a Quote Scenario You No Longer Need in EDGEBIC
Deleting a scenario removes that scenario and the overrides stored on it, and nothing else. In EDGEBIC by User Solutions the parent quote, the product's routing, your work centers, and the live production schedule are all untouched by the delete. That makes pruning a quote's scenario list one of the safest housekeeping jobs in the product, and it is worth doing, because a quote carrying a dozen half-explored what-ifs is a quote nobody can read.
Before you start
Know two things before you remove anything.
Know which scenario you actually sent. Open the quote and read its estimated end date and cost, then match those figures against the scenario list. Applying a scenario copies its results onto the quote, so the numbers on the quote tell you which scenario won. That one is your decision record.
Know that a scenario cannot be rebuilt from memory. A scenario stores parameters and the results of its last run. Running it again days later works against a shop that has moved on, so the same overrides can return a different date. Deleting is not reversible by re-creating.
How to delete a scenario
- On the Quote tab, select the quote and click Scenarios to open the What-If Scenario Analysis view.
- In the scenario list on the left, select the scenario you want to remove.
- Use Delete Scenario.
- Repeat for each scenario you are pruning, then use Back to Quotes to return to the grid.
That is the whole procedure. There is no separate cleanup step, because a scenario owns nothing outside itself.
What survives the delete
This is the part worth internalizing, because planners hesitate here and leave clutter behind.
| Item | Effect of deleting the scenario |
|---|---|
| The scenario's parameters and overrides | Removed. This is all the delete takes. |
| The parent quote | Untouched, including its status, price, and markup. |
| Estimated dates, hours, and cost already applied to the quote | Untouched. Once applied, those figures belong to the quote. |
| The product's routing | Untouched. A scenario never edited the routing to begin with. |
| Work centers and their real capacity | Untouched. A scenario capacity override lives inside the scenario only. |
| The production schedule | Untouched. Scenario runs write nothing to real jobs. |
| Other scenarios on the same quote | Untouched. Scenarios do not reference each other. |
The reason the blast radius is this small is the same reason scenarios are useful in the first place. A scenario is a named set of altered conditions plus the stored output of running them. It never reserved capacity, never edited a machine, and never placed a job. Read the wider boundary in what a scenario can and cannot change in EDGEBIC.
How to check it worked
Three checks, in order.
- The scenario list is shorter and the scenario you removed is gone from the left panel.
- The quote still reads the same. Go back to the quote grid and confirm the estimated start, end, hours, and cost are exactly what they were. If you deleted a scenario you had applied, this is the check that proves applying wrote the numbers onto the quote permanently.
- The comparison still draws. Open the Comparison Analysis tab and tick the scenarios you kept. The lead time, cost, and utilization charts should render one bar per ticked scenario, with the deleted one simply absent. Only simulated scenarios can be included, so if a survivor will not tick, run its simulation rather than assuming the delete broke something.
Common mistakes
Deleting the baseline. The no-override scenario is the least interesting to look at and the most important to keep. Without it a comparison has no zero point, and you lose the record of what doing nothing would have cost. Keep it until the quote is closed.
Deleting the applied scenario too early. The quote keeps the numbers, but it does not keep the reasoning. Six weeks on, when a customer asks why you promised that date, the scenario named after its lever is the answer. Delete probes freely; keep the winner until the quote converts or dies.
Treating delete as a fix for a stale result. If a scenario's numbers look wrong because you changed its parameters and did not re-run it, the fix is to run the simulation again, not to delete and rebuild. Applying an unsimulated or edited scenario is refused with a message telling you to simulate first, which is the system pointing at the real problem.
Letting the list grow instead of pruning as you go. Two to four scenarios per quote is the working range: a baseline plus one per lever you would genuinely execute. Beyond that the comparison charts get crowded and the names stop meaning anything. Delete a probe when it loses, not in a cleanup pass six weeks later. Naming each scenario after its lever rather than its number makes the pruning decision obvious.
Next steps
Once the list is down to a baseline and a winner, the remaining work is on the quote, not the scenarios. Confirm the winning numbers reached the quote by following how to apply a scenario to a quote, re-price if the cost moved, and remember that applying a scenario is not the same as making the change real on the floor. If you sold a second shift on the mill, someone still has to arrange it. For the shape of a clean comparison see how to compare two scenarios side by side, for the levers themselves see boosting a work center's capacity in a quote scenario, and for the traps that produce eleven-scenario quotes in the first place see scenario planning mistakes.
The takeaway
Delete a scenario the moment it stops earning its place. The operation removes that scenario and its overrides and touches nothing else, so there is no risk to the quote, the routing, the work centers, or the schedule. Keep the baseline, keep the scenario you sent, and delete the probes as they lose. See the full quoting flow in the EDGEBIC quoting guide, or bring a real enquiry to a walkthrough of EDGEBIC and we will build the comparison with you.
Deleting a scenario removes that scenario and the overrides stored on it, and changes nothing else. In EDGEBIC by User Solutions the parent quote, its estimated dates and costs, the product's routing, the work centers, and the live production schedule are all untouched. A scenario was never anything more than a saved set of what-if parameters plus the results of running them, so removing one takes only those parameters and those results with it.
No. Applying a scenario copies its estimated dates, hours, and costs onto the parent quote, and from that moment those figures belong to the quote itself. Deleting the scenario afterward does not reach back into the quote and undo the copy. What you lose is the record of how those numbers were produced, which is a real loss when someone asks six weeks later why the promise date was what it was. Keep the applied scenario until the quote is converted or dead.
Yes, and the comparison simply stops showing it. The comparison charts are built from the scenarios you tick under the selection list on the Comparison Analysis tab, and only simulated scenarios can be included at all. Removing one means one fewer bar on the lead time, cost, and utilization charts. Nothing about the remaining scenarios changes, because scenarios do not reference each other.
Work backward from what you promised rather than forward from the list. Open the quote and read its estimated end date and cost, then find the scenario whose results match. That one, plus the no-override baseline, is the decision trail, and both should stay. Everything else was a probe. Delete the probes, because each one only carries its own parameters and results, and removing it cannot disturb the quote or the two you kept. Then rename the survivors after the lever they represent, so the next person reading the list sees a baseline and a chosen alternative instead of eleven variations named Scenario 3 through Scenario 11. The habit that prevents this is holding yourself to a small number of scenarios per quote, roughly the baseline plus one per lever you would genuinely execute, and deleting a probe the moment it loses.
The shop did. A scenario stores its parameters and the results of the last run, not a frozen copy of your capacity. When you run a simulation, the engine works against the real current picture, including the jobs already committed to those machines and the holidays and shift boundaries in force. If days passed between the original run and the re-created one, the load underneath moved, so the same overrides produce a different answer. That is not a fault, it is the whole point of quoting against real capacity, but it does mean a deleted scenario cannot be recovered by rebuilding it from memory. If a scenario's result is going to be cited later, either keep the scenario or apply it to the quote so the numbers land somewhere permanent.
Expert Q&A: Deep Dive
Q: Our sales engineer built eleven scenarios on one quote while chasing a date, and now nobody can tell which one we actually sent. How do we clean this up without losing the decision trail?
A: Work backward from what you promised rather than forward from the list. Open the quote and read its estimated end date and cost, then find the scenario whose results match. That one, plus the no-override baseline, is the decision trail, and both should stay. Everything else was a probe. Delete the probes, because each one only carries its own parameters and results, and removing it cannot disturb the quote or the two you kept. Then rename the survivors after the lever they represent, so the next person reading the list sees a baseline and a chosen alternative instead of eleven variations named Scenario 3 through Scenario 11. The habit that prevents this is holding yourself to a small number of scenarios per quote, roughly the baseline plus one per lever you would genuinely execute, and deleting a probe the moment it loses.
Q: We deleted a scenario, re-created it with what we thought were the same settings, and got a different end date. What changed?
A: The shop did. A scenario stores its parameters and the results of the last run, not a frozen copy of your capacity. When you run a simulation, the engine works against the real current picture, including the jobs already committed to those machines and the holidays and shift boundaries in force. If days passed between the original run and the re-created one, the load underneath moved, so the same overrides produce a different answer. That is not a fault, it is the whole point of quoting against real capacity, but it does mean a deleted scenario cannot be recovered by rebuilding it from memory. If a scenario's result is going to be cited later, either keep the scenario or apply it to the quote so the numbers land somewhere permanent.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
After Conversion, Edit the Order and Not the Quote in EDGEBIC
Once a quote converts, the manufacturing order is the live record. See why quote edits stop reaching production, and what the quote is still good for afterward.
Finding One Quote in a Long List in EDGEBIC
Three filters narrow the EDGEBIC quote grid: status, customer, and sales order. See how they combine, what each one answers, and why the filter also sets the blast radius.
What Happens to a Quoted Price When the Quantity Changes in EDGEBIC
Doubling the order rarely halves the unit cost. See the exact quantity arithmetic behind an EDGEBIC quote, where setup stops amortizing, and why the date scales differently.
