Onboarding Checklist Creator (30-60-90 Day Success)
This prompt creates a role-aware onboarding plan with concrete milestones for the first 30, 60, and 90 days. It goes beyond paperwork by combining logistics, learning, relationship-building, and early wins so a new hire is not just informed, but actually becoming productive. It is especially useful when managers need a repeatable onboarding structure that still feels personalized by role, seniority, and work mode.
GPT / Claude / Gemini4 variables
Prompt
Create an onboarding plan for {ROLE}.
Input:
- Role: {ROLE}
- Department: {DEPARTMENT}
- Seniority: {LEVEL} (entry/mid/senior/leadership)
- Work mode: {MODE} (remote/hybrid/in-office)
Rules:
- Phase activities by 30-60-90 days
- Balance tasks, learning, and relationships
- Include early wins for confidence
- Set clear success criteria for each phase
- Customize for role and seniority
Output format:
PRE-START (Manager prep)
- [Setup task 1]
- [Setup task 2]
- [Equipment/access needed]
DAY 1 AGENDA
9:00 AM - [Welcome and orientation]
10:00 AM - [IT setup]
11:00 AM - [Team introduction]
Lunch - [Buddy/team lunch]
Afternoon - [Key tool training]
WEEK 1 PRIORITIES
Must complete:
- [Administrative task]
- [Access/training]
Must meet:
- [Manager 1-on-1]
- [Buddy check-in]
- [Key stakeholder intro]
Should learn:
- [Company mission/values]
- [Team structure and processes]
MONTH 1 (Learning & Absorbing)
Learning objectives:
- [Understand product/service]
- [Learn key systems and tools]
- [Understand team workflows]
Key tasks:
- [Shadowing opportunities]
- [Training sessions to complete]
- [Documentation to review]
Relationships to build:
- [Cross-functional partners]
- [Mentors or subject matter experts]
Success criteria:
- [Can explain company value prop]
- [Completed required training]
- [Knows who to ask for what]
MONTH 2 (Contributing with Support)
Objectives:
- [First real project/responsibility]
- [Start contributing to team goals]
Key tasks:
- [Specific deliverable 1]
- [Specific deliverable 2]
- [Process participation]
Success criteria:
- [Completes first project with feedback]
- [Participates actively in team meetings]
- [Asks questions and seeks help appropriately]
MONTH 3 (Independent Contribution)
Objectives:
- [Own area of responsibility]
- [Work with minimal oversight on routine tasks]
Key tasks:
- [Ongoing responsibility]
- [Independent project]
Success criteria:
- [Meets quality standards independently]
- [Understands how work connects to goals]
- [Proactively identifies issues/opportunities]
CHECK-IN SCHEDULE
- Day 1 end of day: Quick pulse check
- End of week 1: First week reflection
- End of week 2: Early feedback session
- Day 30: Month 1 review
- Day 60: Month 2 review
- Day 90: Performance review and goal setting
Role: {ROLE}
Department: {DEPARTMENT}
Level: {LEVEL}Quick brief
Purpose
Design onboarding experiences that get new hires productive and engaged quickly.
Expected output
A strong output includes: pre-start preparation for the manager and IT, a realistic day-one agenda, week-one must-do items, learning goals for month one, contribution expectations for month two, ownership targets for month three, key people to meet, and a check-in rhythm that keeps the plan alive.
Customize before copying
Replace these placeholders with your own context before you run the prompt.
{ROLE}{DEPARTMENT}{LEVEL}{MODE}
Works well with
GPT
Claude
Gemini
Variations
Add remote-specific connection activities.
Include technical skills assessment checkpoints.
Make it manager-specific (leadership onboarding).
Add cultural immersion activities for company values.
Create separate manager-owned and new-hire-owned checklists.
Add a 14-day fast-start version for startup environments.
What this prompt helps you do
This prompt creates a role-aware onboarding plan with concrete milestones for the first 30, 60, and 90 days. It goes beyond paperwork by combining logistics, learning, relationship-building, and early wins so a new hire is not just informed, but actually becoming productive. It is especially useful when managers need a repeatable onboarding structure that still feels personalized by role, seniority, and work mode.
When to use it
Use this when hiring a new employee, bringing on a long-term contractor, onboarding a first-time manager, or moving an internal team member into a new role. It is most valuable when you want every new hire to get a consistent experience without reducing onboarding to a generic checklist.
Decision context
A good onboarding plan has to balance speed and confidence. New hires need enough structure to know what success looks like, but not so much process that the first week becomes administrative overload. This prompt is strongest when you already know the role outcomes, key relationships, and systems a person must learn in order to contribute well.
How it works
The prompt breaks onboarding into phases: pre-start setup, day-one logistics, week-one orientation, month-one learning, month-two supported contribution, and month-three ownership. Each phase covers tasks, learning objectives, stakeholder relationships, and success criteria so the plan feels like a progression instead of a long unordered list.
Best practices
Assign an onboarding buddy in addition to the manager. Give the new hire one early win in the first two weeks. Make success criteria visible so expectations are not implicit. Include cultural and social integration, not just tool setup. Customize by seniority, because leadership onboarding should look different from entry-level onboarding.
Common mistakes
Overloading the first week with compliance tasks. Leaving relationship-building to chance. Defining goals too vaguely for days 30, 60, and 90. Skipping role-specific training pathways. Treating remote onboarding like office onboarding with Zoom pasted on top. Waiting too long to gather feedback from the new hire.
What you should expect back
A strong output includes: pre-start preparation for the manager and IT, a realistic day-one agenda, week-one must-do items, learning goals for month one, contribution expectations for month two, ownership targets for month three, key people to meet, and a check-in rhythm that keeps the plan alive.
Limitations
This prompt cannot replace thoughtful management. It also assumes there is at least some role clarity, documentation, and calendar space for check-ins. If the company has no clear expectations or the manager is unavailable, the output may look organized while the real onboarding experience still feels chaotic.
Model notes
Compatible with all major models. GPT usually produces clear timelines and operational detail. Claude tends to add stronger relationship and communication guidance. Gemini can surface creative learning suggestions. Works best when you provide specific role context, team structure, and work mode.
Real-world applications
People ops teams use this to standardize onboarding without making it robotic. Startup managers use it to shorten time to first meaningful contribution. Remote teams use it to make relationship-building more intentional. Department heads use it when hiring multiple people into similar roles and wanting a consistent baseline.
How to tell if it worked
A good onboarding plan reduces time to productivity, increases role clarity, improves new-hire confidence, and helps people build the right relationships early. Signals that onboarding is working include strong 30-day feedback, faster contribution, lower confusion about priorities, and fewer avoidable early churn problems.
Specific recommendations
Ask the model to write separate manager actions and new-hire actions so accountability is clearer. If the role is remote, explicitly request connection rituals and communication expectations. If the role is senior, ask for stakeholder mapping and decision-rights context in addition to task lists.
Where to go next
Use Meeting Agenda for recurring 1-on-1 check-ins, Training Plan for deeper capability development, and Performance Review Prep when converting the 90-day checkpoint into a formal evaluation conversation.
When to skip this prompt
Skip this approach when the role is extremely short-term, the work is informal by design, or you truly need a one-page orientation instead of a structured 90-day ramp plan.