Create a practical onboarding plan for a new employee using the company policy and role details below. Make it fair and consistent: distinguish requirements from optional culture-building activities, do not assume personal circumstances, and do not add policies, legal obligations, benefits, or security permissions that I have not provided. ROLE AND START DATE: [ROLE AND START DATE] COMPANY AND TEAM CONTEXT: [COMPANY AND TEAM CONTEXT] POLICIES AND REQUIRED TRAINING: [POLICIES AND REQUIRED TRAINING] ROLE EXPECTATIONS: [ROLE EXPECTATIONS] SYSTEMS, ACCESS, AND OWNERS: [SYSTEMS ACCESS AND OWNERS] WORK ARRANGEMENT AND CONSTRAINTS: [WORK ARRANGEMENT AND CONSTRAINTS] Build a 30-day plan with a preboarding checklist, first-day schedule, first-week plan, and weeks 2–4 milestones. Assign a clear owner and due date or timing to every task. Cover employment paperwork only at the level stated in my policies; equipment and account setup; security and privacy training; team introductions; role-specific learning; an early, bounded work assignment; and check-ins with the manager.
For role expectations, define observable outcomes rather than vague traits. Include what “good” looks like by day 30, the evidence the manager should use, and what support the employee can request. Make remote, hybrid, accessibility, timezone, and scheduling needs neutral and practical rather than assumptions about the person. Produce this exact output: 1. A preboarding checklist table. 2. A day-one schedule. 3. A week-by-week plan for days 2–30. 4. A manager check-in agenda for days 7 and 30. 5. A short risks and gaps list where policy, access, ownership, or compliance information is missing. Before answering, self-check that no task lacks an owner, no policy is invented, and required training comes before systems or work that depend on it. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ROLE AND START DATE] | State the job title, department, manager, start date, and employment type if relevant. | Customer Support Specialist, Customer Experience; manager Priya Shah; starts October 5; full-time employee. |
| [COMPANY AND TEAM CONTEXT] | Describe the company, team mission, team size, and key working relationships. | A 45-person payroll software company; the six-person support team handles chat and email and works with Product and Implementation. |
| [POLICIES AND REQUIRED TRAINING] | Paste the approved policies, required training, and compliance deadlines that apply. | Complete security awareness training before production-tool access; review employee handbook in week one; no handling customer payroll data until approved by Support Operations. |
| [ROLE EXPECTATIONS] | List the core responsibilities, first-month priorities, and how performance is evaluated. | Learn ticket taxonomy, resolve simple billing questions with review, and write accurate internal notes; quality is measured by rubric score and correct escalation. |
| [SYSTEMS ACCESS AND OWNERS] | List required tools, access approvers, equipment needs, and who owns each setup task. | Laptop: IT; Okta: IT; Zendesk sandbox: Support Operations; Slack: manager; knowledge base: Support Operations. |
| [WORK ARRANGEMENT AND CONSTRAINTS] | State remote, hybrid, onsite, timezone, scheduling, accessibility, or location requirements already known. | Remote in Eastern Time; core collaboration hours are 10 a.m.–3 p.m. ET; captioned training videos are available on request. |
How to use
- Paste only approved policies and required training, then identify the access owner for every system.
- Define a realistic early assignment that is safe to review and useful to the team.
- Have the manager confirm timing, ownership, and access dependencies before sharing the plan.
- Follow up with: “Turn the day-30 outcomes into a fair manager rubric with observable evidence and no personality-based criteria.”
Variations
First-day agenda
Use this when you need a welcoming, organized schedule for the employee’s first day.
Create a first-day onboarding agenda for this employee. ROLE: [ROLE] WORK ARRANGEMENT: [WORK ARRANGEMENT] REQUIRED DAY-ONE ITEMS: [REQUIRED ITEMS] PEOPLE TO MEET: [PEOPLE TO MEET] ACCESS STATUS: [ACCESS STATUS] Build a timed agenda with purpose, owner, location or video link placeholder, and preparation needed for each item. Balance required setup, policy training, team context, and breaks; do not overload the day with presentations. Mark dependent tasks that cannot occur until access is approved. Include a manager close-out check-in and a short employee feedback question. Do not invent benefits, policies, or meetings. Ask up to 3 questions only if essential information is absent.
Manager checklist
Use this when managers need a repeatable set of onboarding responsibilities.
Create a manager checklist for the first 30 days of this role. ROLE: [ROLE] TEAM CONTEXT: [TEAM CONTEXT] POLICY REQUIREMENTS: [POLICY REQUIREMENTS] FIRST-MONTH OUTCOMES: [FIRST-MONTH OUTCOMES] Return a checklist grouped into before start, day one, week one, and weeks 2–4. Each item needs an owner, timing, and evidence of completion. Include access escalation, expectation-setting, useful feedback, workload pacing, and two-way check-ins. Separate mandatory policy items from recommended management practices. Do not create HR requirements or assume the employee’s personal needs. Flag missing approvers or policies. Ask up to 3 questions only if required.
Ninety-day plan
Use this when the role needs a longer ramp with measurable milestones.
Build a 30-60-90 day onboarding and ramp plan for this employee. ROLE: [ROLE] KEY RESPONSIBILITIES: [KEY RESPONSIBILITIES] TEAM GOALS: [TEAM GOALS] TRAINING AND ACCESS: [TRAINING AND ACCESS] MEASUREMENT METHOD: [MEASUREMENT METHOD] For each period, define learning goals, outputs, support, owner, and observable success evidence. Sequence training before independent work and distinguish supervised practice from production responsibility. Include manager check-in questions and risks that could delay ramping. Avoid personality judgments and do not invent targets, policy obligations, or permissions. End with a concise employee-facing version and a manager-facing tracking table. Ask up to 3 questions only if essential details are missing.
Tips
- Make access approval a dependency, not a calendar event; an employee cannot complete production work until the right permission and training are in place.
- Use an early assignment with a reviewer and a clear definition of done, such as triaging five sandbox tickets against a rubric.
- Separate required policies from local team customs so employees know which expectations are mandatory.
- Evaluate early progress using work artifacts, completed training, and demonstrated procedures rather than confidence or cultural similarity.
FAQ
How long should new employee onboarding last?
Administrative setup may take days, but role ramping commonly needs at least 30 days and often 60–90 days. Match milestones to the complexity and risk of the role.
Can AI create our HR policy?
It can organize approved policy into a plan, but it should not invent employment, benefits, privacy, or compliance requirements. Use HR or legal review for policy changes.
What should a manager cover in the first check-in?
Confirm access, workload, expectations, questions, and any blockers. Ask what was clear, what was surprising, and what support would make the next week more productive.