Skip to playbook

HR08·Onboarding Plan

Onboarding Plan & Welcome Comms

Create a role-specific 30-60-90 onboarding plan, welcome communications, and stakeholder briefing for accepted hires.

Before you start

What you’ll need

  • Accepted offer details from the offer and negotiation workflow
  • Access to your organisation’s onboarding policy and checklist templates
  • Onboarding Policy & Checklist
  • Team & Role Context

Who’s involved

  • HR CoordinatorManages the onboarding process, generates welcome communications, and coordinates logistics across departments.
  • Hiring ManagerReviews the onboarding plan for role-specific accuracy and approves milestones before distribution.

Safe use

  • Data HandlingThis workflow processes personal details from accepted offers (start dates, compensation summaries, contact information). Do not paste these inputs into public or unapproved GenAI tools.
  • VerificationGenAI may generate generic milestones or miss role-specific requirements. Verify every onboarding milestone maps to the actual role context and accepted offer terms before distributing to the new hire.

Execution steps

Hybrid

Inputs

  • Confirm the offer has been formally accepted by the candidate
  • Verify the onboarding policy and checklist template are current
  • Confirm the team and role context document includes reporting structure and key tools

Prompt

Generate phased 30-60-90 day onboarding plan

CONTEXT
You will be provided with the following source documents:
1. Accepted Offer Details
2. Onboarding Policy & Checklist
3. Team & Role Context

TASK
Generate a Draft 30-60-90 Onboarding Plan that organises milestones into three phases: Days 1–30 (orientation and foundation), Days 31–60 (skill-building and integration), and Days 61–90 (contribution and review). For each milestone, assign an owner (HR Coordinator, Hiring Manager, or New Hire) and a target completion week.

OUTPUT FORMAT
Use three markdown sections (## Days 1–30, ## Days 31–60, ## Days 61–90). Under each section, use a markdown table with columns: Milestone, Owner, Target Week, Success Indicator. Include five to seven milestones per phase.

EXAMPLE
## Days 1–30: Orientation & Foundation
| Milestone | Owner | Target Week | Success Indicator |
|---|---|---|---|
| Complete IT setup and access provisioning | HR Coordinator | Week 1 | New hire has all system access confirmed |
| Attend team introduction and role walkthrough | Hiring Manager | Week 1 | New hire can describe team structure and key contacts |

CONSTRAINTS
Do not invent role requirements beyond what the preparation pack contains. Do not include specific compensation details or personal information in the plan. Only reference milestones achievable within the stated role context.

Outputs

  • Draft 30-60-90 Onboarding Plan

Verification: Verify the AI did not generate milestones unrelated to the role context or create unrealistic timelines.

GenAI

Inputs

  • Confirm the Draft 30-60-90 Onboarding Plan covers all three phases

Prompt

Draft welcome email and first-week communications

CONTEXT
You will be provided with the Accepted Offer Details, Onboarding Policy & Checklist, Team & Role Context and the Draft 30-60-90 Onboarding Plan for a new hire.

TASK
Draft three welcome communications: (1) a formal welcome email from HR confirming start date, first-day logistics, and key contacts, (2) a hiring manager welcome note introducing the team and first-week expectations, and (3) a first-week schedule summary with orientation sessions and check-in points. Produce these as Draft Welcome Communications.

OUTPUT FORMAT
Use three markdown sections:
- **## HR Welcome Email**: Subject line followed by email body with greeting, logistics paragraph, key contacts list, and sign-off.
- **## Hiring Manager Welcome Note**: Informal tone, two to three paragraphs covering team introduction, first-week focus, and open-door invitation.
- **## First-Week Schedule**: A markdown table with columns: Day, Time Block, Activity, Contact Person.

CONSTRAINTS
Do not include specific salary figures or confidential offer terms in any communication. Do not use generic platitudes — each message must reference concrete details from the preparation pack. Do not assume specific tools or systems beyond what the role context provides.

Outputs

  • Draft Welcome Communications

Verification: Verify welcome messages do not contain confidential offer terms or hallucinated logistics details.

Hybrid

Inputs

  • Draft 30-60-90 Onboarding Plan

Prompt

Refine onboarding milestones with manager feedback

CONTEXT
You will be provided with the Draft 30-60-90 Onboarding Plan and specific feedback from the hiring manager on which milestones to adjust, reorder, or replace.

TASK
Refine the onboarding plan based on the provided feedback to produce a Revised 30-60-90 Onboarding Plan. Preserve the three-phase structure and ensure every milestone has a clear owner and success indicator.

OUTPUT FORMAT
Return the plan using the same three-phase markdown structure (Days 1–30, Days 31–60, Days 61–90) with milestone tables. Append a change log listing each adjustment made from the draft.

CONSTRAINTS
Do not remove milestones required by organisational onboarding policy unless the feedback explicitly overrides them. Do not add milestones unrelated to the role context.

Outputs

  • Revised 30-60-90 Onboarding Plan
  • Confirm every phase retains five to seven actionable milestones
  • Verify each milestone has a designated owner and measurable success indicator
GenAI

Inputs

  • Revised 30-60-90 Onboarding Plan
  • Draft Welcome Communications
  • Confirm the Revised 30-60-90 Onboarding Plan is approved by the hiring manager

Prompt

Create stakeholder onboarding responsibility briefing

CONTEXT
You will be provided with the Revised 30-60-90 Onboarding Plan and the Draft Welcome Communications for a new hire.

TASK
Generate a Stakeholder Onboarding Briefing that summarises each stakeholder’s responsibilities, key dates, and action items across the 90-day onboarding period. This briefing helps managers, HR, and support teams understand their specific contributions.

OUTPUT FORMAT
Use the following markdown sections:
- **## Onboarding Overview**: Two to three sentences summarising the role, start date context, and onboarding approach.
- **## Responsibility Matrix**: A markdown table with columns: Stakeholder, Phase, Key Actions, Deadline.
- **## Critical Checkpoints**: A numbered list of three to five decision points where stakeholders must confirm progress before the next phase.

CONSTRAINTS
Do not include confidential personal details about the new hire. Do not create responsibilities that contradict the approved onboarding plan. Only reference stakeholder roles already identified in the source documents.

Outputs

  • Stakeholder Onboarding Briefing

Verification: Verify the briefing does not assign responsibilities to roles not present in the onboarding plan.

Hybrid

Inputs

  • Revised 30-60-90 Onboarding Plan
  • Draft Welcome Communications
  • Stakeholder Onboarding Briefing

Prompt

Compile final onboarding package for distribution

CONTEXT
You will be provided with the Revised 30-60-90 Onboarding Plan, Draft Welcome Communications, and Stakeholder Onboarding Briefing.

TASK
Compile these documents into two final deliverables: (1) the 30-60-90 Onboarding Plan combining the revised milestone plan with the stakeholder briefing, and (2) the Welcome Communications Package containing all three welcome messages ready for sending. Ensure consistent formatting and remove any duplications.

OUTPUT FORMAT
Return two clearly separated markdown documents. The first uses sections: 'Onboarding Overview', 'Phase Milestones', 'Stakeholder Responsibilities', 'Critical Checkpoints'. The second uses sections: 'HR Welcome Email', 'Hiring Manager Welcome Note', 'First-Week Schedule'.

CONSTRAINTS
Do not alter approved milestones or stakeholder assignments without explicit reviewer instruction. Do not add content beyond what exists in the source documents.

Outputs

  • Confirm the 30-60-90 Onboarding Plan includes all approved milestones and the stakeholder responsibility matrix
  • Verify welcome communications contain no confidential offer terms or hallucinated details
  • Confirm all documents use consistent formatting and terminology

Verification: Verify the compiled package contains all approved milestones and stakeholder assignments with no omissions.

Reference

Guardrails

  • Role-Anchored MilestonesEvery onboarding milestone must link to the specific role context and accepted offer details — reject generic milestones that do not reflect the actual position.
  • Confidentiality BoundaryKeep compensation figures, personal contact details, and negotiation terms out of onboarding plans and welcome communications generated through AI.
  • Policy Compliance CheckCross-reference every AI-generated milestone against the organisation’s onboarding policy to ensure mandatory compliance steps are not omitted.

Pitfalls

  • Accepting AI-generated milestones without verifying each one maps to the actual role context and offer details.
  • Including confidential salary or negotiation details in welcome communications when pasting offer context into the prompt.
  • Using the AI-generated onboarding plan without cross-checking mandatory policy requirements from the organisation’s checklist.
  • Distributing welcome communications before the hiring manager has reviewed and approved the onboarding milestones.

Definition of Done

  • The 30-60-90 Onboarding Plan contains phased milestones for all three periods with owners and success indicators for each.
  • The Welcome Communications Package includes an HR welcome email, hiring manager note, and first-week schedule with no confidential terms.
  • The Stakeholder Onboarding Briefing maps every key action to a responsible stakeholder and deadline.
  • All milestones in the final plan align with the organisation’s onboarding policy and the accepted offer details.

GET FULL ACCESS

Unlock every step, prompt, and downloadable example — for this playbook and the rest of AGASI AiOS, our GenAI capability framework.

We'll send a magic link — no password needed.

AGASI AiOS · HR08 v1.0 · Apr 7, 2026