A useful communication plan names the information, its audience, the person preparing it, and the moment it is needed. The filled template below separates a recurring update from a change-triggered instruction. Use it to plan the conversations and messages before drafting them.
Start with the decisions people need to make
The original fictional example covers a small museum moving an exhibition into another room. Its communication arrangements are supplied teaching assumptions, not recommendations that every team use these channels or deadlines.
The project has three audiences with different needs:
- The sponsor needs the overall schedule, spending decisions, and issues requiring a choice.
- The move team needs the next handoffs and changes to the work sequence.
- Volunteer hosts need the instructions that affect their assigned shifts and visitor directions.
Ask what the recipient will do with the information. That question helps you decide whether a weekly summary is enough, or whether the person needs a separate instruction before taking action.
Use a filled plan with owners and timing
| ID and audience | Information and purpose | Owner and channel | Cadence or trigger |
|---|---|---|---|
| CP1 · Sponsor | Milestone changes, spending decisions, and choices needed for the room move. | Project lead; sponsor review meeting. | Weekly during the move; a separate decision request when a choice cannot wait for that meeting. |
| CP2 · Move team | Next handoffs, work sequence, and dependencies affecting the coming work. | Move coordinator; team planning meeting. | Before each planned move session; revise the briefing when the sequence changes. |
| CP3 · Volunteer hosts | Confirmed entrance, visitor route, and duties affecting the recipient's assigned shift. | Volunteer coordinator; agreed volunteer email list. | When an approved route or duty change affects a shift, before that shift begins. |
These are three planned communication activities, not three messages already sent. The example does not supply a move date, meeting time, actual mailing list, or a record of anyone receiving an update. Your real plan needs those details from the people responsible.
Asana's communication-plan template brings together the information description, audience, owner, channel, and frequency. Use those fields to make the delivery arrangement specific. The right frequency follows the recipient's need and the team's working agreement.
Choose Volunteer hosts in the example. The filtered view brings CP3 and its shift-related purpose together. It should still show who prepares the instruction and which change triggers it; the audience name alone is not a complete plan.
Separate a scheduled update from a time-sensitive instruction
Compare these two plans for CP3:
| Version | What it schedules | What the volunteer can rely on |
|---|---|---|
| Weekly-only proposal | Include route changes in the weekly project summary. | No link between that summary and the next affected shift is specified. |
| Revised teaching plan | Send the confirmed route instruction to affected hosts before their next affected shift. | Timing is tied to the work that needs the instruction. |
The example's Compare timing control displays that change. It does not send the instruction, find the affected people, or prove they have read it.
In a real project, confirm who can approve a route change and how much notice the coordinator needs. If a change arrives too late for the agreed communication process, raise that conflict with the project owner. Writing “before the shift” in a table does not solve an impossible deadline.
The weekly sponsor update can remain in the plan. You are adding a different communication for a different need, rather than expecting one large summary to serve every recipient.
Finish the arrangement before drafting the messages
Give every row a clear information owner. If “the project team” appears in that column, ask who prepares the update and who covers an absence. Confirm the channel with the audience instead of assuming a convenient tool reaches everyone.
For recurring communication, record the actual cadence and any meeting or time-zone details needed to follow it. For a triggered communication, name the event and the recipient's action deadline. Keep “when a route changes” separate from “every Friday.” Both can belong in a plan, but they create different work.
Then review the rows together. Do two owners expect to send the same instruction? Is a decision request scheduled after dependent work starts? Does an audience need a different format or an approved restricted channel? Resolve those questions in the plan before producing a polished message.
Keep sending, acknowledgement, and actual decisions in your normal project records. This template plans what should happen. A record of what did happen serves a different purpose.
Copy a prompt for your project's plan
Create one complete HTML project communication plan.
Project scope and period: [PASTE]
Audience groups and the information/actions each needs: [PASTE]
Information owners and backup arrangements: [PASTE]
Confirmed channels and access/format requirements: [PASTE]
Recurring meetings or update cadence, including time zones: [PASTE]
Change triggers, decision deadlines and notification lead time: [PASTE]
Approval and restricted-information rules: [PASTE]
Build rows with stable IDs, audience, information/purpose,
owner, confirmed channel, and cadence or trigger. Use only my
supplied arrangements. Flag a missing owner/channel/timing or
a stated timing conflict as something to resolve. Do not invent
mailing lists, agreed meetings, approvals, response times or sends.
Keep the plan distinct from actual message and acknowledgement logs.
Include this separate original fictional teaching example:
A museum is moving an exhibition into another room.
CP1: Sponsor; milestone changes, spending decisions, choices
needed; project lead; sponsor review meeting; weekly during
the move, with a separate decision request when a choice
cannot wait for that meeting.
CP2: Move team; next handoffs, work sequence and dependencies;
move coordinator; team planning meeting; before each planned
move session, revising the briefing when the sequence changes.
CP3: Volunteer hosts; confirmed entrance, visitor route and
duties affecting their assigned shifts; volunteer coordinator;
agreed volunteer email list; when an approved route/duty change
affects a shift, before that shift begins.
Label channels and roles as supplied fictional arrangements.
No dates, actual mailing list, sent messages or receipts are supplied.
Provide an All audiences view and audience filters. Filtering
must preserve each row's ID, owner, channel and timing. An empty
filter result must say no matching plan rows, not imply no need
for communication. Include a Compare timing control for CP3:
Weekly-only proposal: route changes appear in the weekly project
summary; its relation to the next affected shift is unspecified.
Revised teaching plan: the confirmed route instruction goes to
affected hosts before their next affected shift.
Show both versions and explain the planning difference.
Provide a separate blank scaffold for my actual project. Do not
send, schedule, approve, collect addresses, infer agreement,
or mark a communication complete. No fake integration/export.
Use at least 16px text, labeled native controls, visible keyboard
focus, and labeled records at 360px without horizontal page
overflow. Put CSS and JavaScript in the file, with no external
assets, network or storage. Return the complete HTML and a
list of arrangements that still need the team's decision.
Read the generated rows with the information owners. Check one recurring update and one change-triggered instruction against the actual project schedule. Replace fictional arrangements before putting the plan into use.
Review the plan with the people doing the communication
Put the HTML plan in your NOS workspace when the team needs to read the audience needs and delivery arrangements together. Ask the volunteer coordinator whether CP3 gives enough notice to prepare the shift instruction, and ask the project lead where a late change should be raised.
After agreeing the wording, you can correct the static introduction or audience explanation on the saved page in visual editing mode. Your colleagues can reopen the existing link to read the correction. If the agreement changes a cadence or owner, update the maintained plan and any separately controlled meeting or contact records too.
Give each owner the agreed communication work through the team's usual channel. The reviewed page helps people understand the plan; the owner still has to prepare and deliver the update.