These 25 prompts are for HR Managers who need to move fast on engagement survey work — writing communications, analysing results, running follow-up conversations, and turning data into decisions. Paste any prompt into ChatGPT or Claude, fill in the variables, and use what comes back.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Launching the Survey: Communications to Employees
You are an HR Manager writing an internal all-staff email launching an annual employee engagement survey.
Company name: {company_name} Survey tool or link: {survey_link} Survey open dates: {open_date} to {close_date} Estimated completion time: {completion_minutes} minutes Confidentiality approach: {fully_anonymous / third-party_anonymised / manager_cannot_see_individual_responses} One thing leadership committed to doing differently based on last year’s results: {last_year_action}
Write a 200 to 250 word email. Open with what changed since the last survey, not with instructions. Explain confidentiality in one plain sentence. Include the survey link and closing date clearly. Close with one sentence that tells employees what happens after the survey closes. Tone: direct, human, no corporate filler.
When to use it: Monday morning of the week the survey goes live, before you brief the leadership team.
Pro tip: If your {last_year_action} is vague (“we improved communication”), the email will land flat and response rates will show it. Be specific: “We added two team social days after last year’s feedback on connection.” Replace the variable with something an employee can remember.
You are an HR Manager writing a reminder message to be sent via Slack or Teams to employees who have not yet completed the engagement survey.
Days remaining before survey closes: {days_remaining} Current completion rate across company: {completion_percent}% Department with lowest completion so far: {low_department} Incentive if any: {incentive_or_none} Tone: {light / direct / urgent}
Write a 100 to 130 word Slack or Teams message. Do not lecture about why surveys matter. Acknowledge the time investment with one honest sentence. Give the exact deadline. If there is an incentive, mention it once without overselling it. Include a clear CTA with the survey link placeholder {survey_link}.
When to use it: 48 hours before the survey closes, when completion is below 60%.
Pro tip: Set {tone} to “light” only if you are above 55% completion already. If you are below 40% with two days left, “light” reads as management not caring. Switch to “direct” and have the relevant department heads send it, not HR.
You are an HR Manager writing a personal email from the CEO to all employees asking them to complete an engagement survey.
CEO name: {ceo_name} Company name: {company_name} One specific business challenge the company is navigating right now: {current_challenge} One honest reason leadership needs employee input on this challenge: {why_input_matters} Survey closing date: {close_date} Survey link placeholder: {survey_link}
Write a 180 to 220 word email in first person from the CEO. Do not make it sound like an HR document. Open with the business challenge, not with “I am writing to”. Make one clear ask in the middle. Close with a commitment, not a platitude. Tone: candid, human, brief.
When to use it: When first-wave response rates stall below 45% after the initial launch email.
Pro tip: Show the draft to the CEO before sending. If they edit out the specific business challenge in {current_challenge} and replace it with something safer, the email loses its only reason to be believed. Push back and keep the specificity.
You are an HR Manager writing a manager briefing note ahead of an engagement survey launch.
Survey launch date: {launch_date} Number of direct reports managers are expected to encourage: {typical_team_size} Three things managers must NOT say to their teams about the survey: {three_dont_says} Two things managers SHOULD say: {two_do_says} How results will be shared back to managers: {results_sharing_method} Deadline for manager acknowledgement: {acknowledgement_deadline}
Write a 250 to 300 word internal briefing note for people managers. Use a numbered list for the dos and don’ts. Be specific about what “encouraging participation” looks like in practice — give one concrete example of something a manager can say in a team meeting. Close with the single most important message managers should take away.
When to use it: One week before launch, when you are running manager enablement sessions or sending pre-read materials.
Pro tip: The {three_dont_says} variable is where this prompt earns its value. Common ones to include: “don’t tell your team you’ll find out what they said”, “don’t tie survey feedback to performance conversations”, and “don’t say the survey is mandatory if it isn’t”. Managers improvise badly without explicit guardrails.
You are an HR Manager writing a post-survey thank you message to all employees confirming the survey is now closed.
Company name: {company_name} Final completion rate achieved: {final_completion_rate}% Date results will be shared back: {results_share_date} Format results will be shared in: {results_format — e.g. all-hands, team briefs, intranet report} One honest acknowledgement about the process: {honest_acknowledgement}
Write a 150 to 175 word all-staff message. Thank employees without being gushing. State the completion rate — employees trust honesty about numbers. Explain clearly when and how they will hear back. Include {honest_acknowledgement} naturally, not as a disclaimer. Tone: warm but brief.
When to use it: Within 24 hours of the survey closing, before results analysis begins.
Pro tip: If {final_completion_rate} is below 50%, do not hide it. Write it in. Employees know participation was low, and pretending otherwise destroys the credibility of whatever actions you announce later.
Analysing Results: Turning Data Into Written Outputs
You are an HR Manager writing an executive summary of employee engagement survey results for the senior leadership team.
Overall engagement score this year: {current_score} out of 100 Overall engagement score last year: {prior_score} out of 100 Top three scoring themes this year: {top_three_themes} Bottom three scoring themes this year: {bottom_three_themes} Most statistically significant change (up or down) since last year: {biggest_shift} One verbatim comment that best represents the dominant employee sentiment: {verbatim_quote}
Write a 300 to 350 word executive summary. Lead with the headline number and year-on-year change. Summarise strengths and concerns in two short paragraphs. Use the verbatim quote once to ground the data in a real voice. Close with three questions the leadership team should be prepared to answer at the review meeting — not recommended actions. Tone: factual, neutral.
When to use it: When preparing the pack for the first leadership debrief after results come in.
Pro tip: End with questions, not actions, in this draft. Leadership teams that receive a summary with pre-written actions often argue about the recommendations and miss the data. Forcing them to sit with questions first produces better decisions in the room.
You are an HR Manager writing a department-level engagement results summary for a single team.
Department name: {department_name} Department head name: {department_head_name} Team size and response count: {team_size} employees, {response_count} responded Department overall score: {dept_score} vs company average: {company_avg} One area where the team scored notably higher than the company average: {strength_area} One area where the team scored notably lower: {concern_area} Any significant demographic or tenure split in results, if known: {demographic_note_or_none}
Write a 250 to 300 word summary briefing for {department_head_name}. Use plain numbers. Highlight the strength first, then the concern. If response count is low (under 10), note that results should be treated with caution without repeating this more than once. Do not include action plans. Close with two discussion questions the department head can bring to their team. Tone: objective, supportive.
When to use it: When preparing individual manager packs before team-level results conversations.
Pro tip: If {response_count} is below 10, tell the department head privately before you send the written brief. The written note of caution is not a substitute for a conversation — managers who see their score for the first time in a document will sometimes spiral or dismiss the data before talking to HR.
You are an HR Manager writing internal talking points for a CEO presenting engagement survey results at a company all-hands meeting.
CEO name: {ceo_name} Presentation length allocated: {presentation_minutes} minutes Overall score and year-on-year movement: {overall_score}, {yoy_change — up/down/flat} The one finding leadership is most proud of: {proud_finding} The one finding leadership found hardest to hear: {hard_finding} Three commitments leadership is making in response to the results: {three_commitments}
Write a structured set of talking points for a {presentation_minutes}-minute section of an all-hands. Use a clear three-part structure: what we heard, what it means, what we will do. Write in first-person as {ceo_name}. Include one moment where the CEO acknowledges the hard finding directly — not defensively. Each talking point should be one to three sentences. Total length: 350 to 420 words.
When to use it: One week before the all-hands, when you are helping the CEO prep their section.
Pro tip: The {hard_finding} section is where all-hands presentations either earn trust or lose it. If the draft you receive from the AI softens the finding, push the prompt again and add: “Do not soften or reframe {hard_finding}. The CEO should name it plainly.” Employees who completed the survey know what they wrote.
You are an HR Manager writing a one-page internal brief on a single engagement theme that scored critically low across the organisation.
Theme name: {low_scoring_theme — e.g. “manager effectiveness”, “career growth”, “workload”} Score for this theme: {theme_score} out of 100 Company benchmark or industry average for this theme: {benchmark_score} Two verbatim employee comments related to this theme: {verbatim_1} and {verbatim_2} Department where this theme scored lowest: {worst_dept} Two root causes HR hypothesises based on the data: {hypothesis_1} and {hypothesis_2}
Write a 350 to 400 word internal brief on this theme for the People & Culture leadership team. Structure it as: what the data shows, what employees are saying, likely root causes, and three questions HR needs answered before recommending interventions. Do not include a solution section. Tone: analytical, candid.
When to use it: When preparing the deep-dive analysis that follows the headline results presentation.
Pro tip: Writing the “questions HR needs answered” section before proposing solutions is the fastest way to stop leadership teams jumping to off-the-shelf programmes that miss the actual problem. This brief format is deliberately solution-free by design — do not add an action section even if the AI offers one.
You are an HR Manager writing an email to a department head whose team showed the largest negative engagement shift in the company this year.
Department head name: {dept_head_name} Department name: {dept_name} Score drop from last year to this year: {prior_score} to {current_score} The theme that dropped most sharply: {sharpest_drop_theme} Any known context HR has about why this may have happened: {known_context_or_none} Proposed next step: {next_step — e.g. “30-minute call this week”, “joint team session”, “coaching referral”}
Write a 200 to 230 word email from HR to {dept_head_name}. Open by acknowledging the data directly, not diplomatically burying it. Show that HR sees the context in {known_context_or_none} if relevant. Propose {next_step} as a concrete ask with a specific timeframe. Tone: direct, private, non-judgmental.
When to use it: In the week after department-level results are shared, before the results go wider.
Pro tip: Send this email before the department head hears about their results from peers or leadership. If they find out the numbers are bad from someone other than HR, the conversation you need to have becomes a defensive one.
Designing Survey Questions: Generating the Right Items
You are an HR Manager drafting a short pulse survey to measure psychological safety within a single team following a recent restructure.
Team name: {team_name} Team size: {team_size} Restructure that occurred: {restructure_description — one sentence} Specific behaviour you want to measure: {target_behaviour — e.g. “willingness to raise concerns with manager”, “comfort speaking up in meetings”} Survey tool being used: {survey_tool — e.g. Culture Amp, Typeform, Microsoft Forms} Desired number of questions: {question_count — 5 to 8}
Write {question_count} survey questions ready to paste into {survey_tool}. Each question should be a single, unambiguous statement employees rate on a 1-to-5 agreement scale. At least two questions should be negatively worded to catch response bias. Do not include open text boxes — this is a scored pulse only. Output as a numbered list with the scale label on the last line: 1 = Strongly Disagree, 5 = Strongly Agree.
When to use it: Within four to six weeks of a restructure, when you want data before the annual survey cycle.
Pro tip: Negatively worded questions (“My manager would hold it against me if I raised a concern”) catch acquiescence bias — the tendency to agree with everything. If every score is above 4.2, check whether you have enough negatively phrased items. If you have none, rerun the prompt with the instruction “at least three questions must be negatively worded”.
You are an HR Manager drafting engagement survey questions specifically for a remote-first workforce where employees have never met their colleagues in person.
Company name: {company_name} Proportion of workforce that is fully remote: {remote_percent}% Main collaboration tools used: {tools — e.g. Slack, Zoom, Notion} Themes you must cover: {required_themes — e.g. belonging, manager connection, career visibility} Number of questions needed: {question_count} Survey scale: {scale — e.g. 1 to 5, 1 to 10, agree/disagree}
Write {question_count} survey questions for a remote workforce on the themes in {required_themes}. Each question must reference the realities of remote work — do not use questions designed for office settings that assume physical presence. Output as a numbered list. Include a one-line note after each question explaining what organisational behaviour it is designed to surface.
When to use it: When adapting a legacy engagement survey that was written when the company was office-based.
Pro tip: Questions like “I feel included in team activities” were written for offices. Remote employees read “activities” as social events they were excluded from and score it low regardless of actual inclusion. Check every item in {required_themes} against this lens before using legacy questions.
You are an HR Manager writing open-text questions for an annual engagement survey to maximise the quality of qualitative responses.
Number of open-text questions allowed