A first-week onboarding packet gives a new hire the context their colleagues already have: who to meet, what the team is working on, recent decisions that shape the role, tools and policies, and a 30-day plan. Paperwork and laptops are the easy part. Context is what decides how fast someone becomes useful.
The onboarding packet template
1. Welcome
- A short note from the manager: why this role exists and what success looks like in 90 days.
- Start date, time, location or joining link, and who meets them.
2. First-week schedule
| Day | Morning | Afternoon |
|---|---|---|
| Day 1 | Welcome, setup, team introductions | Read sections 4 and 5 with buddy |
| Day 2 | Meet key colleagues (section 3) | Shadow a real piece of work |
| Day 3 | Tools and processes walkthrough | First small task |
| Day 4 | Meet partner teams | Continue first task |
| Day 5 | Review week with manager | Agree 30-day plan |
3. People to meet
| Name | Role | Why you should meet them | Booked? |
|---|---|---|---|
| ☐ |
Include a named buddy for the first 30 days.
4. Context: what we are working on
- The team's top three priorities this quarter, and why
- Projects the new hire will join, with current status
- Customers or stakeholders they will deal with
- Words and acronyms used in the team (a short glossary)
5. Decisions that shape this role
| Decision | When | Why | Link |
|---|---|---|---|
This is the section most packets skip. A new hire who knows why things are the way they are stops reopening settled questions. Pull entries from your decision log.
6. Tools and access
- Systems they need, who grants access, and when
- Where documents live
- How the team communicates (which channel for what)
7. Policies to read and accept
- Code of conduct, security, leave, expenses, data protection
- Ask for acknowledgment, not just a link
8. The 30-day plan
| Week | Goal | How we will know |
|---|---|---|
| 1 | Understand context, meet people | Can explain team priorities |
| 2 | Complete first task | Task reviewed |
| 3 | Own a small area | Handles it with light review |
| 4 | Contribute to a decision | Has an opinion with reasons |
Onboarding packet checklist for the manager
- Packet ready two days before start
- Buddy named and briefed
- Meetings booked in the calendar
- Access requested in advance
- Context and decisions sections current (not last year's)
- Day-five review booked
Where Reattend fits
The hardest section to keep current is context and decisions. Reattend builds a first-week packet for joiners from the organization's memory: the decisions, people and context relevant to their role, drawn from their department's memory. Policies can be read and accepted in the Reattend desktop app. You can still use this template by hand; see our team onboarding use case for more.
Frequently asked questions
What should be in a new hire onboarding packet?
A welcome note, the first-week schedule, the people to meet and why, the context of the team's current work, recent decisions that shape the role, tools and access, policies to read, and a 30-day plan with clear first goals.
When should you send an onboarding packet?
Send the practical parts (schedule, where to go, what to bring) a few days before the start date. Share the context and decisions sections on day one, and walk through them together.
What is the difference between an onboarding packet and an onboarding checklist?
The checklist is for the people doing onboarding (IT, HR, manager). The packet is for the new hire: what they need to read, who they need to meet and what they should do first.