Revenue delivered, and how much of it landed on the agreed date
Two more figures are now live on your dashboard and in the KPI dictionary, and both hang off the same question: what does it actually take for a piece of work to count as delivered?
Delivered now means something you can point at
An engagement counts as delivered when three things are true: every milestone is complete, the customer has acknowledged each one, and every bill against it is settled. That middle condition is new. Until now the platform had no record of a customer agreeing that a piece of work was done — only of the team saying so.
Customers can now acknowledge a completed milestone from their own project view. It changes nothing about the project: no status moves, nothing unblocks, and no invoice waits on it. If a customer does not use the portal, a CSM or SDM can record the acknowledgement for them, and the record shows which of the two it was.
Revenue delivered
The contracted value of the engagements that reached delivered in the period, with the count of those same engagements beside it. Both come from one list of records, so the value and the count cannot disagree — open the figure and the engagements are there, adding up to exactly what the headline says.
Because delivered waits on the final bill, every row carries two dates: the day the last milestone was accepted, and the day the engagement was delivered. A payment that lands a month late moves the second date and not the first, so a slow payer never reads as a delivery slowdown. Work finished in one month and billed in the next counts in the later month, and the earlier month is not restated.
Twelve months of history sit behind it, month by month, on the same records.
On-time delivery rate
The share of those engagements delivered on or before the date agreed with the customer. An agreed change to the delivery date resets the date measured against, and the number of engagements whose date moved is shown next to the figure. An engagement with no agreed date recorded sits in its own bucket with its count, rather than being quietly treated as on time.
Behind it are four counts over the same engagements — delivered on time, delivered to plan, escalation-free, and billed without query. Each is a plain count of something the platform records, and each opens to the engagements behind it.
These four are what happened. Satisfaction is what the customer said. They are reported side by side and never merged into one score, and they are allowed to disagree — when they do, that gap is usually the most useful thing on the page.
Two things worth knowing
Nothing historic has been marked as acknowledged. Engagements that are otherwise finished but carry no acknowledgement are shown in their own group with a count, so the figure starts thin and fills in honestly as acknowledgements arrive, rather than opening with a number nobody agreed to.
And “billed without query” runs from today. A bill that was queried and then resolved before this release left no record behind it, so the measure says which date it counts from rather than implying a clean history.