First day, first week, and first month onboarding

First-day, first-week, and first-month onboarding is a manager-facing timeline: access and introductions on day one, role clarity in week one, and early delivery plus feedback in month one. It is not a second copy of HR’s task list and not a reprint of system stages. HR joining chores stay on the employee onboarding checklist. Offer-to-active pipeline states stay on hire-to-activate onboarding. Product context is Dayzen onboarding (new-joiner pipeline, pre-onboarding forms, activation emails, optional welcome SOP assignment). Dayzen does not automatically perform every human step on this calendar. It does not provision laptops or run the welcome tour. This page does not invent retention statistics; it is a practical plan, not a proof that a timeline “reduces attrition by X percent.”

Who this calendar is for

The primary reader is the hiring manager (or the person who will actually direct the work). HR still owns documents, the activation gate, and the employee record. IT still owns devices if you have an IT function. The manager owns whether the person knows what good work looks like this month.

If a welcome SOP is assigned at activation, treat it as reminders and named tasks — not as the software completing coffees, shadowing, or feedback. Check the SOP off when the human work happened. Do not check it off because the pipeline says Activated.

Write the plan against the joining date you actually locked. If the date slips, shift the calendar on the same person. Do not create a second employee because “month one already started on the old Monday.”

Before day one (manager, not a pipeline recap)

You do not need to operate HR’s stages. You do need a few facts from them: joining date, work location or remote pattern, role title as offered, and whether activation is expected before they arrive. If those are missing, ping the onboarding owner once, with the identity, not a new spreadsheet.

Prepare three named things:

1. A buddy or first-week contact who is not on leave that week.
2. A first assignment small enough to finish in a few days, with a definition of done.
3. A intro list: who they must meet in week one (team, one cross-functional partner, the person who approves leave if that is not you).

If they are remote, the “desk” is a calendar of calls and a written channel. If they are on site, the desk and badge are IT or admin tasks you confirm exist — you still do not treat Dayzen as the provisioning system.

Do not wait for induction class to do this preparation. Induction is a session with a curriculum; your calendar can note the slot without becoming L&D’s attendance sheet.

Day one: arrive, access, humans

Day one’s job is that the person can exist at work without improvising. In practice:

• Confirm they are expected. Reception, the team channel, and you. A surprise joiner is an HR packet problem or a date that never reached you.
• Confirm they can log in to what they need that day. If activation happened, they should have the account setup the product actually sends. If something failed, it is an HR or IT ticket with an owner — not a speech about culture.
• Introductions. Team names, how you communicate (which chat, which meeting), who the buddy is, where they sit or which link is the team stand-up.
• The first assignment in writing. Even a reading list plus a two-paragraph summary counts. “Shadow everyone” is not an assignment.
• Logistics that block work. Hours, meal, emergency contact already on file (HR’s form), how to report they arrived. Do not re-collect the pre-onboarding form as a printout unless a field is actually missing.

What day one is not: a full strategy offsite, a complete handbook recitation, or finishing every HR checklist line. If a document is still an allowed open item, HR owns the chase. You own not leaving the person in a corridor.

Length: a structured morning plus a real first task beats eight hours of slides with no buddy. If an induction session is booked on day one, protect an hour either side for manager time. Sitting only in a classroom on day one is induction without orientation.

End of day one: a short check — can they open the tools they were promised, do they know tomorrow’s first meeting, do they have your contact. Capture blockers in one note to HR/IT. Do not capture them only in your head.

Week one: role clarity and a working rhythm

Week one turns “arrived” into “can operate.” Manager work:

• Role in this team. What the offer title means here: current priorities, what is out of scope for month one, who else owns adjacent work.
• Meet the intro list. You set the meetings; the buddy can walk them between. Do not assume HR scheduled your cross-functional coffee.
• Shadowing with a purpose. One process, one customer, one report — then a debrief. Endless shadowing with no debrief is occupancy.
• Cadence. The stand-up, the weekly 1:1, the channel they must read. Put the 1:1 on the calendar now, not “when things settle.”
• Access gaps that showed up in real work. Folder permissions, a tool nobody requested in the HR form. Route those to the owner. Dayzen onboarding will not invent a VPN client.

By Friday of week one you should be able to say, in a sentence, what they will try to finish in week two. If you cannot, the first assignment was theatre.

HR’s week-one checklist might still include remaining papers or payroll fields. That is parallel. Do not hold all work until every document is pretty unless policy forbids work without activation. If they are not active, they should not be in systems that require an employee login — that is the hire-to-activate gate, not your preference.

Week one is a bad time to rewrite the job. If the work is not what was offered, that is an employment-record conversation with HR, not a quiet “we’ll see.” This calendar assumes the offer role is the role.

Month one: delivery and feedback, not a silent probation verdict

Month one is early delivery on that first-week trajectory, plus feedback while examples are fresh. It is not confirmation of employment, not a performance-appraisal product, and not Dayzen PMS (PMS in Dayzen is a Project Management System for delivery work — not this topic).

Manager work across the remaining weeks:

• One or two outcomes that can actually complete (a shipped small change, a owned report, a closed set of tickets), with quality comments.
• A weekly 1:1 that includes “what is still confusing” and “what I will decide so you are not blocked.”
• Introduction to the next ring of people (a skip-level or a key customer) if the role needs it — not a random coffee marathon.
• A mid-month check against the first assignment’s done definition. Adjust the work, do not only extend the shadowing.
• A month-end note: what they did, what support they still need, whether the role match still looks true. File it where your team files manager notes. Do not treat a chat “you’re doing fine” as the record if you will later need the examples.

If your organisation uses probation, month one may sit inside that stage. Probation length and confirmation rules are policy and contract, not a nationwide constant on this page, and not an onboarding pipeline column. Do not use this calendar as a hidden legal clock.

Do not quote industry “first-90-day retention” numbers. You do not need them to justify a 1:1. You need the 1:1 because people cannot guess your standards.

What the manager does not own

Work	Owner	Why it is not this calendar
Pre-onboarding form, document gate, activation	HR / onboarding owner	Checklist and hire-to-activate
Laptop, email tenant, MDM	IT (your process)	Not a Dayzen onboarding claim
Payroll structure, first-cycle fields	HR and payroll	Record must be payroll-ready; you do not type CTC from memory
Induction attendance	L&D or facilitator	Session object; you only free the calendar
Creating a second employee ID	Nobody should	Same person, possibly delayed date

You can chase HR if day one is blocked by activation. You cannot replace the gate by adding them to a team chat as a guest and calling it done.

A pasteable skeleton (adapt, do not pad)

Day 1. Meet buddy. Team intro. Tools that must work today. First assignment in writing. End-of-day blocker note.

Days 2–5. Role scope. Intro list. One shadow + debrief. 1:1 booked. Friday: week-two outcome named.

Weeks 2–4. Progress on that outcome. Weekly 1:1. Access nits routed. Mid-month check. Month-end written note.

Remote variant: replace desk walk with a recorded team map and shorter, more frequent calls in week one. Site variant: include the safety or reception step your location actually uses, without turning this into a nationwide legal briefing.

If two joiners start the same Monday, still write two first assignments. A shared “read the wiki” is not a plan.

How this sits next to the owners

When HR says onboarding is complete, they may mean activated. Ask if you need to. Your week-one plan can start the same morning. When hire-to-activate shows Filling Details, do not schedule a customer meeting that needs production access. The system stage is a constraint on this calendar; it is not the calendar.

When the checklist still has HR tasks in week two, keep working if they are active. Parallel tracks. Merge them only in a single daily stand-up if you like; do not merge the documents.

A manager timeline is dates and humans. A checklist is HR tasks. A pipeline is system states. Dayzen can assign a welcome SOP and mark a record active. It will not have the first-week conversation for you.

Keep this article as the calendar. Point the checklist at anyone asking for PAN collection steps. Point hire-to-activate at anyone asking for Offer Sent versus Ready to Activate. Stop before you invent outcome percentages or an IT provisioning module that does not exist.