To quantify a blocker's impact for executives, work out three numbers in a fixed order. First, the days go-live moves, taken from the dependency chain and not guessed. Second, the dollar cost: a daily rate times those days, plus any one-off exposure, shown as a range. Third, a simple customer-risk rating. Then rank every blocker across your rollouts in one table that says who must decide, and by when.
How many days does a blocker actually move go-live?
A blocker moves go-live only by the blocked days that float in the plan cannot absorb. If the blocked task sits on the critical path, every blocked day is a go-live day. If the task has float, subtract the float first. A blocker off the critical path can cost no go-live days, so say that plainly.
Work it out in your plan, not from memory. Count everything in working days, and use the same unit for the cost figures later.
- Find the blocked task in the plan. Note the date it needed to start and the date it can now start, given the earliest realistic answer from whoever is blocking it.
- Count the blocked days. That is the gap between the two dates, in working days.
- Check the float. Float is how many days a task can slip before anything after it moves. Most project plans show it as a slack or float field on the task. On the critical path, float is zero.
- Calculate the slip. Go-live slip is the blocked days minus the float, or nothing if the float covers it.
- Add remobilisation. If the team rolls onto other work while waiting, ask the delivery lead how many working days it takes to get them back and productive. Add those days.
- Write the date, not only the count. "Go-live moves from [original date] to [new date]" is easier to act on than a number of days.
If you do not keep a dependency-linked plan, trace the chain by hand: list the tasks that cannot start until the blocked one finishes, and follow them to go-live. That trace is the evidence an executive will ask for.
How do I turn slip days into a dollar figure?
A blocker's total exposure is a daily rate times the slip days, plus a separate one-off exposure line for renewal risk and penalties. Build the daily rate from delayed revenue and services burn, counted per working day, and keep each part visible so finance can check every input.
LogRocket gives the base formula as lost value per unit of time multiplied by the length of the delay. The version below splits the daily part from the one-off part so nothing is multiplied twice.
Daily rate = delayed revenue per working day + services burn per working day
One-off exposure = renewal or expansion exposure + penalties and SLA credits
Total exposure = (daily rate × slip days) + one-off exposure
Slip days and the daily rate must use the same day unit. This guide uses working days throughout. If finance prefers calendar days, convert the slip to calendar days as well and state the unit in a footnote.
Daily rate: delayed revenue
If subscription billing or revenue recognition starts at go-live, divide the annual contract value by [working days in your year], then multiply by the slip days. Label this honestly. Often it is revenue moved later, not revenue lost, and finance will check. If the subscription is already billing, the cost is the customer's lost time to value, which belongs in customer risk instead.
Daily rate: services burn and margin
Multiply the daily cost of the people held on the project by the slip days, then add the extra hours for rework, repeated meetings, and re-planning. Continuum PSA recommends tracking actual effort against budgeted hours and logging a decision delay as its own variance reason rather than burying it under general delivery. On fixed-fee work, this is the number that shows margin being spent.
One-off exposure: renewal and expansion
Take the contract value at the next renewal or the expansion under discussion, and multiply it by how much the delay raises the chance of losing it. The result is one expected amount for the blocker. Add it once to the one-off line; do not multiply it by slip days. beefed.ai recommends objective measures such as likelihood times impact and expected monetary value so escalation is data-driven. Use the account owner's judgment for the probability and say whose judgment it is.
One-off exposure: penalties and SLA credits
Read the contract. Missed go-live dates, service credits, and acceptance deadlines are one-off amounts, not daily rates, so add them once to the one-off line and only if the new date crosses the trigger.
Compare the cost with the fix
Once you have a daily rate, any option to clear the blocker becomes a return-on-spend question. Playbook shows the arithmetic: if a month of delay costs $400K, a day costs $20K, so spending $5K to save one day returns $15K net, a 3-to-1 return. Whatever unit a monthly figure starts in, convert it to your chosen day unit before comparing. Put the cost of each fix next to the cost of waiting in the same email so the executive can compare them in one place.
How do I score customer risk without false precision?
Customer risk is best shown as its own rating in a separate column, never converted into dollars or multiplied into the cost. Rate churn risk, reference risk, and escalation risk on the same small scale, then report the highest of the three with its written reason. Keeping risk separate stops a soft judgment from inflating a hard number.
Use one scale for all three factors. beefed.ai scores likelihood and impact each from 1 to 5, and you can rate each factor below on that same 1 to 5 scale. If you already priced renewal exposure in the one-off line, the churn rating explains that amount rather than adding to it.
| Factor | What to ask | Evidence to cite |
|---|---|---|
| Churn risk | Would this delay change the renewal conversation? | [renewal date], [account owner's view], [recent sentiment] |
| Reference risk | Has this customer agreed to speak to prospects or appear in our marketing? | [sales or marketing commitment] |
| Escalation risk | Is the customer's sponsor already frustrated or going above the team? | [recent emails or meeting notes] |
To combine the three, report the highest factor score as the account's rating, and write the reason beside it, for example "[score], churn: renewal on [date] and sponsor raised the delay on [date]". Taking the highest score keeps one serious concern from being averaged away, and the reason tells executives exactly what to ask about.
Why show a range instead of one number?
A range shows executives you know which inputs are uncertain, and it holds up when someone challenges an assumption. Give a low, likely, and high figure for slip days and for total exposure, and name the single assumption that moves the number most. One precise-looking figure invites an argument about the figure instead of a decision.
For each blocker, write three lines:
- Low: [slip days] working days, [amount], if [best realistic answer date].
- Likely: [slip days] working days, [amount], if [expected answer date].
- High: [slip days] working days, [amount], if [worst realistic answer date], including [penalty or credit triggered].
The swing between low and high is itself useful. It shows how much a fast decision is worth.
How do I rank blockers across the whole portfolio?
Rank blockers across rollouts by cost per day of delay first, then by how soon the decision deadline falls. Cost per day tells executives where waiting is most expensive; the deadline tells them what expires first. Show customer risk as a separate column so it can break ties or flag exceptions, without changing the dollar figures.
Black Swan Farming frames cost of delay as a rate per unit of time, which is what lets you compare blockers on different projects. The same page shows that adding time criticality on top of value gives a non-zero cost of delay to work with zero value. Use the daily rate you already built and do not add an urgency score to it; urgency belongs in the decide-by date.
Steps for the roll-up:
- Ask each project lead for the same fields, in the same units, before the portfolio review.
- Drop blockers with no go-live slip and no one-off exposure into a watch list below the table.
- Sort the rest by likely daily rate.
- Move any blocker whose decision deadline falls before the next review to the top, whatever its rank.
- Use the customer-risk column to break ties and to flag any account the executive should call personally.
- Check that every row has a named owner outside your team. A blocker your own team can clear belongs in your delivery meeting, not the executive view.
What does one blocker look like worked from start to finish?
A worked blocker carries the same inputs through slip, cost range, risk rating, its table row, and the decision email, so each number traces back to evidence. The illustrative walk-through below uses placeholders only. Replace each bracket with your project's figures and keep the source of each input beside it.
Illustrative example, placeholders only, all days counted as working days:
- Slip. The task waiting on [customer] has been blocked for [blocked days] working days. The plan shows [float] days of float. Slip is [blocked days] minus [float], plus [remobilisation days] to bring the team back, giving [slip days]. Go-live moves from [original date] to [new date].
- Daily rate. Delayed revenue per working day is [annual contract value] divided by [working days in your year]. Add services burn per working day, [daily team cost]. Together they give [daily rate].
- One-off exposure. Renewal exposure is [renewal value] times [added chance of loss, from account owner], giving [amount]. Add [penalty amount] only if the new date crosses [penalty trigger]. One-off exposure is [amount], added once and not multiplied by slip days.
- Total exposure. [daily rate] times [slip days], plus [one-off exposure], gives [total amount]. Repeat for the low and high cases as in the range section above.
- Risk rating. Churn [score], reference [score], escalation [score]. Reported rating: [highest score], because [reason].
- Table row. [rank] | [customer] | [one-line blocker] | [low] / [likely] / [high] days | [daily rate] | [total amount] | [rating and reason] | [decision in one sentence] | [owner] | [decide-by date].
- Email. Copy the row's figures into the decision email template in the next section, add the options with their cost and days saved, and send it to [owner].
What should the executive table and email say?
The executive view should fit on one slide: each blocker, its slip, its cost, its customer risk, the decision needed, the owner, and the decide-by date. Pair it with a short email per top blocker that answers what is blocked, what it affects, what waiting costs, and who decides.
Portfolio table
| Rank | Customer | Blocker | Go-live slip (low / likely / high) | Cost per day | Total exposure (likely) | Customer risk | Decision needed | Owner | Decide by |
|---|---|---|---|---|---|---|---|---|---|
| [rank] | [customer] | [one-line blocker] | [days] / [days] / [days] | [amount] | [amount] | [rating and reason] | [decision in one sentence] | [name] | [date] |
For the slide version, keep rank, customer, likely slip, total exposure, customer risk, decision needed, owner, and decide-by, and move the full range, cost per day, and blocker detail into the decision email or a backup slide.
Decision email for one blocker
Continuum PSA suggests every escalation answer four questions: what is blocking progress, what work, date, budget, or resource plan is affected, what it costs if no decision is made, and who owns the decision. A template built on those questions:
Subject: Decision needed by [date]: [customer] go-live
[Blocker in one sentence], waiting since [date].
Impact: go-live moves from [original date] to [new date] (likely), [range] working days. Cost of waiting is about [amount per working day], plus [one-off amount] in one-off exposure, [total amount] in total, mostly [revenue timing / services burn / penalty]. Customer risk is [rating] because [reason].
Options: A. [option], costs [amount], saves [days]. B. [option], costs [amount], saves [days]. C. Wait, costs [amount] and risks [penalty or renewal exposure].
Recommendation: [option], because [reason].
Decision needed from: [name], by [date]. After that, [what changes].
What will executives push back on?
Executives usually challenge the inputs, not the method, so answer before they ask. Expect questions about whether revenue is delayed or lost, whose churn estimate it is, and why the slip is not simply the blocked days. Put each assumption in a footnote with its owner.
The honest limits are worth stating:
- Delayed is not lost. Most go-live revenue arrives later rather than never. Say which it is.
- Day units must match. Slip and the daily rate both use working days in this method. State the unit so finance does not have to guess.
- Probabilities are judgments. A churn likelihood from an account owner is an informed opinion. Label it that way.
- Some projects carry no revenue line. For internal rollouts or work you cannot price yet, Black Swan Farming offers a qualitative value-and-urgency grid as a starting point.
- Numbers do not replace the ask. A quantified blocker still needs a named decision-maker and a date.
How do I keep the numbers current between reviews?
Keep blocker impact numbers current by recalculating slip and cost whenever the blocked date changes, not only before the review. Store the inputs with the blocker in your project tool, note the evidence for each, and update the decide-by date if the options change. Rough numbers that are current serve a decision better than precise ones that are out of date.
A short routine works: each project lead updates the blocked date, float, and daily rate in the project record, flags any blocker whose high-end slip now crosses a contract trigger, and sends the decision email as soon as a blocker enters the top of the table. On many projects the executive who has to decide is the project sponsor, so the decision email is really a request to the sponsor. If you use Unblockd, the decision email can go out as one of its asks to the sponsor by email with one-tap answers (no account). After the decision, record what the team does next, so the following review shows the blocker closed with its evidence.