These prompts help HR Managers write complete onboarding plans, welcome communications, and training schedules without starting from scratch. Each prompt produces a finished document you can customize and send within minutes.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
First Day Welcome Communications
You are writing a welcome email for a new hire’s first day at work.
New hire: {employee_name} Role: {job_title} Department: {department_name} Start date: {start_date} Manager: {manager_name} First day schedule: {morning_activity}, {afternoon_activity} Company culture note: {one_thing_that_makes_company_special} Dress code: {casual / business_casual / formal}
Write a 250 to 350 word welcome email that covers arrival time, parking instructions, what to bring, and sets an encouraging tone. Include one specific detail about their role that shows you’re prepared for their arrival. End with your direct contact information and an invitation to reach out with questions.
When to use it: Sunday evening before a Monday start, or the day before any new hire begins.
Pro tip: Reference something specific from their interview to make the welcome feel personal, not templated.
You are creating talking points for a new hire’s first-day introduction to their immediate team.
New hire: {employee_name} Background: {previous_company_or_experience} Role: {job_title} Team size: {number_of_people} Team’s current priority: {main_project_or_focus} New hire’s main responsibility: {primary_job_function} Fun fact about new hire: {hobby_or_interest}
Write a 150 to 200 word introduction script the manager can use when presenting the new hire to their team. Include their background, what they’ll be working on, and one personal detail. Structure it as natural talking points, not a formal speech.
When to use it: 10 minutes before walking into the team meeting or Slack introduction.
Pro tip: Practice the introduction out loud once – reading it cold makes it sound robotic.
You are writing a first-day schedule for a remote new hire.
New hire: {employee_name} Role: {job_title} Time zone: {new_hire_timezone} Manager: {manager_name} Key stakeholders to meet: {person_1}, {person_2}, {person_3} Main tools they’ll use: {primary_software_or_platform} Department: {department_name}
Create a detailed 6-hour first-day schedule with specific times, meeting purposes, and 15-minute buffer periods. Include tech setup, introductions, and one hands-on task. Format as a clear timeline they can follow independently.
When to use it: When onboarding remote employees who need more structure than in-person hires.
Pro tip: Schedule their first real work task for day two – day one is overwhelming enough without pressure to produce.
You are drafting a new hire announcement for the company-wide Slack channel.
New hire: {employee_name} Role: {job_title} Department: {department_name} Start date: {start_date} Background: {previous_role_or_company} What they’ll work on: {main_responsibility} Personal detail: {hobby_interest_or_fun_fact}
Write a 100 to 150 word announcement that introduces them to the broader company. Include their background, what they’ll be doing, and one personal detail that gives colleagues a conversation starter. Keep the tone welcoming but professional.
When to use it: First day morning, before the new hire sees other company communications.
Pro tip: Post this early in their first day so colleagues can welcome them throughout the week, not just on day one.
You are creating a new hire’s first-week goal sheet.
New hire: {employee_name} Role: {job_title} Manager: {manager_name} Department priorities: {main_team_focus} First project: {initial_assignment} Key relationships to build: {person_1}, {person_2}, {person_3} Learning priority: {skill_or_system_to_master}
Write 5 to 7 specific, measurable goals they should complete in their first week. Include relationship-building, system access, and one small deliverable. Format as clear action items with success criteria. Keep goals achievable to build early confidence.
When to use it: End of first day, as a roadmap for the rest of their first week.
Pro tip: Make one goal about teaching them something small – learning by explaining helps retention.
Department-Specific Training Plans
You are writing an onboarding plan for a new sales team member.
New hire: {employee_name} Sales territory: {geographic_or_account_region} Quota start date: {when_they_begin_selling} CRM system: {salesforce_hubspot_or_other} Main product lines: {product_1}, {product_2}, {product_3} Sales manager: {manager_name} Top competitor: {main_competitor_name}
Create a 3-week training plan with specific daily activities. Week 1: product knowledge and CRM setup. Week 2: shadowing calls and competitor analysis. Week 3: first solo prospects with support. Include measurable checkpoints and who delivers each training component. Format as a detailed schedule with accountability measures.
When to use it: Week before a sales hire starts, so you can coordinate with product teams and senior reps.
Pro tip: Have them lose a practice pitch badly in week 2 – failing safely builds resilience for real rejections.
You are creating an onboarding plan for a new customer service representative.
New hire: {employee_name} Support channels they’ll handle: {phone_email_chat_or_combination} Ticket system: {zendesk_freshdesk_or_other} Product complexity level: {simple_moderate_or_complex} Team size: {number_of_support_agents} Supervisor: {supervisor_name} Common issue types: {issue_1}, {issue_2}, {issue_3}
Write a 2-week training plan that moves from observation to full independence. Include specific hours of shadowing, practice scenarios, and gradual responsibility increase. End with success metrics for their first month. Format as daily schedules with clear progression markers.
When to use it: When hiring customer service reps who need confidence before handling real customer issues.
Pro tip: Record their practice calls for review – hearing themselves builds awareness faster than feedback alone.
You are writing an engineering onboarding plan for a mid-level developer.
New hire: {employee_name} Programming languages: {primary_language}, {secondary_language} Development environment: {tech_stack_or_framework} First project: {initial_assignment} Code review partner: {senior_developer_name} Repository access level: {read_write_or_admin} Team methodology: {agile_scrum_or_other}
Create a technical onboarding plan covering development setup, codebase exploration, and first meaningful contribution. Include specific repositories to review, coding standards documentation, and a starter bug or feature. Structure as milestones over 10 business days with technical checkpoints.
When to use it: Before technical hires start, so you can prepare development environment access and assign a code buddy.
Pro tip: Give them a real bug to fix in week 2, not a practice exercise – solving actual problems builds investment.
You are creating an onboarding plan for a new marketing coordinator.
New hire: {employee_name} Marketing channels they’ll support: {social_email_content_or_paid} Brand voice: {professional_casual_or_specific_tone} Marketing manager: {manager_name} Current campaigns: {campaign_1}, {campaign_2} Content calendar tool: {asana_monday_or_other} Target audience: {customer_demographic_or_segment}
Write a 2-week onboarding plan that covers brand guidelines, campaign analysis, and content creation practice. Include reviews of past successful campaigns, competitor research, and one small content piece to create. Format with specific deliverables and review points.
When to use it: When onboarding marketing team members who need to understand brand voice before creating content.
Pro tip: Have them audit a competitor’s campaign in week 1 – external analysis is easier than internal critique for new hires.
You are writing an onboarding plan for a new finance team member.
New hire: {employee_name} Role focus: {accounts_payable_financial_analysis_or_budgeting} Accounting software: {quickbooks_sap_or_other} Reporting manager: {manager_name} Month-end responsibilities: {specific_tasks_or_reports} Compliance requirements: {sox_gaap_or_other} Key stakeholders: {department_1}, {department_2}
Create a detailed onboarding plan covering system access, process documentation, and gradual responsibility assumption. Include specific financial processes to observe, practice transactions, and first independent task. Structure over 3 weeks with increasing complexity and oversight reduction.
When to use it: Before finance hires start, ensuring proper system access and compliance training coordination.
Pro tip: Start them on prior month’s data for practice – live month-end closes are too high-pressure for learning.
Manager Relationship Building
You are writing a new hire’s first one-on-one agenda with their direct manager.
New hire: {employee_name} Manager: {manager_name} Role: {job_title} Days since start date: {number_of_days} Initial observations: {what_seems_to_be_going_well} Potential concerns: {any_early_challenges_noticed} Communication preference: {in_person_video_call_or_phone}
Create a 45-minute one-on-one agenda focused on relationship building and early feedback. Include questions about their experience so far, clarification on role expectations, and goal-setting for the next 30 days. Structure with specific time allocations and conversation starters that encourage honest dialogue.
When to use it: End of first week, to catch issues early before they become problems.
Pro tip: Ask “What’s one thing that surprised you so far?” – their answer reveals gaps between expectation and reality.
You are creating a 30-day check-in script for a new hire’s manager.
New hire: {employee_name} Role: {job_title} Initial goals set: {goal_1}, {goal_2}, {goal_3} Manager observations: {what_is_working_well} Areas for development: {skills_or_behaviors_to_improve} Team integration level: {how_well_fitting_with_colleagues} Workload assessment: {overwhelmed_appropriate_or_light}
Write a structured conversation guide for a 30-day performance check-in. Include specific questions about goal progress, challenges faced, and support needed. Balance praise with constructive feedback and end with adjusted goals for the next 30 days. Format as talking points with suggested phrasing for difficult conversations.
When to use it: Day 28-30, to formally assess early performance and make course corrections.
Pro tip: Start with what they’ve done well – new hires are already anxious about performance feedback.
You are writing a new hire feedback request email to their temporary buddy or mentor.
Buddy/Mentor: {mentor_name} New hire: {employee_name} Mentoring duration: {number_of_weeks} New hire’s role: {job_title} Key areas to assess: {technical_skills}, {cultural_fit}, {communication_style} Feedback deadline: {specific_date} Manager requesting: {your_name}
Write a 200 to 300 word email requesting structured feedback from their assigned buddy or mentor. Include specific questions about integration, skill demonstration, and any concerns. Make it easy to respond with clear categories and space for both positive observations and improvement areas.
When to use it: Week 3-4 of onboarding, when patterns are clear but adjustment is still possible.
Pro tip: Ask for examples, not just ratings – “communicates well” is useless, “explains complex ideas clearly” is actionable.
You are creating a skip-level meeting agenda for a new hire with their manager’s manager.
New hire: {employee_name} Role: {job_title} Direct manager: {manager_name} Skip-level manager: {senior_manager_name} Time with company: {weeks_or_months} Department: {department_name} Recent project: {current_assignment_or_responsibility}
Write a 30-minute skip-level meeting agenda that builds relationships without undermining the direct manager. Include questions about company vision alignment, career development interests, and high-level feedback on their experience. Structure to encourage strategic thinking while respecting reporting relationships.
When to use it: Month 2-3, once they’re settled but still forming impressions about leadership and direction.
Pro tip: Share the agenda with their direct manager first – skip levels should support, not surprise, the reporting relationship.
You are writing role expectation clarification talking points for a struggling new hire.
New hire: {employee_name} Role: {job_title} Specific performance gaps: {area_1}, {area_2} Time in role: {weeks_or_months} Manager: {your_name} Support offered so far: {training_mentoring_or_resources} Improvement timeline: {realistic_timeframe_for_progress}
Create a supportive but clear conversation outline addressing performance concerns. Include specific examples, clear expectations moving forward, and concrete support offerings. Balance accountability with encouragement and end with mutual agreement on success measures. Structure as a coaching conversation, not disciplinary action.
When to use it: When a new hire isn’t meeting expectations but you believe in their potential with clearer guidance.
Pro tip: Document this conversation immediately after – improvement plans need specific starting points and measurable progress markers.
System and Process Training
You are writing a technology setup checklist for a new remote employee.
New hire: {employee_name} Role: {job_title} Primary tools: {software_1}, {software_2}, {software_3} Hardware provided: {laptop_monitor_or_other} IT contact: {it_support_person} Security requirements: {vpn_two_factor_or_other} First day tech needs: {what_must_work_immediately}
Create a detailed technology setup guide with step-by-step instructions, troubleshooting contacts, and success verification steps. Include security protocol setup, essential software installation, and communication tool configuration. Format as a checklist they can complete independently with clear success criteria for each step.
When to use it: 2-3 days before a remote hire starts, giving time to resolve issues before their first day.
Pro tip: Test their setup with a brief video call the day before they start – technical problems on day one kill momentum.
You are creating a process documentation overview for a new operations team member.
New hire: {employee_name} Department processes: {process_1}, {process_2}, {process_3} Documentation location: {confluence_sharepoint_or_other} Process owner contacts: {person_1}, {person_2}, {person_3} Critical deadlines: {daily_weekly_or_monthly_requirements} Error escalation path: {