Executive Summary To maintain an accurate recruitment tracker and consistent follow-up cadence, you need (1) a single source of truth for candidate data, (2) a standardized pipeline with stage definitions, (3) an activity-based follow-up SLA per stage, and (4) lightweight governance (weekly checks + QA rules) so nothing slips or gets lost.

Key Recommendations

1. Build your tracker around “stages + owners + next action”

Instead of only tracking “status,” make every candidate row include:

• Candidate ID + core details (name, contact, source, role applied)
• Current stage (with clear definitions)
• Process owner (recruiter) + hiring manager (if applicable)
• Next scheduled step (date/time)
• Next action + channel (call/email/WhatsApp/interview)
• Follow-up due date (auto-calculated)
• Last activity date + notes (what happened, outcome, who engaged)

Why this works: accuracy improves when the tracker is driven by required next actions, not past updates.

1. Use a standardized pipeline with “exit criteria” per stage

Example pipeline (edit to your reality):

• Applied / Resume received
• Screened (pass/fail + rationale)
• Interview 1 scheduled
• Interview 1 completed
• Interview 2 scheduled
• Interview 2 completed
• Final / Case / Panel (as applicable)
• Offer discussion / negotiation
• Offer accepted / rejected
• Closed (no response / withdrawn)

For each stage, define:

• What qualifies as “entered” (e.g., “Screened = recruiter completed phone screen and updated scorecard”)
• What qualifies as “exited” (e.g., “Interview 1 completed = scorecard submitted + notes logged”)

1. Define follow-up cadence with SLAs by stage

Use a simple SLA grid so every candidate gets consistent treatment. Example cadence (for a typical 2–4 week process):

• After application received (0–2 days): first outreach within 24–48 hours
• Screen stage pending response from candidate:
• Day 2–3: follow-up 1
• Day 5–6: follow-up 2
• Day 8–9: follow-up 3 (then tag as “No response—nurture” or “Closed” based on your policy)
• Hiring manager scheduling (interview scheduling window):
• If not scheduled within 3 business days: recruit “nudge” to hiring manager
• If not completed within 7 business days: escalate to recruiting lead/HRBP
• Interview completed but decision pending:
• Hiring manager decision due within 2 business days
• If delayed: recruiter follow-up daily (or every 2 business days) until decision recorded
• Offer stage:
• Offer follow-up every 2 business days until accepted/rejected
• Rejection / closure:
• Communicate outcome within 24–72 hours of the decision (even if candidate still matters for future roles)

The point isn’t the exact numbers—it’s that every stage has a predictable “touch rhythm” for both candidate and internal stakeholders.

1. Assign ownership rules so updates happen reliably

Common failure: “someone will update it.” Fix it with role clarity:

• Recruiter owns: tracker accuracy, candidate outreach, follow-up cadence, stage progression
• Hiring manager owns: decision + scorecard submission by SLA
• Admin/TA ops (if any) owns: data hygiene, scheduling confirmations, bulk rejection emails

Rule of thumb: if the hiring manager cannot update the system, require them to submit scorecards within the same SLA so the recruiter can update immediately.

1. Create “auto-reminders” and “do-not-skip validations”

Whether you use ATS (recommended) or a CRM/spreadsheet, add two safety checks:

• Reminder triggers: “Next action due” alerts (daily review)
• Validation rules: stage cannot change without (a) interview notes or (b) candidate outcome + timestamp

This prevents the tracker from becoming a passive log.

1. Add a QA routine: daily micro-check + weekly pipeline audit

Daily (15 minutes):

• Sort by “Follow-up due” and “Next action missing”
• Reach out to candidates whose due dates are today/overdue
• Confirm any interview events scheduled correctly

Weekly (60 minutes):

• Pipeline aging: candidates stuck > SLA threshold
• Stage conversion rates (e.g., applied → screen, screen → interview)
• Hiring manager responsiveness (decision SLA breaches)

1. Track “candidate experience” fields (small effort, big impact)

Include:

• Candidate communication log (short)
• Sent templates used (optional)
• Reason codes for rejection / drop-off
• Consent/preferences (e.g., WhatsApp vs email)

This improves consistency and reduces repeated questions.

How to implement fast (practical setup)

• Choose your tool structure:
• Best: ATS with workflow + reminders
• Good: CRM + pipeline stages + automated tasks
• Minimum: spreadsheet + calendar reminders (works only with strict cadence discipline)
• Define your stage list + SLA grid (1 page)
• Create tracker columns (as above)
• Set a “daily overdue follow-up” view
• Start with one role/pipeline for 2–3 weeks, then refine

Business Impact

• Higher offer acceptance: fewer candidates feel ignored
• Faster hiring cycles: internal delays become visible and managed
• Better reporting: stage conversion + time-in-stage becomes accurate
• Reduced recruiter effort: fewer manual “chasing,” more system-driven next steps

Risks & Mitigations

• Risk: Tracker becomes inaccurate due to late updates
• Mitigation: enforce “stage change requires notes/outcome + timestamp,” plus daily overdue review
• Risk: Follow-up cadence feels spammy or inconsistent
• Mitigation: cap touches per stage, personalize first outreach, and use rejection quickly once decided
• Risk: Hiring manager delays break cadence
• Mitigation: decision SLAs + escalation path + require scorecard submission

Immediate Next Steps

1. Draft your pipeline stages + exit criteria for one open role.
2. Define your SLA cadence by stage (use the example grid; adjust to your average process length).
3. Set up tracker fields: Stage, Owner, Next action, Next due date, Last activity, Notes/Outcome.
4. Create two views: “Follow-ups due today/overdue” and “Aging > SLA.”
5. Run a 2-week pilot and tighten the rules based on what actually slipped.

If you need help implementing these recommendations or would like expert guidance tailored to your organization, the team at Zunavish would be happy to assist.