Cost Window Allocation

Split the total target into subsystems with a cost window each — no subsystem eats the budget alone.

Time1 h
FormatTeam
StageTarget

Cost Window Allocation: what it is and why it works

Cost window allocation turns a single target cost into a band with three levels, optimistic, realistic and pessimistic, and gives each subsystem its own slice of that band. The window reflects the real uncertainties around the target price: market positioning, option mix and volume scenarios. Each level is tied to a design rule that says which features stay in the product if the business ends up at that level. The realistic target is frozen for day-to-day design work, while the full window is kept as a reference for gate reviews.

A single number hides uncertainty and invites a false sense of precision; a window makes the uncertainty visible and pre-decides what happens when it materializes. Because every subsystem has its own window, an overrun in one area shows up at the next review instead of after integration, when the only option left is to squeeze the others. Designing to the pessimistic end protects margin if the market softens, and the design rules prevent feature decisions from being reopened every time the forecast moves. The method builds directly on target cost definition, feeds cost risk assessment with explicit ranges, and gives target attainment tracking a clear yardstick at each gate.

What you need

The agreed target cost and the price and margin assumptions behind it
The main uncertainties: price positioning, option take rates, volume scenarios
The product breakdown into subsystems with a first cost allocation
A list of features and options that could be adjusted if cost pressure rises
Availability of sales and finance for one joint review

What you get

An optimistic, realistic and pessimistic cost target for the product and for each subsystem
Design rules linked to each level, stating which features survive at the pessimistic end
A frozen realistic target used in daily design work
A window record used as the reference at each gate review

When to use it

When one function’s overruns are discovered after integration is too late.

How to do it, step by step

List the uncertainties around the target price: positioning, options, volume scenarios.
Define a window: optimistic, realistic, pessimistic cost targets.
Attach each window to a design rule: what features survive at the pessimistic level?
Check the window with sales and finance in one meeting.
Freeze the realistic target and keep the window for gate reviews.

Worked example: Mobile screening plant for aggregates

Illustrative scenario — figures are realistic but not from a real company.

A manufacturer of track-mounted screening plants for quarries is developing a new mid-size model. Pricing depends on whether the machine is positioned against premium or value competitors, and volume forecasts range from 40 to 70 units a year. The initial target cost was a single figure, $330,000, which nobody fully trusted.

The team listed three uncertainties: positioning against two different competitor sets, take rate of the remote-monitoring option, and annual volume.
Finance translated these into a window: optimistic $345,000, realistic $330,000, pessimistic $314,000 allowable cost, then split each level across powertrain, screen box, conveyors, chassis and controls.
For the pessimistic level, the team wrote design rules: one standard diesel-electric drive only, remote monitoring moved from standard to paid option, and a single conveyor width across the range.
Sales and finance reviewed the window in one meeting; sales pushed back on the conveyor rule, and the compromise was two widths with a common frame.
The realistic figure was frozen for design work and the window table became a standing slide in every gate review.

Result. At the second gate, the screen box was running $6,000 above its realistic window while the chassis was below. Because the windows were explicit, the overrun was visible early and the team simplified the screen box access doors instead of cutting chassis strength. When a key competitor cut prices before launch, the pessimistic design rules were already agreed and applied within weeks, keeping the margin close to plan.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

Making the window so wide that every outcome looks acceptable.Base each level on named scenarios with evidence, and challenge any window where the pessimistic case has no consequence for the design.
Setting only a product-level window, so subsystems compete for the slack.Give each subsystem its own window and review them individually at gates.
Defining the window without saying what changes in the design at each level.Attach concrete design rules, such as which options become paid or which variants are dropped, to the pessimistic level.
Letting the realistic target drift every time the forecast changes.Freeze the realistic target formally and change it only through a documented gate decision.

Frequently asked questions

What is a cost window in target costing?

A cost window is a range of acceptable product cost, usually expressed as optimistic, realistic and pessimistic targets, instead of a single target figure. It reflects uncertainty in price, options and volume. Each level can be split across subsystems and linked to design rules, so the team knows in advance how the product changes if costs or market conditions move toward the unfavorable end.

Should you design to the pessimistic or the realistic cost target?

Most teams freeze the realistic target for day-to-day work but make sure the design can reach the pessimistic level through predefined rules, such as moving a feature to a paid option. Designing directly to the pessimistic end gives the most protection but can strip value the market would pay for. The right choice depends on how exposed the product is to price pressure.

How wide should a cost window be?

Wide enough to cover the scenarios the business genuinely considers plausible, and no wider. Derive the limits from specific price, option-mix and volume scenarios rather than a fixed percentage. A window that never triggers a design decision is too wide to be useful; one that is breached at every review probably ignores real uncertainty.

Origin

Scenario-based target setting — cost engineering practice; aligned with target costing literature.

Used in these playbooks

Target setting workshop 1 h

One hour to set a defensible target cost: top drivers, scenario window, business case check — with confidence grades on every number.

Related methods

More in “Target”

Set the cost the market allows — before designing a single part.