These 25 prompts are for HR Managers who need to write promotion announcement emails today — not next week, not after three rounds of edits. Each prompt takes a specific scenario, accepts your real inputs, and returns a finished email you can copy, trim slightly, and send.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration across multiple announcements in one session.
Single Employee Promotions — Standard Announcements
You are an HR Manager writing an internal promotion announcement email for the whole company.
Employee name: {employee_name} Previous role: {previous_job_title} New role: {new_job_title} Department: {department} Effective date: {effective_date} One or two specific wins that earned this promotion: {key_achievements} Tone: {formal / conversational}
Write a 200 to 250 word company-wide email announcing this promotion. Open with the announcement in the first sentence — no wind-up. Name the specific achievement in sentence two or three. Include one sentence on what the new role covers and who the employee now leads or reports to. Close with a short congratulations line that invites colleagues to reach out. No superlatives. No “we are thrilled beyond words”. Just clear, warm, professional.
When to use it: Monday morning after a Friday sign-off on the promotion paperwork, when you need the all-staff email out before 9am.
Pro tip: If the employee is moving from an individual contributor role to people management for the first time, add “This is {employee_name}‘s first people-management role” to your variables and tell the prompt to include one sentence acknowledging the transition. It sets expectations with the team without making it a big deal.
You are an HR Manager writing a promotion announcement email to a single department, not the whole company.
Employee name: {employee_name} New title: {new_job_title} Department receiving the email: {department_name} Manager who approved the promotion: {approving_manager_name} Start date in new role: {start_date} Changed responsibilities the team will notice day-to-day: {responsibility_changes} One personal quality worth naming: {personal_quality}
Write a 180 to 220 word email from the HR Manager to the {department_name} team. Announce the promotion, describe what changes practically for the team (who owns what now, any reporting changes), and mention the one personal quality. Tone: direct and genuine. Avoid generic praise. End with a single-sentence prompt for team members to congratulate {employee_name} directly.
When to use it: When a promotion is department-specific and a company-wide blast would feel disproportionate — a team lead stepping up to senior team lead within a 12-person function, for example.
Pro tip: Paste the responsibility changes as bullet points in the variable field. The AI will convert them into readable prose. If you write them as prose yourself, you tend to get a paraphrase of your own phrasing back, which defeats the purpose.
You are an HR Manager drafting a promotion announcement email on behalf of a department head who will send it under their own name.
Employee name: {employee_name} Promoted to: {new_role} Sender name and title: {sender_name}, {sender_title} Length of time in previous role: {tenure_in_role} Project or result that defined the case for promotion: {defining_project_or_result} Team size the employee now manages or joins at senior level: {team_size} Tone: {warm-professional / business-formal}
Write a 220 to 270 word email from {sender_name} to the department. Write it in first person as if the department head is speaking. Reference {defining_project_or_result} with one specific detail. Acknowledge {tenure_in_role} briefly. Close with an instruction — something the team should do next, like update Slack handles, book intro time, or attend the handover meeting on {effective_date}.
When to use it: When the department head asks HR to ghost-write the announcement email and will forward it with minor edits. Common when the head is travelling or swamped during a busy close period.
Pro tip: After the AI generates the draft, paste it back and ask: “Does this read like a department head wrote it or like HR wrote it? Adjust voice if needed.” Ghost-written emails often default to HR language (“we are pleased to confirm”) when they should sound like the individual leader.
You are an HR Manager writing a promotion announcement for an employee who is being promoted but staying in the same team with the same colleagues.
Employee name: {employee_name} Old title: {old_title} New title: {new_title} What actually changes in their day-to-day: {what_changes} What stays the same: {what_stays_same} Any awkwardness to acknowledge (e.g. others applied, peer now becomes senior): {sensitive_context — write “none” if not applicable} Audience: {immediate_team_only}
Write a 160 to 200 word email to the immediate team. Be clear about what changes and what does not. If {sensitive_context} is not “none”, acknowledge the situation in one measured sentence without over-explaining or apologising. Keep the tone matter-of-fact and positive. No fanfare. End with one forward-looking sentence about what the team can expect from {employee_name} in the new capacity.
When to use it: When someone gets a title change and salary bump but functionally keeps the same desk, same slack, same teammates — and the team already knows the promotion was happening. The risk here is under-communicating the change, not over-celebrating.
Pro tip: If {sensitive_context} involves a peer who also applied and didn’t get it, do not reference the other candidate even obliquely. Ask the AI explicitly to avoid any phrasing that could be read as comparative. Read the draft twice with that lens before sending.
You are an HR Manager writing a promotion announcement email for a long-tenured employee who has been with the company for many years and is finally moving into a senior leadership title.
Employee name: {employee_name} Years at company: {years_tenure} Previous title: {previous_title} New title: {new_title} Two or three contributions over their tenure worth naming: {career_contributions} What this role means for the organisation going forward: {strategic_relevance} Audience: {whole_company / leadership_team / department}
Write a 280 to 320 word email. Open with the announcement. Spend the middle paragraph on career arc — use {career_contributions} to show progression, not just longevity. One sentence on {strategic_relevance} to explain why this role matters now. Close warmly but not effusively. Avoid phrases like “a true pillar of our culture” or “embodies everything we stand for”. Be specific throughout.
When to use it: When someone has been in the same band for five or more years and this promotion is a meaningful milestone, not a routine step. The email needs to honour tenure without sounding like a retirement speech.
Pro tip: “Years at company” by itself reads as a loyalty reward. Make sure {career_contributions} contains at least one result — a number, a product shipped, a team built — so the email reads as merit-based, not seniority-based.
Promotions With Sensitive or Complex Context
You are an HR Manager writing a promotion announcement email for an employee who is being promoted after a period of performance improvement.
Employee name: {employee_name} New role: {new_role} Time since improvement period ended: {months_since_pip_closed} Growth area that improved: {growth_area} Recent achievement that triggered the promotion: {recent_achievement} Audience: {immediate_manager_and_skip_level_only — keep internal} Tone: {measured / understated}
Write a 150 to 180 word email to the immediate manager and skip-level only. Do not reference the improvement period by name. Focus on the growth area that improved and the recent achievement. Announce the promotion cleanly. The email should read as a fresh start, not a rehabilitation story. No hedging, no qualifiers like “despite past challenges”. Keep it forward-looking.
When to use it: When you are notifying leadership of the promotion before the all-staff announcement goes out — so they are not surprised — but you do not want the history circulated in writing.
Pro tip: Never include the words “PIP”, “performance plan”, or “improvement period” in any promotion email, even internal ones. These documents can be forwarded. Write the variable {growth_area} as a skill (“stakeholder communication”) not as a deficit description (“struggled to manage up”).
You are an HR Manager writing a promotion announcement for a situation where two employees were considered and only one is being promoted.
Promoted employee name: {promoted_employee_name} Promoted employee new title: {new_title} The other employee’s name (for your reference only — do not name them in the email): {other_employee_name} Reason promotion went to {promoted_employee_name} — keep this neutral: {differentiating_factor} Who receives this email: {team_lead_and_hr_business_partner_only} What you need the lead to do after reading: {required_next_step}
Write a 140 to 170 word internal briefing email from HR to the team lead and HR Business Partner. Announce the decision. Use {differentiating_factor} in one sentence to explain the reasoning without disparaging the other candidate. State clearly what {required_next_step} is and by when. Do not reference the other employee by name anywhere in the draft.
When to use it: Before the public announcement goes out, when the team lead needs context so they can manage the reaction of the employee who was not selected.
Pro tip: Send this briefing email at least 24 hours before the public announcement. The team lead needs time to have a one-on-one with the unsuccessful candidate before that person reads it in an all-staff email. The prompt produces the briefing; you still own the sequencing.
You are an HR Manager writing a promotion announcement for an employee who is being promoted to a newly created role that did not exist before.
Employee name: {employee_name} New role title: {new_role_title} What gap or need this role addresses: {business_problem_this_role_solves} Why this employee was chosen to build the role: {selection_rationale} Who they will report to: {reporting_line} Expected scope in the first 90 days: {initial_scope} Audience: {company_wide}
Write a 250 to 290 word company-wide announcement. Introduce the new role first — what problem it solves and why now. Then announce {employee_name} as the person stepping into it. Use {selection_rationale} to explain the fit in concrete terms. Include {initial_scope} so colleagues know what to bring to {employee_name} and what to hold. Close with one sentence on reporting line and start date.
When to use it: When the promotion is tied to an org design decision, not just a performance reward. Colleagues will have questions about what the new role actually does — the email needs to answer them before people hit reply.
Pro tip: Put the role rationale before the person’s name in the email. If you lead with the person, readers assume it’s a standard promotion and miss the structural change. This sequencing is the one thing the AI will get wrong if you do not specify it explicitly — the variable order in your prompt matters.
You are an HR Manager writing a promotion announcement for an employee who is being promoted into a role that involves managing former peers.
Employee name: {employee_name} New title: {new_title} Names of former peers now reporting to them (first names only): {direct_report_names} What the team should expect during the transition: {transition_expectations} Tone: {matter-of-fact} Any specific authority or decisions {employee_name} now owns: {new_decision_authority}
Write a 200 to 240 word email to the team. Announce the promotion clearly in sentence one. Use one sentence to acknowledge the transition — that this is a new dynamic and normal adjustment time is expected — without making it heavy. State {new_decision_authority} explicitly so the reporting line is unambiguous. End with a practical note: first team meeting under new structure is {first_meeting_date}. Tone should normalise the change without dismissing it.
When to use it: When you know the team has worked side-by-side for two or more years and the promotion will land with some friction. Getting the authority lines in writing early prevents two weeks of “who do I go to for X” confusion.
Pro tip: Have {employee_name} review this draft before it goes out — not to change the announcement, but to confirm they are comfortable with the phrasing around their new authority. A manager who reads their own announcement for the first time when the team does will feel blindsided, even if the promotion itself was planned.
You are an HR Manager writing a promotion announcement for an employee who has been promoted but is also leaving the country to work from a new location.
Employee name: {employee_name} New title: {new_title} New location: {new_location} Time zone impact on team collaboration: {timezone_note} What does not change: working relationship, deliverables, team: {what_stays_same} Effective date: {effective_date} Audience: {immediate_team}
Write a 190 to 230 word email. Lead with the promotion. Acknowledge the relocation to {new_location} in the second paragraph — frame it as context, not a disruption. Include {timezone_note} so the team knows what to expect practically. Reaffirm {what_stays_same} to settle any worry about continuity. Close with the effective date and a note on how to reach {employee_name} during transition.
When to use it: When a promotion coincides with a relocation — common after a return-to-office policy change that prompted someone to negotiate a remote promotion as part of the deal.
Pro tip: Mention the time zone impact in a factual, non-apologetic tone. Something like “Working hours will overlap with UK time from 10am to 2pm” is more useful than “There may be some scheduling adjustments.” Concrete beats diplomatic every time.
Executive and Leadership Level Promotions
You are an HR Manager drafting a promotion announcement for a VP-level or above appointment, to be sent by the CEO.
Promoted individual: {employee_name} New title: {new_title}, reporting to: {ceo_name} What they are taking over or building: {scope_of_role} Previous role and company or internal history: {background_summary} Strategic priority this role connects to: {company_strategic_priority} Audience: all staff CEO’s preferred tone: {confident / warm-formal / understated}
Write a 300 to 350 word email from {ceo_name} in first person. Open with the appointment. Second paragraph: connect {scope_of_role} to {company_strategic_priority} — this explains the why. Third paragraph: brief background on {employee_name} using {background_summary}, one or two sentences. Close: direct, no inspirational quotes, no “I am confident they will” hedging — state it as a decision, not a hope.
When to use it: After a board sign-off on a senior appointment, when the CEO needs a polished all-staff email out the same day without going through three rounds of comms review.
Pro tip: If the CEO has a recognisable voice in previous communications, paste one of their past emails into the same session and ask the AI to match the voice before writing the draft. Leadership announcement emails ghost-written in generic HR language are easy to spot and undermine credibility.
You are an HR Manager writing an internal announcement for a C-suite