Resume Screening Automation Consistent shortlists with the reasons, without reading 400 CVs
Every application is scored against the role's written criteria with a quote as evidence — a person still makes the call.
- Installed for you · one-time$249
- Run for you$247/month
- Custom build · this process$3,500–6,000 one-time
- Starts whenATS event (application received)
Covers one ATS and up to 3,000 applications a month. Jurisdictions with specific automated-decision rules (NYC Local Law 144, EU AI Act high-risk provisions) need the custom build with the required audit and notice features. Custom builds start at $2,000 site-wide; this band is for this process and its integrations.
Resume Screening Automation is an automation Agentmelt installs in Google Sheets. The free template is a file you import yourself; the kit ($49) adds the setup guide and prompts. Installed for you costs $249 one-time and is live within two working days of access, with a recorded walkthrough and 30 days of fixes. Run for you costs $247/month, with setup and maintenance included. A custom build of this process is $3,500–6,000 one-time; custom builds start at $2,000 site-wide. No call is needed for any option. Written by Max Zeshut; last revised 2026-09-21.
Reference stack: Claude + n8n. Node names are on each step; the file is under the template.
Founder at Agentmelt
Reviews every build before it goes live; the workflow escalates to a person, never past one.
What is resume screening?
Resume screening automation applies the role’s written criteria — the same criteria, the same way — to every application, and explains each score so the recruiter can disagree: applications are parsed from the ATS, must-have and nice-to-have criteria are scored with a quote from the resume as evidence, claims worth verifying are flagged, and a ranked shortlist with the reasoning is written back to the ATS. Nobody is rejected by the workflow; the recruiter decides, and every decision carries its reason. Protected attributes are excluded from what the model sees, and a monthly audit reports pass-through rates by group.
- Two hundred applications per role and the recruiter reads the first forty.
- Screening depends on who is screening and how tired they are.
- A strong candidate with an unusual CV format was never seen.
- The hiring manager’s criteria were never written down.
- We could not show an auditor why anyone was rejected.
If two of these are yours, this is the process to look at first. Free audit — or read on.
What it looks like once it runs.
Resume screening automation applies the role's criteria — the same criteria, the same way — to every application, and explains each score so the recruiter can disagree. The workflow parses applications from the ATS, scores must-have and nice-to-have criteria with evidence quotes, flags claims to verify, and produces a ranked shortlist with the reasoning; the recruiter decides who to call.
- Continuously An application arrives. The role's must-haves and disqualifiers, written in plain language, are loaded.
- +1 min The resume is read into structured fields; each criterion is scored met / partly / not, with a quoted line as evidence.
- +2 min Gaps and claims to verify are listed for the interview; the ranked shortlist is written to the ATS as a scorecard.
- Friday Score distributions and pass-through rates are reported so the criteria stay fair.
A posting draws 300–800 applications. Recruiters skim for keywords, screening depends on who is doing it and how tired they are, strong candidates with unusual backgrounds are missed, and there is no record of why anyone was rejected.
Every application is scored against written criteria within minutes, with the evidence. The recruiter opens a ranked list with explanations, reviews the top band and a random sample of the rest, and every decision is logged with its reason. Time-to-shortlist falls from days to hours and screening is consistent across recruiters.
Trigger, then 8 steps.
All eight steps run without anyone; a person sees only what the guardrails escalate.
ATS event (application received)
Receive the application
Resume, cover letter, application answers and the job requisition id from the ATS.
Load the role criteria
Must-haves, nice-to-haves and disqualifiers for the role, written by the hiring manager in plain language and approved by HR; weights per criterion.
Parse the resume
Roles, dates, employers, skills, education, certifications and locations into structured fields, with the source text kept for quoting.
Score against criteria with evidence
Each criterion scored met / partially / not met with a quote from the application as evidence; the agent is instructed to ignore name, photo, age, gender, nationality and school prestige unless a certification is a legal requirement.
Flag verification items
Gaps, overlapping dates, claims that need checking (certifications, seniority) listed for the interview.
Build the ranked shortlist
Weighted score and band (strong / possible / unlikely); disqualifier matches are listed separately with the rule, never silently dropped.
Present to the recruiter
Scores, bands and explanations written back to the ATS as a scorecard; the recruiter reviews the strong band plus a random sample from the others and moves candidates forward.
Audit and bias monitoring
Weekly: score distributions and pass-through rates by self-reported demographic group where legally collected; anomalies flagged to HR.
No step waits for a person.
What the workflow hands to someone, by rule:
- Pass-through rates by group are monitored where lawful, and criteria that skew are reviewed.
Every application is scored against written criteria within minutes, with the evidence
Every application is scored against written criteria within minutes, with the evidence.
No decisions needed. Anything the guardrails flag is handed to a person; the rest ran alone.
Each pattern page explains it in plain words and lists every automation that uses it.
The template is built on n8n (how the n8n AI Agent node works); the same steps run on Make, Zapier or plain code. The tool is chosen to fit your accounts, you own the result, and the template comes in all three formats.
Data it touches
- ATS applications (Greenhouse, Lever, Ashby, Workable, Teamtailor)
- Role criteria sheet (hiring manager + HR)
- Company screening policy and legal constraints
Guardrails
- No candidate is rejected automatically; the workflow ranks and explains, recruiters decide.
- Protected characteristics are excluded from scoring by instruction and by stripping fields before the model sees them.
- Every score carries an evidence quote; unexplained scores are not shown.
- Pass-through rates by group are monitored where lawful, and criteria that skew are reviewed.
Consistency is the benefit; explanation is the safeguard
The value of automated screening is that criteria are applied the same way to application 1 and application 700. The risk is that a model applies criteria you did not write. Two design choices manage that: criteria are written in plain language by the hiring manager and HR, and every score comes with a quote from the application. A recruiter who sees “not met: no evidence of managing a team — resume lists individual contributor roles” can agree or overrule in seconds, and the overrule is logged.
Regulatory posture
Automated employment decision tools are regulated in several jurisdictions — bias audits and candidate notices in New York City, high-risk classification under the EU AI Act, and general anti-discrimination law everywhere. The workflow is designed as decision support: it does not reject anyone, it strips protected data before scoring, it logs every decision, and it monitors pass-through rates. Where a jurisdiction requires a formal audit or notice, that is configured in the custom build with your counsel.
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Intake, scoring pipeline, ATS write-back, monitoring |
| Claude | Parsing and evidence-based scoring |
| Greenhouse / Lever / Ashby | ATS of record |
| Google Sheets | Role criteria the hiring manager edits |
Want this running without building it?
$247/month
We set it up in your tools, run it on our servershost it on our n8n cloud (or deploy it to your own n8n, Make or Zapier), watch it, and fix it when something changes. Setup included, cancel monthly; the automation stays yours if you leave.
$3,500–6,000 one-time
Your systems, your rules, your edge cases. A one-off build delivered into your accounts to keepon Claude and n8n, delivered into your accounts to keep, with documentation and a recorded walkthrough.
Covers one ATS and up to 3,000 applications a month. Jurisdictions with specific automated-decision rules (NYC Local Law 144, EU AI Act high-risk provisions) need the custom build with the required audit and notice features.
Also sold one-time, installed in your own accounts, as part of the recruiters package — do it yourself $49 · installed for you $249 · done for you $490.
When this becomes a custom build.
The subscription covers the standard version — $247/month, setup and maintenance included. Three things move it to a custom build ($3,500–6,000 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
A jurisdiction with automated-decision rules — NYC Local Law 144, the EU AI Act — that needs audit and notice features.
More than one ATS, or above 3,000 applications a month.
Structured interviews or assessments scored alongside the resume.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Frequently asked questions.
Does it reject candidates?
No. It ranks, explains and flags. Recruiters make every decision, and the decision and reason are recorded in the ATS.
How does it avoid bias?
By stripping names, photos and demographic signals before scoring, instructing the model to score only against the written criteria with evidence, monitoring pass-through rates by group where lawful, and keeping humans in every decision. It reduces inconsistency between recruiters, which is itself a bias source.
Which ATSs are supported?
Greenhouse, Lever, Ashby, Workable, Teamtailor and SmartRecruiters via API; others via email intake of applications.
Does resume screening automation reject candidates?
No. It scores and ranks against the written criteria with evidence, flags what to verify, and presents the shortlist; the recruiter decides, including on the rejects, and the reason is recorded. Silent automated rejection is the practice regulators are writing rules about, and the workflow is built not to do it.
How does automated screening avoid bias?
By scoring only against written, job-related criteria; by excluding names, photos, ages, addresses and other protected attributes from what the model reads; by quoting the evidence for every score so a person can check it; and by reporting pass-through rates by group monthly so drift is caught. It is more auditable than a skim of forty CVs — and the audit is the control.
Which applicant tracking systems are supported?
Greenhouse, Lever, Ashby and Workable directly; others through exports. Jurisdictions with automated-decision rules — New York City’s Local Law 144, the EU AI Act — need the audit and notice features configured for them, which is a custom build on the same workflow.
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Greenhouse — Harvest API developers.greenhouse.io/harvest.html
- NYC DCWP — Automated employment decision tools (Local Law 144) www.nyc.gov/site/dca/about/automated-employment-decision-tools.page
- eCFR — 29 CFR Part 1607, Uniform Guidelines on Employee Selection Procedures www.ecfr.gov/current/title-29/subtitle-B/chapter-XIV/part-1607