A joining checklist for Indian SMEs: documents, assets, access, statutory enrolments

A new employee arrives on a Monday. No desk was decided, the laptop request went in that morning, and the manager who hired her is at a customer site until Wednesday. By the time her bank details reach payroll, the cut-off has passed, so her first salary is wrong and the first thing the company does for her is apologise.

None of that is a documentation problem. Every item on the list would have been done — just not by anyone in particular, and not by any particular date. A joining checklist is not a list of documents. It is a list of owners and deadlines that happens to have documents attached.

Three moments, three owners

The single most useful change is to stop treating joining as one event. It is three, and they have different owners.

1. 1

   Offer accepted to day minus one

   Owner: HR. Everything that can be collected or arranged before the person walks in — documents, bank details, asset requisition, access requests, seat, and the induction slot in the manager's calendar. The point of this phase is that day one has nothing left to arrange.

2. 2

   Day one

   Owner: the hiring manager. Someone is expected, someone receives them, and the day has a shape. The manager being unavailable on a joiner's first day is a scheduling decision, not bad luck — the joining date was known weeks earlier.

3. 3

   First week to first payroll

   Owner: HR again. Completeness checks, statutory enrolments confirmed, and joining inputs into payroll before the cut-off rather than after the first salary.

The checklist

Adapt the rows; keep the columns. A row without a name against it will not happen, and a row without a date will happen late.

BEFORE JOINING                          Owner    By        Done
-------------------------------------------------------------
Signed offer / appointment letter on file  HR    D-7        [ ]
Identity and address proof collected       HR    D-5        [ ]
Education / previous employment proofs     HR    D-5        [ ]
Bank details for salary credit             HR    D-5        [ ]
Statutory enrolment info collected         HR    D-5        [ ]
Emergency contact and address              HR    D-5        [ ]
Laptop / phone / tools requisitioned       IT    D-5        [ ]
Email, systems and door access requested   IT    D-3        [ ]
Seat / locker / uniform arranged           Admin D-3        [ ]
Induction slot in manager's calendar       Mgr   D-3        [ ]

DAY ONE
-------------------------------------------------------------
Received by a named person                 Mgr   D-day      [ ]
Assets issued and signed for               IT    D-day      [ ]
Access working, tested with the employee   IT    D-day      [ ]
Policy handbook issued and acknowledged    HR    D-day      [ ]
Role, reporting line and first-month aims  Mgr   D-day      [ ]

FIRST WEEK
-------------------------------------------------------------
Document file checked for completeness     HR    D+3        [ ]
Statutory enrolments actioned / confirmed  HR    D+5        [ ]
Payroll inputs submitted before cut-off    HR    cut-off    [ ]
Probation review date diarised             HR    D+5        [ ]
Induction to other departments scheduled   Mgr   D+5        [ ]

Documents: collect once, check twice

The documents commonly collected at joining are identity and address proof, evidence of education and previous employment, bank details for salary credit, and the information needed for statutory enrolments. What matters more than the list is that somebody checks the file for completeness a few days in, while the employee is still easy to ask.

The reason to be strict about this is almost never the joining itself. It is the exit, two years later, when a document nobody collected is suddenly needed. Every record you cannot find at exit was one that should have been collected in the first week, which is why getting employee onboarding right pays back at the other end of the employee's time with you.

Assets and access

Two rules save most of the trouble here. Issue assets against a signature, listing make, model and serial or asset number. And request access three days early, because access requests are the item most reliably underestimated — an email address takes minutes, but the approval to create it sometimes takes days.

Keep the issued-asset record somewhere that will still be findable at exit. If assets live in a spreadsheet one person maintains, clearance at exit becomes an argument about what was issued. Holding it in the same place as the employee record — which is what core employee management in an HR system is for — removes that argument entirely.

Why the payroll row is the one that gets missed

Joining inputs reaching payroll after the cut-off is the most common single failure, and it is structural: joining is an HR event, the cut-off is a payroll date, and in a small company nobody owns the join between them. Put the cut-off date on the joining checklist itself rather than assuming it will be remembered, and the failure mostly disappears.

If you are already fixing this, fix it alongside the rest of the monthly input calendar rather than on its own — the two are the same problem, and employee onboarding work that ignores the payroll calendar tends to solve joining beautifully and still deliver a wrong first salary.

Make it boring

The measure of a joining process is not how welcoming day one felt. It is whether the fifth joiner this quarter had the same day one as the first, and whether you can say, for any of them, which documents you hold. Boring and identical is the goal. The warmth is the manager's job, and managers are much better at it when nothing is on fire.

The first-week conversation nobody schedules

One item is missing from most joining checklists and costs more than any document: a short conversation at the end of the first week between the new employee and their manager. Not an appraisal, and not an induction — fifteen minutes on what has been confusing so far and what they still do not know.

It is worth scheduling because it is the only point at which a new joiner will tell you what is wrong with your onboarding while they still notice. By month two they have adapted to the gaps and stopped seeing them, and the same gaps then greet the next person.

Keep a running note of what comes out of those conversations and amend the checklist quarterly. A joining process improved this way converges on something that fits your business within a few hires, which is faster than any template.

The joiner who was announced to nobody

One omission appears on no checklist and causes more first-week damage than any missing document: nobody told the existing team that someone was starting.

The new person arrives, the team works out who they are by lunchtime, and somebody asks whether this means a restructure. Where the role is genuinely new, or replaces someone who left recently, the silence gets filled with a version that is usually worse than the truth.

It costs one message, sent two days before, saying who is joining, what they will be doing, who they report to, and who is looking after them in the first week. The fourth item is the one people forget and the one that most determines how the first days go, because in its absence nobody is quite responsible and everyone assumes someone else is.

The same applies to the systems and access side. IT, facilities and payroll each need to know in advance rather than on the day, and the common failure is that they are told by the person who wants something rather than by a process that told all three at once when the offer was accepted. That single trigger point removes most of the first-week friction, and it is the easiest part of the checklist to automate.

It also does something for the probation decision later. A manager who has spoken properly to a new joiner in week one finds the confirmation conversation straightforward, because expectations were set while there was still time to meet them — which is where employee movement picks the story up.