New Hire First Week Onboarding Plan Builder (YAML)

1role: Thoughtful people manager and onboarding designer for small and mid-sized teams
2task: >
3  Turn my notes about a new team member, their role, and my team into a complete first week
4  onboarding plan as YAML: preparation before day one, a day-by-day schedule, people to meet,
5  access and equipment, learning goals, a small first contribution, check-ins, and a simple
6  way to collect feedback, so the new hire feels welcome and productive without being overloaded.
7
8inputs:
9  new_hire_role: junior customer support specialist
10  start_date_and_hours: Monday 09:00, full time, Monday to Friday
11  work_setup: hybrid, office on Monday and Wednesday, remote the rest of the week
12  team: six people in support, one team lead, works closely with the product team
13  manager_availability: I am in meetings most afternoons, mornings are free
14  tools_and_systems: helpdesk tool, team chat, shared docs, internal knowledge base
15  first_contribution_idea: answer simple tickets with a buddy reviewing replies
16  known_constraints: laptop delivery can take two days, one teammate on holiday
17
18ask_first:
19  - Who can be the onboarding buddy, and how much time they can give each day
20  - Which accounts and permissions take the longest to approve, and who approves them
21  - The two or three things the new hire must understand by the end of week one
22  - Any mandatory trainings (security, privacy, health and safety) and their deadlines
23  - The new hire's preferences if known (accessibility needs, preferred name and pronouns, time zone)
24  - What a good end of the first month looks like for this role
25
26rules:
27  - Spread information across the week; no day should have more than three hours of meetings or trainings.
28  - Every day must include focused time to practice, one human connection, and a short end-of-day check-in.
29  - Put anything with a lead time (laptop, accounts, building access, payroll forms) in a pre_start checklist with an owner and a due date.
30  - Give the first contribution a clear, low-risk scope, a reviewer, and a definition of done.
31  - Never invent names, systems, or policies; if missing, write "MANAGER TO FILL" and list it under missing_info.
32  - Keep language warm and inclusive; avoid jargon or explain it in the glossary.
33  - Do not include passwords or personal data in the plan; say how credentials will be shared securely.
34  - If inputs are missing, use sensible defaults and mark them as assumptions.
35  - Output only valid YAML matching output_format. No prose outside the YAML.
36
37output_format:
38  summary:
39    role: string
40    start: string
41    week_one_goals: [string]
42    assumptions: [string]
43    missing_info: [string]
44  pre_start_checklist:
45    - item: string
46      owner: string
47      due: string
48      done: boolean
49  welcome_message_draft: string
50  days:
51    - day: string
52      location: string
53      theme: string
54      schedule:
55        - time: string
56          activity: string
57          with: string
58          purpose: string
59      focus_time: string
60      end_of_day_check_in: [string]
61  people_to_meet:
62    - name_or_role: string
63      why: string
64      when: string
65      format: string
66  access_and_equipment:
67    - system: string
68      access_level: string
69      requested_by: string
70      ready_by: string
71  learning_plan:
72    - topic: string
73      resource: string
74      time_needed: string
75      check_understanding: string
76  first_contribution:
77    description: string
78    reviewer: string
79    definition_of_done: [string]
80    target_day: string
81  buddy_guide:
82    daily_time: string
83    responsibilities: [string]
84  feedback:
85    end_of_week_questions: [string]
86    manager_reflection: [string]
87  glossary:
88    - term: string
89      meaning: string
90  week_two_preview: [string]