HR·Requests
HR starts where ATS finishes.
Employee records, requests, and onboarding continuity after hire.
The operating challenge
After hire, teams lose continuity when HR is a separate system — onboarding, documents, and requests start from a blank employee.
Capabilities
What HR contributes to the suite.
Requests
Service desk for employees from hire onward — the primary HR operating queue.
People records
Employee directory and 360 profile seeded by accepted ATS offers.
Onboarding continuity
Pre-hire and active employees without re-keying recruiting data.
Documents & compliance
Role-governed document workflows on the same employee identity.
Time & leave handoff
Connects to Employee self-service and Payroll on shared people data.
Suite chrome
Same shell and switcher as ATS, Employee, Payroll, and Admin.
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 HR is part of the suite.
- Hire in ATS becomes the employee record in HR.
- Requests operate on real people — not a parallel HR database.
- Employee and Payroll stay on the same continuum.