- Industry
- IT Company
- Department
- HR
- Team
- People Operations
- Kind
- Assistant
- Approver
- Head of People
- Code
- HRS-09
It turns each signed offer into a new-hire plan: right-to-work and the background checks the company and its clients require, NDA, IP assignment and security policy acknowledgements, laptop and least-privilege access requests, security training before any client system access, a buddy and first-week tasks. For hires going straight onto a client project it lines up the client's own induction and access process.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the HR and resourcing system: the offer, role profile, country checks and the client engagement's requirements..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of People with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it raises the equipment and access requests and tracks the onboarding tasks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The onboarding checklist: pre-employment checks by country, client background-check requirements by engagement, contract and IP assignment documents, access provisioning by role and the first-week plan.
Reads from
the HR and resourcing system: the offer, role profile, country checks and the client engagement's requirements.
Acts in
the ticketing and service management system: it raises the equipment and access requests and tracks the onboarding tasks.
Hands back
An object with employee_id, checks (a list with check, status and due), documents (a list with document and status), access_requests (a list with system and level), first_week (a list of tasks), buddy and blockers.
Asks a person when
Access beyond the role profile is requested, a client check is outstanding at start, or a contractor needs privileged access.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Start the plan (days before start) | 15 | Checks and equipment begin this early. |
| Right-to-work check before start | On | When on, no one starts without it. |
| Client access only after security training | On | When on, no client system access is requested before security and data-protection training is done. |
| Access beyond the role | needs the approver | What happens to access requests beyond the role profile. |
| First check-in (days) | 30 | The manager checks in at this point. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Begin checks and equipment 15 days before start.
- When on is true, no one starts without a right-to-work check, and no one joins a client project before the client's required checks clear.
- Every hire signs the NDA, IP assignment and acceptable use policy before access.
- Request access by role profile only; access beyond it needs the approver.
- When on is true, request client system access only after security training is complete.
- Contractors follow the contractor checklist and never get employee benefits or payroll set-up.
See the Employee Onboarding Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.