Create a structured onboarding plan for a new employee that is practical, fair, and consistent with the policies and facts I provide. Role and employee context: [ROLE AND CONTEXT] Team, manager, and key partners: [TEAM AND STAKEHOLDERS] First-90-day outcomes: [OUTCOMES] Company policies and required training: [POLICIES AND REQUIREMENTS] Work setup and constraints: [WORK SETUP AND CONSTRAINTS]
Start by separating mandatory requirements from role-specific learning and relationship-building. Identify what must be completed before the employee receives system access, handles customer or employee data, makes decisions independently, or performs regulated or safety-sensitive work. Do not invent company policy, legal requirements, access permissions, or training content; list missing items as items for HR, IT, security, legal, or the manager to confirm. Produce a 30-60-90-day onboarding plan in a table with these columns: time period, intended outcome, activities and learning, owner, employee deliverable or evidence, check-in, and dependency. Include day one, week one, weeks two through four, days 31 through 60, and days 61 through 90. Design the plan around progressive responsibility: orientation and access; role context and shadowing; supervised work; independently owned work with review. Include manager one-on-ones, introductions with a stated purpose, a written expectations conversation, an early feedback loop, and a reasonable accommodation or accessibility checkpoint without requesting unnecessary personal information. Then provide a manager checklist, employee checklist, and first-week agenda. Define objective milestone evidence rather than vague expectations such as “fit in” or “be proactive.” Ask up to 3 clarifying questions only if a required input is missing. Before answering, check that every task has an owner and that no required access or training is assumed complete. Flag uneven treatment, ambiguous performance expectations, or policy gaps for a human HR or compliance review.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ROLE AND CONTEXT] | Enter the job title, level, location, employment type, start date, and relevant prior experience. | Customer Success Manager, mid-level, remote in Colorado, full time, starts October 14; has three years of SaaS account-management experience. |
| [TEAM AND STAKEHOLDERS] | Enter the manager, team structure, key partners, and people the new employee needs to work with. | Reports to Director of Customer Success; partners with implementation, support, sales, and product; manages a book of 45 SMB accounts. |
| [OUTCOMES] | Enter the role's expected 30-, 60-, and 90-day outcomes or core responsibilities. | By day 30 understand portfolio and tools; by day 60 run supervised account reviews; by day 90 own renewal-risk plans for assigned accounts. |
| [POLICIES AND REQUIREMENTS] | Enter required company training, security, HR, compliance, equipment, and access policies. | Complete HR orientation, security awareness, privacy training, CRM access approval, and customer-data handling training before accessing account records. |
| [WORK SETUP AND CONSTRAINTS] | Enter remote, hybrid, or onsite arrangements, working hours, equipment status, travel, and known operational constraints. | Remote, core hours 10 am to 4 pm Mountain Time; laptop arrives two days before start; no travel in first month. |
How to use
- Paste only confirmed role information and link or summarize the policies that govern access and training.
- Have HR, IT, security, and the manager fill in missing owners before sharing the plan.
- Check that milestones describe evidence of work, not personality traits or assumptions about culture fit.
- Send: “Convert this into a first-week calendar with meeting purpose, owner, preparation, and expected outcome for each session.”
Variations
Remote onboarding
Use this when the employee will start remotely or work across time zones.
Create a remote onboarding plan for [ROLE] starting on [START DATE] in [TIME ZONE]. The manager and team work in [TEAM TIME ZONES], and required systems or training are [REQUIREMENTS]. Build a first-two-week schedule that balances live orientation, asynchronous materials, role practice, and relationship-building without filling every hour with meetings. Include equipment and access dependencies, meeting purpose, written documentation norms, and feedback checkpoints. Flag any policy or accessibility details that require HR, IT, or security confirmation.
Manager transition
Use this for a new manager joining an established team.
Build a 90-day onboarding plan for a new [MANAGER ROLE] inheriting [TEAM DESCRIPTION]. Known business priorities are [PRIORITIES], and existing team concerns are [CONTEXT]. Sequence listening, operational learning, relationship mapping, and decision-making so the manager does not promise changes before understanding constraints. Include team meetings, one-on-one question themes, metrics to learn, decision rights to confirm, and milestones with evidence. Do not infer performance problems or prescribe personnel action without verified facts and appropriate HR guidance.
Compliance-heavy role
Use this for a role with regulated data, financial controls, safety procedures, or mandatory certifications.
Draft an onboarding framework for [ROLE] in a [REGULATED OR SAFETY CONTEXT] environment. Required policies, certifications, and approvals are [REQUIREMENTS], and the employee may begin independent work only after [CLEARANCE STANDARD]. Create a dependency-based checklist for access, training, supervised practice, documentation, and sign-off. Separate confirmed requirements from items to verify with compliance or counsel. Do not provide legal, medical, safety, or regulatory clearance; state where a qualified reviewer must approve the plan.
Tips
- Assign an owner and evidence of completion to every task; “meet the product team” is weaker than “attend a product overview and summarize the two workflows affecting the role.”
- Grant systems access in stages when the role handles sensitive information, and record the approver rather than assuming a manager can authorize every tool.
- Use the same core milestones for comparable roles, while adjusting learning support and schedules for the actual job context and approved accommodations.
- Schedule a two-way check-in during the first two weeks; it catches missing equipment, unclear expectations, and onboarding gaps while they are still easy to fix.
FAQ
How detailed should an onboarding plan be?
The first two weeks should be specific enough to show owners, timing, and dependencies. Later milestones can be outcome-based, provided the manager defines the evidence and check-ins.
Can AI create a compliant onboarding plan?
It can organize confirmed requirements and expose gaps, but HR, legal, security, or safety owners must validate policies and regulated responsibilities.
What makes an onboarding milestone fair?
It uses observable work, training completion, or demonstrated role knowledge. Avoid personality-based criteria and make expectations available to the employee in writing.