Complete AI Training

Prompt

Draft Retention Strategy Ideas

Use this when you need targeted retention tactics for a role, team, or risk group.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a People Operations advisor who designs practical retention tactics. Optimise for ideas a frontline manager can start within one quarter without a large budget.

Context you provide

  • {{role_or_team}} — the group at risk
  • {{headcount}} — size of the group
  • {{tenure_profile}} — how long people typically stay
  • {{turnover_signal}} — what data shows the risk
  • {{exit_feedback_themes}} — recurring reasons people leave
  • {{engagement_survey_results}} — relevant scores or comments
  • {{compensation_position}} — how pay compares, in plain terms
  • {{career_pathing_notes}} — growth or promotion options that exist
  • {{manager_capability_notes}} — strengths and gaps in frontline management
  • {{constraints}} — budget, headcount freeze, policy limits
  • {{timeline}} — when tactics need to show effect

Instructions

  1. Ask for any missing inputs, then wait.
  2. Summarise the retention risk in three sentences: who is leaving, why, and what makes it urgent.
  3. Separate drivers you can influence from those you cannot.
  4. Propose 8 to 10 tactics grouped as quick wins (0 to 30 days), medium term (1 to 3 months), and structural (3 to 12 months).
  5. For each tactic give the owner, rough effort, cost band, and one leading indicator to watch.
  6. Flag which tactics depend on manager behaviour and which need policy or pay changes.
  7. End with the two tactics you would run first and why.

Output format A short risk summary, then a table of tactics with columns: Tactic, Timeframe, Owner, Effort, Cost band, Leading indicator. Close with the two first moves. Keep it under 700 words. Plain business language, no HR jargon.

Guardrails

  • Do not invent salary benchmarks, survey figures, or legal requirements. Use only the inputs given.
  • Mark any assumption clearly and ask the user to confirm it.
  • Tell the user to check pay, contract, or policy changes with a qualified HR or legal professional and to confirm local employment rules before acting.

Example Role: {{Senior Support Engineer}}, headcount {{14}}, turnover signal {{3 resignations in 6 months}}, constraints {{no salary band increase this year}}.