Most onboarding ends when the paperwork does. The new hire has a laptop, an email address and a seat. From week 2 they are treated as a normal employee who happens to know nothing yet.
That gap is where early attrition comes from. Someone who leaves inside 3 months usually decided in week 3.
What is the first 90 days actually for?
One measurable thing. Getting a new hire to the point where they produce work at the standard the role needs, without supervision on routine tasks. Everything else serves that.
Write down what that looks like before they join. For a payroll executive it might be closing a full cycle with one review pass. For a BD role it might be running discovery calls alone. If you cannot state it, you cannot tell whether onboarding worked or whether you simply stopped noticing.
Where does the statutory clock start?
On the joining date, not at confirmation. The Employees State Insurance Corporation says "ESIC provides reasonable Medical Care for self and family from day one of entering into insurable employment."
That matters for onboarding design. PF at 12% with a 15,000 wage ceiling, ESI at 3.25% employer and 0.75% employee up to 21,000, and the 1948 and 1952 Acts behind them all attach immediately. A probation period is your arrangement. It does not delay any of this. Details sit with the Employees Provident Fund Organisation.
What should the ramp look like?
| By day | The hire should | Manager checks |
|---|---|---|
| 30 | Run routine tasks with review, know who owns what | Is anything still blocked on access or information |
| 60 | Own a defined slice end to end | Is the work at standard, where is the gap |
| 90 | Work unsupervised on the routine, escalate the rest correctly | Confirm against the standard written before joining |
Put the dates in the calendar on the joining date. A checkpoint that relies on the manager remembering will slip, and the one that slips is always day 30, which is the one that still has time to fix something.
Why make day 30 about obstacles, not performance?
Because at 30 days a hire cannot be fairly judged on output. They can tell you exactly what is in the way, and they will, if the conversation is about removing obstacles rather than rating them.
Three questions get most of it. What has taken longer than it should. What did you expect to find that is missing. What has nobody explained yet. Those answers are also the best audit of your onboarding you will get, because the person noticing the gaps is the only one seeing them fresh.
In what order should real work arrive?
Sick leave is live from the start as well. ESIC says "ESIC provides 70% of average daily wages in cash during medical leave, upto 91 days in two consecutive benefit periods." A hire who falls ill in month 1 is covered, provided the enrolment was filed. Two failure modes, equally common. Weeks of reading documentation, which teaches nothing and signals there was no plan. Or a critical deliverable in week 1, which produces a visible failure the hire then carries.
What works: a small real task in week 1, a recurring routine task by week 2, ownership of something with a deadline by the end of month 1. Each step should be finishable.
Which number tells you it worked?
The share of hires who leave within 90 days, read per manager and per role. A company-level figure hides the problem. A per-manager figure usually finds it in one or two teams, and the cause is almost always the same: no ramp plan, so the hire spent 6 weeks guessing.
For the national backdrop, the Ministry of Statistics and Programme Implementation says "Worker Population Ratio (WPR) in usual status (ps+ss) for persons of age 15 years and above was 58.2% during July 2023 to June 2024." Most of the people you hire are leaving another job to join you, which raises the cost of a bad first 90 days. Pair it with time to the day-90 standard for the people who stay. Where that drifts longer, onboarding is decaying even though nobody has resigned yet.
Most onboarding metrics measure activity instead. Forms completed, briefs delivered, checklists ticked. None of them tell you whether it worked. Wider workforce context is published by the Ministry of Statistics and Programme Implementation, whose 2024 release covers the wider workforce picture.
How do you keep the programme current?
The day-30 answers and the exit reasons from early leavers are the only real inputs. Collect them in one place and revise the checklist quarterly.
Onboarding is not a document to finalise. It is a process that decays as teams, tools and roles change, and the only thing keeping it current is somebody reading what the last 10 joiners said.
Where should the record live?
A 90-day programme needs joining data, asset assignment, policy sign-offs and checkpoint dates against one employee record. In a folder and 3 spreadsheets, the day-60 checkpoint quietly stops happening.
247HRM carries the employee record from the candidate stage in applicant tracking through leave and payroll with no re-entry, so the onboarding trail is a by-product of running the process.
For what has to be ready before day one, see the day-one onboarding checklist.