A New-Hire First-Week Checklist That Actually Works

If a new hire can't answer seven basic questions by the end of their first Friday, they'll start looking for a new job on Monday. That's not an exaggeration, it's statistics: according to the Jobvite Job Seeker Nation Study, 33% of new hires leave within the first 90 days (Jobvite, 2018), and 70% of employees decide whether "the job is a fit" within the first month (BambooHR, 2023). Most of that decision is made in the first week.

Most onboarding programs follow the same template: a giant 80-page PDF about the company's history, access credentials issued three days after the start date, a buddy assigned on paper who never reaches out, and a first 1:1 where the manager asks "so, how's it going?" and waits for a detailed answer from someone who hasn't even learned their deskmate's last name.

That's not onboarding — it's a random set of activities HR runs to tick a KPI. Real onboarding works differently. Below is a practical plan, no theory and no fluff.

The Seven Questions a New Hire Must Be Able to Answer by Friday

This is the baseline checklist for judging whether a first week went well. If, by Friday evening, the new hire can confidently answer all seven, you're in good shape. If only half — you have a problem.

#	Question	What "answered" means
1	Who's my manager and how do I reach them?	Name, messenger, email, time of the regular 1:1 — nothing starts without this.
2	Who's on my team and who's responsible for what?	A list with photos, roles, areas of responsibility. Recognizes at least 5 by sight.
3	What do I need to accomplish in my first month?	3–5 concrete goals. Not "study the docs," but "set up X, get Y working."
4	What tools do I need and do I have access?	All access provisioned before day one. If not, you lose 2–3 days for nothing.
5	Where do I find answers to everyday questions?	Policies, procedures, contacts, vacation, sick leave — one entry point, not three.
6	When is my first full 1:1 with my manager?	Scheduled concretely (day 2, 11:00). Not "sometime next week."
7	How do things actually work here?	Chat tone, meeting format, "when to ask questions," 1:1 frequency, dress code.

These seven questions cover 80% of a new hire's cognitive load in the first week. When they have the answers, they relax and start thinking about the work rather than "how things are set up here." When they don't, they spend the first week on reconnaissance, lose focus, and you get a slow start.

A simple rule: the HR team should walk through this checklist as a new hire themselves — twice a year, sitting down at a freshly hired person's computer (with their consent). If any of the seven questions can't be answered in 2 minutes, you have a hole in the process.

Day 1 — What's Mandatory and What's Optional

The most common day-one mistake is trying to cram everything in. Registration in ten systems, infosec training, a video greeting from the CEO, lunch with the team, a lecture on culture, and three welcome PDFs. By the end of the day the new person leaves the office with a buzzing head and not a single real action to their name.

What's mandatory on day one:

• The manager greets them in person. Not HR — the manager. 15 minutes, coffee, a rundown of the coming month. It signals that the person is valued and their arrival was anticipated.
• All access is ready before they arrive. Email account, badge, portal, messenger, all the needed systems. If the first day is devoted to "provisioning access," you've burned the first impression.
• A 30-minute team intro. Standup format: each person spends 1–2 minutes saying what they do. No presentations.
• A first useful task completable in 1–2 hours. Not "read the docs," but a real action that goes into the work. A psychological win on day one is very valuable.
• One buddy with a name, a role, and the phrase "message me with anything." Not from HR. Not "they'll come by sometime." A specific person, introduced in person.

What's optional but desirable: a welcome kit (merch, a card, something symbolic — it works, but isn't a priority), a 15-minute intro with one of the adjacent departments, lunch with the team.

What NOT to do on day one: long training videos about company history, product quizzes, paperwork (anything that can be moved into the HR system gets moved there). Loading them up with tasks from day one isn't needed either: a new hire's brain isn't plugged into the context yet, and the tasks will be done poorly.

Days 2–5 — Structure Without Overload

From day two you need a simple, predictable structure — each day closing one psychological task.

Day 2 — a full 1:1 with the manager. 30 minutes, "let's get to know each other" format. The manager explains what they expect in the first month, what the 3–5 goals are, what good work in this role looks like. Not the employee's report, but the manager's investment in the foundation of the relationship.

Day 3 — the first meaningful task. Not "read the docs." Real work whose result goes to the team. Sized to be completable in about 1.5 working days. It shouldn't be a critical task, so the cost of a mistake is low, but it must be real.

Day 4 — the first feedback received. On the task's result. Specific, to the point: what worked, what to tweak. Not "all good, keep it up." It signals "around here, we talk about the work."

Day 5 — first-week retro. 30 minutes with the manager. What they liked, what bugged them, what's unclear. A heads-up on next week's plan. This closes the first week emotionally and reduces the anxiety of "how am I doing overall?"

In the background — the buddy. At least one touchpoint a day: "how are you, any questions?" This is the person to bring the questions to that feel awkward to ask the manager or HR. Without a buddy, the first week feels like loneliness, especially for new hires on a distributed team.

What NOT to Do in the First Week

A few patterns we see at every other company that reliably kill onboarding.

• An 80-page onboarding PDF. Nobody reads it. Turn it into short, topic-based materials available in the portal on demand. A PDF is a form of "we did onboarding so we can talk about it," not a real tool.
• 6-hour video courses on company history. If someone wants to learn the history, they'll give it 30 minutes. If they don't, they'll watch 6 hours half-attentively while scrolling their phone. Cut the essentials into a mandatory minimum, the rest optional.
• A buddy with no commitment. If the buddy is just a line — "John Smith" — with no clear instruction to "reach out on day one, message at least once a day the first week," the buddy doesn't exist. Better no buddy than a token one.
• "Set up your access when you find the time." Never. That's HR/IT's job, not the employee's, and it's done before they arrive.
• Silence at the first 1:1. "So, how's it going?" is a weak question. Better: "Tell me what you expected to see and what you actually saw. What surprised you?" A specific question gets a specific answer.
• Loading them to 100% from day one. A new hire's brain isn't plugged into the context yet. Give 30–40% load in the first week, so there's time for getting acquainted, reading materials, soaking things in.
• Isolating the new hire in a solo task. The first task should require talking to the team — otherwise the person sits in a corner and never connects. Early socialization isn't a nice option, it's a retention tool.

A 7-Day Plan Template — Take It and Copy It

If you'd rather not invent it from scratch, here's the schema we use ourselves and hand to clients.

Day 1 (Monday): Manager greeting, access, team intro (30 min), a first micro-task, buddy introduction.

Day 2 (Tuesday): A full 1:1 with the manager (30 min), first-month goals, an overview of the main tools and where things live.

Day 3 (Wednesday): The first meaningful task begins. Contacts 1–2 colleagues for the work. Buddy check.

Day 4 (Thursday): Task completed, first feedback received on the result. 30 min with a senior colleague on the role's subject area.

Day 5 (Friday): First-week retro with the manager (30 min), next week's plan, a check against the seven checklist questions.

Days 6–7 (weekend): Actually the weekend. No "want to flag a couple of things in the chat," no "read this document." If you want to burn out a new hire in week one, that's the fastest way.

On the Monday of week two — the next meaningful task and the second full 1:1. The seven-question check — every two weeks in the first month, then once a month through day 90.

The Bottom Line

Onboarding isn't about documents or corporate values. It's about the speed at which a new person feels they're in the right place: they know the manager, know the team, know what they need to do in the first month, and can see there's someone nearby to turn to.

Bad onboarding is the most expensive line item in HR. If you lost someone on day 60, you lost the cost of hiring (roughly 1.5–2 months' salary), plus the manager's time, plus the team's missed opportunities. Good onboarding costs an order of magnitude less and works without fail.

Next, on 1:1s with your manager. Twelve questions that change a team in a quarter, and how to separate "operational 1:1s" from "developmental" ones.

If you want the ready-made 7-day plan template, it's linked in the article card. No signup, in Google Docs, copy it and adapt.