Academy / Recruiting operations, CRM and pipeline discipline

LESSON 4 OF 6 · ADVANCED

Use stage aging to find stalled work

Track how long records remain in a stage and distinguish waiting on a candidate from waiting internally. Review overdue next actions and use them to fix the process, not automatically blame the recruiter. Aging is meaningful only when stage dates and definitions are reliable. Some searches legitimately take longer than others.

Learning objective

Define an aging review with reason codes and a next action.

About 2 minutes reading + 12 minutes practice. Take longer when needed.

Apply the method

Measure stage age from a defined event and pair it with a reason. Distinguish waiting on internal action, waiting on a candidate, awaiting a required approval and intentionally paused. Review whether the next action is still appropriate and who can remove the blocker. Compare like searches rather than ranking every role against one deadline. Aging can reveal poor coordination, but it does not alone diagnose recruiter performance. Keep date changes auditable so moving a record backward or editing an entry date cannot hide a delay.

A worked application

Fictional example: An executive candidate is waiting for a panel while a service candidate has requested a later conversation. Both records are 14 days old, but the appropriate actions differ. The executive search needs internal scheduling escalation. The service candidate needs respect for the agreed timing. A dashboard that labels both disengaged would direct the wrong intervention.

Common mistake to avoid

Do not reset stage dates to make the dashboard look current. Preserve the history and fix the actual blocked work.

Work through the case

FICTIONAL SCENARIO

An executive candidate has waited two weeks for an interview panel. The delay is internal scheduling, not candidate disengagement.

Make it practical

Define an aging review with reason codes and a next action.

Compare your reasoning with a worked response

Use a small, consistent set of reasons and assign someone to resolve the blocker. Avoid arbitrary promises that every role should move at the same speed.

Takeaway

Use the method to explain your decision, identify what you still need to verify and choose an accountable next step.

Treat the response as a model for reasoning, not the only possible wording. Adapt it to the role, evidence and appropriate organizational guidance.

Next lesson →

Sources for this course