Employee onboarding checklist: the first week, made repeatable

An employee onboarding checklist exists because the same things go wrong every time someone joins: an account that was not created, a laptop that arrived late, a first task nobody prepared, and a manager in meetings all day. None of it is complicated. All of it is forgettable, which is exactly what a checklist is for.

The version that works is split by timing and has an owner on every line.

Before the first day

• Contract signed and returned, and the start date confirmed in writing.
• Accounts created: email, chat, the tools they will use in week one. Not every tool — the ones they need to start.
• Equipment ordered and delivered, tested if it is going to someone remote.
• First-week plan written: what they should be able to do by Friday, and the first real task.
• Buddy assigned — someone who is not their manager, for the questions people do not want to ask a manager.
• Calendar invitations sent for day one, plus the recurring meetings they should attend.
• The team told who is joining, when, and what they will work on.

Day one and week one

• A person meets them, physically or on a call, in the first fifteen minutes. Silence on day one is what people remember.
• Access verified by actually logging in together, not assumed from a confirmation email.
• Handbook and the two or three policies that matter now, not the whole library.
• A first task they can complete this week — small, real, and useful. Shipping something in week one changes how the job feels.
• Introductions with the three people they will work with most, scheduled rather than left to chance.
• End-of-week check-in with the manager: what is unclear, what is missing, what surprised them.

The single most common failure is access. Create every account before the start date and test one login per system yourself — a new joiner spending day two waiting on a password reset loses momentum that is hard to recover.

Weeks two to twelve

1. Set explicit expectations for thirty, sixty and ninety days, written down and agreed rather than implied.
2. Schedule the ninety-day conversation on day one, so it happens even in a busy quarter.
3. Give ownership of something small and real by week three. Waiting until someone is fully ramped teaches them to wait.
4. Ask what was confusing in week two, while they still remember and before it becomes normal.
5. Check the tool sprawl: what did they end up needing that was not on the list, and add it for next time.
6. Update the checklist after every joiner. It is the only document that improves by being used.

Ettex Board is a natural home for this: a board template per joiner with columns for before, week one and first month, one card per item with a single assignee and avatar, due dates, checklists inside cards to break a card into steps with visible progress, colour labels for IT, HR and manager tasks, comments and @mentions so questions sit on the task, activity history per card, live updates for everyone at once, and export to CSV or JSON. The first-week plan and the policies themselves live as documents, linked from the cards.

What makes onboarding fail

• A checklist owned by nobody, so it exists but is not run.
• Everything scheduled on day one — six meetings and a policy library is not a welcome, it is an ordeal.
• No first task, so the first week is passive and the person learns that waiting is normal here.
• Access requested on the start date rather than before it.
• A remote joiner treated as an office joiner minus the office. Remote onboarding needs more deliberate contact, not less.

A good employee onboarding checklist is boring, owned and updated after every joiner. Accounts before day one, a real task in week one, and a conversation at ninety days that was booked on day one.