Free checklist · Onboarding

First Week Onboarding Checklist

A first week onboarding checklist covers the five days after arrival, when an employer's job is to supply context rather than tasks. It sequences how the organisation works, who the new hire needs to know, which systems they will use daily, one small piece of genuine work, and a Friday conversation that surfaces problems while they are still cheap to fix.

Week one is where onboarding either becomes a programme or reverts to sink or swim. The new hire now has a working laptop and a desk, which makes it tempting to hand over a backlog and step away. That produces someone who can complete tasks but cannot judge which tasks matter. The purpose of the first week is orientation in the literal sense: understanding where things are, how decisions get made, who to ask, and what good looks like here. This checklist is written for the manager and the people team running that week.

Set the shape of week one before Monday

An unplanned week fills with whatever is urgent for everyone else. Draft the week as a calendar before the new hire arrives, with named sessions, named hosts and deliberate gaps. Send it on the first day so the person can see the week ahead rather than discovering it one meeting at a time.

Leave at least a third of the week unscheduled. New hires need time to read, to write things down and to follow up on the questions they were too polite to ask in the meeting itself.

  • Draft the full week as calendar invitations before the start date
  • Name a host for every session so none of them quietly get cancelled
  • Leave at least a third of the week deliberately unscheduled
  • Share the week plan with the new hire on day one
  • Confirm each host has agreed to their session rather than just being invited
  • Keep afternoons lighter than mornings

Teach how the company works before what the job is

New hires arrive with a reasonable understanding of their profession and almost none of your organisation. The gap that slows them down is rarely technical. It is not knowing who decides, how work is prioritised, what the company sells and to whom, and which internal words mean something different here.

Cover the commercial picture explicitly, even for roles that never speak to a customer. An engineer or an analyst who understands how the company makes money makes better decisions in the small moments that nobody reviews.

  • Walk through what the company sells, to whom, and how revenue works
  • Explain how work is prioritised and who approves what
  • Share the current company or department objectives in writing
  • Provide a glossary of internal acronyms, product names and team names
  • Show the organisation chart and explain the reporting lines that matter to this role
  • Point to where decisions are recorded and where discussion happens

Book the introductions that build the internal network

The people a new hire needs are not always the people nearest their desk. Identify the five to eight individuals this role depends on, brief each of them on why the meeting is happening, and book short sessions across the week rather than clustering them.

Give the new hire something to ask. A standard set of three questions turns an awkward introductory call into a useful one and produces notes the person can actually reuse.

  • List the five to eight people this role genuinely depends on
  • Brief each host on the purpose before the invitation goes out
  • Give the new hire three standard questions to ask in every introduction
  • Spread introductions across the week rather than stacking them on one day
  • Include at least one person outside the immediate team
  • Ask the new hire to keep a short note per person and review it on Friday

Run this checklist inside your hiring pipeline

Free 1-user plan · No credit card

Move from watching to doing with one small real task

By midweek the new hire should complete something that genuinely counts, however small. Practice exercises and sandbox environments feel safe but teach very little, because nobody reviews them seriously and nothing depends on the outcome.

Choose the task for its teaching value rather than its urgency. Something that touches two or three systems, requires asking one colleague a question and ends in a visible result will teach more about how work moves here than a week of documentation.

  • Choose a first task that is real, small and low risk if it goes wrong
  • Pick work that requires touching more than one system or team
  • State clearly what done looks like before the task starts
  • Pair the new hire with a colleague for the first attempt rather than reviewing afterwards
  • Review the completed work properly, with specific feedback
  • Avoid assigning anything with an external deadline in week one

Run tools training in short sessions tied to real use

A two hour walkthrough of every internal system produces almost no retained knowledge. Break training into short sessions, each immediately before the new hire has to use that tool for something, and record them so people can rewatch rather than reschedule.

Order matters. Teach the tools used daily first and defer anything used monthly or quarterly until the moment it is needed, at which point ten minutes of instruction will stick better than an hour did in week one.

  • Teach only the tools used daily during the first week
  • Keep each session short and place it immediately before first real use
  • Provide recorded walkthroughs so sessions can be rewatched
  • Set up the new hire's own views, filters and notification settings with them
  • Confirm access to any secondary systems that were deferred from day one
  • Note which tools were deferred and when they will be covered

Establish the manager one to one and the feedback loop

The check-in rhythm set in week one tends to persist, so set it deliberately. Short daily contact in the first days, moving to a scheduled weekly one to one by the end of the week, gives enough support without hovering.

Feedback has to run both ways from the start. If the first time a new hire is asked for their view is in a month three survey, the useful observations, the ones only a newcomer can make, will already have faded.

  • Hold a short manager check-in daily for the first three days
  • Schedule the recurring weekly one to one before the end of week one
  • Agree how the new hire should raise a blocker and how quickly to expect a response
  • Ask explicitly what has been confusing or contradictory so far
  • Write down what the new hire says is unclear and resolve it by the following week
  • Confirm the buddy relationship is working and change it if it is not

Check for early warning signs by Friday

Certain patterns visible at the end of week one predict trouble reliably: the new hire has met almost nobody, cannot describe what their team is currently working on, has had no manager conversation longer than five minutes, or is still blocked on access from day one.

Run a deliberate Friday review against those signals rather than waiting for a formal milestone. Everything on that list is recoverable in week two and much harder to recover in month two.

  • Confirm every access and equipment issue from day one is now closed
  • Ask the new hire to describe what their team is currently working on
  • Check the scheduled introductions actually happened and rebook any that did not
  • Ask what they expected this week that did not happen
  • Confirm the first task was completed and reviewed
  • Agree the two or three focus areas for week two in writing

Get this checklist emailed to you

We'll send this checklist plus the rest of the onboarding pack — and the occasional hiring tip. No spam, unsubscribe anytime.

No spam — just the resource and the occasional hiring tip. Unsubscribe anytime.

FAQ

First Week Onboarding Checklist — FAQs

How much work should a new hire produce in their first week? +
One small, real, completed piece is a reasonable target for most roles. The point is to learn how work moves through the organisation, not to contribute capacity. Loading a full workload in week one usually means the person learns the mechanics of the task without learning why it matters, which surfaces as poor judgement later.
How many meetings should be scheduled in the first week? +
Fewer than most plans contain. A useful rule is that no more than two thirds of the week should be booked, leaving genuine time to read, absorb and follow up. A back to back first week looks thorough on a calendar and produces someone who has heard everything and retained very little.
Should the buddy be from the same team as the new hire? +
Usually yes for practical questions, since a teammate knows the tools and the daily rhythm. Some employers assign a second contact from another team to give a wider view and a safe place to ask questions the person might not want to raise with a direct colleague. The buddy should not be the line manager either way.
What if the new hire seems quiet or disengaged in week one? +
Check the conditions before drawing conclusions. Quiet in week one often means unclear expectations, no completed task, or no one to ask small questions of. Ask directly what they are waiting on and what is unclear. Treat a genuine engagement concern as a conversation to have in week two, not a judgement to form on day three.
Do we need a formal first week agenda for every role? +
A shared template with role specific edits works better than either extreme. Company context, policy basics and core tools are the same for everyone and should be standardised. The introductions, the first task and the systems training are role specific and should be written by the hiring manager each time.
When should benefits and policy sessions happen? +
After the first few days, once the immediate practicalities are settled. Benefit decisions often carry enrolment deadlines, so check what those are and work backwards, but scheduling them in the first hours competes with orientation and tends to produce decisions made without attention.
How do we onboard someone whose manager is new to managing? +
Give the manager the same structure you would give the new hire: a written list of what they own, the questions to ask in each check-in and a named person in HR to escalate to. First time managers rarely lack willingness, they lack a model of what a good check-in contains.
Pitch N Hire ATS

Run this checklist inside your hiring pipeline

Pitch N Hire is an applicant tracking system. The steps on this page become stages in a pipeline, so nothing is skipped and everyone can see where each candidate stands.

  • Turn process steps into pipeline stages the team follows
  • See exactly where every candidate is, without status meetings
  • Keep notes, feedback, and documents on the candidate record

Free for 1 user · No credit card · Talk to a real hiring expert

Built for recruiters & hiring teams

Onboard new hires from the same system you hired them in

Pitch N Hire keeps the offer, the paperwork trail, and the candidate record in one place — so nothing is retyped between hiring and day one. Start free with the 1-user plan.

Prefer to talk? Book a demo · Talk to sales · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo