For any asset that generates revenue, schedule and cost are not comparable constraints — every day of delay has a computable price at full margin — and almost no organisation computes it before deciding how much to spend compressing the schedule.
Ask the executive accountable for your largest delivery what one day is worth, and note how the room answers. Somebody will price a day of acceleration to two decimal places: the second crew, the overtime loading, the air freight, the premium on an expedited approval. Nobody will produce the value of the day being bought.
That is one side of a trade priced to the cent and the other left blank, which is not a trade but a purchase decision made on the invoice alone. It reliably yields the same answer: acceleration looks expensive and is declined, delay looks free and is absorbed.
The asymmetry is trained. A teaching brief widely used to develop project managers fixes three things on a single page: the date by which the existing asset must be sold, the profit the project must generate, and the months from public closure until it must be open and earning again, with a grant funding the closed interval. Those facts compute the cost of a day before any schedule exists. The material built on that brief never computes it. Its compression guidance weighs extra crews against the risk of overlapping activities and stops; its rollback analysis prices a proposed delay to closure at the cost of the bridging finance, never at the value of the days.
For an asset that earns once it opens, this is the wrong shape of analysis. A dollar of cost is a dollar. A day of delay is a day of contribution never earned, plus fixed cost incurred anyway, plus interest on capital not yet working. Schedule and cost are not comparable constraints on a triangle: one converts into the other, at a rate the enterprise can calculate and usually has not.
The Strategic Context
More of the enterprise's value arrives through delivery vehicles that produce revenue-generating assets: a hotel, a plant, a fleet placed with customers, a platform that begins charging on a launch date. Each was approved on an earnings stream with a start date, then handed to a function measured on cost and schedule variance rather than on the earnings the asset was authorised to produce.
Two ledgers result. The project's opens at approval and closes at handover, and speaks in spend against budget. The asset's opens at handover and runs for years, and speaks in margin. The day of delay sits on the boundary, which is why it belongs to neither and is charged to no one.
The distinction sharpens as the unit of management grows. On a project, a day is a schedule variance in a status pack. At programme level it moves a revenue start date and changes what the enterprise can commit to next. At portfolio level days should compete: deliveries ranked by what a day is worth on each, with acceleration money directed to the highest, as capital is. Almost none can, because the ranking needs a number nobody has been asked to produce.
Consider a hypothetical boutique hotel of sixty keys, built to open ahead of a leisure season. It earns nothing until it opens, yet from the day the pre-opening team is hired, payroll, insurance, security, systems and interest on drawn debt run at full rate. Every one of those figures sits in the model that authorised the project, alongside contribution per occupied room and the occupancy ramp. The delivery team was given the capital budget and the programme, with the earnings side stripped out.
What Leaders Misread About Time and Money
Four readings recur, and each survives because the number that would correct it does not exist.
The first treats schedule and cost as commensurable constraints, tradeable by judgement. The familiar triangle teaches the trade-off and supplies no exchange rate, so the trade is settled by whichever side carries a number, and cost always does.
The second is the opposite error, and it damages the argument more than the balance sheet. Somebody computes the daily price from revenue rather than contribution, produces a figure large enough to justify anything, and the idea is dismissed as advocacy. The correct input is contribution margin at the performance actually achievable in the period concerned.
The third is the belief that a lost day is recovered later. It is not: delay either shifts an entire earnings stream or deletes days from the mature end of a fixed horizon, and both are worth more than the slow first days a team pictures when it imagines catching up.
The fourth assumes the delay is already priced, because the contract carries a remedy for late completion. A negotiated remedy is a transfer, usually capped, reflecting what a supplier would accept rather than what a day is worth to the buyer: a floor on recovery, not a measure of loss. What the enterprise absorbs once a supplier's liability runs out is owned by [Related article: The Liability Cap Nobody Adds Up]; this article stops at the value of the day, and does not follow the absorbed loss beyond the cap.
Reframing the Issue
The governing question changes shape once the number exists: not what acceleration will cost, but what price the enterprise should pay for a day, given what a day is worth.
The reframing cuts both ways, which is why it survives contact with a finance function. The figure justifies compression where the price of a day is below its value and forbids it where the price is above. Enterprises routinely err in both directions at once, over-accelerating a visible project of modest daily value while absorbing months on an asset worth many times more per day whose sponsor is less audible. This is not an argument for spending more, but for spending where it pays.
Computing the Price of a Day
The earnings side, counted at the right end
Start with the earning unit and its contribution margin at maturity, taken from the investment case that authorised the project rather than from the project's cost plan. The two documents rarely speak to each other, and only one contains the reason the enterprise is building anything.
Then decide which day is actually lost. Where the asset has a fixed end — a lease term, a concession, a franchise period — delay does not defer earnings but deletes them from the mature end of the horizon, and the daily figure is mature contribution margin. Where the life is open-ended, the loss is the value of shifting the whole stream, which approximates the same mature daily margin discounted at the enterprise's own rate. Either way the number is far higher than the ramp-up day most teams reach for.
The cost side that does not stop
Add everything that burns while the asset is not earning: retained payroll and pre-opening staff, financing on drawn capital, insurance, security, rates and systems, contracted supply that commences on a date whether or not the asset can consume it, and any bridging facility standing in for revenue that has not arrived. For most assets this side is available within a day, because every line already sits in an approved budget.
Together the two sides produce a rate. What they do not produce is a constant, which is where most attempts stop too early.
Days are not all the same size
Date-triggered events convert a smooth rate into a curve with cliffs: a facility expiring on a date, a lease commencing on one, an approval with a validity period, a seasonal window that closes. On the hypothetical hotel, thirty days that move an opening from the start of a peak season to the end of it can cost several times what ninety days would in a shoulder period: the days lost are the days at the peak of the year, not at the margin of the schedule.
The corollary is immediate: acceleration money should not be spread evenly across a programme but concentrated on protecting the expensive days, which means knowing which days those are before the schedule is committed. Which criteria push the hardest work past the last moment at which it could be reversed is owned by [Related article: From Sequencing Rule to Point of No Return]; this article prices the day, and does not examine the sequencing rules that put the difficult work where the days are dearest.
Take a second hypothetical: a lessor placing commercial laundry equipment into customer sites under fixed-term leases that commence at commissioning. Delay defers rather than destroys, but capital is idle while it does so and the fleet turns more slowly across the year. The price of a day is the daily lease contribution on each unit awaiting commissioning plus the financing cost of idle capital, computable per machine per day with more precision than any construction estimate. It usually is not computed, because the installation team is measured on cost per unit installed, and that measure points away from asking what a delay is worth.
Decision Framework
The instrument is the daily margin figure: a dated, published statement of what one day of delay to first revenue costs the enterprise, produced before the schedule baseline is approved and owned by the executive accountable for the asset's earnings, not by the project.
It is built in five steps, none needing new data.
| Component | Where it comes from | Common error |
|---|---|---|
| Contribution per earning day | The approved investment case | Using revenue instead of margin |
| Which day is lost | Asset horizon: fixed term or open-ended | Counting a ramp-up day rather than a mature one |
| Continuing burn | The approved pre-opening and financing budgets | Omitting financing and retained payroll |
| Date-triggered cliffs | Facility expiries, lease starts, approval validity, seasonal windows | Treating the rate as a constant |
The fifth step is publication. The figure is issued as a calendar rather than a scalar: the value of a day, by month, for the coming eighteen months, with the cliffs marked. A single number invites the wrong decision in the wrong month.
Three rules make it operate. First, no compression proposal and no decision to accept delay may be approved unless the daily margin figure for the affected period appears on the same page as the cost. Second, days are bought only when the fully loaded cost of compression sits below the value of the days protected, with a safety margin for the real possibility that compression is paid for and does not work. Third, any delay crossing a marked cliff is a board decision, whatever its length.
Two boundaries matter. The figure needs a start point, and when the clock legitimately starts is owned by Article 49 in this collection. The market from which acceleration is bought was narrowed years before the tender by qualification measuring administrative capacity rather than delivery capability, the subject of [Related article: The Shortlist Was Decided Years Before the Tender]; this article assumes the field exists and prices what the enterprise should pay inside it.
From Strategy to Execution
Immediately, compute the figure for the two largest in-flight deliveries that earn on opening, and put it on the next board pack beside the schedule. The inputs already sit in approved documents; the work is arithmetic and a decision about who signs it.
Over the next two quarters, make it a gate condition: no investment approval without a daily margin figure and its calendar, no compression business case without both sides of the trade on one page. Change the delivery scorecard so the leader is measured against the date of first revenue, not only cost variance: a scorecard rewarding underspend on a late asset buys the wrong thing deliberately.
Over a year and beyond, run it at portfolio level: rank deliveries by the value of a day, hold acceleration funding centrally, and allocate it to the highest daily value rather than the most audible sponsor. Negotiate delay remedies and early-completion incentives against the enterprise's own number rather than a template.
Signals to Monitor
Watch for compression proposals that argue cost alone; the missing side of the trade is the diagnostic. Watch for delay decisions taken below the person accountable for the asset's earnings. Watch for revenue start dates moving quietly in the model while schedule variance is reported as contained. Watch for identical delay remedies across contracts covering dissimilar assets, which shows the figure came from a precedent rather than the asset. Watch for acceleration spending spread evenly instead of concentrated where the calendar is expensive. And watch for a first-year earnings forecast revised down in the same month a schedule slips, with nothing connecting the two.
Questions for the Leadership Team
- What is one day worth, in contribution margin, on each of our three largest revenue-generating deliveries, by month of the coming year?
- On our last three acceleration decisions, what did we pay per day bought, and against what value?
- Which date-triggered cliffs — facility expiries, lease commencements, approval validity, seasonal windows — fall in the next eighteen months, and who holds that calendar?
- Who is accountable for the first year of earnings on our largest delivery, and were they in the room when the schedule was baselined?
- How do the delay remedies in our delivery contracts compare with our own daily figure for the same assets?
- When we last absorbed a month of delay, where was that decision recorded, and what did the paper say the month was worth?
Closing Perspective
An enterprise that cannot price a day is not managing the trade-off between time and money. It accepts whichever side of the trade carries a number, and on a revenue-generating asset that side is always cost. The consequence is systematic: acceleration under-bought, delay under-resisted, and an earnings stream starting later than the investment case promised, for reasons that never reach a variance report because they were never priced.
The responsibility sits with whoever approves the schedule. Approving a baseline without the value of a day beside it is neither neutral nor a deferral. It sets the price of a day at zero, and every decision downstream will honour that price faithfully.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.