Case predictions, delay drivers and what-if: when a case will finish and what slows the process

Expected to finish

• When an open case is opened on the employee portal, its timeline shows Expected to finish: the most likely date, a range (25th to 75th percentile) and the chance of taking longer than usual.
• It compares finished cases of the same source that reached the case’s current step and took at least as long from there as the case has already waited. They share as many of the source’s breakdown columns (such as supplier or region) with the case as still leaves 10; the last columns are dropped first.
• Expected finish = when the case reached its step + the median of their remaining time. The usual time is the 80th percentile of the source’s finished cycles.
• The basis (how many cases, which step, which columns matched) is shown with it. With fewer than 10 comparable cases it says too few, with the count; a finished case shows none. When the organization counts working days, so do the figures.

See the delay drivers and simulate

1. Open the process page of a cases table and, on a published source, click View next to Delay drivers.
2. The list is ranked by the extra days in all, at most 10: a value of a column (such as “Supplier = A”) with at least 10 finished cases whose median cycle is longer than the others’.
3. Click Simulate: if those cases took at most the others’ median, how the source’s median cycle and its share within the usual time would change, and the days saved in all.

Who sees what

• A case’s prediction goes only to people who see the case. Delay drivers and what-if go to people who may read the project’s process data, as with metrics.
• Every case of the source counts, but only medians, ranges and shares are shown, never another case.
• Reading Cases through OData adds PredictedFinish, PredictedFrom, PredictedTo and RiskScore, under the same rules as the portal.