HRMS · Hiring

The candidate becomes
the employee.

Postings, applications captured from a form candidates fill without an account, and an internal path for people already on the payroll. When someone is hired, the record they already have becomes the employee record rather than being typed again.

Where most ATS products stop. At the offer — leaving the employee record, the payroll setup and the statutory IDs to be re-keyed by someone else.

Openings

Postings, internal and external.

Job postingsRoles as records with their own lifecycle, rather than a document emailed around.
Internal recruitmentA path for people already employed, because an internal move should not require applying as a stranger.
Public captureApplications arrive from a form the candidate fills without creating an account or being chased for a login.
Applications

Tracked through the decision.

Applications as recordsHeld against the posting they came for, so a role’s pipeline is visible rather than living in an inbox.
Through to hiredThe stages a candidate moves through are on the record, which is what makes a hiring report possible at all.
Straight answers

What this does not do.

Kept against the code rather than a roadmap, because finding out during a demo is worse than reading it here.

No job-board syndicationPostings are not pushed out to external boards from here. If you advertise on one, you are posting there separately today.
Nearby

Related capabilities.

Employee records · Payroll · Interviews in Meetings

Hire once, not twice.

The person you hired is already a record. Payroll starts from it.