Skip to Content
ChangelogSLA timing now follows a project the whole way, not just at intake

SLA timing now follows a project the whole way, not just at intake

The stage timers you configure under Configure → SLA only ever applied to brand-new requests. Once a project moved past intake, the clock stopped: nothing was measured against your targets, and the on-track, at-risk and breached labels could not appear no matter how long a project sat.

Every stage of the journey is now measured.

  • Experts see time against target on the work queue, with overdue projects called out instead of reading as on track.
  • CSMs get a real stage and a real band on the blocker queue, so a project that has stalled in scoping, bidding or delivery surfaces on its own.
  • SDMs see adherence figures that count the whole journey rather than the first step.
  • Projects that are delivered or out for a satisfaction survey now sit under Move to completion in the expert workbench, where the closing stages belong, rather than staying mixed in with live delivery work.

Finished and qualified-out projects deliberately carry no timer — nothing is outstanding on them, so nothing counts against a target.

Your configured targets, warning and breach thresholds are unchanged, and so is what each band means. What changed is how much of the journey they are applied to.

Last updated on