Plan stakeholder communication and engagement
Who needs to know what, when, and how — and how to keep them engaged.
The prompt
Role: Act as a programme manager building a stakeholder engagement plan.
Context: Programme purpose and change involved: [PURPOSE_CHANGE]. Stakeholders / groups and what we know about their interest, influence and current stance: [STAKEHOLDERS]. Key messages and any sensitivities: [MESSAGES_SENSITIVITIES]. Channels available: [CHANNELS]. Milestones that need communication: [MILESTONES]. Constraints: [CONSTRAINTS].
Task: Produce: (1) a stakeholder map (influence x interest) with the current and target stance for each and the gap; (2) an engagement approach per stakeholder/group (inform / consult / involve / collaborate) with the rationale; (3) a communication plan - message, audience, channel, sender, timing/cadence, and the feedback loop; (4) the risky stakeholders and a specific plan to move them; (5) how you will measure engagement.
Format: Sections: Stakeholder map (table) | Engagement approach | Communication plan (table) | At-risk stakeholders & plan | Engagement measures. ~500 words.
Verification: Flag any stance assessment that is an assumption rather than evidenced; ensure every milestone has a communication and every stakeholder a clear approach.
Validation: Pressure-test against the most resistant stakeholder: is the plan to shift them specific and realistic, or wishful? Sharpen it.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- PURPOSE_CHANGE
- STAKEHOLDERS
- MESSAGES_SENSITIVITIES
- CHANNELS
- MILESTONES
- CONSTRAINTS
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Plan an MFA or password manager rollout across the companyBuilds a phased rollout plan with pilot groups, user communications, support prep, and handling of edge cases.
- Write a project charterDefines a project's purpose, scope, objectives, stakeholders, and success criteria.
- Spot where stakeholders' expectations don't match the planCompares what each stakeholder expects with what the project will actually deliver, and helps you close the gaps early.
- Plan a group project and split the work fairlyA fair task split, timeline, and team agreement for a school group project, including what to do if someone doesn't pull their weight.