Candidate Pipeline Organizer

Put structure around hiring so that no candidate is lost, no interview happens without criteria, and the pipeline's health is visible at a glance. Small teams lose good candidates to disorganization far more often than to compensation — a week of silence reads as rejection to a strong applicant. This skill sets up the stages, the scorecards, and the weekly ritual that keep a pipeline honest.

When to use this skill

Several roles or many candidates are in flight and tracking lives in inboxes and memory
Candidates keep going quiet mid-process, or worse, the team goes quiet on them
Interviewers give verdicts like "good guy, not sure" and decisions wobble
A founder or manager is hiring for the first time and wants a system before volume hits
Someone asks to "get on top of hiring" or build a candidate tracker

First-run setup

Define the stages once, each with an entry rule, an exit rule, and a service-level target. The recommended default:

Applied      -> Screen        exit: screen decision      SLA: 5 business days
Screen       -> Interviews    exit: loop completed       SLA: 10 business days
Interviews   -> Debrief       exit: hire/no-hire logged  SLA: 2 days after loop
Debrief      -> Offer         exit: offer accepted/lost  SLA: 3 business days
Any stage    -> Closed        always with a reason and a sent message

Every stage transition is somebody's named job. A stage without an owner is where candidates go to be forgotten.

Workflow

Normalize intake: every candidate gets one record with name, role, source, current stage, owner, next action with a date, and last-contact date. A candidate without a dated next action is by definition stuck — make that state impossible to ignore.
Write scorecards before interviews are scheduled: four to six competencies per role, each with one line describing what strong evidence looks like. Interviewers score independently, in writing, before hearing anyone else's view. No scorecard, no interview.
Assign each interviewer a lane — competencies they own — so the loop covers the role instead of asking the same favorite question four times.
Run the weekly pipeline review walking stages right to left, offers first: for every candidate confirm next action, owner, and date; flag anything beyond its SLA; close out anyone the team has silently decided against but not told.
Hold the communication cadence: acknowledge every application within two business days, update active candidates weekly even when the update is "no update", and send rejections within three days of the decision with a sentence of respect for their time.
Log debrief outcomes as decisions with reasons — scores first, discussion second, so the loudest voice does not become the hiring bar.
Review the funnel monthly: conversion between stages, time-in-stage, and source quality. Fix the widest leak first; it is usually debrief-to-offer delay, not top-of-funnel volume.

Output format

Maintain the tracker as a table — one row per candidate — plus a weekly summary:

| Candidate | Role | Stage | Owner | Next action (date) | Last contact | Flag |

Weekly summary: candidates per stage, SLA breaches (named), offers out,
decisions needed this week, sources of this week's best two candidates.

Common failure modes

Stages defined but SLAs not, so "in process" quietly means "in limbo"
Scorecards written after the interviews, to justify the vibe
The strongest candidate parked while the team waits for a unicorn to compare against
Rejections batched monthly, burning the employer's reputation one silence at a time
A tracker nobody owns, updated the night before the review
Debriefs where the most senior voice speaks first and the scores drift to follow it

Quality bar

No candidate exists without an owner and a dated next action
No interview happens without a scorecard, and no debrief starts before scores are in
Every closed candidate received a closure message — silence is not an outcome
SLA breaches are visible and named in the weekly summary, not smoothed over
Candidate records hold evaluation evidence, never gossip; write every note as if the candidate could read it, and share records only with people in the hiring decision