04 / Customer Economics & Cash
The Rush Order Borrowed Another Job’s Margin
Trace the work displaced by a rescue, the cost of restoring it and the customer promise that ultimately absorbed the difference.
The example below is illustrative.
Follow Friday into the rest of the month
The rush job shipped Friday and earned a $12,000 premium. Three weeks later a different customer received a service credit for a job that had missed its installation window. The overtime was charged to the regular schedule. The outside finishing work went through procurement. The rush order could still appear profitable because the operating response crossed three jobs, two reporting periods and several owners.
A legitimate rush job can be valuable to the buyer and profitable to the company. The relevant comparison is the rush plan against the schedule that could otherwise have shipped, through the point when that schedule is restored. The salesperson’s job margin and the scheduler’s displacement record describe different parts of the same decision.
Reconstruct the schedule and the recovery
Recover the version of the plan that existed immediately before the exception. Identify the binding resource on that date. Record the tasks whose start or end times changed and trace commitments that depended on them. Ask managers to mark which costs would have occurred anyway. Three weeks of activity following a rush job is a search window, not a claim of causation.
| Difference from the feasible original schedule | Contribution effect |
|---|---|
| Rush work earns $26,000 after its own ordinary incremental delivery costs, excluding premium | +$26,000 |
| Rush premium | +$12,000 |
| Overtime attributable to restoring one displaced job | −$7,000 |
| External finishing to save a different commitment, net of avoided original spend | −$6,000 |
| Service credit required on a third job | −$5,000 |
| Incremental contribution of a fourth job cancelled, net of avoidable costs | −$9,000 |
| Net if the customer would order elsewhere without the rush | +$11,000 |
| Net if the same customer would accept the normal date | −$15,000 |
The $26,000 enters this comparison because the customer would have placed the order elsewhere if the company refused Friday. If the customer would have placed the same order at the ordinary date, the $26,000 belongs on both sides and drops out of the rush decision. The same schedule consequences would then turn the $12,000 premium into a $15,000 loss relative to standard delivery. There is a distinct case in which the rush replaces a future job under a persistent constraint. Use the relevant alternative calendar rather than expecting the baseline job to happen at an unspecified point.
Trace causation over job boundaries
Tie each charged item to a schedule or cost entry and the specific commitment it changed. Confirm that outside finishing and overtime are distinct remedial actions, and that the credited job still earned its normal contribution before the credit. If an existing order was lost entirely, recognize its lost incremental contribution once. Do not also charge all its quoted revenue or the penalties the company no longer owes. If a supplier delay would have caused the service miss anyway, remove the service credit from the rush effect unless the changed schedule made the loss worse.
Where records are incomplete, calculate a conservative attributed subtotal and a plausible upper estimate. The missing evidence should affect which authority approves the rescue. The best next investment may be saving a pre-exception schedule and connecting credits to commitments rather than imposing a general ban. When Every Department Is Right and the Company Is Wrong provides the larger handoff argument. This review puts a dollar amount against the changes across those handoffs.
The installation case “Everyone did their job. The truck still shouldn’t have left.” shows why a locally sound action can still put the whole commitment at risk. Here the scarce hours moved to the rush are Effective Capacity borrowed from other commitments. When the same cross-customer tradeoff recurs, assign a named decision right. See The Recurring Decision Is a Missing Decision Right.
Use the reconciliation to redesign a repeated pattern. If the extra cost comes from setup breaks, offer emergencies inside a dedicated slot or at the next natural product changeover. If it comes from missed installations, obtain a feasible alternate date before promising an expedite. If most of the harm comes from special parts, test a buyer-funded spare or a prequalified substitute. Measure the same cost after the change. A premium that funds routine recovery may still reward a recurring problem the customer would gladly help prevent.
Protect the emergency worth accepting
Suppose the regular schedule contains open qualified capacity and the work uses an already approved configuration. The rush would earn a premium with no displaced jobs and no deferred recovery. The week’s calendar should support that answer. A strategic emergency can also warrant accepting a known negative immediate contribution. Make the retention purpose explicit, set the exposure limit and assign the exception to a leader who can own the company-wide result.
If the same buyer requests “emergency” access weekly, use the incident records to price a standing service tier or reserve. The capacity reservation article shows how that contract buys access before the emergency occurs.
Put a price and owner on the next rescue
Review three recent rush approvals. On one sheet, write what would otherwise ship, the customer alternative to the rush, the earliest recovery point, the cost categories to check, and the person who can authorize reallocation across customers. Set a forecast range. Reconcile at the next period close when expediting bills, credits and recovery costs appear. Where a promised premium consistently misses the range, revise the terms or move approval to the person who can see and accept the exposure.
Take this to your team. Which existing customer promise would pay for the next rescue if every affected order were reviewed together?