Column header mismatch
Generic CSVs need manual mapping.
Every ATS has its own schema. A generic CSV requires you to map columns one-by-one in the importer — fine for one role, painful at agency throughput.
AI shortlist exports
AI screening exports that land in your ATS clean.
An AI screening pass is only useful if the result lands in the tools your team already runs on. ShortlistTable ships CSV / XLSX presets shaped for Greenhouse, Ashby, Lever, Workable, Bullhorn, and JobAdder — AI verdicts and evidence columns both survive the round-trip into the importer.
6 ATS presets · Evidence columns survive · XLSX with formatting
shortlisttable.app / export
Export preset
- Greenhouse — candidate import✓
- Ashby — application import
- Lever — candidate CSV
- Workable — bulk candidates
- Hiring manager XLSX
- Generic CSV
Preview
shortlist-q2-backend.csv| Name | Kafka in prod | On-call ≥ 12mo | Review priority |
|---|---|---|---|
| Alice Chen | Yes | Yes | Call first |
| Marco Silva | Review | Yes | Review fit |
| Nina Patel | No | Review | Hold |
6
ATS-specific presets
Evidence
Survives the export
XLSX
Hiring-manager format
0
Manual column re-mapping
Why generic CSVs break
Most exports break on the other side.
A CSV that comes out of one tool and into another usually requires a manual re-mapping pass: headers don’t match, commas inside fields explode rows, evidence ends up in a “notes” field nobody reads. The recruiter spends an hour cleaning up an export that was supposed to save them time.
We solved this by writing presets for the destinations recruiters actually use. Each preset is tested against the importer of the target ATS — Greenhouse, Ashby, Lever, Workable, Bullhorn, JobAdder — so the file lands cleanly without the manual cleanup pass.
Quoting / escaping
Resume sentences contain commas. Generic CSVs explode.
Evidence columns contain sentence-length text. Without proper quoting and escaping, those cells break the row layout and the importer rejects the file.
Evidence buried in notes
If evidence isn’t a column, it’s gone.
Generic exports often pack evidence into a single notes field. The hiring manager opens the CSV, sees the verdicts, and never reads the evidence.
Export presets
Six destinations, one clean export.
01 · Feature
ATS-shaped CSV presets
Headers, field formats, and required columns matched to Greenhouse, Ashby, Lever, Workable, Bullhorn, and JobAdder importers.
GreenhouseAshbyLeverWorkableBullhornJobAdder
02 · Feature
Evidence columns preserved
Every screening column has a paired evidence column. Citations, source pages, and recruiter overrides all survive the export.
Kafka in prod (yes/no)
Kafka in prod — evidence
Kafka in prod — source
03 · Feature
Hiring-manager XLSX
When the destination is a hiring manager (not an ATS), we ship an XLSX preset with colour-coded verdicts and conditional formatting so the sheet reads at a glance.
Call first · 12 candidatesReview fit · 8Hold · 47
04 · Feature
Per-row export selection
Export the shortlist only, all reviewed candidates, or everything — including the hold queue. Filtered by any column.
Shortlist onlyAll reviewedIncluding hold
05 · Feature
Editable column mapping
If your ATS isn’t one of the presets, edit the column header mapping once and save it as a custom preset for your workspace.
Pick base preset→Edit headers→Save preset
06 · Feature
Quoted and escaped
Sentence-length evidence with commas, quotes, and newlines — properly escaped per RFC 4180 so the importer accepts the file.
Sample cell“Owned primary on-call for the payments event bus across 14 services.”
How it compares
ATS exports vs the alternatives.
| Property | Generic CSV tools | Manual XLSX | ATS-to-ATS export | ShortlistTable |
|---|---|---|---|---|
| ATS-specific presets | ✕Generic only | ✕Manual | –Limited destinations | ✓6 ATS presets |
| Evidence as columns | –Notes field | –Manual | ✕Usually dropped | ✓Paired evidence columns |
| Proper CSV quoting | –Sometimes | –Manual | –Varies | ✓RFC 4180 |
| XLSX with formatting | ✕CSV only | ✓Manual | ✕Rare | ✓Colour-coded preset |
| Per-row filtering on export | ✕All or nothing | ✓Manual | –Limited | ✓Any column |
✓ Supported– Partial / manual✕ Not supported
FAQ
Common questions on exports.
Will it import into my ATS without manual mapping?+
If you’re on Greenhouse, Ashby, Lever, Workable, Bullhorn, or JobAdder — yes, the presets are matched to their importers. For other systems you can edit the column header mapping once and save it as a custom preset for your workspace.
What happens to the evidence columns in a CSV?+
Every screening column gets a paired evidence column. The importer on the other side either picks it up (if the schema has a matching field) or stores it on the candidate as a note. Either way, it’s not silently dropped.
Does the XLSX preset have conditional formatting?+
Yes — verdict cells are colour-coded green / amber / red, the review-priority column has bold formatting, and headers are styled. Opens cleanly in Excel, Numbers, and Google Sheets.
Can I export only the shortlisted candidates?+
Yes. You can export any subset of the table — filtered by priority, by a specific column verdict, or by manual selection. The default preset exports the “call first” bucket only.
What about non-Latin characters and accented names?+
Exports are UTF-8 encoded with a BOM for Excel compatibility. Names, evidence, and notes preserve the original character set.
Can I push directly to my ATS instead of CSV?+
Native push to Greenhouse and Ashby is on the roadmap. Today, the CSV preset is the path. Most agency users prefer this anyway — they keep a copy of the shortlist for their own records.
Land in any ATS
Stop hand-mapping CSV exports.
Build a shortlist, pick your ATS, hit export. Try free on 25 resumes — no credit card.