These 25 prompts are for HR Managers who need something ready to send today — a welcome email, a 30-day check-in script, a manager brief, a first-week agenda. Fill in the variables, paste into ChatGPT or Claude, and use what comes back with light editing.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Day-One Welcome Communications
You are an HR Manager writing a personalised welcome email to a new employee on their first day.
New employee name: {employee_name} Job title: {job_title} Department: {department} Direct manager name: {manager_name} One thing that stood out in their interview: {standout_detail} Office or remote: {work_arrangement} Tone: {warm_and_professional / casual / formal}
Write a 200 to 250 word welcome email from HR. Open with their name and a genuine, specific welcome that references {standout_detail}. Include three things they should know about their first day (who to ask for, where to go or log in, what the first hour looks like). Close with an invitation to reach out directly. Do not use “excited to have you on board” or “we’re thrilled”. Use plain, direct language.
When to use it: The morning before a new starter’s first day, when you need something that doesn’t read like a mail merge.
Pro tip: If {standout_detail} is vague, pull one sentence from your interview notes — even a specific question they asked works. That single detail is what makes the email feel written for them rather than copied from last month’s hire.
You are an HR Manager writing a Slack or Teams welcome message to announce a new employee to their department.
New employee name: {employee_name} Job title: {job_title} Start date: {start_date} Previous company or background in one line: {background_summary} One fun or personal detail they shared: {personal_detail} Channel this will be posted in: {channel_name} Tone: {upbeat / low-key / formal}
Write a 100 to 130 word Slack or Teams announcement. Lead with the employee’s name and role. Include {background_summary} in one sentence. Work {personal_detail} in naturally — not as a bullet, as a sentence in the flow. End with a prompt for teammates to say hi. No bullet lists. No headers. Write it as a short paragraph.
When to use it: The morning of a new hire’s first day, before your 9am standup, when you want the team intro to feel human rather than a copy-paste announcement.
Pro tip: Post this yourself from the HR account, not the manager’s account. When it comes from HR it signals the company cares, not just the line manager. If {personal_detail} was something sensitive (they mentioned moving cities, a health change), leave it out and use a professional detail instead.
You are an HR Manager writing a first-day briefing document for a new hire’s direct manager to use during their 9am welcome meeting.
New employee name: {employee_name} Job title: {job_title} Manager name: {manager_name} Key onboarding priorities in the first week: {three_priorities} Systems or tools to introduce on day one: {tools_list} One thing the manager should avoid saying or doing based on the new hire’s profile: {avoid_note} Meeting length: {meeting_length_in_minutes}
Write a one-page briefing document for {manager_name} to use as a talking guide for the welcome meeting. Structure it in three sections: Opening (how to start the conversation), Agenda (what to cover and in what order, timed to {meeting_length_in_minutes} minutes), and Close (how to end so the employee knows what happens next). Include {avoid_note} as a discreet note at the top labelled “HR note — not for sharing”. 300 to 380 words total.
When to use it: The day before a new hire starts, when you’re briefing a manager who’s onboarded someone before and thinks they don’t need prep. They do.
Pro tip: The {avoid_note} field is the most valuable variable here. Use it for real information — “this employee left their last job due to a toxic manager, don’t open with jokes about how hard the role is” — not generic advice. Managers read the HR note. It lands.
You are an HR Manager writing a personalised first-week schedule email for a new employee.
New employee name: {employee_name} Role: {job_title} Start date: {start_date} Key meetings in week one (list up to five with day and time): {week_one_meetings} Required training or compliance modules: {training_modules} Buddy or peer assigned to them: {buddy_name} Any gaps in week one they should use for self-directed reading: {reading_or_self_study}
Write a 280 to 320 word email to {employee_name} laying out their first week. Present the schedule in a clean day-by-day format (Monday through Friday). After the schedule, add a two-sentence note explaining why the week is structured this way — what the logic is. Close with {buddy_name}‘s name and a one-line prompt to reach out to them for anything unofficial. Tone: practical and reassuring, not over-enthusiastic.
When to use it: Two days before a new hire starts, so they can read it over the weekend and arrive with a mental map of the week rather than a blank wall of anxiety.
Pro tip: Include at least one obvious gap in the schedule — a 90-minute block labelled “no meetings, settle in” on day two. New hires notice when every hour is packed. A visible breathing space signals psychological safety before they’ve said a word.
You are an HR Manager writing a welcome letter from the CEO or senior leader to include in a new employee’s onboarding pack.
CEO or leader name: {leader_name} Leader title: {leader_title} Company name: {company_name} Company mission in one sentence: {mission_statement} One thing the company genuinely struggles with that new employees should know: {honest_challenge} One specific thing new employees are expected to contribute: {contribution_expectation} Tone: {direct / inspiring / personal}
Write a 250 to 300 word welcome letter from {leader_name}. Open with the company’s mission, not with “welcome to the team”. Address the new employee as “you” throughout. Include {honest_challenge} framed as something the company is actively working on — not a warning, not a disclaimer. End with {contribution_expectation} as a direct ask, not a platitude. Do not use phrases like “family”, “we move fast”, or “the sky’s the limit”.
When to use it: When you’re refreshing onboarding materials and the existing CEO letter hasn’t been updated since 2021 and mentions a strategic priority that no longer exists.
Pro tip: Run {honest_challenge} past the CEO before using it. Leaders often approve something in conversation they then want softened in writing. Get sign-off on that specific sentence before the whole letter is printed or sent.
First-Week Manager and Buddy Scripts
You are an HR Manager writing a conversation script for a buddy to use during their first informal check-in with a new employee.
Buddy name: {buddy_name} New employee name: {employee_name} New employee’s role: {job_title} Day this conversation happens: {day_of_week} of week one One specific thing the new employee is likely to find confusing based on the role: {likely_confusion} Format: {in-person / video call}
Write a 300 to 350 word conversation script for {buddy_name}. Structure it in four beats: opening small talk (2 to 3 lines), a question about how the first days have gone (with a follow-up prompt if the answer is “fine”), a natural way to address {likely_confusion} without making it feel like a HR checklist, and a close that sets up the next touchpoint. Write it as actual dialogue — lines {buddy_name} can say word for word, with stage directions in brackets for tone or pause.
When to use it: When you’ve assigned a buddy but haven’t given them anything to work with, and you know from experience that “just be friendly” is not a briefing.
Pro tip: The “what if they say fine” follow-up prompt is the most important part of this script. New hires almost always say fine in week one. Write the follow-up as a specific, non-threatening question: “What’s one thing that’s taken longer to figure out than you expected?” works far better than “Is there anything you need?”
You are an HR Manager writing a 30-day check-in meeting agenda for a new employee’s line manager.
New employee name: {employee_name} Job title: {job_title} Manager name: {manager_name} Known struggle or slow start in the first 30 days: {known_issue} One win or positive signal from the first 30 days: {early_win} Meeting length: {meeting_length_in_minutes} Any probation or performance concern: {probation_flag: yes / no}
Write a structured meeting agenda for {manager_name} to run the 30-day check-in with {employee_name}. Include five agenda items with suggested time splits that add up to {meeting_length_in_minutes} minutes. For each item, write two to three lines of guidance for the manager on how to run that part of the conversation, referencing {known_issue} and {early_win} where relevant. If {probation_flag} is yes, include a discreet section at the end labelled “If needed: probation language” with one to two sentences the manager can use. Total: 350 to 420 words.
When to use it: When a manager comes to you the morning of a new hire’s 30-day check-in and asks “what should I cover?” — this produces something they can walk into the room with.
Pro tip: If {probation_flag} is yes, brief the manager verbally before the meeting, not just in the agenda doc. Written probation language in an agenda creates a paper trail that can become a problem if the document is shared or screenshotted. Keep that section out of any version sent to the employee.
You are an HR Manager writing a manager briefing note before a new hire’s first performance conversation at 60 days.
New employee name: {employee_name} Job title: {job_title} Manager name: {manager_name} Two or three specific observations from the first 60 days (positive and developmental): {observations} Agreed goals set at hire: {original_goals} Current status against those goals: {goal_status: on_track / behind / ahead} Any HR-sensitive context the manager needs to know: {hr_context}
Write a one-page briefing note for {manager_name} to read before the 60-day conversation. Include four sections: What to reinforce (specific behaviours to name), What to address (how to raise {observations} if any are developmental, using the SBI model — Situation, Behaviour, Impact), Goals update (how to discuss {goal_status} without it feeling like a formal review), and HR note (a discreet section covering {hr_context} labelled clearly as confidential). 380 to 440 words.
When to use it: When you want the 60-day conversation to be more than a manager saying “how’s it going?” — especially when there are early development signals you need handled carefully.
Pro tip: If {hr_context} includes anything from a protected characteristic, disability accommodation, or personal disclosure the employee made during onboarding, state explicitly in the HR note that this information should not be referenced in the meeting, only used to inform the manager’s approach. That distinction matters legally.
You are an HR Manager writing a peer introduction email that a new employee can send to key colleagues in their first week.
New employee name: {employee_name} Job title: {job_title} Department: {department} Two things {employee_name} is working on in their first 90 days: {first_projects} One thing {employee_name} wants to learn from colleagues: {learning_ask} Tone: {professional / warm / concise}
Write a 180 to 220 word email from {employee_name} to key colleagues they’ll be working with. It should not sound like an HR template. Write it in first person as {employee_name}. Open with a brief, specific intro that mentions {job_title} and {department} without being robotic. Include {first_projects} naturally as context for why they’ll be working together. Include {learning_ask} as a genuine ask, not a flattery opener. End with a low-friction invitation to connect (not “let’s get coffee” unless that matches {tone}). No bullet points.
When to use it: When a new hire tells you they’ve been put on a cross-functional project and doesn’t know how to introduce themselves to people they haven’t met yet.
Pro tip: Give the employee this email to review and edit before sending — don’t send it on their behalf. They need to own the voice. If they change the whole thing, that’s fine. Your job was to give them a starting point, not a script they’re locked into.
You are an HR Manager writing a structured talking guide for a manager to use when walking a new hire through the team’s unwritten norms and culture.
Manager name: {manager_name} Team name or department: {team_name} Three unwritten norms that new joiners typically get wrong: {three_norms} Communication style the team uses: {communication_style} One thing the team values that doesn’t appear in any company document: {informal_value} New employee name: {employee_name}
Write a 300 to 360 word talking guide for {manager_name} to use in a 20-minute informal conversation with {employee_name} in week one. Structure it as three conversational sections: How we communicate (covering {communication_style}), How we work together (covering {three_norms} in plain language, framed as helpful context not rules), and What we care about (covering {informal_value} as something the team genuinely lives by). For each section, give {manager_name} two specific sentence starters they can use to open the topic naturally.
When to use it: When you know from exit interviews or early turnover that new hires often describe feeling like they “didn’t understand the culture” — and you want to address that in week one, not month three.
Pro tip: The {three_norms} field is where this prompt earns its keep. Don’t write generic norms. Use real ones from your team — “don’t reply to the MD’s emails on Sunday even if he sends them, he doesn’t expect a response until Monday” is infinitely more useful than “we value work-life balance”.
Compliance, Paperwork, and Admin Follow-Up
You are an HR Manager writing a follow-up email to a new employee who has not completed their mandatory compliance training.
New employee name: {employee_name} Job title: {job_title} Training module name: {module_name} Original deadline: {original_deadline} Days overdue: {days_overdue} Consequence if not completed by new deadline: {consequence} New deadline: {new_deadline} Tone: {firm_but_fair / formal / direct}
Write a 180 to 220 word email. Do not open with “I hope this email finds you well”. State clearly that {module_name} is overdue by {days_overdue} days. Set the new deadline of {new_deadline} in the first paragraph. State {consequence} plainly in the