Revenue at risk, with each engagement counted once
Your dashboard now tells you what your at-risk work is actually worth. The figure that sat there before added four overlapping categories together, so an engagement that was both running late and had an unhappy customer behind it was counted twice, and the total could come out larger than the work it was drawn from. It counts each engagement once now, however many things are wrong with it.
What gets flagged
An engagement is flagged when any of three things is true:
- its customer is at renewal risk — the same flag your customer health figure raises, read from there rather than worked out a second way
- it has sat in one stage for more than 30 days
- that customer’s satisfaction averages 2 or below on the five-point scale they answer on
Each flag carries its own total and its own count, so you can see which problem is holding the money. What you cannot do is add those three totals together, and the screen says so plainly: an engagement carrying two flags appears in two of them. Only the headline figure counts anything once.
Open it and every flagged engagement is listed with its contracted value, its customer, and every flag it holds. Those values add up to exactly the headline figure.
A slice, not a second pot
Revenue at risk is stated as a share of your active service revenue, naming the total it came out of. It is part of that money rather than money sitting beside it, so nothing adds the two together or sets one against the other.
Work you have already delivered is not in it — that risk went with the delivery. An engagement priced outside your reporting currency is left out and its count stated beside the figure, the same way active service revenue treats it, rather than converted at a rate nobody agreed.
Two things it does not claim
Delay against a date you agreed with the customer is not measured. Work still in flight carries no such date, so days in stage stands in for it — and the definition says outright that this is the weaker test rather than presenting the two as the same thing.
Scope reductions are not measured at all. Nothing in the system records a job getting smaller, so rather than estimate one, the definition states it as an exclusion.
What has gone
The revenue leakage card has been removed from your dashboard, and the risk page it linked through to has gone with it — both showed the old added-up figure, and nothing else pointed at that page. The renewal-risk table you reached through the card is still there, in the same dashboard section as the new figure.
The two thresholds — over 30 days in stage, satisfaction of 2 or below — are shown on the metric’s definition in the KPI dictionary. They change with a release, not by anyone adjusting a number in the product.