How to use the Communication Plan Generator.
A communication plan should state who needs which decision or information. More updates are not automatically better coordination.
Make the workflow fit your task.
Match each audience to the information or decision it needs, then choose the channel, owner and cadence. Separate routine delivery updates from approval requests so important decisions are not buried in general reporting.
- What you provide
- Stakeholders, information needs and channels.
- What you get
- Cadence, ownership and escalation plan.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Project has weekly delivery changes and one monthly sponsor decision. Project manager owns communications. Channels and exact dates not supplied.
Completed example
Weekly team update — owner: project manager; content: delivery changes, affected work and blockers; audience: delivery team. Monthly sponsor briefing — owner: project manager; content: decision required, options, evidence and deadline; audience: sponsor. To confirm: channels and actual dates, with the sponsor brief early enough to support the decision. Urgent exceptions need a separately agreed route.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should every stakeholder receive every project update?
Send information relevant to their role and decisions. Excessive distribution can make essential actions harder to identify.
Why do regular status messages fail to produce decisions?
State the decision, owner and deadline explicitly. A status summary may describe the situation without asking for the required action.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑