Review work that is taking unusually long
Use elapsed work age to trigger timely conversations about blockers.
How this works
Use elapsed work age to trigger timely conversations about blockers.
Use elapsed work age to focus conversations on blockers and next actions. Compare like-for-like work and distinguish total age from time spent in the current state; an old item may have a valid wait or a different service class.
Before you start
Defined operating scope
Open work items can be compared with historical cycle times to prompt a blocker discussion.
Required source material
Obtain Open work items; Historical cycle times. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The start date is missing or inconsistent. Mark age unknown and request correction rather than assigning zero.
Prepare the inputs
- open_items
- Required
IDs, start dates, states and owners
Define when active work begins.
- historical_cycles
- Required
Completed items and durations
Use comparable work types and valid timestamps.
- age_rules
- Required
Review checkpoints and calendar convention
Specify calendar versus business time.
- context
- Required
Blocked periods and agreed due dates
Keep known waiting reasons visible.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check open_items, historical_cycles, age_rules, context before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected open_items and any missing required fields.
Calculate each item’s current age
- Calculate each item’s current age from the agreed start event and reporting cutoff using deterministic time arithmetic.
- Recompute age from the agreed start and cutoff, including timezone boundaries.
Checkpoint: A saved intermediate result for: Calculate each item’s current age.
Compare it with agreed historical checkpoints
- Compare against historical checkpoints for the same work type, retaining sample-size limitations.
- Check historical cohorts exclude cancelled or incomparable items where the definition requires it.
Checkpoint: A saved intermediate result for: Compare it with agreed historical checkpoints.
Ask owners to review blockers and next actions
- Ask owners to review blockers, dependencies and next actions, recording explanations instead of automatically reprioritizing or blaming.
- Recompute age from the agreed start and cutoff, including timezone boundaries.
Checkpoint: A saved intermediate result for: Ask owners to review blockers and next actions.
Reconcile the proposed result
- Recompute age from the agreed start and cutoff, including timezone boundaries.
- Check historical cohorts exclude cancelled or incomparable items where the definition requires it.
Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.
Package the result and unresolved work
- Investigate context before reprioritizing; an old item is not automatically low quality.
- Age is a conversation trigger, not a quality or employee-performance score.
Checkpoint: An aging-work review queue. Unresolved items remain visible in the review record.
Decisions along the way
The start date is missing or inconsistent.
Mark age unknown and request correction rather than assigning zero.
The historical comparison mixes unlike work types.
Split the baseline or state that comparison is not reliable.
An old item is waiting on an agreed external date.
Record the valid wait and schedule an appropriate review instead of declaring failure.
What you will produce
aging-work-review-result.json
JSONAn aging-work review queue. Label proposed and completed states separately.
Include: item_id · age · comparison_group · review_checkpoint · blocking_context · owner · next_action · status · evidence_reference · review_note
aging-work-review-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving context.
Include: source_reference · question · owner · next_action
Check the result
- Recompute age from the agreed start and cutoff, including timezone boundaries.
- Check historical cohorts exclude cancelled or incomparable items where the definition requires it.
- Inspect open_items and historical_cycles in both the original and output; confirm that record identity and interpretation survived the transformation.
- Investigate context before reprioritizing; an old item is not automatically low quality.
When something goes wrong
The start date is missing or inconsistent.
Mark age unknown and request correction rather than assigning zero. Retain the affected evidence and recovery status.
The historical comparison mixes unlike work types.
Split the baseline or state that comparison is not reliable. Retain the affected evidence and recovery status.
An old item is waiting on an agreed external date.
Record the valid wait and schedule an appropriate review instead of declaring failure. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Review work that is taking unusually long for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Item W-3 began 12 calendar days ago; similar items usually trigger review at day 10. It is waiting for a customer document promised tomorrow.
Expected result
Synthetic expected result: Queue W-3 for owner review with age 12 and the documented dependency. Proposed next action is checking tomorrow’s document, not automatically escalating performance.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure owner-confirmed blockers surfaced; false alerts and time to a next action.
Stop or revise
An old item is waiting on an agreed external date. Pause affected records and apply this recovery: Record the valid wait and schedule an appropriate review instead of declaring failure.
Keep the scope clear
- Age is a conversation trigger, not a quality or employee-performance score.
- Owners decide reprioritization and escalation after reviewing context.
Check before using
Investigate context before reprioritizing; an old item is not automatically low quality.
Business activities
- Deliver recurring client work
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Open work items · Historical cycle times
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow