ATS Segment Hubs: The Evidence Brief Before You Shortlist
The wrong ATS shortlist usually starts with the wrong question.
“Which candidate tracking system has the most features?” is not the buying question. The better question is: which tool matches the constraint you cannot avoid?
That constraint may be price, compliance, migration, hiring-manager adoption, or the simple fact that a spreadsheet has become the system of record for people data.
The segment hub map
Use these hubs before comparing vendors.
| Segment hub | Real constraint | First evidence to collect | Evidence status |
|---|---|---|---|
| Spreadsheet replacement | The team needs one pipeline owner and fewer manual handoffs. | Current columns, stages, duplicate candidate rules, resume storage location. | Local discovery required. |
| 50-500 tech team | Interview structure and hiring-manager adoption matter more than raw posting volume. | Scorecard workflow, calendar stack, HRIS integration, approval chain. | Source-needed for vendor-specific fit. |
| Workday or Taleo migration | The buyer is escaping admin burden but cannot lose history. | Export rights, attachment handling, audit trail needs, stage mapping. | Vendor-verify. |
| Compliance-sensitive buyer | Recordkeeping, consent, retention, and reporting have legal consequences. | OFCCP/GDPR requirement list reviewed by counsel. | Legal-review-needed. |
| Free or low-cost ATS | Budget is tight, but the team still needs repeatable hiring. | Plan limits, user limits, job limits, export rights, support model. | Vendor-verify. |
Pricing reality comes before feature comparison
A low advertised price can still be the wrong economic fit.
Before reading a review, mark the pricing model:
- Per recruiter seat.
- Per employee headcount.
- Per active job.
- Custom annual contract.
- Free or low-cost plan with usage limits.
Do not treat any vendor price as durable unless it is verified against the current vendor page or a current contract source. Pricing pages change, discounts vary, and implementation fees often sit outside the headline plan.
Evidence label: vendor-verify.
Compliance pages need narrower language
An ATS can provide compliance-related features. It cannot make a hiring process compliant by itself.
For OFCCP, GDPR, retention, audit trails, consent, and DPAs, the useful content is not a promise. It is a checklist of questions:
- Can the system preserve candidate records for the required period?
- Can admins export the records in a usable format?
- Are candidate consent and deletion workflows configurable?
- Are action logs tied to named users rather than shared accounts?
- Is a DPA available, and who must approve it?
Evidence label: legal-review-needed.
Migration evidence beats migration optimism
Migration pages should not say a move is easy unless the proof is local.
The practical migration brief needs five fields:
- Source system: Workday, Taleo, Greenhouse, Lever, Ashby, or spreadsheet.
- Data shape: candidates, attachments, scorecards, notes, stage history, consent records.
- Destination requirement: what must survive the move.
- Cutover risk: what breaks if the team switches mid-hiring cycle.
- Verification task: the vendor export/import question to ask before signing.
If any of those fields are unknown, label the claim source-needed.
Decision rule
Start with the segment hub when the buyer is still defining the problem.
Move to vendor reviews only after the constraint is clear.
Choose for the constraint, not the feature list.