Skip to content
ONE3.ai

How it works · Flow F5

One employee record from requisition to exit

Requisition, job description, applications, interviews, offer, onboarding, payroll, reviews and exit run on one People record. AI assists; humans make every hiring decision.

What the Hire to retire flow does

Hire to Retire runs on one Employee record. A person who is hired, paid, rostered, reviewed and trained is the same record in every People module.

A requisition is raised and its budget approved. An agent drafts the job description with a DEI language check. The job publishes to the careers site and job boards. Applications are parsed and given a matching score with an explanation — and a human shortlists. Screening, interview scheduling and scorecards follow. The offer letter is drafted, approved and e-signed. Background verification runs through a licensed provider. On joining, the employee record is created, IT access and assets are provisioned, and payroll is set up. A learning path and a buddy follow.

Each month attendance and leave feed a payroll run that needs R4 approval, then statutory filings. Goals, reviews and skills inform promotions and succession. At exit: clearance, full-and-final settlement, access revocation and knowledge handover.

Hiring decisions stay with humans. AI never auto-rejects candidates, and matching scores are explainable and bias-audited. People (HR) is planned for W3 (Year 2); it is outside the Year-1 boundary.

Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.

Hire to retire, step by step

Thirteen steps. HR roles are advisory: AI recommends, people decide.

  1. 1

    1. Requisition and budget approval

    **People (HR) · Recruit.** A hiring manager raises a requisition. Budget is approved per DoA.

  2. 2

    2. JD drafted with a DEI language check

    **JD agent (HR & Talent, advisory).** Drafts the job description and flags exclusionary language. A human edits and approves.

  3. 3

    3. Publish

    **People (HR) · Recruit · integrations.** The job publishes to the careers site and job boards.

  4. 4

    4. Parse and match with explanation

    **Recruit · screening assistant.** Resumes are parsed. Each match score shows why. Scores are bias-audited. AI never auto-rejects.

  5. 5

    5. Screening and human shortlist

    **Human gate.** Questionnaires or async interviews run, then a human shortlists.

  6. 6

    6. Interview scheduling and scorecards

    **Interview scheduling agent · Office · Calendar.** Interviews are booked and structured scorecards collected.

  7. 7

    7. Offer letter, approval and e-sign

    **Office · Docs and Sign.** The offer is drafted, approved by the right person and e-signed. The hire/no-hire decision is human.

  8. 8

    8. Pre-boarding and verification

    **People (HR) · licensed BGV provider.** Documents are collected and verified through a licensed provider (verify).

  9. 9

    9. Employee created, access and payroll set up

    **People (HR) · Core HR · IT & Security · Finance.** Action `hrm.employee.create` triggers IT access, assets and payroll setup.

  10. 10

    10. Onboarding learning path

    **People (HR) · Learning.** A learning path and a buddy are assigned.

  11. 11

    11. Attendance, payroll (R4) and filings

    **People (HR) · Attendance & Leave · Payroll.** The monthly payroll run needs R4 human approval, then statutory filings.

  12. 12

    12. Goals, reviews and succession

    **People (HR) · Performance.** Goals, reviews and skills inform promotions and succession. AI is advisory.

  13. 13

    13. Exit

    **People (HR) · IT & Security.** Clearance, full-and-final settlement, access revocation and knowledge handover.

Advisory only

AI never auto-rejects candidates. Matching scores are explainable and bias-audited before release and periodically. Hiring, firing, promotion and pay decisions are made by people. Some jurisdictions regulate automated hiring tools — verify with counsel per market.

Guardrails and KPIs

ItemDetail
GuardrailsNo auto-reject; explainable, bias-audited matching; humans make hire/no-hire decisions
Human gatesBudget approval; shortlist; offer approval; payroll run (R4)
KPIsTime-to-hire, cost-per-hire, offer acceptance, 90-day attrition, payroll accuracy (target 100%), statutory filing on-time %

Questions about this flow

Does the AI decide who gets hired?

No. AI drafts, parses, explains and schedules. People shortlist and make every hire or no-hire decision.

How is bias handled?

Screening and matching assistants are audited for disparate impact before release and periodically. Results are visible to tenant admins.

Can payroll run automatically?

No. The payroll run is an R4 Action and always needs human approval with a second factor.

Is this in Year 1?

No. People (HR) is planned for W3, starting in Year 2. Domain experts for payroll are hired before the suite is built.

Are statutory filings handled?

The plan covers Indian statutory items such as PF, ESI and PT. Each one is verified with domain experts and a chartered accountant before GA.

Tell us how you hire and pay

People (HR) is a Year-2 app. Teams who share their current process help us scope it properly.

Become a design partner