Employee Onboarding Process: A 90-Day Checklist

Employee Onboarding Process: A 90-Day Checklist

Most Indian SMBs treat the employee onboarding process as a paperwork event. Someone from HR meets the new hire at 10 am, hands over a form set, collects photocopies of ID documents, shows them a desk, and disappears. By 4 pm the new joiner has signed everything, met nobody who matters, and has no idea what they are supposed to deliver in the next three months.

That is not onboarding. That is joining formalities.

A real employee onboarding process is a designed program that starts the moment a candidate accepts the offer and runs through to the end of the first 90 days. It has phases, owners, deadlines, and measurable outcomes. Done well, it cuts early attrition, shortens time-to-productivity by weeks, and reduces the quiet tax that every founder pays when a new hire spends their first month asking basic questions in a WhatsApp group.

This guide gives you the full structure: the four phases, a complete onboarding checklist you can copy, a 30-60-90 framework, a RACI table, metrics with formulas, and the specific failure modes that show up in fast-growing Indian companies with 20 to 500 people. It is written for HR managers, founders, and people ops teams who need something they can implement next Monday, not a theory paper.

Why the Employee Onboarding Process Deserves Real Investment

Ask any founder what their most expensive recruitment problem is and they will usually say hiring itself — job boards, consultant fees, interview time. But the more expensive problem is the hire who joins and leaves within 90 days, or the hire who stays but takes six months to do what they should have done in two.

Both problems trace back to onboarding.

Early attrition is mostly an onboarding failure

When someone quits in the first three months, the reason is rarely "the work was too hard." The reasons that actually come up in exit conversations are:

• The role was different from what was described. Nobody reset expectations after joining, so the gap between the interview pitch and the daily reality went unmanaged.
• No clarity on what success looks like. The new hire never got written goals, so they never knew whether they were doing well.
• No manager attention. The hiring manager was travelling, in a release crunch, or simply assumed the person would "figure it out."
• Social isolation. Especially in hybrid and remote setups, a new joiner who does not form three or four working relationships in the first month tends to disengage.
• A better counter-offer landed during notice period. This one is a pre-boarding failure, not a post-joining one.

Every single item on that list is preventable with process. None of them require budget. They require someone to own the sequence and a system that reminds people to do their part.

Time-to-productivity is a real cost line

Think about what a new hire costs you before they contribute. Salary from day one. The hiring manager's time. The time of every colleague who answers their questions. Tools and licences. If a mid-level hire on ₹12 lakh a year takes 100 days to reach full productivity instead of 60, that gap is roughly 40 days of paid salary plus the drag on everyone around them — and it repeats for every hire you make.

Structured onboarding compresses that ramp. Not because the person learns faster, but because they stop wasting time on avoidable friction: waiting for laptop approval, not knowing who owns a process, discovering on day 20 that there is a documented playbook nobody told them about.

Onboarding is where your employer brand is actually decided

Candidates form an opinion of your company in the first two weeks and then defend that opinion for years. A new hire who had a smooth, warm, organised first fortnight will refer friends. One who spent day one waiting for a laptop and day five chasing HR for their email ID will tell that story at every future interview. In a market where good referrals are the cheapest hiring channel available to an SMB, this matters more than any careers page.

The Four Phases of the Employee Onboarding Process

Break the program into four phases. Each has a distinct goal, a distinct owner, and a distinct definition of done.

The single biggest mistake is collapsing all four into one. Companies that "do onboarding" usually mean day one only. The phases that move the needle most on retention are pre-boarding and days 31-90 — precisely the two that get skipped.

Phase 1: Pre-boarding (Offer Acceptance to Day 0)

Pre-boarding is the stretch between offer acceptance and the joining date. In India this is typically 30 to 90 days because of notice periods, and it is the riskiest window in the whole employee onboarding process. This is when candidates get counter-offered, get a second offer, or simply go cold because nobody from your side spoke to them for six weeks.

The no-show problem

Offer-drop rates in Indian hiring are high enough that most SMBs plan for it informally — hiring managers keep a backup candidate warm. That is a workaround, not a fix. The fix is deliberate engagement during notice period.

A practical offer-to-joining engagement cadence:

1. Within 24 hours of acceptance — send a warm welcome email from the hiring manager (not HR). Two paragraphs. What you are excited about, what the first project will likely be, and a note that HR will be in touch with joining steps.
2. Week 1 — HR sends the digital onboarding link: document upload, personal details form, bank details, statutory declarations. Give a clear deadline and explain why each item is needed.
3. Every 2 weeks — a short, low-pressure touchpoint. A company update, a product launch note, a photo from an offsite, an article the team wrote. Nothing that demands a reply.
4. T-minus 3 weeks — confirm the joining date in writing. This is when counter-offers usually land, so an explicit reconfirmation surfaces wobbles early.
5. T-minus 1 week — send the day-one logistics email: reporting time, address with a map link, whom to ask for at reception, dress code, what to carry, and the first-day agenda. For remote joiners, send the courier tracking number for the laptop.
6. T-minus 2 days — the hiring manager sends a short message: "Looking forward to Monday. Here's what your first week looks like."
7. T-minus 1 day — an internal announcement to the team: who is joining, into what role, reporting to whom, and who the buddy is.

None of this takes more than a few minutes per touchpoint. Together they materially reduce no-shows, because the candidate has an emotional relationship with your company before day one rather than just a PDF offer letter.

Document and data collection: the pre-boarding checklist

Collect documents digitally before day one, not on day one. Nothing kills first-day energy faster than 90 minutes of form filling. Keep your list defensible and job-relevant, and collect only what you actually need.

Identity and personal details

• Government photo identity proof
• Permanent Account Number (PAN) details for tax deduction
• Aadhaar or equivalent identity number, where your policy requires it
• Current and permanent address with proof
• Date of birth proof
• Passport-size photograph
• Personal email and mobile number
• Emergency contact name, relationship, and number
• Blood group (useful for on-site emergencies)

Employment and education

• Education certificates and mark sheets for the highest relevant qualification
• Previous employer relieving letter and experience letter
• Last three months' salary slips or salary certificate, if your policy requires it
• Prior employer income details for the current financial year, so that tax deduction at source is computed correctly across the full year rather than restarting from zero
• Professional certifications relevant to the role

Banking and payroll

• Bank account number, account holder name, and IFSC
• Cancelled cheque or bank statement header for account verification
• Salary structure acknowledgement and any flexible benefit plan choices
• Tax regime election for the financial year

Statutory and social security

• Provident fund Universal Account Number (UAN) if previously allotted, plus previous member ID details
• PF nomination details, including nominee name, relationship, share, and address
• Gratuity nomination details
• Employee State Insurance details and dependent particulars where applicable
• Declarations relating to prior PF membership and pension scheme history

Statutory requirements change from time to time and vary by state, establishment type, headcount, and employee wage level. Treat the list above as a working template and verify the current rules and applicable thresholds with your payroll advisor or compliance consultant before finalising your own form set.

Policy acknowledgements and agreements

• Appointment letter acceptance
• Code of conduct acknowledgement
• Confidentiality and intellectual property agreement
• Prevention of sexual harassment (POSH) policy acknowledgement
• Information security and acceptable use policy acknowledgement
• Data privacy notice acknowledgement, covering what employee data you collect and why
• Conflict of interest declaration
• Asset issuance acknowledgement

IT, asset, and access provisioning

Provisioning has a lead time that HR consistently underestimates. Laptop procurement, licence purchase, security approvals, and courier delivery to a tier-2 city can each take a week. Work backwards from the joining date.

T-minus 10 days:

• Raise the asset request: laptop, charger, bag, mouse, headset, and any role-specific hardware such as a test device or a field phone
• Confirm asset availability or trigger procurement
• Create the employee record in the HRMS with a unique employee ID

T-minus 5 days:

• Create the corporate email account and add to relevant groups and distribution lists
• Provision access to core systems: chat, project management, document storage, code repository, CRM, design tools, whatever your stack is
• Set up single sign-on and enforce multi-factor authentication
• Assign licences and confirm they are paid for, not on a trial that expires mid-month
• Prepare the access matrix by role so that provisioning is a template, not a debate

T-minus 2 days:

• Image and test the laptop; install the standard software set and endpoint security
• Ship or hand over the device with an asset acknowledgement form
• Add the employee to payroll with correct grade, cost centre, location, and salary structure
• Add to attendance and leave systems with the correct shift, week-off pattern, and leave balances
• Book the desk, access card, or building pass
• Add to relevant recurring meetings and calendar invites

A rule worth adopting: no joining date is confirmed until IT confirms the asset and access plan. If the laptop cannot be there on day one, either move the joining date or have an explicit plan B — a loaner machine, or a first day that is deliberately paperwork and people rather than systems.

Everything else HR should finish before day 0

• Assign a buddy and brief them on their role
• Share the 30-60-90 draft with the hiring manager for review
• Block the day-one and first-week calendar invites
• Prepare the welcome kit: notebook, pen, T-shirt or mug, a handwritten note if you can manage it
• Prepare the desk with name card and a printed first-week agenda
• Set up the seating so the new hire is not alone in a corner
• Prepare the internal announcement with a short, human bio the person has approved
• Confirm whether the joiner needs any accommodation — accessibility, dietary, prayer space, medical

Phase 2: Day One

Day one has one job: make the person feel that they were expected and that joining you was the right decision. Everything else is secondary.

The failure mode is obvious once you name it. A new hire arrives, the manager is in a meeting, HR is handling three joiners at once, the laptop is "coming by evening," and the person sits for two hours scrolling on their phone. That memory sticks.

A day-one agenda that works

Adapt the timings to your reality, but keep the shape: people first, systems second, work third. And keep at least one unstructured slot — a wall-to-wall day one is exhausting for someone who is already nervous.

The five things that must be true by end of day one

1. The new hire has working credentials to at least email and chat.
2. They have met their manager one-on-one for at least 30 minutes.
3. They know the name and number of their buddy and their HR contact.
4. They have been introduced to the team, by name, either in person or over a call.
5. They know what they are expected to do tomorrow morning.

If any of these is missing, day one did not succeed regardless of how many forms got signed.

Things to deliberately not do on day one

• Do not schedule four hours of compliance video training. Spread it across the first two weeks.
• Do not put the person into a client call as a silent observer with no context.
• Do not give them a laptop with no admin rights and no way to install anything.
• Do not ask them to "read the wiki" for six hours. Curate a short, ordered reading list instead.
• Do not have the manager on leave. If the manager cannot be there, move the joining date.

Phase 3: The First 30 Days

The first month converts a new joiner from a guest into a contributor. Three things run in parallel: induction and compliance, systems and process fluency, and relationship building. On top of these sits one deliverable — a small, real, shippable first win.

Induction and compliance training

Structure induction as a series of short sessions rather than one marathon. A workable spread across weeks one and two:

• Company and strategy — what we sell, to whom, our market position, our goals for the year
• Product or service deep dive — a working demo, the customer problem, the competitive context
• Function walkthroughs — 30 minutes each with sales, marketing, product, engineering, operations, finance, and HR, so the new hire understands who does what
• Customer exposure — listen to a support call, read five support tickets, sit in on one customer conversation
• POSH awareness — what constitutes harassment, how the internal committee works, how to raise a complaint, and confirmation that the process is confidential and non-retaliatory. Make this a live session, not a checkbox video. Keep an attendance record.
• Information security and data privacy — password hygiene, phishing recognition, device security, handling of customer and employee personal data, what may and may not be shared externally, and what to do if a device is lost
• Health and safety — evacuation routes, first aid, emergency contacts, and for field or plant roles, the full safety protocol with any required certification
• Anti-bribery, conflict of interest, and code of conduct — with concrete examples relevant to your business, not generic slides

Record who completed what and when. Compliance training attendance is one of the few onboarding records you may genuinely need to produce later.

The buddy program

A buddy is not a mentor and not a manager. A buddy is a peer who answers the questions the new hire is embarrassed to ask their boss: Is it okay to log off at 6? Does anyone actually read these status updates? Who really approves budgets? Where is the good coffee?

How to run a buddy program that does not fizzle:

• Pick someone in the same function or an adjacent one, 6 to 24 months into the company — long enough to know how things work, recent enough to remember what confused them.
• Never assign the buddy role to someone who is already overloaded or in a delivery crunch.
• Give the buddy a written charter: greet on day one, lunch in week one, a 20-minute check-in each week for four weeks, and be reachable on chat.
• Give the buddy time. Say explicitly that two hours a week for a month is expected and accounted for.
• Recognise buddies. A mention in the monthly all-hands or a small voucher costs almost nothing and keeps the program alive.
• Ask the new hire in the week-4 check-in whether the buddy relationship worked. If a buddy is consistently absent, quietly rotate them out.

Manager responsibilities in the first 30 days

The hiring manager is the single largest variable in whether onboarding works. Make their responsibilities explicit and time-bound:

• Week 1: Daily 15-minute check-in. Share the 30-60-90 plan in writing. Introduce the new hire to the five people they will work with most, personally — not over email.
• Week 2: Hand over the first real task. Small, low-risk, finishable within a week, and genuinely useful. Shadowing only goes so far; people learn by doing.
• Week 3: First feedback conversation. Two things going well, one thing to adjust. Ask what is unclear.
• Week 4: 30-day review against the plan. Reset priorities for days 31-60. Ask directly: "Is this job what you expected? What surprised you?"

Managers will tell you they do not have time for this. The counter is simple: this is roughly four hours spread over four weeks, against the alternative of a rehire costing weeks of recruitment and months of lost output.

First-30-days outcomes

By day 30 the new hire should be able to:

• Explain what the company does and who the customers are, in their own words
• Navigate the core tools without help
• Name the ten people they work with most and what each of them owns
• Complete all mandatory compliance training
• Deliver one small piece of real work end to end
• Articulate their own goals for days 31-90

Phase 4: Days 31 to 90

This is the phase most companies drop entirely, and it is the phase where retention is actually decided. By day 31 the novelty has worn off, the welcome messages have stopped, and the new hire is now judging whether this was a good move based on the work itself.

What changes after day 30

The mode shifts from learning to delivering. The manager moves from daily contact to weekly structured 1:1s. The buddy relationship becomes informal. The new hire starts owning outcomes rather than tasks.

Days 31-60: independent delivery with a safety net

• Assign a piece of work with a real deadline and a real stakeholder
• Move from "here is how to do it" to "here is the outcome, tell me your plan"
• Have the new hire present something to a wider group — a demo, a findings summary, a process proposal. This builds visibility, which builds belonging.
• Broaden the network: two cross-functional coffee chats, either in person or on video
• Mid-point feedback at day 45, written and specific
• Check pay, benefits, and reimbursement have all worked correctly. A payroll error in month two undoes a lot of goodwill.

Days 61-90: full ownership and forward planning

• The new hire owns their area with normal supervision, not special supervision
• They contribute in team planning and raise their own ideas
• They can onboard the next person into at least one process — the clearest test of whether learning actually landed
• Day 90 review: performance against the plan, strengths, development areas, goals for the next quarter
• Confirmation decision, where applicable, handled through your standard probation policy. Whatever that policy says, the decision should never be a surprise — if someone is not tracking well at day 90, they should have heard it clearly at day 30 and day 60.

A note on speaking honestly

Managers frequently avoid hard feedback during the first 90 days because they do not want to demoralise a new person. This backfires. A new hire who gets vague positive noises for three months and then a difficult confirmation conversation feels ambushed, and rightly so. Early, specific, kind feedback is the single most respectful thing you can give a new joiner.

The Complete Employee Onboarding Checklist

Here is the full onboarding checklist in one table. Copy it, delete what does not apply to you, and add your own items. The value is in having named owners and deadlines — a checklist with no owner column is a wish list.

Fifty-nine items looks like a lot. In practice, in a decent HRMS, roughly forty of them are automated triggers and the rest are calendar events. The list is long because onboarding genuinely has many moving parts — the point of writing it down is that nothing depends on somebody remembering.

The 30-60-90 Plan: Turning Onboarding into Performance

A 30-60-90 plan is the bridge between onboarding and performance management. Without it, the new hire's first quarter is a series of ad-hoc tasks with no narrative. With it, both sides know what "on track" means.

Write it before day one. Share it in week one. Review it at each milestone.

A worked example: an inside sales executive

• Day 30: Knows the product and pricing well enough to run a discovery call. Has shadowed 15 calls, run 5 with the manager listening. CRM hygiene at 100 percent. Understands the ICP and disqualification criteria.
• Day 60: Running discovery calls solo. Owns a defined lead segment. Hitting 60 percent of the ramped activity target. Has closed or meaningfully advanced at least one opportunity.
• Day 90: At 90 percent of a full quota-carrying rep's activity target. Managing their own pipeline reviews. Has contributed at least one improvement to the call script or objection-handling document.

A worked example: a backend engineer

• Day 30: Local environment running. Shipped 3 to 5 small changes to production. Understands the service map, deployment pipeline, and on-call structure. Has reviewed others' pull requests.
• Day 60: Owns a feature end to end from spec to release. Participates in design discussions. Has done a supervised on-call shadow shift.
• Day 90: On the on-call rotation. Leads a small technical initiative. Has written or improved one piece of internal documentation.

Notice that both plans are specific and observable. "Get familiar with the codebase" is not a goal. "Ship 3 to 5 changes to production" is.

Who Does What: An Onboarding RACI

Onboarding fails at handoffs. HR assumes IT is provisioning; IT is waiting for a ticket; the manager assumes HR has shared the plan. A RACI table kills that ambiguity. R is responsible (does the work), A is accountable (owns the outcome), C is consulted, I is informed.

Print it. Put it in your onboarding folder. When something is missed, this table tells you exactly who to talk to — and, more usefully, prevents the miss in the first place.

Remote and Hybrid Onboarding

Remote onboarding is not on-site onboarding over video. The things that happen incidentally in an office — overhearing a conversation, catching someone at the coffee machine, seeing that everyone leaves at 7 — do not happen remotely. You have to manufacture them.

What changes for remote hires

• Logistics move earlier. The laptop must ship at least five working days before joining, with tracking shared. Build in buffer for tier-2 and tier-3 delivery.
• Documentation must be genuinely digital. No "courier the signed forms." Digital forms, digital signatures, digital storage.
• Day one is shorter and more social. Video fatigue is real. Cap synchronous sessions at four hours and break them up.
• Introductions must be scheduled. Book fifteen-minute 1:1 video calls with eight to ten colleagues across the first two weeks. Left to chance, they will not happen.
• Over-communicate norms. Working hours, response time expectations, when it is fine to be offline, camera-on conventions, which channel is for what. Remote new hires spend enormous energy guessing at norms.
• The buddy matters more. In an office, a new hire has ten people they can turn to. Remotely, they have whoever answers on chat. Make the buddy explicitly available.
• Create low-stakes social contact. A fifteen-minute virtual coffee, a team channel for non-work chatter, a monthly online game. It feels forced at first; it works anyway.
• Watch for silence. If a remote new hire has not posted in any channel for three days, that is a signal, not an efficiency.

Hybrid specifics

For hybrid teams, coordinate the first two weeks so the new hire's office days overlap with their manager's and their buddy's. Nothing is worse than commuting in to sit alone. Fix the overlap explicitly in the calendar before joining.

Onboarding Blue-Collar, Field, and Frontline Staff

Most onboarding advice is written for desk workers. For manufacturing, retail, logistics, field sales, security, facilities, and delivery roles, the employee onboarding process needs a different shape.

What is different:

• Volume and speed. You may onboard 30 people at a branch opening or a seasonal peak. The process must be batch-friendly.
• Documentation gaps are common. Missing bank accounts, no prior UAN, name mismatches across ID documents, no email address. Build assisted document collection into the process — a data-entry desk with a scanner and a person to help — rather than assuming self-service.
• Mobile-first, low-bandwidth. Onboarding must work on an entry-level Android phone over a patchy connection, and increasingly through a WhatsApp-style flow rather than an app that must be downloaded.
• Language. Deliver induction and safety content in the local language. Translated slides are not enough; the trainer must be able to answer questions in that language.
• Safety and compliance dominate. For plant, warehouse, and field roles, the safety induction is the single most important onboarding element, with demonstrated competence and a record of it, not just attendance.
• Attendance and shift setup matters immediately. Biometric or geo-tagged attendance enrolment, shift and roster assignment, and overtime rules should be configured on day one because pay accuracy depends on them from the first shift.
• Uniform, PPE, and tools. Sizes, issue records, and replacement policy.
• Supervisor is the whole experience. There is no buddy program in most frontline settings; the shift supervisor is HR, manager, and mentor. Train supervisors on the first-week routine, because they are the retention lever.
• The first pay cycle is the retention test. Frontline attrition spikes when the first salary is wrong or late. Get the payroll master data right before the first shift.

A practical adaptation: compress the framework to a 7-day, 30-day, 60-day rhythm rather than 30-60-90, since frontline roles typically reach full productivity faster and attrition risk is concentrated in the first two weeks.

Measuring the Employee Onboarding Process

If you cannot measure onboarding, you cannot improve it and you certainly cannot defend investing in it. Five metrics are enough for an SMB.

1. Time to productivity

Formula: Average number of calendar days from joining date to the date the manager confirms the employee is performing at the expected level for their role.

Define "expected level" per role in advance — ideally as the day-90 line in the 30-60-90 plan. Ask the manager a single question at day 30, 60, and 90: "Is this person performing at the level expected for the role?" The first "yes" gives you the date.

Track it by role family. Your target is a downward trend, not an absolute number.

2. 90-day attrition rate

Formula: (Number of employees who exited within 90 days of joining ÷ Number of employees who joined in the same period) × 100

Split it by voluntary and involuntary. Voluntary 90-day exits point at onboarding, role clarity, or manager quality. Involuntary ones point at your hiring bar and interview process.

3. Onboarding NPS

Formula: % Promoters (score 9-10) − % Detractors (score 0-6), from the question "On a scale of 0-10, how likely are you to recommend our onboarding experience to a friend joining a new company?"

Ask at day 30 and again at day 90. The day-30 score measures logistics and welcome; the day-90 score measures role clarity and manager quality. When they diverge, you learn something specific.

4. Document completion rate before day one

Formula: (Number of new hires with 100% of mandatory documents and acknowledgements complete before their joining date ÷ Total new hires) × 100

This is the cleanest measure of whether your pre-boarding actually works. If it is below 80 percent, your forms are too long, your reminders are too weak, or your process is not digital.

5. Offer-to-join conversion (no-show rate)

Formula: (Number of candidates who joined ÷ Number of candidates who accepted an offer) × 100

Track it against the length of the notice period. If conversion collapses for candidates with 90-day notice periods, your pre-boarding engagement cadence is the fix, not your compensation.

Supporting indicators worth watching

Turning metrics into action

Numbers only matter if they change something. Set a quarterly onboarding review with three questions: which metric moved, why, and what one change will we make next quarter. One change per quarter, implemented properly, beats a redesign nobody follows.

Common Failure Modes in the Employee Onboarding Process

These are the patterns that show up repeatedly in growing Indian SMBs. Diagnose honestly.

1. Onboarding is owned by nobody. HR thinks the manager owns it, the manager thinks HR owns it, and the new hire falls between. Fix: name a single accountable owner per hire, usually the hiring manager, with HR running the process.

2. Everything happens on day one. Forms, training, tool setup, introductions, first task — all compressed into eight hours. The new hire retains none of it. Fix: spread across pre-boarding and the first two weeks.

3. Documentation is chased after joining. Payroll then scrambles at month-end, PF enrolment is delayed, and the first salary is wrong. Fix: make document completion a pre-condition for the joining date being confirmed.

4. The manager is unavailable in week one. The most common single cause of a bad start. Fix: joining dates get blocked in the manager's calendar; if the manager cannot commit, move the date.

5. The offer-to-joining gap is silent. Six weeks of nothing, then a no-show. Fix: the fortnightly engagement cadence described earlier.

6. Induction is a slide deck from three years ago. Wrong org chart, discontinued products, a founder quote nobody says any more. Fix: assign an owner and a quarterly refresh date to every induction asset.

7. No written goals. The new hire works hard on the wrong things for a month. Fix: 30-60-90 plan, written, shared in week one, no exceptions.

8. Feedback is withheld to be kind. Then the day-90 conversation is a shock. Fix: mandatory written feedback at day 21 and day 45.

9. Onboarding stops at day 15. The checklist ends, the attention ends, and the new hire is left alone precisely when the honeymoon fades. Fix: make the day-30, day-60, and day-90 reviews non-negotiable calendar events.

10. Process exists but only in someone's head. It works until that person is on leave or leaves the company. Fix: put the workflow into a system, not a personal spreadsheet.

11. The same process for every role. A senior finance controller and a junior support associate get identical onboarding. Fix: a common core plus role-specific ramp modules.

12. Nobody measures anything. So nothing improves and the program is the first thing cut in a lean quarter. Fix: the five metrics above, reviewed quarterly.

How Onboarding Software Automates the Process

You can run onboarding on a spreadsheet and a set of calendar reminders. It works up to about 20 hires a year. Beyond that, the coordination overhead grows faster than the team, and things start slipping quietly.

Here is what onboarding software inside an HRMS actually removes from your plate.

Pre-boarding automation

• A candidate portal where the new hire uploads documents, fills personal and bank details, enters PF and nominee details, and e-signs policy acknowledgements — from their phone
• Automatic reminders for pending items, so HR is not manually chasing
• Validation at entry: IFSC format, PAN format, mandatory field checks, file type and size — which prevents most of the errors that surface at payroll time
• A live pre-boarding dashboard showing every upcoming joiner and exactly what is pending for each

Workflow and task orchestration

• Task templates that fire automatically when a joining date is set: IT gets the provisioning task, admin gets the seating task, payroll gets the enrolment task, the manager gets the 30-60-90 task
• Role-based checklists, so a field sales hire and a developer get different task sets from the same trigger
• Escalation when a task is overdue, so gaps surface before day one rather than on it
• A single status view: for any joiner, what is done, what is pending, and who is holding it up

Data flow into the rest of HR

The biggest hidden win is that data entered once flows everywhere. Personal and statutory details go straight into payroll. Grade and location go into the salary structure. Shift and week-off go into attendance. Leave balances are created on joining. Reporting manager and department populate the org chart. There is no re-keying, and therefore no transcription errors showing up as a wrong first salary.

Induction, training, and acknowledgements

• Assign induction and compliance modules automatically on joining
• Track POSH, information security, data privacy, and code of conduct completion with timestamps
• Store signed acknowledgements against the employee record, retrievable in seconds during an audit

Reviews, feedback, and probation

• Auto-scheduled 30, 60, and 90-day review forms sent to the manager
• Onboarding surveys triggered at day 30 and day 90
• Probation and confirmation reminders raised well before the due date, so decisions are made on time rather than lapsing by default

Reporting

• Time to productivity, 90-day attrition, onboarding NPS, document completion, and day-one readiness in one dashboard
• Trends by department, location, manager, and role family — which is how you find out that one team has a structurally worse onboarding experience than the rest

What software will not fix

Software will not make a manager care. It will not write a good 30-60-90 plan for a role you have not thought about. It will not create warmth. What it does is remove the administrative load so that the human parts — the manager's time, the buddy's attention, the honest feedback — actually happen instead of being crowded out by chasing forms.

Templates You Should Build Once and Reuse

Three templates carry most of the load. Build them once, keep them in a shared folder, and adapt per hire.

1. The welcome email (sent within 24 hours of offer acceptance)

• Subject line with the person's name and a genuine welcome
• Two lines from the hiring manager on why they are excited
• Confirmed joining date and reporting time
• A sentence on what the first project or focus area will likely be
• Names and contact details of the HR contact and the assigned buddy
• What happens next and by when (documents, laptop, day-one agenda)
• A link to something useful: a product demo, a recent blog post, a team page
• A clear "reply to me directly if anything comes up" line

2. The day-one agenda (sent one week before joining)

• Reporting time, full address with map link, whom to ask for at reception
• Dress code and what to carry
• Hour-by-hour schedule for the day, with names of who they will meet
• Wi-Fi and access instructions
• Lunch arrangement
• Contact numbers for HR, buddy, and manager
• What the first week looks like at a glance
• For remote joiners: courier tracking, video call links, and a note on what to do if the device is delayed

3. The 30-60-90 plan (drafted before joining, shared in week one)

• Role purpose in one sentence
• Key stakeholders and what each of them needs from this role
• Day-30 outcomes, with how each will be measured
• Day-60 outcomes, with how each will be measured
• Day-90 outcomes, with how each will be measured
• Learning resources: documents, systems, people to meet
• Review dates already in the calendar
• A short section the new hire fills in themselves at day 30: what surprised them, what they need, what they would change

A fourth template worth having is the exit-from-onboarding audit — a one-page day-90 check confirming every document, acknowledgement, training record, and review is complete and filed. Ten minutes per hire, and it saves you from discovering a missing acknowledgement two years later.

A Simple Rollout Plan If You Have Nothing Today

If you are starting from scratch, do not try to build all of this in one go. Sequence it.

Week 1: Write down what happens today, honestly, from offer acceptance to day 30. Identify the three things that break most often.

Week 2: Build the document checklist and move it to a digital form. Set a rule that documents close before the joining date is confirmed.

Week 3: Write the day-one agenda template and the welcome email template. Run them for the next joiner.

Week 4: Assign owners using the RACI table. Get IT provisioning on a fixed lead time.

Month 2: Introduce the 30-60-90 plan for every new hire. Start the buddy program with three volunteers.

Month 3: Add the day-30 and day-90 surveys. Start tracking document completion rate and 90-day attrition.

Month 4 onward: Move the workflow into your HRMS so it runs without anyone remembering, and start reviewing metrics quarterly.

That is a quarter of part-time effort for a program that will serve you for years.

Frequently Asked Questions

How long should the employee onboarding process last?

Ninety days is the right default for most roles. Documentation and orientation finish in the first week, systems and process fluency in the first month, and independent delivery by day 90. Senior leadership hires often need 120 to 180 days because their ramp involves building relationships and credibility across the organisation. Frontline and entry-level roles may reach full productivity in 30 days, but keep structured check-ins running to day 60 because attrition risk stays high well past the point of productivity.

What is the difference between pre-boarding and onboarding?

Pre-boarding covers everything between offer acceptance and the joining date: engagement touchpoints, document and data collection, statutory enrolment preparation, asset and access provisioning, and day-one planning. Onboarding starts on day one and covers orientation, induction, training, relationship building, and performance ramp. Pre-boarding is the phase most companies skip, and it is the phase that determines whether the candidate turns up at all.

Who should own the employee onboarding process — HR or the hiring manager?

Both, with different accountabilities. HR owns the process: the checklist, the system, the compliance elements, the coordination across IT, payroll, and admin, and the metrics. The hiring manager owns the outcome: role clarity, the 30-60-90 plan, feedback, and whether the person becomes productive. When only HR owns it, onboarding becomes paperwork. When only the manager owns it, it becomes inconsistent and things get missed. The RACI table earlier in this article splits it cleanly.

What documents should we collect before day one?

At minimum: government photo identity, PAN details, address proof, education certificates, previous employment relieving and experience letters, bank details with a cancelled cheque, PF/UAN and nominee details, gratuity nomination, prior employer income details for the current financial year, and signed acknowledgements of your code of conduct, POSH policy, confidentiality agreement, information security policy, and data privacy notice. Collect only what you need for employment, payroll, and statutory purposes, tell employees why you are collecting it, and store it securely with restricted access. Statutory requirements vary by state, establishment type, and headcount, so verify the current rules applicable to you with a qualified advisor.

How do we reduce no-shows on the joining date?

Treat the notice period as an engagement window, not a waiting period. Send a personal welcome from the hiring manager within 24 hours of acceptance, keep a fortnightly touchpoint going, reconfirm the joining date in writing about three weeks out, share the day-one agenda a week ahead, and have the manager send a personal note two days before. Also track your offer-to-join conversion by notice-period length — if drop-offs cluster around long notice periods, engagement frequency is your lever.

What should a buddy actually do?

Greet the new hire on day one, have lunch with them in the first week, hold a 20-minute check-in each week for the first four weeks, and be reachable on chat for the small questions. The buddy explains the unwritten norms — meeting culture, who to ask for what, how decisions really get made. The buddy is explicitly not responsible for performance, goals, or feedback; those belong to the manager. Give buddies a written charter and recognise them publicly, or the program quietly dies within two months.

How is remote onboarding different?

Everything that happens by accident in an office has to be scheduled remotely. Ship the laptop at least five working days early with tracking. Make all documentation digital end to end. Cap day-one video sessions and build in breaks. Schedule eight to ten fifteen-minute introduction calls across the first fortnight. Write down norms that are obvious in person — working hours, response expectations, channel etiquette. Lean harder on the buddy, and watch for silence in chat as an early disengagement signal.

What are the best metrics to track for onboarding?

Five will cover you: time to productivity (days from joining to the manager confirming expected-level performance), 90-day attrition rate (early exits divided by joiners in the period), onboarding NPS (measured at day 30 and day 90), document completion rate before day one, and offer-to-join conversion. Track them by department and role family so you can see where the problem actually sits, and review them quarterly with a commitment to change one thing.

Can a small company with no HR team run this properly?

Yes, and it matters more at that size because each hire is a larger share of the team. Start with three things: collect documents digitally before the joining date, run the day-one agenda properly, and write a 30-60-90 plan for every hire. Those three alone will put you ahead of most companies your size. Add the buddy program and the surveys once the basics are habitual, and move the workflow into a system before you cross roughly 25 hires a year.

Bringing It Together

A good employee onboarding process is not complicated. It is a sequence of small, obvious things done reliably: talk to the candidate during notice period, collect documents before they arrive, have the laptop ready, put someone at the door to greet them, tell them what success looks like in writing, give them a peer to ask silly questions, and check in at 30, 60, and 90 days with honest feedback.

None of it is clever. All of it is easy to skip when you are busy, which is exactly why it needs to live in a system rather than in someone's memory.

The compounding return is real. New hires reach full productivity weeks earlier. Early attrition falls, which means fewer rehires, which means your recruiters work on growth roles instead of backfills. Managers spend less time on repeated explanations. And your team starts referring their friends, because the story they tell about their first month is a good one.

Pick one phase and fix it this quarter. If your no-show rate is the problem, fix pre-boarding. If new hires are still confused at day 45, fix the 30-60-90 plan. If everything feels chaotic on day one, fix provisioning lead times. One change, properly implemented, beats a grand redesign that nobody follows.

Ready to stop running onboarding on spreadsheets and reminders? CozyHR brings pre-boarding document collection, automated task workflows across HR, IT, and payroll, induction and compliance tracking, 30-60-90 reviews, and onboarding analytics into one place — with employee data flowing straight into payroll, attendance, and leave so nothing gets re-keyed. Try CozyHR and give your next hire a first 90 days worth talking about.