The employee onboarding checklist for IT companies

Why onboarding fails at small IT companies

Onboarding at a 20-person company usually lives in one senior person's head and a Slack thread called #welcome-yevhen. It works — until two people start the same week, the office manager is on vacation, or the new hire is remote and can't absorb process by osmosis. The symptoms are always the same: day-one laptop scramble, access granted ad hoc over the first month (a security problem, not just an annoyance), and a new engineer who is technically hired but practically idle for two weeks — at agency rates, an expensive silence.

The fix isn't a 40-page handbook. It's a checklist with an owner and a due date on every line, instantiated automatically for every hire.

Before day one (owner: hiring manager + ops)

• Signed contract + personal data collected once, into the HR system — not into a spreadsheet emailed around
• Equipment ordered and shipped (remote: at least 5 business days early)
• Accounts created: email, Slack/Teams, Git provider, project tracker, HR system — from a standard access matrix per role, not improvisation
• Employee record created: manager, department, start date, role — so approvals and org chart work from day one
• First-week calendar drafted: intro calls with manager, buddy, team; project context session booked
• Buddy assigned (a peer, not the manager) and told what a buddy does
• Welcome message drafted for the team channel — who is joining, role, what they'll work on

Day one (owner: manager)

• Hardware works, all accounts log in — verified in the first hour, not discovered at noon
• 30-minute manager 1-on-1: what success looks like in the first month, how you work together, when you meet
• Team intro (15 minutes is enough) + buddy lunch or call
• Security basics: password manager, 2FA everywhere, device policy, who to ping about anything suspicious
• One small real task assigned — merged code or a closed ticket on day one beats any slide deck
• Time-off policy + how to book leave shown in the HR system (it's the first thing people quietly wonder about)

Week one (owner: manager + buddy)

• Project context: the client, the codebase tour, the definition of done, the deploy process
• Timesheet habit started — first week logged, corrected together if wrong (for services teams this is revenue hygiene, not bureaucracy)
• Access review: everything from the role matrix granted, nothing extra (least privilege from week one)
• End-of-week 1-on-1: what's confusing, what's missing, first feedback both ways
• For client-facing roles: introduced to the client with a clear scope of what they own

30 / 60 / 90 days (owner: manager)

• Day 30: expectations check-in against the success criteria from day one — in writing, not vibes
• Day 60: first real feedback cycle (peer + manager); growth areas named; grade/ladder position confirmed
• Day 90: probation decision made consciously and communicated; goals for the next quarter set

If a check-in reveals a mis-hire, deciding at day 90 is cheaper and kinder than discovering it at month eight — that's what the scheduled checkpoints are for.

The part templates forget: offboarding is onboarding in reverse

Every access granted in this checklist must be revoked on exit — and at an IT company, a forgotten Git account or a still-active VPN is a genuine security incident waiting to happen. Keep the exit checklist next to the entry one: handover owner named, access revocation from the same matrix, equipment return, final-pay inputs to your accountant, and a short exit interview while the feedback is still fresh.

How Helia HR runs this

• Per-department onboarding templates with owners and due dates relative to the start date — every new hire gets their checklist instantiated automatically, nothing lives in anyone's head.
• Scheduled check-ins so day-30/60/90 conversations actually happen, and 1-on-1s with private manager notes for the feedback trail.
• Hire-to-employee handoff: a candidate accepted in the recruitment pipeline becomes an employee record with the checklist already attached.
• Offboarding built in: standard exit checklists (handover, access revocation, equipment, final pay) plus a structured exit interview.

FAQ

How long should onboarding take?

Structured checkpoints for 90 days; productive work from week one. If a new engineer hasn't shipped anything in the first two weeks, the process — not the person — usually needs the attention.

Does a 10-person company really need this?

A lighter version, yes — the cost of one bad first week is the same at any size, and the checklist takes an hour to write once. The payoff compounds with every hire after.

Who should own onboarding?

One name per line beats one owner for everything: ops owns equipment and accounts, the manager owns expectations and check-ins, the buddy owns "how things actually work here".