How to keep track of candidates after back-to-back screens: the fields, the close-out and the weekly sweep

Recruiters who run eight screens a day keep track by writing, not remembering. Before the next call starts, they record the same few fields for every candidate: a status, the next step with a date, the one detail that sets this person apart, and anything they promised on the call. After each block of calls they spend ten minutes closing out, updating the ATS stage, setting a dated reminder for every next step and sending what they promised, and once a week they sweep for anyone stuck or waiting. Then nothing depends on what you can recall at four in the afternoon.

This page is about the tracking system: what to log, where, and the routines that keep it current. The other half of the problem, keeping your judgment sharp across a long day with prep cards, a three-line note and gaps between calls, is in how to keep candidates straight on high-volume screening days.

What should you record for every candidate before the next call?

Use the same fields every time, in the same order, so a gap stands out. The examples are invented.

What goes in the note itself, and what to leave out, is covered in how to write candidate notes in your ATS. The questions that produce these fields on the call are in the recruiter phone screen template.

How do you close out a block of back-to-back screens?

Book ten to fifteen minutes after every block of three or four calls and treat it as a meeting. Work down the list in this order:

1. Move every candidate to the right ATS stage. A screened candidate still sitting in "New" is invisible to the hiring manager and to your own reports.
2. Paste the fields above into each record, starting with the hook line.
3. Set a dated reminder for every next step. Most systems have one. Greenhouse, for example, lets recruiters schedule follow-up reminders for specific candidates that appear on the assigned user's dashboard, and can set them for several candidates at once with its bulk edit (follow-up reminders; in bulk, as of October 2026).
4. Send what you promised. Job description, pay band, benefits summary, scheduling link. If it cannot go now, the reminder from step 3 covers it.
5. Send or schedule clear rejections. A same-day, polite no is better for the candidate than a week of silence; wording is in the candidate rejection email templates.
6. Give every Hold a decision date. "Hold until the HM reviews the first three, decide by Friday" is a plan; "Hold" alone is a candidate who never hears back.
7. Clear your scratchpad. Anything on paper or in a day sheet is now in the ATS; bin the sheet.

Submit candidates who are ready during the same close-out if you can; the timings for that are in the screen to submittal workflow.

What a finished close-out looks like

Invented example: four morning screens for one warehouse operations lead requisition, closed out at 11:40. Every row has an owner and a date; none says only "Hold".

At four in the afternoon, after four more calls for a different role, this table and its reminders answer every question about the morning without anyone having to remember it.

Should the tracker live in the ATS or a spreadsheet?

The rule that works: the ATS is the record, anything else is a scratchpad that lives one day. A long-lived spreadsheet of candidates is still candidate data, with the retention questions covered in how long to keep interview notes.

How do you track promises so nobody is left waiting?

Candidates remember exactly what you said you would do. Recruiters running eight calls a day forget, not from lack of care but because the promise was one sentence in a thirty-minute conversation. Three habits close the gap:

• Write the promise as you make it, in the promises field, with a day: "Call Thu either way".
• Set the reminder before the next call, not at the end of the day.
• Promise less and keep it. "You'll hear from me by Friday, whatever the answer" is better than "I'll call tomorrow" when tomorrow depends on a hiring manager.

How do you find a candidate later when you only remember one detail?

• Lead the ATS note with the hook, in plain words that search will match: "3PL returns, 40 staff", not "great ops background".
• Name calendar events with the hook, such as "Dana, 3PL returns, Ops Lead", so the day's calendar doubles as an index.
• Use the same tags every time, for example the requisition number and "screened" with the week, so a filter brings back one week's screens for one role.
• Keep the hook neutral and job-related. "Spanish and English, bilingual customer service" is a hook; anything about appearance, age, family or health is not, and should never be written.

What does a weekly sweep look like?

Thirty minutes at the same time each week, working from ATS filters rather than memory. The thresholds below are examples; set your own.

1. Candidates in a "screened" stage for more than five business days (example threshold) with no next step.
2. Reminders that are overdue or were dismissed without the task being done.
3. Holds past their decision date.
4. Rejections decided but not sent.
5. Duplicate records for the same person, merged with your ATS's own tool rather than by copying notes across.
6. Promises still open from last week.

What if your tracker and your memory disagree?

Trust the note written at the time; that is why you wrote it. If a record is wrong, correct it with a dated line ("Corrected 14 Oct: notice is 4 weeks, not 2; confirmed by email") rather than overwriting it. If you are not sure which of two candidates said something, leave it out of both records and ask with a short call.

Where do transcripts and AI notes fit?

A transcript, used with the candidate's consent, answers "who said what" when you check a detail, but it is not a tracker: it has no status, no next step and no promise list. Use it to fill the fields, then track the fields. Interview Signal (we make it) is one example of a tool that can export each interview as a CSV row for a tracker or as a note shaped for Bullhorn, Greenhouse, Lever or JobAdder; it has no ATS integration, so those notes are pasted by hand at the close-out.

Examples and thresholds on this page are invented or illustrative. ATS features are described from the linked help pages as of October 2026.