Onboarding New Employees: The Admin's Playbook

HR owns the program. Hiring managers own the role. The administrative assistant — formally or informally — owns whether the new hire's first week works. The laptop ready, the badge active, the calendar pre-populated, the right people booked for introductions, the lunch order remembered, the unfamiliar systems pre-explained: each of these is small, all of them together are what makes the difference between a calm first week and a chaotic one.

This page is the operational playbook for that work. It is distinct from your own first 90 days as a new admin — that page is about being onboarded; this one is about running the onboarding for someone else. It also pairs naturally with the desk manual guide, because the artifact a new hire actually wants on day three is some version of a desk manual for their new role.

The Two-Week Pre-Boarding Window

Almost everything that goes wrong on a new hire's first day was decided during the two weeks before they arrived. The pre-boarding window is when the admin's contribution is most leveraged.

What to confirm immediately after the offer is signed

• Start date and arrival logistics. Where they go on day one, who meets them, what time, what the dress code expectation is, and whether they need a parking pass or any visitor badge to enter the building before their permanent badge is ready.
• Hardware and software needs. Laptop model, additional monitor, keyboard, mouse, headset, mobile phone if applicable. Software accounts to provision — email, the messaging tool, the project management system, the CRM, the HR system, the expense system, anything specific to their role. The IT lead-time is real and is almost always the binding constraint for first-day readiness.
• Access requirements. Building badge, system access, VPN credentials, any specific systems requiring a separate account-creation request. Many companies have role-based access templates; identify which one fits before you start filing tickets.

The pre-boarding email

One week before start, the new hire should receive an email with everything they need to walk in calmly:

• The exact address, including building entrance and floor.
• Who they will meet first and how to identify them.
• The first-day schedule at a high level — without overpromising, since plans change.
• What to bring (ID for I-9 in the US, equivalent documentation elsewhere) and what not to bring (their own laptop, expecting it will be needed).
• Lunch arrangements — whether it is provided, whether they will go out, what to expect.
• Dress code, including any team-specific norms.
• Your name and direct contact, so they have a real person to ping if anything is unclear before they arrive.

Resist the urge to make this email beautiful. A clear, specific, scannable email is more valuable than a designed welcome packet that buries the practical information.

Day One Setup at the Desk

The new hire's desk on day one is a small theatre piece. The cost of getting it right is hours of admin work over the prior week; the value to the new hire is enormous.

What should be at the desk before they arrive

• Their laptop, already powered on and at the login screen, with their username pre-filled if your system allows.
• A note showing their email address, their temporary password, and the one or two URLs they need first (the company intranet, the HR system).
• Notebook and pen, and any company-branded items if those are part of your culture.
• A printed or digital copy of their first-week schedule.
• An office map if the building is big enough to need one, with relevant locations marked — their team, the bathrooms, the kitchen, your desk, the printer, the conference rooms.
• The Wi-Fi network name and password, even if they will be on the wired network — the question always comes up.

What should not be there

• A fifty-page printed handbook. Nobody reads this on day one. Send the digital version, point them to it on day three when they have capacity.
• Login forms for nine different accounts. Stagger account introductions across the week.
• Items left over from the previous occupant. Especially their personal items, and especially any sensitive files.

The First-Week Schedule

The schedule is the single most important deliverable the admin produces for a new hire. Build it deliberately, not by inviting whoever is free to claim a slot.

What to include

• HR and compliance items first thing on day one. Forms, policy review, benefits enrollment. Get them done before the new hire's brain has filled with names and acronyms.
• The first 1:1 with their manager early. Ideally within the first three hours. The hiring manager sets the tone; the rest of the week works better if that conversation has already happened.
• An IT setup block. Even with a pre-provisioned laptop, the new hire will spend 60-90 minutes on first-time logins, two-factor enrollment, software installs, and email configuration. Block the time so it does not crowd out something else.
• Introductions paced across the week. Three introductions on day one, three on day two, three on day three. The "meet everyone in one day" pattern is exhausting and produces no retention.
• Genuine downtime. Block 30 minutes here and there for the new hire to actually do work. A schedule packed wall-to-wall with introductions tells them their time is not respected.
• Lunch with the team or a specific peer on day one and at least once more during the week. Lunches build relationships in ways that scheduled introductions do not.

What to leave out of the schedule

Skip the broad all-team introductions in week one. They overwhelm the new hire and get nobody anywhere meaningful. The right time for those is week three or four, after the new hire has formed enough context to know who is who.

The Buddy Assignment

One of the highest-leverage things an admin can arrange is a designated peer the new hire can ask the small questions to — questions they will not ask their manager because the questions feel too small, but that compound into confusion if unanswered.

What a good buddy looks like

• Same level or one level above the new hire — not their manager.
• Similar role or adjacent role, so the small questions make sense to them.
• Someone who has been with the company at least a year, and ideally was themselves onboarded recently enough to remember what was confusing.
• Someone with the bandwidth to actually answer questions for a week or two, not the most overworked person on the team.

What to brief the buddy on

Send the buddy a short note before the new hire arrives. The new hire's name, role, start date, and a one-line ask: "Be the person they can ask the small questions for the next two weeks. Lunch on day one if you can; ad hoc after that. Not a formal mentorship — just a real person they can ping." The lighter the framing, the more often it actually happens.

The Quiet Details

Three small things separate good onboarding from generic onboarding:

Get the name right

Confirm pronunciation and preferred name before day one. Use it correctly when introducing them. The number of new hires who quietly accept being called the wrong version of their name in their first week is high; the number for whom it does not matter is much lower than people assume.

Notice the small accommodations

Did they mention a dietary restriction during the offer process? Pass it along to whoever is ordering lunch. Did they mention they have to leave early Wednesday for a personal appointment? Block their calendar accordingly. The act of having remembered something they only mentioned once lands more meaningfully than any welcome gift.

Send a check-in on day three

A short message — "Just checking in: how is the first few days going? Anything I can help with?" — sent on day three or four catches small problems before they become quiet resentments. Most replies are "all good, thanks." A small share are problems you can fix in five minutes that would otherwise spiral.

What a Good First Week Produces

By the end of week one, a well-onboarded new hire should:

• Be logged in to every system they need, with two-factor enrolled.
• Have met their direct team and a handful of cross-functional peers.
• Know where to find the answers to the questions they did not ask — the buddy, the desk manual, the intranet, the HR portal, you.
• Have done at least one piece of real work, however small, so they end the week feeling productive rather than processed.
• Have a clear picture of what the next two weeks look like.

None of this is heroic. All of it is the result of two weeks of small, careful work and a deliberately designed schedule.

Common Mistakes

• Booking the laptop too late. IT lead times are the binding constraint on a clean day one. File the request the moment the offer is signed, not after the start date is confirmed.
• Treating onboarding as a single hand-off. Onboarding is a two-to-three-week investment, not a day-one event. Build the schedule for the full first month.
• Designing for the company's convenience, not the new hire's experience. Wall-to-wall meetings are convenient for the people running them and exhausting for the new hire.
• Skipping the documentation handoff. The new hire needs the equivalent of a desk manual for their role within the first two weeks — what their team owns, where the canonical files live, who handles what.
• Forgetting the offboarding handoff. If the new hire is replacing someone, the predecessor's accumulated context cannot be re-derived. Where possible, schedule overlap between the outgoing and incoming employees, and document what could not be captured live.
• Not closing the loop with the hiring manager. A short check-in with the manager at end of week one — "anything I should adjust for week two?" — surfaces issues before they become structural.

The work pays off twice. Once for the new hire, who has a clean first week. And once for you, because the onboarding system you build for one new hire becomes the template for the next. Document it once, and the second onboarding takes a fraction of the time. The structural place for that template is your desk manual; the broader role-context for any new joiner is in first 90 days as an administrative assistant if they happen to be joining your team.