The hiring manager's onboarding responsibilities

Hiring-manager onboarding is the people-and-work side of joining: a named buddy or first-week plan, introductions, first assignments, and early feedback. HR still owns the document gate and activation. That HR task list stays on the employee onboarding checklist. System stages from accepted offer to active stay on the onboarding product and its guide, not on this page: see Dayzen onboarding. After activation, Dayzen can assign welcome SOPs through SOP management; that is a written work packet, not a claim that software completes every human conversation. This page is for the manager who said yes to the hire. It is not a second HR checklist, not IT device provisioning, and not MDM or laptop inventory as a Dayzen feature.

If the manager treats day one as “HR will handle it,” the new person meets processes and no work. If HR treats day one as “the manager will handle it,” the new person meets a team with no record, no joining date, and no punch path. Split the work on purpose.

What the manager owns (and what they do not)

The manager owns outcomes the joiner will feel as “this is my job”:

• A named person to sit with in week one (buddy, peer guide, or the manager themselves if the team is tiny).
• A written first-week plan: meetings, tools they are allowed to use, and what “done” looks like for the first assignment.
• Introductions to the people the role actually depends on — not a 40-person CC list with no context.
• Time on the calendar for questions in week one, and a scheduled feedback conversation before the end of month one.

The manager does not own, unless your company has formally dual-hatted them:

• Collecting identity documents, bank details, or statutory calculation inputs for payroll.
• Creating the employee ID or marking the person active.
• Issuing offer letters or revising CTC.
• Provisioning laptops, phones, or MDM enrolment as if Dayzen were an ITAM product. Raise an IT ticket in whatever tool you already use; do not wait for HR to “also be IT.”

HR’s checklist remains HR-ops tasks: packet, forms, activation, letters you require. The manager should know the joining date and whether activation has happened. They should not re-run the document hunt in a parallel spreadsheet.

Before day one: three manager actions

Once the joining date is locked, the manager should spend a short, dated block of time — not a heroic weekend — on:

1. Name the buddy. One person, informed, with cover if they are on leave that week. “The team will look after them” is not a name.
2. Write the first assignment. Something real, bounded, and reviewable in a week. Reading a drive folder is orientation, not work. If the role cannot do real work until access exists, write the access-dependent tasks separately from the human tasks (intros, process walkthroughs) that do not need every system.
3. Book the first-week conversations. Manager 1:1 on day one or two. Buddy overlap on day one. The two or three stakeholders the role will ping by Friday. Put them on calendars before the joiner arrives so the week is not improvised in a corridor.

Ask HR one question: will they be active on morning of joining, or should the manager plan a human-only morning? Do not discover that at 10:00. Dayzen onboarding can show pipeline progress to people who have access; it does not replace the manager asking.

If Dayzen assigns welcome SOPs on activation, the manager’s job is to treat those SOPs as the written baseline — read them, do not duplicate them in a private Notion page that will drift — and to add team-specific work the SOP cannot know (this squad’s stand-up, this customer, this repo). SOPs are procedures. They are not a performance-appraisal product and not Dayzen PMS. PMS here means Project Management System for delivery work, which is not this topic.

Day one: presence, not a tour of every tool

On day one the manager (or the named deputy) should be available at the start of the joiner’s working hours. A same-day “sorry, in a client call” with no deputy is an onboarding failure, even if HR’s papers are perfect.

A workable day-one sequence:

• Welcome and the practical facts: where to sit or how the remote day works, hours, who to ping if blocked.
• Introduce the buddy and walk the first-week plan on one page.
• The first assignment in writing, including what “ask me” means versus what they should try first.
• A short intro to the immediate team — names and why they will interact — not the whole company all-hands replay.

Leave HR’s induction session, if you have one, on HR’s calendar. Orientation and induction are not this article’s taxonomy; do not rename them. The manager’s job is work and belonging in the team, not restating the employee handbook.

Do not spend day one hunting a laptop as if that were the manager’s core craft. If a device is late, say so, switch to the human plan, and keep the IT ticket owned by IT. Dayzen does not provision devices. A missing laptop is a parallel delay, not proof that onboarding “hasn’t started.”

Week one: first work that can be seen

By the end of week one, the joiner should have produced something the manager can comment on: a draft, a reviewed ticket, a customer summary, a process note — whatever the role actually ships. If week one is only accounts and reading, the first feedback meeting will be empty and the person will not know the quality bar.

The buddy’s job in week one is interruptible help: “how we file this,” “who actually decides,” “what not to ping the CEO about.” The buddy is not a second manager and not HR. If the buddy is drowning, the manager still owns the plan; they cannot outsource accountability.

Introductions should be purposeful. Each meeting needs a sentence: “You will send them weekly numbers” or “They approve leave when I am out.” A coffee with no purpose is optional kindness, not a substitute for the dependency map.

Attendance and leave in week one follow company policy, not the manager’s vibe. If the joiner needs a half day for a bank visit, the manager should know whether that is leave, permission, or a documented exception. Do not invent a private week-one holiday.

Month one: feedback that is dated

Schedule a conversation before the end of month one with three questions in writing beforehand:

1. What is clear about the role, and what is not?
2. What have you shipped, and what blocked you?
3. What should change in month two (scope, access, pairing)?

Write a short note after the meeting: date, who attended, and any change to the plan. That note is operational, not a performance-appraisal methodology. Dayzen does not claim an OKR or appraisal product on this page. If probation reviews exist in your company, they are a later lifecycle event with their own owner — not a reason to skip month-one feedback.

Early feedback should be specific. “You’re doing great” with no example does not teach the bar. “The client email needed the number in the first line” does.

How the manager and HR stay in sync

Moment	Manager	HR / onboarding
Joining date locked	Buddy, plan, calendar holds	Packet, forms, activation gate
Activation	Confirm they can work as planned	Mark active; welcome SOPs if you use them
Day one	Presence, intros, first assignment	HR checklist items that are still HR’s
Week one	Visible work and buddy cover	Unblock record issues; do not become the buddy
Month one	Dated feedback note	Record hygiene; not a second manager 1:1

If activation slips, the manager adapts the plan (human tasks first) rather than creating a shadow employee in a team sheet. If the offer is withdrawn, the manager cancels the calendar holds; they do not “keep the seat warm” in the org chart.

Failure modes managers actually cause

• No named deputy on day one. The joiner waits in reception or a video lobby.
• Buddy announced in the all-hands only. The buddy did not know.
• First assignment is “get up to speed.” Unreviewable; week one vanishes.
• Manager re-collects PAN and bank details. Duplicates HR’s gate and trains the joiner that the record is informal.
• Feedback only when something breaks. Month one becomes a complaint, not a course-correct.

None of these require a statistic. They are process defects you can see in a calendar and a 1:1 note.

HR can activate a record. Only the manager can make the first week look like the job that was offered.

What this page refuses to become

It is not the hire-to-activate pipeline. It is not the HR onboarding checklist. It is not a first-day / first-week / first-month calendar owned by a sibling article if you already use that split — here the audience is the manager’s responsibilities, not a second timeline brand. It is not IT provisioning. It does not link an unbuilt welcome-SOP essay; the live SOP feature is the product home for procedures assigned at activation.

Keep Dayzen onboarding for the record path. Keep SOP management for the written welcome packet you assign. Keep the HR checklist for papers and gates. Put the buddy, the first assignment, the intros, and the dated feedback on the manager — in writing, with names and dates, before day one rather than after the person has already guessed how the team works.

---

Hiring-manager onboarding is a named buddy, a first-week plan, purposeful introductions, first work that can be reviewed, and a dated month-one conversation. HR keeps the document gate and activation. Dayzen can assign welcome SOPs when someone becomes active; it does not issue laptops. Do not turn the manager into a second HR admin, and do not treat a perfect employee record as a substitute for a manager who showed up.