Back to all articlesManager routines

Review Overdue Actions Without Repeating the Same Status Question

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The weekly review reaches the same action again. The owner says it is still in progress. The manager asks when it will be finished. A new date goes into the tracker, and nothing changes about the missing input, competing work, or unclear acceptance criteria.

To review overdue action items usefully, classify why each item is late, inspect evidence for that explanation, and choose a response that changes the conditions for completion. Record a specific revised commitment and an intervention trigger. Keep the original deadline visible rather than replacing it.

This is an internal accountability routine, not a disciplinary process. Its purpose is to distinguish work that needs help, work that needs redefining, work that should stop, and work that needs a more explicit execution commitment.

1. Replace the status question with a decision question

“Is it done yet?” establishes a fact the overdue list already suggests. “What needs to change for this to finish?” creates a decision, but it still needs evidence to avoid another vague conversation.

For each overdue action, ask these questions in order:

  1. What exists now? Ask for the draft, completed portion, decision record, or other observable evidence of progress.
  2. What specifically prevents completion? Identify the missing input, unresolved choice, displaced capacity, remaining work, or unperformed next step.
  3. Which condition will we change? Decide who will unblock, clarify, reprioritise, resize, or recommit.
  4. What will happen next, and when will we intervene? Record a deliverable, an owner, a date, and a trigger that does not require waiting for another missed deadline.

Do not accept “busy,” “waiting,” or “nearly there” as complete explanations. They can be accurate starting points, but none tells a manager which decision to make. Ask what work displaced the action, whose input is missing, or what remains unfinished.

2. Classify the cause without turning it into a label for the person

Use the following categories as working diagnoses. They describe the current action, not the owner's character. More than one may apply; choose the primary cause that must be addressed first and note any secondary cause.

  • Blocked dependency: A necessary input, access decision, approval, or contribution is outside the owner's control. Look for the request, the named dependency owner, and what cannot proceed without it. Respond by securing a commitment, choosing a workaround, or changing the sequence.
  • Unclear scope: The owner and reviewer cannot agree on what completion means. Look for conflicting requirements, unresolved acceptance criteria, or repeated rework. Respond by defining the required output and explicitly excluding unnecessary work.
  • Changed priority: Other work has legitimately displaced the action. Look for the priority decision and its capacity implications. Respond by restoring its place in the queue, pausing it, or cancelling it.
  • Underestimated effort: The outcome is clear, but the remaining work exceeds the original plan. Look for completed components, newly discovered tasks, and an estimate of what remains. Respond by splitting delivery, reducing scope, adding suitable capacity, or extending the commitment.
  • Lack of follow-through: The action was understood, feasible, and sufficiently prioritised, yet the agreed next step did not happen. Check the other explanations before using this category. Respond with a concrete execution commitment and an earlier evidence checkpoint.

A missing input is not automatically the whole explanation. An owner might have requested it too late, or might still be able to complete independent work. Separate responsibility for resolving the dependency from responsibility for progressing everything else.

3. Use a filled review table, not an empty reporting template

Fictional worked example: The following internal review takes place on 14 October. All people, actions, dates, and quantities are hypothetical. The table is split into two linked panels so that the evidence and the resulting commitments remain readable. Each action ID connects the panels.

CAUSE AND DECISION
ID | Action; owner; original due date
   | Cause evidence
   | Manager decision

A1 | Finalise onboarding checklist; Maya; 10 October
   | Blocked dependency: draft exists, but Facilities has not
   | confirmed the access steps requested on 8 October.
   | Manager obtains a Facilities commitment; Maya continues
   | editing sections that do not depend on that answer.

A2 | Publish weekly reporting guide; Leon; 9 October
   | Unclear scope: reviewers disagree about whether the guide
   | must cover every exception or only the standard process.
   | Manager limits this version to the standard process and
   | a named route for exceptions; broader coverage is excluded.

A3 | Clean up internal project archive; Priya; 11 October
   | Changed priority: manager reassigned Priya to an urgent
   | operational handover on 7 October without pausing this item.
   | Pause archive work; retain history and set a restart review.

A4 | Reconcile equipment register; Omar; 10 October
   | Underestimated effort: 2 of 5 location lists are reconciled;
   | the remaining lists contain duplicate asset identifiers.
   | Split delivery: finish the clean records first and track
   | duplicate resolution as a linked action.

A5 | Submit rota handover notes; Eva; 11 October
   | Lack of follow-through: agreed format and source notes
   | exist; no blocker or competing priority is identified;
   | the planned drafting session did not happen.
   | Agree a protected drafting session and inspect the draft
   | before the final commitment.
REVISED COMMITMENT AND INTERVENTION
ID | Commitment recorded on 14 October
   | Trigger for further intervention

A1 | Manager: secure Facilities answer by 15 October, noon.
   | Maya: checklist ready for review by 16 October, 16:00,
   | conditional on receiving the answer at the agreed time.
   | If no answer by noon on 15 October, manager decides
   | whether an interim checklist is usable or work must wait.

A2 | Leon: standard-process guide ready for review by
   | 16 October, noon, using the agreed acceptance checklist.
   | If a reviewer adds an exception before then, manager
   | decides whether to defer it or explicitly change scope.

A3 | Priya: no delivery commitment while paused.
   | Manager: review restart or cancellation on 21 October.
   | If handover work continues, manager chooses again;
   | the archive action does not silently return to active work.

A4 | Omar: reconciled clean-record list by 17 October, 15:00;
   | duplicate-resolution plan with remaining effort by then.
   | If the next location reveals another type of discrepancy,
   | review scope before extending the commitment again.

A5 | Eva: draft by 15 October, noon; final notes by 16 October,
   | 15:00 after review against the agreed format.
   | If no draft exists at noon on 15 October, review the failed
   | execution plan that day rather than waiting for final due.

The important output is not the category name. Each row now contains a management choice that can be checked. The manager also owns commitments: obtaining an answer, protecting scope, or deciding whether paused work should resume.

4. Preserve the deadline history and make the current promise clear

Silently replacing a due date makes a late action look as though it was always planned for later. It also removes information needed to understand repeated deferrals and unrealistic planning.

Keep a small, append-only decision history. A spreadsheet, shared document, or task record can support this recommended practice; it does not require a particular application feature.

  • Original commitment: The original deliverable, owner, and due date.
  • Review entry: The review date, evidence, diagnosed cause, and decision.
  • Current commitment: The revised output, owner, date, acceptance criteria, and any explicit condition.
  • Intervention trigger: The event or checkpoint that requires another decision.
  • Outcome: Completed, cancelled, paused, superseded, or still active, with the relevant reason.

Make the current commitment easy to find; preserving history should not force readers to reconstruct the plan from a long comment thread. Keep the active promise near the top and retain dated changes below it.

If the deliverable changes substantially, close the original as superseded and link the replacement. Do not mark it completed merely because the team has agreed to do something different. Likewise, a paused action needs a review date, not a fictional delivery date.

5. Match the response to the cause—and expose the trade-off

A revised date alone is appropriate only when the underlying plan remains credible and the reason for the change is understood. Otherwise, it merely moves the next uncomfortable conversation.

Unblock without taking over everything

For a dependency, name both the action owner and the person responsible for securing the input. The owner remains responsible for independent work and for signalling when the dependency threatens the plan. The manager handles decisions or coordination beyond that owner's authority. Taking over the entire action may resolve today's delay while making ownership less clear next time.

Reduce scope without hiding unfinished work

A smaller deliverable can be useful if it meets a real internal need. State what it includes, what it excludes, and where excluded work will go. Calling an incomplete output a “first version” without acceptance criteria leaves the original ambiguity intact.

Reprioritise without pretending capacity is unlimited

If the action is still important, identify what will move out of its way. If nothing can move, pause or cancel it explicitly. Keeping everything active preserves the appearance of commitment while leaving owners to make unrecorded priority choices.

Address follow-through with observable work

When the plan was feasible but the next step did not occur, another verbal assurance adds little information. Agree on a visible intermediate output. Keep the checkpoint proportionate: enough to test whether execution has restarted, not a requirement to report every small activity.

6. Recover when the revised plan also fails

A second miss should trigger a review of the previous diagnosis and intervention, not an automatic repeat of the same remedy. Ask whether the promised management change actually happened. A manager who never secured the dependency cannot reasonably treat the resulting delay as unexplained owner inaction.

If the intervention happened but the action still stalled, inspect the evidence again:

  • The blocker moved: Identify the new dependency and decide whether the sequence remains viable.
  • The estimate is still unreliable: Break the remaining work into inspectable pieces before setting another final date.
  • Scope reopened: Confirm who can approve changes and whether the original commitment still applies.
  • Capacity disappeared again: Make the competing priority decision explicit rather than asking for both outcomes.
  • The execution commitment failed: Examine whether the next step was specific, feasible, and actually protected.

If nobody can describe a credible path to completion, record a decision to pause, reassign, redesign, or cancel the action. Leaving it indefinitely “in progress” is not a neutral choice; it keeps an unsupported commitment on the list.

7. Run the next review around evidence and decisions

Before the meeting, ask owners to add the current work product, the remaining obstacle, and their proposed response. In the meeting, confirm straightforward completions briefly and spend discussion time on decisions that need other people, authority, or a priority trade-off.

End each discussion by reading back the changed commitment and trigger. An owner should be able to correct an unrealistic assumption immediately, particularly when completion depends on another person's input.

For the next review, use this hypothetical trial: take five overdue actions and complete the two-panel record for each. Check three things at the following review:

  1. How many have a supported cause, rather than a generic status explanation?
  2. How many agreed interventions actually happened, including the manager's commitments?
  3. How many reached the promised output or triggered a timely decision before another deadline passed?

Keep original deadlines and subsequent changes visible throughout the trial. The observable improvement to look for is not simply fewer overdue rows. It is fewer unsupported promises: actions either progress under changed conditions, receive an explicit new decision, or leave the active list for a documented reason.

Manager routinesAction accountabilityWeekly reviewsTeam execution

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications