Employee onboarding checklist for Indian companies

Most onboarding failures happen before the person walks in: the laptop is not ready, the offer terms do not match what the recruiter said, and payroll misses the first cycle because PAN details arrived late. Onboarding is not a welcome kit; it is a sequence of small tasks with owners and deadlines. Here is a checklist that works for Indian companies of 10 to 500 people, organised by timeline.

Day minus 7 to minus 3: before joining

• Offer and acceptance on record. Signed offer letter with CTC breakup, joining date, probation terms, notice period. Verbal changes made during negotiation must appear in the letter.
• Document collection started. Ask for PAN, Aadhaar, bank account details (cancelled cheque or passbook copy), passport-size photo, education certificates, and relieving or experience letters from the last employer. PAN is non-negotiable before the first payroll run; without it you cannot deduct TDS correctly.
• Background verification initiated if your company does it: previous employment and education checks take time, so start now.
• UAN and PF details requested. If the person has an existing Universal Account Number, collect it so PF continues on the same account rather than creating a duplicate.
• IT ticket raised for laptop, email account, and access to the tools their team uses. This is the single most commonly missed item.
• Seating, ID card and biometric enrolment requested where applicable.

Collecting all this over email produces a mess of attachments. A structured pre-joining form, like the onboarding flow in core HR, lets the candidate upload everything once and lets HR see what is missing at a glance.

Day 1: joining day

• Verify originals of PAN, Aadhaar and education documents against the copies submitted.
• Issue the appointment letter if your process separates it from the offer.
• Hand over assets against a signed asset acknowledgement: laptop with serial number, ID card, access card, SIM if provided.
• Add the employee to payroll with the correct date of joining, PF and ESI details where applicable, and the declared tax regime.
• Walk through key policies and take sign-off: leave, attendance, code of conduct, PoSH awareness, IT and data security. Signed acknowledgements matter later; store them with the employee's records.
• Introduce the buddy: one named colleague, not the manager, responsible for answering small questions for the first month. This one habit does more for new-joiner comfort than any welcome email.
• Manager holds a 30-minute conversation covering what the first two weeks look like and what good looks like at 30 days.

Week 1: days 2 to 7

• Employee completes their own profile: emergency contact, blood group, address, nominee details for PF and gratuity.
• Investment declaration submitted for TDS purposes so the first salary is taxed on real numbers, not defaults.
• Access to team documents, code repositories or client folders granted and confirmed working.
• First real task assigned. People settle faster when they ship something small in week one.
• HR checks in once, briefly: any document still pending, any access still broken.

Days 8 to 30

• Weekly manager 1:1s, even 20 minutes, focused on removing blockers.
• Buddy check: is the pairing actually being used, or did it die after day 2.
• Complete any pending verification results and close the file.
• Day-30 check-in, done by HR or the manager with three questions: what is working, what is confusing, what did we promise in hiring that has not shown up. The last question surfaces problems while they are still fixable. Record the answers.

Making the checklist stick

A checklist only works if every item has one owner and a due date, and if someone can see the whole board. Assign tasks to HR, IT, admin and the manager separately; do not let "HR handles onboarding" mean HR chases four departments by phone. Task-based onboarding in a system such as ZekoHR's people ops module shows exactly which items are open per joiner, and the documents collected land directly in the employee's file rather than in someone's inbox.

Review the checklist twice a year. Every time a joiner hits a gap, add the missing item. Within a few cycles the process becomes uneventful, which is precisely what good onboarding feels like.