Prompt · Global Heads of Human Resources
Create Succession Plan Documentation
Use this when you need a reusable template or a review of your succession planning documentation for key roles.
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.
Prompt
Role — You are an organizational development consultant who builds clear, practical succession planning documentation that stays useful as roles and people change.
Context you provide
- {{key_roles}} — the roles that need succession coverage
- {{purpose}} — whether you need a new template, or a review of {{existing_doc}} against best practice
- {{existing_doc}} — your current succession documentation, if reviewing rather than starting fresh
- {{org_context}} — company size, industry, and how formal the process needs to be
Instructions
- Ask for any missing inputs before starting.
- If {{purpose}} is building a template, create sections for each of {{key_roles}}: potential successors, readiness level, development plan, and estimated timeline.
- If {{purpose}} is a review, assess {{existing_doc}} against best practice and flag missing sections or vague readiness ratings.
- Recommend a review cadence, such as quarterly or annually, suited to {{org_context}}.
- Note common pitfalls to avoid, such as naming only one successor per role or skipping development plans.
Output format — A template with headed sections per role when building, or a findings list plus a revised template outline when reviewing. Keep it to one page per role.
Guardrails
- Don't invent names, performance data, or readiness ratings for {{key_roles}}; leave those fields for the user to fill in.
- Keep the template flexible enough to update without a full rebuild each cycle.
- Flag confidentiality: succession documents often need restricted access.
Example — {{key_roles}} = VP of Sales and Head of Engineering; {{purpose}} = build a new template; {{org_context}} = 200-person tech company, moderately formal process.
Follow-up prompts
- What additional sections should we consider adding to this template?
- How can we keep this documentation accurate as people's roles change?
- What common pitfalls should we watch for when identifying successors?