Task-Boundary Mode How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
Dashboard / Cycle Time / Stage-to-Stage Wait Time
Benchmark
Medium Impact

Stage-to-Stage Wait Time

Wait vs Touch
stage-by-stage decomposition
Benchmark Measurement This finding is an observation that informs strategy — not a direct savings opportunity. It measures workforce behavior and AI readiness to guide where the savings-producing findings will have the greatest impact.

Description & Data Evidence

Decomposing case cycle time by PV stage shows vast wall-clock spans (49,392h total) with only 3.6h of focused interaction (dwell). 13,602 stage-mapped events provide an effort proxy where dwell is unavailable. Worst inter-stage transition: 'Intake -> Assessment' averages 24.3h gap.

Self-Evaluation Scores

The platform grades each finding on four dimensions (1–5 scale). Low scores flag findings that need more data or clearer remediation before acceptance.

Overall 4/5
Actionability 3/5
Specificity 4/5
Remediation Alignment 3/5

Key Findings

  • Stage wall-clock spans total 49,392h; focused dwell totals 3.6h
  • 13,602 stage-mapped events across 8 PV stages
  • Worst transition gap: 'Intake -> Assessment' at avg 24.3h
  • Dwell only captured for click/browser events (~19%); event count used as secondary effort proxy
  • Wall-clock includes idle, multitasking, and queuing time between interactions

Remediation Ideas

  • Automated stage advancement triggers when prerequisites are met
  • Real-time workflow dashboard showing cases waiting at each stage
  • SLA alerts for inter-stage gaps exceeding thresholds
  • Parallel processing of independent stages where workflow permits