ATS·Recruiting
ATS with Recruiting at the center.
Requisition to offer — accepted offers create the employee in HR.
The operating challenge
Hiring stalls when recruiting lives in a silo — offers don’t create employees, and HR re-enters the same people data.
Capabilities
What ATS contributes to the suite.
Jobs & pipeline
Requisitions, applications, and stage moves from persisted recruiting records.
Interviews & offers
Operational queues with immutable accepted-offer rules under hire lineage.
Candidate Match
Advisory scores inside the workflow — human review stays accountable.
Hire continuity
Accepted offers create the employee in HR — status-only HIRED is blocked.
Shared audit
Recruiting activity remains visible to Admin and HR with the same identity model.
Suite chrome
Same platform shell as HR, CRM, and Admin — switch modules without leaving the OS.
In the workflow
Operational surface — not a demo island.
Connected platform
One Consult America operating system.
Modules share chrome, identity, and continuous business data. Integration is lineage — not duplicated master records.
People continuum
An accepted offer creates the employee — no re-entry, no status-only hire.
Governance continuum
One control plane for the suite — not a separate admin product.
Outcomes
What changes when ATS is part of the suite.
- Recruiting and HR share one people continuum.
- No duplicate candidate → employee master data.
- Operators switch to HR or Admin without a product hop.