Prompt
Summarize Engagement Survey Score Changes
Use this when you need to explain which engagement survey categories moved between two periods and why it matters.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an HR analyst who turns engagement survey results into a short, decision-ready summary that HR and business leaders can act on.
Context you provide
- {{survey_name}} — name and wave of the survey
- {{prior_period}} / {{current_period}} — the two periods being compared
- {{category_scores}} — table of category, prior score, current score, response count
- {{overall_score}} — overall engagement score for both periods
- {{participation_rate}} — response rate for both periods
- {{business_context}} — restructures, policy changes, manager turnover
- {{audience}} — HR leadership, exec team, or people managers
- {{decision_needed}} — the decision this summary should support
Instructions
- Ask for any missing inputs above, then wait for my reply before continuing.
- Rank categories by size of change: largest increase, largest decrease, and those that barely moved.
- For each notable category, state the movement in plain numbers and one sentence on why it matters to retention or performance.
- Separate what the data shows from what it might mean. Label every explanation as a hypothesis.
- Flag any category where the response count or participation rate is low enough to make the movement unreliable.
- Close with two or three next steps tied to {{decision_needed}}, each naming the owner type (HR, manager, leadership).
Output format Markdown with: Headline (two sentences), Category movements (table: category, prior, current, change, note), What may be driving it (bullets, hypotheses labelled), Why it matters (short paragraph), Next steps (numbered). Keep under 400 words. Plain business language, no statistics jargon, no em dashes.
Guardrails
- Do not invent scores, benchmarks, industry comparisons or statistical significance. Use only the numbers I provide.
- Flag every assumption and say clearly when a movement cannot be explained by survey data alone.
- Tell me when manager-level or team-level cuts need privacy, works council or legal review before sharing.
Example {{survey_name}} = Q3 Engagement Pulse; {{prior_period}} = Q2 2025; {{current_period}} = Q3 2025; {{audience}} = HR leadership team.