The announcement says a new request form launches next month.
The requester needs to know where to submit. The reviewer needs to know which queue to watch. The fulfillment coordinator needs to know where existing work finishes.
Write the plan around those actions. Give each message a sender, a delivery point, a timing rule, and someone responsible for answering the next question.
Prosci's communication guidance recommends a structured plan with targeted audiences, channels, senders, timing, and feedback. UCSF connects change impact assessment to communication planning. The worksheet and example messages below are proposed editorial methods. They are not either organization's template or a promise of adoption.
Start With a Decision People Can Act On
Consider a fictional team that has approved a move from shared-inbox intake to a request form and queue. The process owner sets the transition for November 16, 2026, at 09:00 UTC. Every date, role, request, and message in this example is synthetic.
The approved rule is specific: requests submitted at or after that time use the form. For this example, submission means receipt by the inbox or queue, using its recorded timestamp. Requests already in the inbox remain there until completion. Reviewers monitor both places during the transition. Fulfillment coordinators complete each request in the system where it began.
The decision does not promise a faster service or change a response commitment. It changes the intake location and the record used to track work. Keep claims about results out of the announcement unless the team has evidence for them.
Put the approved decision at the top of the communication record. Reference the decision owner and version. Use a date in an instruction only after the decision owner confirms it.
Connect the record to the consulting project plan. Project milestones determine when preparation work must finish. The communication record determines what each audience receives about those milestones.
Separate Confirmed Facts From Open Questions
Before drafting messages, make two short lists in the same record. Confirmed facts can appear as instructions. Open questions need an owner and an answer date.
For the fictional change, confirmed facts include the transition time, the boundary for existing requests, and the queue owner's role. The process owner has also confirmed that the form issues a request identifier.
Two questions remain open: which approved help channel will handle access problems, and how requesters without queue access will see completion. Do not invent answers to make the first notice feel finished.
| Item | Current state | Answer owner | Next update |
|---|---|---|---|
| New-request boundary | Confirmed: November 16 at 09:00 UTC | Process owner | Update only if decision changes |
| Existing inbox requests | Confirmed: finish in the inbox | Review lead | Include in every transition reminder |
| Access-help channel | Open: channel not selected | Transition coordinator | Confirm by November 9 |
| Completion visibility | Open: requester view not confirmed | System owner | Confirm by November 9 |
An open question is part of the communication plan. Tell the audience when an answer is due and where the update will appear. If a required answer slips, ask the decision owner whether the transition can still proceed.
Keep a version date beside the lists. A sender should not have to reconstruct current facts from several chat conversations.
Copy This Audience and Message Worksheet
Use one row per message and audience. Several roles can receive the same message when their action and feedback route match. Split the row when either differs.
| Audience | Sender | Message and task | Channel | Timing | Owner | Feedback route |
|---|---|---|---|---|---|---|
| [Affected role] | [Recognized sender] | [Confirmed change and required action] | [Accessible delivery point] | [Date, time zone, and trigger] | [Person maintaining this row] | [Question destination and answer owner] |
| Requesters | Process owner | Submit new requests through form at or after boundary; retain identifier | Team email with current record reference | November 9, after open questions resolve | Transition coordinator | Process owner through agreed question thread |
| Reviewers | Review lead | Monitor queue and inbox; retain existing inbox work | Review-team briefing and written record | November 12, before coverage confirmation | Review lead | Review lead's question thread |
| Fulfillment coordinators | Fulfillment lead | Complete requests in their original system | Written handoff in team workspace | November 12, after procedure approval | Fulfillment lead | Fulfillment lead through handoff record |
Sender and owner answer different questions. The sender communicates the decision. The owner keeps the message row accurate and tracks the reply. One person can hold both responsibilities, but record that choice.
Choose channels each audience can access during normal work. Confirm that the linked record opens for recipients before treating it as the source of instructions. A message pointing to an inaccessible page leaves the action unresolved.
Keep the worksheet small enough to maintain. Link the approved procedure for detailed steps. Repeat the transition boundary in the message itself so the reader can identify which work it covers.
Draft the Advance Notice From Confirmed Facts
Suppose the fictional owners resolve both open questions on November 9. They select an existing team help thread for access questions. They confirm that requesters receive completion information in the form's confirmation view.
Those details now enter the record as approved facts for this invented workflow. They do not describe a real product's capabilities. Check the actual configuration before using similar language.
The process owner can now draft this requester notice:
Example advance notice. Not sent.
New service requests use the request form from November 16, 2026, at 09:00 UTC. The current transition record contains the form location and instructions.
Requests already in the shared inbox stay there until completion. Do not submit those requests again.
Retain the identifier shown after submission. The confirmation view provides completion information.
Post access questions in the team help thread referenced in the transition record. The process owner collects procedure questions there. The next clarification is due November 12.
This notice states the action, boundary, and question route. It avoids saying everybody is ready. It also avoids asking requesters to interpret a project status report before finding the submission rule.
Before delivery, check the draft against the approved facts. Then confirm the audience, sender, channel, and current record reference. A communication plan can hold a proposed message without authorizing anyone to send it.
Give the Transition-Day Reminder One Job
The transition-day reminder should help the reader choose the right action now. Keep background explanation in the advance notice and reference record.
Use a distinct reminder for reviewers because their responsibility covers both intake paths. In this fictional example, their reminder reads:
Example transition-day reminder. Not sent.
From 09:00 UTC today, November 16, new requests use the form and queue. Review the queue for new submissions.
Continue reviewing requests that began in the shared inbox. Those requests finish there. Do not create duplicate queue records for them.
The review lead owns coverage questions. Record unresolved cases in the review-team question thread. The next review of transition questions is at 15:00 UTC today.
The requester receives a shorter reminder focused on submitting and retaining the identifier. The fulfillment coordinator receives the original-system completion rule. Keep those messages in their own rows with their own evidence of delivery.
Do not insert a new requirement into a reminder because it seems helpful. Route a proposed rule to the process owner. Update the approved record before presenting that rule as an instruction.
Keep Delivery, Acknowledgement, Understanding, and Use Separate
A sent message establishes a recorded sending event. It does not establish that the recipient understood the transition. Define the evidence you intend to collect before labeling a row complete.
For this worksheet, use four distinct evidence fields:
| Evidence type | Example record | What remains unknown |
|---|---|---|
| Delivery | Notice appears in the agreed channel with recipient access confirmed | Whether each intended recipient saw it |
| Acknowledgement | Reviewer confirms receipt of the current notice | Whether the reviewer can apply its boundary |
| Understanding | Reviewer describes where a pre-transition request remains | Whether ordinary work follows that rule |
| Observed use | An authorized process review finds a new request in the queue | Whether other requests follow the rule |
These are proposed evidence distinctions. They are not product analytics definitions or a training scorecard. An opened email supplies no direct observation of request routing.
Keep observations narrow. One correctly routed request supports a statement about that request. It does not justify “the team has adopted the workflow.” Note the reviewed period and sample boundary when recording observed use.
Do not turn communication follow-up into learner evaluation. When someone reports missing access, assign the access problem. When the procedure is unclear, assign the wording decision. Keep the communication owner responsible for a clear answer and its distribution.
Publish a Clarification Without Inventing a New Rule
Suppose a fictional requester asks whether an inbox request submitted before the boundary should be resubmitted after a reviewer asks for missing information. The approved original-system rule already answers that question.
The process owner can draft a follow-up clarification:
Example follow-up clarification. Not sent.
A request received in the shared inbox before November 16 at 09:00 UTC remains there, including replies that provide missing information. Do not submit it again through the form.
Requests submitted at or after the boundary use the form. This clarification restates the approved rule. The transition date is unchanged.
The process owner added this answer to the current transition record. Bring unresolved boundary questions to the same team help thread. The next question review is November 17 at 15:00 UTC.
Add the question and accepted answer to the existing record. Record who confirmed the interpretation. The clarification should point readers toward one maintained answer.
Use asynchronous communication practices to make the decision retrievable after the conversation ends. Keep private request contents outside a broad team question thread. A generic boundary question can be answered without copying the underlying request.
Update the Same Record When a Date Changes
Now consider an alternative branch of the fictional scenario. Before transition day, the process owner moves the boundary from November 16 to November 18 at 09:00 UTC. This branch replaces the earlier date; both schedules do not apply together.
Change the confirmed-facts list first. Preserve the old date in a short revision entry. Record the authorizing role, decision time, reason supplied by the owner, affected messages, and current date.
Then review every unsent row. Move the reminder. Check reviewer coverage and fulfillment instructions against the revised boundary. Do not silently assume the same people remain available.
For notices already delivered, create a correction row identifying the recipients who received the old date. State the replacement date and whether any other rule changes. Keep the superseded notice's delivery record so the owner can see who needs the correction.
An unanswered question follows the same discipline. If completion visibility remains unconfirmed on November 9, preserve its open status. Record the missed answer date and next review. Ask the process owner whether that gap changes the transition decision.
Do not release a reminder that describes a blocked or replaced plan as current. A row marked ready yesterday needs another check when its controlling fact changes.
Hand Follow-Up to a Named Owner
Choose a review point after the transition. At that review, inspect unanswered questions, corrections still needed, and the limited evidence available about use. State what remains unknown.
Assign ongoing procedure questions to the process owner. Assign system-access questions to the designated help owner. Give unresolved requests an owner through the ordinary workflow rather than leaving them in the announcement thread.
The operations handover record can carry those responsibilities after transition coordination ends. Include the current procedure, the question route, and any unresolved boundary decision.
Close a communication row when its agreed delivery and follow-up work is complete. Keep broader workflow readiness and adoption claims outside that status. A message can be delivered while an access problem remains open.
Keep the next action clear.
Sources
- Prosci: 5 Steps to Better Change Management Communication + Template. Structured audience-specific planning, senders, channels, timing, and feedback. Checked 2026.10.28.
- UCSF Product Toolkit: Change Impact Assessment. Impact findings as inputs to change and communication planning. Checked 2026.10.28.