TEMPLATE

Employee Onboarding Template

A board for the six months after someone accepts an offer: paperwork, equipment, a first week that isn't improvised, and check-ins that actually happen.

Employee onboarding template
Offer accepted
Priya Nair: joins 1 Sep
Paperwork · 6 max
PAN & Aadhaar verification: Priya Nair
PF nomination: Rohan Mehta
Equipment & access
Laptop + badge: Rohan Mehta
First week
Buddy assigned: Priya Nair
30/60/90
30-day check-in: Ananya Rao

Separate from hiring: a card only appears here once an offer has been accepted.

Why most employee onboarding templates stop being used

Most onboarding checklists are written once, printed, and slowly stop matching reality. The laptop-provisioning step still names a process IT changed eighteen months ago, or the checklist lives in a folder nobody in HR opens after week one. A board only stays current if it's the thing people actually work from, not a document that describes a process kept somewhere else.

Paperwork, equipment and culture get mixed into one undifferentiated list. Getting a laptop provisioned and getting introduced to the team are different kinds of work, owned by different people, on different timelines. Flattening them into one checklist means nobody owns the whole thing and everybody assumes someone else is tracking it, which is how a new hire arrives to a desk with no working login and a manager who assumed IT had it covered.

Onboarding stops the day someone starts. The actual failure point for new hires is usually week six, not day one: the point where the initial welcome has worn off and nobody has checked whether the role matches what was promised in the interview. A checklist that ends at "first day" never catches that, and by the time a manager notices something is wrong, the new hire has usually already started quietly looking elsewhere.

It's confused with recruitment. Sourcing, screening and interviewing are a different process with a different owner, run before there's an employee to onboard at all. That lives on the recruitment project template. This board deliberately starts one step later: a card only appears once an offer has been accepted, not before. Merging the two into one long pipeline tends to leave both halves half-done.

Nobody owns the whole thing. HR owns paperwork, IT owns equipment, the hiring manager owns the first week, and without one board all three can see, each assumes the others are handling their piece. The new hire is the only person who experiences all three at once, usually as three separate small failures on the same first Monday.

Remote and hybrid hires expose the gaps faster. A missed laptop shipment or a login that wasn't provisioned in time is recoverable in an office, where someone can walk over and fix it in person. For a hire joining from home, the same gap means an entire first morning spent locked out with no one nearby to ask, which is usually the moment the new hire forms their real first impression of the company.

What's inside

The structure, and why each part is there

Offer accepted

The starting card, created the moment a candidate accepts, carrying name, start date and manager. This is the exact handoff point from the recruitment board: hiring's job ends here, HR's begins, and nothing about candidate sourcing carries forward onto this board.

Paperwork & compliance, WIP-limited

ID verification, tax and provident fund forms, background checks, all capped per HR coordinator so one person isn't quietly processing nine new hires' documentation at once with nothing flagged as behind until a start date arrives with paperwork still incomplete. It's the same WIP-limit mechanic that keeps any ShipSprint board honest: the number on the column heading is a promise about what one person can actually keep on top of, not an aspiration.

Equipment & access provisioning

Laptop, accounts, badge, building access, owned by IT and facilities, not HR, and visible on the same board so a new hire's start date doesn't silently arrive without a working login because the request sat in an inbox no one checked that week.

A first-week checklist page

The built-in wiki holds a first-week plan per hire: who they're meeting, what they're reading, what their manager expects by Friday. Any line can become a task, so "send welcome email" doesn't quietly not happen because it was never anything more than a mental note.

30/60/90 check-ins

Three scheduled cards per hire, due on a fixed cadence rather than left to a manager's memory. The point where onboarding actually gets tested is week six, and this is the column built to catch it before a new hire has already mentally checked out.

One subscription, HR's own vocabulary

This board sits alongside engineering's and marketing's boards on the same account, using HR's own terms, candidates, onboarding checklists, policy pages, rather than a generic task list relabeled with HR words bolted on.

A policy wiki, not just a checklist

Leave policy, expense process, the reporting structure: written once as wiki pages with history, and linked from the new hire's onboarding card instead of re-explained by whichever manager happens to be asked first. Because every page keeps its edit history, a policy update doesn't just overwrite the old version silently; there's a trail of what changed and when, which HR teams usually only wish they had after someone's asked why a policy contradicts what they were told on day one.

How to use it

  1. 01Open a workspace and load the HR template. It comes with a sample new hire already moving through the columns, so the structure is visible before you add a real person. Free for up to five people, permanently.
  2. 02Create the card when the offer is accepted, not on the start date. The gap between those two dates is exactly when paperwork and provisioning need to happen, and it's frequently shorter than HR expects.
  3. 03Split paperwork and provisioning across the people who actually own them. HR does not own IT's queue, and putting both on one card just hides whichever one is behind until it's too late to fix before day one.
  4. 04Write the first-week plan before the start date, not on it. A manager improvising a first week in real time is the most common reason new hires describe onboarding as disorganised, even when every form was filed correctly.
  5. 05Set the 30/60/90 check-in dates the same day you create the card. Scheduled in advance, they happen; left to be scheduled later, they routinely don't, because whoever owns them is already three sprints into other work by day thirty.
  6. 06Assign a buddy in the first-week plan, not as an afterthought. A named peer contact for questions too small to ask a manager consistently shows up in what new hires remember about their first two weeks.

The structure is not proprietary. Any tool with columns and due dates can hold it. It's written up here because the parts that get skipped under time pressure, provisioning ownership and the 30/60/90 cadence, are exactly the parts that determine whether a new hire feels set up or improvised.

If you take three things
  • This board starts after an offer is accepted; recruitment is a separate board that ends where this one begins
  • Paperwork and equipment provisioning need separate owners, or neither gets tracked properly
  • Onboarding usually fails at week six, not day one, so schedule the 30/60/90 check-ins up front
FAQ

Common questions

No. There are no screenshots, no keystroke logging and no activity tracking anywhere in ShipSprint. This board tracks onboarding tasks and check-in dates, not what a new hire does at their desk.

Keep reading

Related pages

See it on your own work.

A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.

14-day full-access trial · sample project included · no card required