Candidate Pipeline Tracker: See Every Submission and Where It Stalled

A candidate pipeline tracker exists to answer two questions on demand. For the client: how many candidates are live against this role and what stage is each at. For the agency owner: which stage is quietly killing submissions, and on which account.

How it is done today

The usual setup is a spreadsheet per client, a WhatsApp group per mandate, and a recruiter's memory holding the rest. Statuses are updated before the client call and not much in between, so the sheet describes last Tuesday.

The failure is rarely the spreadsheet itself. It is that a status column records the present and destroys the past. Once yesterday's stage is overwritten, nobody can say how long a candidate sat waiting on client feedback, which is the number that decides whether the client or the desk is the bottleneck.

Split the data into two objects. The candidate master holds the person. The submission holds that person against one role.

Candidate master

• Candidate ID, name, mobile, email — mobile is the deduplication key.
• Current employer, designation, total and relevant experience.
• Current CTC, expected CTC, notice period, buyout possible.
• Current location and willingness to relocate.
• Source — job portal, referral, inbound, database — recorded once and never overwritten.
• Do-not-contact flag and last contacted date.

Submission record

• Client and role, plus the recruiter who owns this submission.
• Stage and stage-entered date — the date matters more than the stage.
• Submitted date, client feedback date, feedback text.
• Interview round, mode, scheduled date and outcome.
• Offer date, offered CTC, expected joining date, joined date.
• Drop reason — counter-offer, location, compensation, client rejection, candidate withdrawal.
• Days in current stage — calculated, and the first column to sort by.

An illustrative example for a single mid-level role, not benchmark data. The point is not the numbers but what the shape reveals once stage dates exist.

Read the last column before the third. Six median days sitting in submitted means the client is slow to respond, which is an account conversation, not a sourcing problem. The 43 per cent shortlist rate says the brief is being read reasonably well. The offer-to-join step is where this role actually lost, and that is a notice-period management problem with a known remedy.

Ownership stops being implicit

With one recruiter, ownership is obvious. With four, every submission needs a named owner and a rule for who contacts a candidate already in play, or the agency starts competing with itself inside a single mailbox.

Follow-up becomes scheduled rather than remembered

Screening calls, interview reminders and notice-period check-ins are predictable events. In a CRM they become sequences with due dates and assigned owners, so a busy week does not silently drop the candidate who was about to accept.

Reporting stops being a Friday task

Because stage changes are stamped as they happen, the per-role funnel and the recruiter-wise submission count are already calculated. The client update becomes an export rather than an evening of reconciliation.

Using a status column with no history

Overwriting the stage destroys the only data that explains delay. Keep the date each stage was entered, even if you keep nothing else.

Free-text everything

Notice period written as two months, 60 days and 2 Months cannot be filtered. Structure the four or five fields you will actually search on.

No drop reason

Rejected is not a reason. Without a short, fixed list of drop reasons, the pattern behind repeated losses on one account stays invisible.

Tracking activity instead of outcomes

Calls made is easy to count and rarely diagnostic. Submissions per role and stage conversion tell you where to intervene.

Continue with lead management software, CRM with a built-in dialer, WhatsApp CRM, CRM vs Excel, the tools library, and industry CRM pages.