Cycle time and delivery
How long from request to review, and are we delivering on time?
Request-to-route cycle time — selected periodC.1
19days
Not affected by Status
Smartsheet
C.1
not decided
Gate variance days — selected periodC.2
+4.5days
Not affected by Status
No source yet
C.2
not decided
Projects with no activity — as at todayC.3
26projects
No source yet
C.3
not decided
Cycle time distributionC.4
Each number is a count of routed requests. 423 requests, 90th percentile 30 days. T-11 — no target set. The band is drawn only once an owner agrees the number; no target agreed; existing Smartsheet 3-day review figures are not yet mapped to this band. Identical to Blockers 4.3. Not affected by Status.
Smartsheet
C.4
not decided
Planned and actual days by stageC.7
- Planned
- Actual
Planned time comes from each project's own gate plan; it is not a target. 205 gates passed in Last 90 days; days from the previous gate's actual date. Request intake has no previous gate.
No source yet
C.7
not decided
Days in stage by stageStage sort order · the same measure Stages 3.2 draws as barsC.6
| Stage | Live projects | Median days in stage | Longest days in stage |
|---|---|---|---|
| Request intake | 13 | 22 | 39 |
| Assessment & qualification | 15 | 15 | 29 |
| Route decision | 9 | 12 | 26 |
| Pre-sales & offer | 15 | 19 | 41 |
| Present & negotiate | 7 | 10 | 27 |
| Agreement | 14 | 33 | 60 |
| Delivery | 22 | 36 | 68 |
| Feedback & closure | 3 | 7 | 23 |
Live projects is a count; the other two columns are days. Sequential conditional formatting is off because the three columns are different units and one ramp across them would compare a count with a duration. No target set on any stage — T-13 needs one target per stage, and none is agreed.
No source yet
C.6
not decided
As at 29 Sep 2026 · EPMS refreshed 29 Sep 2026 06:12 UTC · one source, no second system