Sourcing without the bloat: a shortlist workflow that doesn't need an ATS migration
Boutique firms, staffing agencies, and small in-house teams: a four-step screening workflow that runs alongside whatever ATS (or no ATS) you already have.
You do not need an ATS migration to fix your screening workflow. Most of the bottleneck — the painful part where someone opens 80 PDFs and copies bullet points into a spreadsheet — sits between sourcing and the first screening call. You can replace that one piece without touching the rest.
The four-step lightweight workflow
- Source as you do today — LinkedIn search, referrals, agency network, inbound. Whatever produces the resume pile.
- Drop the pile into one place: a folder, an email tag, a Drive folder. No system change required.
- Run a screening pass: one pass per role, with 5–10 columns specific to that role. The output is a sheet, one row per candidate, with per-criterion evidence.
- Hand the top of the sheet to whoever does the screening call. Their ATS or CRM gets updated downstream, after the call.
Crucially: there is no migration. Your ATS still owns candidate data and stages. The new piece is just the sheet, and it lives wherever your recruiters already work — Notion, Sheets, Excel, an email.
When this beats an ATS-native screening flow
- Boutique search firms running 3–10 active roles. The ATS-native scoring is built for high-volume corporate recruiting, not for the per-role customisation a boutique firm needs.
- Staffing agencies submitting candidates to clients. The shortlist sheet is the deliverable. You are not trying to feed an internal pipeline, you are trying to send a clean candidate summary by EOD.
- Early-stage in-house teams without a real ATS yet. The shortlist sheet is your ATS until you outgrow it — usually around hire 50.
What changes once you adopt this
- Time-to-shortlist drops to hours, not days. The recruiter no longer manually re-reads every resume.
- Shortlist quality becomes auditable. Every "yes" comes with the resume sentence behind it. Disagreements happen on the evidence, not on opinions.
- Onboarding new recruiters takes less time. They inherit the screening columns, not the tribal knowledge.
Frequently asked questions
Does this work alongside Greenhouse / Ashby / Lever?
Yes. ShortlistTable produces a CSV / XLSX you can import into Greenhouse, Ashby, Lever, or simply attach to a hiring-manager email. The ATS stays the source of truth for candidate data.
What about candidate privacy / GDPR?
Treat the shortlist sheet with the same privacy posture as any other candidate document — restrict access, set a retention policy, and delete rejected candidate rows according to your jurisdiction's rules. ShortlistTable workspaces support per-workspace retention.
When should I actually migrate to a full ATS?
Usually when you are managing more than ~50 active candidates across more than ~5 roles, or when the lack of automated stage tracking starts costing you offers. Until then, the lightweight workflow is usually a better fit.
Keep reading
How to build screening columns for hard-to-fill roles
A working recruiter’s guide to writing screening criteria that distinguish real candidates from string-matchers — with concrete examples for engineering, sales, and operations roles.
Keyword matching vs semantic screening: what actually changes for recruiters
Traditional ATS parsers match exact strings. Semantic screening matches meaning — and it changes how you build your screening criteria, not just how fast you sift.
Parse a batch of resumes
Convert one resume to a row
Ready to try this on a real pile?
ShortlistTable runs source-backed screening across PDF and DOCX resumes at batch scale.
Try free on 25 resumes