Resume Screening Checklist for Recruiters: 12 Checks in Order

A good resume screening checklist has twelve checks in a fixed order: hard requirements first, then evidence of the work, then fit with the role's level and context, then a recorded decision. Run it the same way on every application and each resume takes about two minutes. The order matters more than the length of the list, because it stops you spending ten minutes admiring a resume that fails a knock-out in the first line.

This is the checklist we would use on a stack of applications for one role. It works on paper, in a spreadsheet or in software. It assumes you have already turned the job description into a short screening scorecard; without that, a checklist just gives you a tidier form for the same inconsistency.

Before you open the first resume

Three things need to exist before any reading happens.

1. A list of five to eight requirements, each one something you could verify from a document.
2. The two or three knock-outs, written as plain yes or no questions.
3. A place to record the decision and the reason, one line per candidate.

If any of these is missing, stop and write it. Fifteen minutes here saves hours across a pile of two hundred.

The twelve checks

Pass or fail checks (about 20 seconds)

1. Right to work and location. Does the candidate meet the legal and logistical basics for the role? If the form already asked, you are only confirming it.
2. Required credentials. A licence, registration or certification that the role cannot be done without. Check that it is current and appears in the resume as more than a line in a list.
3. Minimum scope. Instead of counting years, check whether the most recent role involved the kind of work the job needs. A "marketing manager" who ran one newsletter and a marketing manager who ran a budget are different applicants with the same title.
4. Readable document. If the file is corrupt, empty or missing pages, that is a parsing problem, not a candidate problem. Ask for another copy before rejecting. See resume parsing explained.

Evidence checks (about 90 seconds)

1. Evidence for each requirement. For every item on the scorecard, find a specific line in the resume. A skill in a list counts for less than a skill attached to something the person did.
2. Ownership. Look for verbs that show who did the work. "Responsible for" and "involved in" tell you the role existed. "Built", "negotiated" and "cut" tell you what the person did.
3. Recency. Evidence from last year outweighs evidence from eight years ago, unless the skill does not decay.
4. Outcomes where they exist. A result is a bonus, not a requirement. Plenty of good work has no number attached, and demanding one filters for resume style rather than ability.

Context checks (about 20 seconds)

1. Level match. Is the scope of past roles in the range of this one, allowing a step up or sideways move? Over and under-qualification are both worth a note, not an automatic no. See overqualified candidates.
2. Tenure pattern. Note anything unusual, then decide whether it needs a question. Short stints and gaps have many ordinary causes. See reading employment gaps.

Decision checks (about 10 seconds)

1. Yes, maybe or no. Three buckets are enough for a first pass. A ranked list of 200 gives a false sense of precision.
2. One line of reasoning. Write the specific thing that decided it: "Ran quarterly close for two entities, no controls exposure." That line is what you use when a hiring manager asks why, and it is what a candidate is owed if they ask for feedback.

What to leave off the checklist

Some things feel like screening criteria and are not.

Recording and reviewing decisions

Keep the log simple: candidate, bucket, one-line reason, reviewer, date. After the first twenty resumes, read your own "maybe" bucket. If it is more than a third of the pile, the criteria are too loose or your knock-outs are missing.

Two reviewers on the same ten resumes is the fastest way to check the checklist works. Where you disagree, the disagreement is almost always a requirement that was written two ways. Fix the wording, not the people.

Where software fits

A checklist is the manual version of what screening software does. In Resume World you define the criteria once, every application is scored against the same ones, and each score points to the line in the resume behind it, so checks 5 to 8 are done for you and you spend your time on the maybes. The decision still belongs to a person. Details are on the AI resume screening software page, and the full manual process is in how to screen resumes.

A worked example

Say you are hiring a support team lead. The scorecard has five requirements: led a team of at least four, handled escalations, wrote or maintained support documentation, worked in a tool-based helpdesk, and handled a queue of real volume. The knock-outs are location and weekend availability.

A resume arrives. Check 1 to 4 pass in under half a minute. Under check 5, the candidate lists "Team Lead" at a 30-person company, with a bullet saying they "coached 5 agents and ran weekly QA reviews". That is evidence for the team requirement. Escalations show up as "owned the escalation queue for billing disputes", which counts. Documentation is missing, and nothing in the resume suggests it. The candidate worked in a helpdesk tool by name, and the volume is not stated.

Check 9 puts the scope in range. Check 10 shows two years in the current role and four before it, which needs no comment. The result is a "maybe, leaning yes", with the note: "Leads 5, owns billing escalations; no evidence of documentation or volume. Ask both on the call." That took about two minutes, and the phone screen now has two specific questions to ask. See phone screen questions for how.

When the checklist stops working

If most resumes land in "maybe", the scorecard is too loose. If almost none pass, the requirements are probably inflated, which is a job description problem you should fix before screening further. If two reviewers keep disagreeing on the same check, rewrite that line of the scorecard until a third person would read it the same way.