These prompts create finished onboarding emails for every stage of the new hire journey. Copy the prompt, fill in the variables, paste into ChatGPT, and get a polished email ready to send. No templates to customize later—just working emails.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Welcome and First Day Preparation
You are an HR Manager writing a welcome email to a new employee who just accepted their offer.
Employee name: {employee_name} Job title: {job_title} Start date: {start_date} Manager name: {manager_name} Department: {department} Office location: {office_location_or_remote} First day time: {start_time} Parking/building details: {access_instructions}
Write a 250-300 word welcome email with an enthusiastic but professional tone. Include what to expect on day one, where to go, what to bring, and one specific thing about the team they’re joining. End with your direct contact for questions.
When to use it: The moment you get verbal or written acceptance of an offer, before sending formal paperwork.
Pro tip: Include a specific detail about their team or recent company win—it shows you’re thinking of them as part of the group, not just processing paperwork.
You are an HR Manager sending first-day logistics to a remote new hire.
Employee name: {employee_name} Start date: {start_date} Manager name: {manager_name} IT contact: {it_contact_name} Shipping tracking: {equipment_tracking_number} Welcome meeting time: {meeting_time_timezone} Team introduction call: {team_call_details} Company Slack/Teams: {platform_name}
Write a 200-250 word logistics email covering equipment delivery, virtual first-day schedule, and tech setup expectations. Use a helpful, organized tone. Include what happens if equipment doesn’t arrive on time.
When to use it: 2-3 business days before a remote employee’s start date, after equipment has been shipped.
Pro tip: Always include timezone clarifications for remote hires—even if they’re in your timezone, it eliminates one potential source of first-day confusion.
You are an HR Manager writing to a new hire whose start date needs to be delayed.
Employee name: {employee_name} Original start date: {original_date} New start date: {new_date} Reason for delay: {reason: compliance_pending / background_check / internal_restructure / client_project} Delay duration: {days_or_weeks} Impact on salary: {starts_new_date / no_change / partial_compensation} Your contact: {your_phone_and_email}
Write a 150-200 word email explaining the delay. Use an apologetic but confident tone. Acknowledge the inconvenience, explain next steps, and reaffirm their position is secure. End with how they can reach you for concerns.
When to use it: As soon as you know a start date will shift, regardless of the reason—speed matters more than having every detail finalized.
Pro tip: Lead with the new date in the subject line and first sentence. Buried ledes create anxiety and phone calls you don’t need.
You are an HR Manager sending onboarding paperwork instructions to a new hire.
Employee name: {employee_name} Paperwork platform: {platform_name} Login details: {how_they_get_access} Required documents: {i9_items_tax_forms_direct_deposit} Benefits enrollment deadline: {deadline_date} IT security training: {required_yes_no} Background check status: {completed / in_progress / required_documents}
Write a 300-350 word email breaking down what they need to complete before day one vs. what happens during their first week. Use clear, step-by-step language. Include estimated time to complete each section and what happens if they miss deadlines.
When to use it: 1 week before start date, after you’ve confirmed all systems are set up and they have access.
Pro tip: List items in order of importance, not alphabetical order. I-9 verification and tax forms matter more than picking a healthcare plan.
You are an HR Manager writing a pre-boarding email to a new manager-level hire.
Employee name: {employee_name} Job title: {management_position} Team size: {direct_reports_number} Key team members: {two_to_three_names_roles} First week priorities: {immediate_projects} Stakeholder meetings: {key_people_theyll_meet} Department budget: {budget_overview_yes_no} Previous manager context: {transition_promotion_replacement}
Write a 400-450 word strategic onboarding email focused on leadership transition. Cover team dynamics, immediate priorities, and stakeholder relationships. Use a collaborative, strategic tone that positions them for early wins.
When to use it: For manager-level hires, 3-5 days before their start date, after you’ve coordinated with their new team.
Pro tip: Include one specific challenge the team is currently facing—new managers want to add value quickly, and this gives them a concrete place to focus.
Documentation and Compliance
You are an HR Manager explaining benefits enrollment to a new employee who seems overwhelmed.
Employee name: {employee_name} Benefits deadline: {enrollment_deadline} Family status: {single / married / children} Health plan options: {number_of_options} Default option: {what_happens_if_no_selection} Benefits meeting: {scheduled_yes_no} HR contact for questions: {contact_person} Open enrollment period: {next_opportunity_to_change}
Write a 250-300 word email simplifying benefits decisions. Break down the choice into 2-3 key questions they need to answer. Use reassuring, non-technical language. Emphasize they can get help and that most decisions aren’t permanent.
When to use it: When a new hire emails asking for clarification on benefits, or after they’ve logged into the system but haven’t started enrollment.
Pro tip: Most people get stuck on health insurance. Start with “here’s what most people in your situation choose” to give them a decision-making shortcut.
You are an HR Manager following up on incomplete I-9 documentation.
Employee name: {employee_name} Start date: {start_date} Missing documents: {specific_items_needed} Acceptable alternatives: {document_options} Compliance deadline: {legal_deadline} Consequences: {cannot_start_work / must_stop_working} HR office hours: {when_they_can_come_in} Remote verification options: {available_yes_no}
Write a 200-250 word follow-up email that’s firm but helpful. Explain exactly what you need, when you need it, and what happens if deadlines aren’t met. Include specific alternatives and make scheduling easy.
When to use it: 24-48 hours after sending initial I-9 instructions if documents aren’t uploaded or scheduled.
Pro tip: People often think they need originals of everything. Clearly state what can be photocopied vs. what must be original to save everyone time.
You are an HR Manager explaining mandatory training requirements to a new hire who’s asking to skip modules.
Employee name: {employee_name} Training modules: {specific_required_courses} Time requirement: {total_hours} Completion deadline: {specific_date} Compliance reason: {legal / certification / client_requirement} Previous experience: {their_claimed_background} Exemption process: {available_yes_no} Manager awareness: {manager_knows_requirement_yes_no}
Write a 300-350 word email explaining why training can’t be waived. Acknowledge their experience while reinforcing requirements. Use a professional, non-negotiable tone that maintains relationship quality. Offer support for completion but not exemption.
When to use it: When experienced hires push back on training they think is beneath their level or redundant.
Pro tip: Lead with the compliance or client requirement reason—it positions this as a business necessity, not HR bureaucracy.
You are an HR Manager sending a document correction request to a new employee.
Employee name: {employee_name} Document type: {tax_form / direct_deposit / emergency_contact} Specific error: {what_needs_fixing} Correct format: {example_of_proper_completion} System impact: {payroll_delay / compliance_issue / none} Correction deadline: {when_needed_by} How to fix: {system_steps} Your availability: {when_they_can_reach_you}
Write a 150-200 word email requesting document corrections. Use a matter-of-fact, helpful tone. Be specific about what’s wrong and exactly how to fix it. Avoid making the employee feel stupid while ensuring quick resolution.
When to use it: Same day you notice form errors, before they create downstream problems in payroll or compliance systems.
Pro tip: Include a screenshot or specific example when possible. “Format should be 123-45-6789, not 123456789” prevents back-and-forth emails.
You are an HR Manager explaining background check delays to a new hire who’s getting anxious.
Employee name: {employee_name} Background check type: {basic / financial / security_clearance} Expected timeline: {original_timeframe} Current status: {what_phase_its_in} Delay reason: {high_volume / verification_issues / court_records} Start date impact: {no_change / might_delay / will_delay} Employee action needed: {none / provide_additional_info / contact_references} Your next update: {when_youll_follow_up}
Write a 250-300 word status update email that reduces anxiety while being realistic about timelines. Use a calm, informative tone. Explain what’s normal vs. concerning and what they should do while waiting.
When to use it: When background checks are taking longer than the standard timeline you initially communicated.
Pro tip: Be specific about whether delays affect start date. Vague reassurances create more anxiety than honest timeline updates.
Team Integration and Setup
You are an HR Manager introducing a new hire to their immediate team before their first day.
New employee: {employee_name} Job title: {job_title} Background: {brief_previous_experience} Start date: {start_date} Team members: {names_and_roles} Team meeting cadence: {how_often_team_meets} Current team priorities: {major_projects} Team communication style: {formal / casual / mixed}
Write a 200-250 word team introduction email from you to the existing team about the new hire. Use an enthusiastic, professional tone. Include enough background to start conversations but maintain appropriate privacy. End with how the team can help during onboarding.
When to use it: 2-3 days before a new hire’s start date, after confirming the hire is definitely starting on schedule.
Pro tip: Include one professional accomplishment and one personal detail (like “avid rock climber” or “former teacher”) to give team members conversation starters.
You are an HR Manager coordinating a new hire’s first week schedule with their manager.
New employee: {employee_name} Manager: {manager_name} Department: {department} Key stakeholders: {people_they_need_to_meet} Training schedule: {mandatory_sessions} Equipment needs: {laptop_phone_access_cards} Workspace assignment: {desk_location_or_remote_setup} First week goals: {specific_outcomes}
Write a 300-350 word coordination email to the new hire’s manager outlining the first week plan. Use a collaborative, organized tone. Include HR responsibilities vs. manager responsibilities, and specific timing for key activities.
When to use it: 1 week before start date, after you’ve confirmed logistics but before the manager starts planning their own agenda.
Pro tip: Block time in the manager’s calendar for onboarding activities when you send this email. Don’t make them remember to do it later.
You are an HR Manager setting up a buddy system assignment for a new hire.
New employee: {employee_name} Buddy: {buddy_name} Buddy’s role: {job_title} Assignment duration: {weeks_or_months} Buddy responsibilities: {specific_expectations} Meeting frequency: {daily / weekly / as_needed} Topics to cover: {company_culture_practical_tips} Check-in schedule: {when_hr_follows_up}
Write a 250-300 word email to both the new hire and their assigned buddy explaining the partnership. Use an encouraging, clear tone. Set expectations for both parties and provide conversation starters for their first meeting.
When to use it: 1 week before start date, after confirming the buddy is available and willing to participate.
Pro tip: Give the buddy specific talking points for week one. “Show them where the good coffee is” is more actionable than “help them adjust to company culture.”
You are an HR Manager explaining workspace assignments and office logistics to a hybrid new hire.
Employee name: {employee_name} Hybrid schedule: {days_in_office} Assigned desk: {location_or_hoteling} Parking information: {cost_location_alternatives} Building access: {badge_hours_security} Office amenities: {kitchen_gym_other} Remote work expectations: {communication_availability} Equipment for home: {what_they_take_home}
Write a 300-350 word office logistics email covering both in-person and remote work setup. Use a practical, welcoming tone. Include specific locations, costs, and policies. Address common questions about hybrid schedules.
When to use it: 3-5 days before start date, after desk assignments and IT equipment are confirmed.
Pro tip: Include a simple office map or floor plan reference. New people spend too much mental energy on basic navigation their first few weeks.
You are an HR Manager facilitating introductions between a new hire and key stakeholders outside their immediate team.
New employee: {employee_name} Job title: {job_title} Key stakeholders: {names_departments_why_theyll_work_together} Meeting purpose: {project_collaboration / ongoing_relationship / one_time_introduction} Timeline for meetings: {first_week / first_month} Background context: {why_these_relationships_matter} Introduction format: {email_intro / scheduled_meetings / informal}
Write a 250-300 word stakeholder introduction email that facilitates relationship building. Use a diplomatic, professional tone that helps both parties understand the value of connecting. Include suggested meeting topics.
When to use it: End of first week or beginning of second week, after the new hire has settled into basic routines.
Pro tip: Make the introductions mutual—explain to each stakeholder why they should care about building this relationship, not just why the new hire needs to meet them.
Technical Setup and Access
You are an HR Manager coordinating IT setup issues for a new hire whose equipment isn’t working properly.
Employee name: {employee_name} Technical issue: {login_problems / hardware_malfunction / software_missing} IT ticket number: {reference_number} Workaround available: {yes_no_temporary_solution} Impact on productivity: {cant_work / limited_functionality / minor_inconvenience} Expected resolution: {timeline} Alternative equipment: {available_yes_no} IT contact: {direct_person_and_contact}
Write a 200-250 word problem-solving email that acknowledges frustration while coordinating solutions. Use an empathetic, action-oriented tone. Provide clear next steps and maintain confidence in resolution.
When to use it: When new hires report technical problems that prevent them from completing onboarding tasks or starting work.
Pro tip: Offer a direct phone number for urgent IT issues during someone’s first week. Email ping-pong with IT creates unnecessary stress for new hires.
You are an HR Manager explaining system access and security protocols to a new hire.
Employee name: {employee_name} Systems they need: {specific_software_platforms} Security training required: {mandatory_modules} Password requirements: {complexity_change_frequency} VPN setup: {required_yes_no} Multi-factor authentication: {required_systems} Data classification: {confidential_materials_they_handle} Violation consequences: {progressive_discipline_termination}
Write a 350-400 word security orientation email that’s thorough but not overwhelming. Use a serious, clear tone that emphasizes importance without creating paranoia. Include practical examples of good security practices.
When to use it: During first week, after basic IT setup is complete but before granting access to sensitive systems.
Pro tip: Include one real example of a security breach consequence (without naming names) to make the policies feel concrete rather than theoretical.
You are an HR Manager troubleshooting remote access issues for a new hire working from home.
Employee name: {employee_name} Connection problem: {vpn / wifi / software_access} Home internet speed: {sufficient_insufficient_unknown} Troubleshooting attempted: {steps_theyve_tried} Impact on meetings: {missing_calls / audio_issues / cant_access_files} IT remote support: {available_scheduled} Backup location: {office_coworking_other} Timeline pressure: {client_meetings / project_deadlines}
Write a 250-300 word technical support coordination email. Use a patient, solution-focused tone. Escalate appropriately while providing interim solutions. Address both immediate needs and longer-term setup.
When to use it: When remote new hires can’t consistently access company systems during their first week.
Pro tip: Have a backup plan ready—sometimes new hires need to work from the office temporarily while home connectivity issues get resolved.
You are an HR Manager explaining email and communication system setup to a new hire.
Employee name: {employee_name} Email address: {their_new_company_email} Communication platforms: {slack_teams_other} Meeting software: {zoom_teams_webex} Calendar integration: {outlook_google_other} Signature requirements: {format_required_info} Distribution lists: {which_ones_theyre_on} Communication norms: {response_time_availability_hours}
Write a 300-350 word communication setup email that covers tools and culture. Use a friendly, informative tone. Include both technical setup and soft expectations about communication style and response times.
When to use it: Day 1 or 2, after email accounts are active but before they start regular communication with team members.
Pro tip: Include examples of good email signatures and calendar invites. New hires often overthink these small details when they should focus on bigger priorities.
You are an HR Manager helping a new hire resolve persistent login problems across multiple systems.
Employee name: {employee_name} Affected systems: {list_of_platforms} Error messages: {specific_error_text} Password reset attempts: {successful_unsuccessful} Account provisioning status: {active_pending_needs_admin} Business impact: {cant_complete_onboarding / missing_training / work_blocked} Escalation path: {it_director / system_admin} Temporary solutions: {guest_accounts / shared_logins / manual_processes}
Write a 200-250 word escalation coordination email that takes ownership of the problem. Use a confident, problem-solving tone. Coordinate between IT and the new hire while keeping everyone informed of progress.
When to use it: When technical problems persist beyond 24 hours and are preventing a new hire from completing essential onboarding tasks.
Pro tip: Copy the new hire’s manager on escalation emails so they know the delay isn’t the employee’s fault and can adjust expectations accordingly.
Follow-up and Check-ins
You are an HR Manager conducting a one-week check-in with a new hire who seems to be struggling.
Employee name: {employee_name} Specific concerns: {technical_issues / team_fit / workload / confusion_about_role} Manager feedback: {positive / mixed / concerning} Onboarding completion: {behind_schedule / on_track / ahead} Support requested: {additional_training / buddy_system / manager_meeting} Early warning signs: {specific_behaviors_or_comments} Next check-in: {timeline} Escalation threshold: {when_to_involve_manager}
Write a 300-350 word supportive check-in email that addresses concerns directly. Use an encouraging but realistic tone. Offer concrete help while gathering information about potential problems. Balance support with accountability.
When to use it: End of first week when you notice signs that onboarding isn’t going smoothly, before small problems become big ones.
Pro tip: Ask one specific question about their biggest challenge so far. Generic “how are things going” questions don’t surface real problems.
You are an HR Manager following up on completed onboarding tasks and next steps.
Employee name: {employee_name} Completed items: {training_paperwork_meetings} Outstanding tasks: {what_still_needs_done} 30-day goals: {specific_expectations} Performance expectations: {metrics_or_milestones} Regular check-in schedule: {frequency_with_manager} HR availability: {when_they_can_reach_you} Success indicators: {how_to_know_theyre_on_track}
Write a 250-300 word transition email that moves from onboarding to regular employment. Use a confident, forward-looking tone. Summarize what’s been accomplished and set clear expectations for the next phase. Reduce HR check-in frequency appropriately.
When to use it: End of second or third week, when formal onboarding tasks are mostly complete and the employee is transitioning to normal work routines.
Pro tip: This email officially “graduates” them from new hire status. Make it feel like an accomplishment, not just an administrative update.
You are an HR Manager addressing onboarding feedback from a new hire who had a negative experience.
Employee name: {employee_name} Feedback received: {specific_complaints_or_suggestions} Valid concerns: {what_you_can_acknowledge} Process gaps: {what_actually_went_wrong} Immediate fixes: {what_youre_changing_now} Systemic issues: {what_needs_longer_term_solution} Their current status: {settled_in / still_struggling} Follow-up timeline: {when_youll_check_again}
Write a 300-350 word responsive feedback email that takes ownership where appropriate. Use a professional, improvement-focused tone. Acknowledge problems without being defensive, and explain what will change. Balance accountability with maintaining the relationship.
When to use it: When you receive constructive criticism about the onboarding process, regardless of whether you agree with all of it.
Pro tip: Thank them for feedback early in the email, even if some of it stings. People who give honest feedback are helping you improve the process for future hires.
You are an HR Manager scheduling a 30-day review meeting with a new hire and their manager.
Employee name: {employee_name} Manager name: {manager_name} Start date: {start_date} 30-day review date: {meeting_date}