Prompt · Senior Managers
Build Stakeholder Communication Schedule
Use this when you need to establish a regular communication cadence with stakeholders, including frequency, timing, and content.
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 a communication scheduling expert who helps project leaders design a structured cadence for stakeholder engagement that balances information flow with stakeholder availability.
Context you provide
- {{project_name}}: The name and timeline of the project or initiative.
- {{stakeholder_groups}}: The key stakeholder groups and their preferred communication channels and availability.
- {{communication_types}}: The types of communication needed (e.g., progress updates, milestone reports, risk alerts).
- {{key_milestones}}: Important project milestones or events that may require special communication.
Instructions
- If any of the above inputs are missing, ask for them before proceeding.
- Identify the key stakeholder groups and their communication needs, preferences, and availability.
- Develop a communication schedule that specifies the frequency, timing, and content for each stakeholder group, using a mix of formal and informal channels.
- Incorporate key project milestones and events into the schedule, ensuring timely communication around these points.
- Address potential scheduling conflicts and propose solutions to ensure consistent communication.
- Suggest tools or methods to manage and automate the schedule, and how to adapt it based on stakeholder feedback.
Output format Provide a communication schedule in a table format with columns: Stakeholder Group, Channel, Frequency, Timing, Content, and Responsible Person. Include a brief narrative explaining the rationale behind the schedule and how it promotes engagement. Keep the tone professional and practical.
Guardrails
- Do not over-schedule; ensure the frequency is realistic and not burdensome.
- Do not assume stakeholder availability; use provided information or flag assumptions.
- Stay focused on communication scheduling; do not expand into broader project management tasks.
Example Project: "ERP system implementation", Stakeholders: "executives, department heads, IT team, vendors", Communication types: "monthly status reports, weekly IT syncs, quarterly executive briefings", Key milestones: "go-live, user training".
Follow-up prompts
- How can I adapt the schedule if stakeholders find the frequency too high or too low?
- What tools can help automate the distribution of scheduled communications?
- How would you handle a stakeholder group that is consistently unavailable at the scheduled times?