How to write candidate notes in your ATS

A good ATS note answers a question someone will ask later, not just what happened on the call today. The fix is a structured template with the same fields every time — role fit, compensation, availability, risk, next step — instead of a paragraph of prose, because structured fields are what makes a candidate findable by search six months from now, when neither you nor the hiring manager remembers the details.

This is a different problem from what goes wrong inside interview notes. For the compliance side — what never belongs in a note, with rewrites — see what not to write in interview notes. For a hiring manager capturing notes live during the interview itself, see how to take interview notes as a hiring manager. This page is about the recruiter's own record in the ATS, written after the call, and built to be searched later.

What an ATS note is actually for

Three different readers use the same note, at three different times, and a note that only serves the first one fails the other two:

• You, in six months. A former candidate reapplies, or fits a new role. Can you tell, from the note alone, whether to call them again without redoing the whole screen?
• Your team, today or next week. A colleague covers your desk, or searches the ATS for anyone with a specific skill or certification. Does the note contain the words they would search for?
• Compliance, if it is ever requested. Notes can become part of a hiring record. Does the note describe job-related facts, not impressions of the person?

A structured note template for every stage

Use the same field structure at every stage so the record reads consistently as it grows. Fill only what applies; leave the rest blank rather than padding it.

[SCREEN NOTE — after the initial call]
Role fit: [which must-haves confirmed, in one line each]
Compensation: [stated expectation, base/bonus, how firm]
Availability: [notice period, earliest start]
Motivation: [why looking, in their words if possible]
Risk / gap: [what to probe further, stated plainly]
Other processes: [interviewing elsewhere? stage?]
Next step: [submit / hold / pass, and why]

[SUBMITTED NOTE — when sent to a client or hiring manager]
Submitted to: [client/team], [date]
Client-visible summary: [the version they would see — see submittal
  template]
Internal-only: [negotiation posture, competing offers, anything not
  meant for the client]

[CLIENT FEEDBACK NOTE — after client response]
Outcome: [advance / pass / no response by date]
Client's stated reason: [in their words, not your interpretation]
Candidate informed: [date, method]

[POST-INTERVIEW NOTE — after client or panel interview]
Client feedback received: [date, from whom]
Candidate's own debrief: [how they read the interview]
Next step: [second round / offer stage / pass, and why]

Each block is short by design. A note that runs to several paragraphs of prose is harder to scan and, in practice, gets skipped by whoever needs it next.

Write for search, not just for today

A note that reads clearly today can still be useless in a search six months later if it uses vague language instead of the specific terms someone would search for. This is the single biggest difference between an ATS note and a set of interview notes: the note has to survive being found by a keyword, not just being read once in context.

If your ATS supports tagging, tag consistently: the same certification or tool should always be tagged the same way across your whole team's records, not "PMP" from one recruiter and "Project Management Professional" from another. Agree on the tag list once, in writing, rather than letting it form by habit.

Internal notes versus client-visible notes

Keep these visually and structurally separate, not just mentally separate, because the easiest way to send a client something you should not is copying from a note that mixes both.

• Client-visible: role fit, availability, compensation the candidate agreed to share, and any risk you would raise with the client directly.
• Internal-only: your honest read on negotiation room, competing offers and how real they seem, your confidence level in the candidate, and anything the candidate told you in confidence that is not relevant to the client's decision.

If your ATS has a permissions setting that hides internal notes from client-facing exports or portals, use it, and test it once with a real export rather than assuming it works as described.

A worked example: vague note to structured note

The second version is longer to write but faster to use later: a colleague searching for "Postgres" or reviewing the record before a submission sees exactly what is confirmed and what is still open, instead of having to re-contact the candidate to find out what "a little unsure" meant.

Keeping notes fast: write them the same hour

Speed and quality trade off in the wrong direction once notes are written from memory. A structured template with short fields, filled in immediately after the call, is faster than a well-written paragraph composed later — the fields tell you what to write, so there is no blank page to face. If your screens are recorded with a tool like Interview Signal, pulling the exact wording for the "evidence" fields straight from the transcript is faster and more accurate than reconstructing it from memory. If you interview across states or record calls for accuracy, tell the candidate at the start of the conversation; the wording and the states requiring both-party consent are covered in our consent guide.

Consistency across a team

One recruiter's well-organized notes do not fix a desk-wide search problem if everyone else writes differently. Three things make the template stick:

1. Put the template in the ATS itself, as a note type, saved snippet, or custom field set, rather than a document people have to remember to open.
2. Review a small sample monthly, not for grading individuals, but to catch drift — a field that has quietly stopped being filled in, or a tag being used two different ways.
3. Bring it up in onboarding, not as a policy read once, but as one of the first things a new recruiter is shown, alongside their first real candidate call.

A monthly sample check is quick: pull ten random screen notes from the past month and check two things — does each note have every field filled or clearly marked not applicable, and could a colleague act on it without calling the candidate back to ask something the note should already answer. A pattern of missing compensation fields, for example, usually traces back to one step in the call script being skipped, not to ten separate recruiters independently forgetting to ask.

When a candidate resurfaces for a different role

This is the moment a structured note pays for itself. A candidate you screened eight months ago for a role that closed reappears as a possible fit for something new, and the only question that matters is whether the old note answers today's requirements without a full re-screen.

Flag which fields age well (skills, certifications, general seniority) and which do not (compensation, availability, motivation) so whoever reopens the record does not treat an eight-month-old notice period as current. A quick "last confirmed [date]" line on time-sensitive fields does this without adding a new template section.

What still belongs in the compliance article, not here

This page is about structure and searchability. It does not cover which words create legal risk in a hiring record — protected characteristics, appearance commentary, speculation about a candidate's personal situation. That is a different problem with a different fix, covered fully in what not to write in interview notes, including a full rewrite table. Use both: structure from this page, judgment from that one.