Two claims are sixty days old. One entered the approval queue yesterday after a lengthy evidence review. The other has been ready for the same approver for three weeks. Sorting by overall age alone puts them side by side and hides the more actionable difference.
Define a clock for the decision
Capture the date a claim entered its current stage, when the next actionable task became ready and the owner of that task. A note added by an administrator should not automatically restart the action clock. Define which event genuinely advances the work, such as receiving requested evidence or completing an authorised review.
Test the weekly report with individual files
Take the two oldest rows in each stage and reconstruct the dates from their histories. A long wait for an external document needs a chase owner. An approved packet sitting in an internal queue needs a handoff owner. Report the number awaiting each kind of action and the oldest relevant date. Supervisors can then allocate capacity using an explanation that individual handlers recognise in their own caseload.
More to discover in Numerish.
Explore related insights and practical enterprise workflows.



