AI Field Manual
FM-PM-06 · Guide

Project Management  ·  Intermediate

Adapt one hard message for a sponsor, a team and a vendor

The go-live is slipping four weeks. The sponsor needs to approve a revised date, the team needs to know what changes for them, and the vendor needs to hear that their late delivery caused it, without the relationship collapsing. That's three messages with three purposes. If the facts differ between them, by even one date, someone will notice.

Status
Published
Reading time
About 12 minutes
You'll need
The verified facts of the change, what you need from each audience, the relationship context, and an approved AI assistant
Last reviewed
November 2026
Before you start

What AI is for here, and what it isn't

Hard messages fail in two ways: the facts are wrong or inconsistent, or the tone makes the reader defensive. AI helps with both if you use it in the right order. It's good at taking one set of facts and adapting framing, detail and vocabulary to each audience's concerns, and at checking that all versions still say the same thing.

What it can't judge is the relationship. It doesn't know that the sponsor hates being surprised in front of their peers, that the vendor's account manager is an ally against their own delivery team, or that this team has already absorbed two slips and morale is thin. It also can't decide what you ask for. The ask, the timing, and anything you'd only say in person stay with you.

Step 1

Write the facts once

Before writing any message, write a short fact sheet. Every message will come from it, and nothing that isn't on it goes into any message.

  • What changed: stated plainly. "Go-live moves from 3 March to 31 March."
  • Why: the cause, as far as it's verified. Separate confirmed facts from your working explanation.
  • Impact: on dates, budget, scope and people.
  • What's being done: the recovery plan, with owners and dates.
  • What you need: from each audience separately.
  • What you don't know yet: stated honestly, with when you'll know.

Get the facts checked by someone else before you write the messages. The most damaging error in a hard message is a wrong number that has to be corrected the next day.

Step 2

Decide what each audience needs

For each audience, write one line each for: what they care about, what they need to decide or do, and what would make them defensive.

Audience What they care about What you need What makes them defensive
Sponsor Business impact, their credibility upward, options A decision on the revised date Surprise, options presented as fait accompli, blame-shifting
Team What changes for their work, whether this reflects on them Re-planning input, continued focus Vague reassurance, hints of blame, being told last
Vendor The relationship, contractual exposure, their reputation A recovery commitment with dates Public blame, threats before facts, surprise escalation

This takes five minutes and does more for the messages than any amount of wording.

Step 3

Draft the three versions from one source

The multi-audience message prompt
You are helping a project manager communicate a difficult change.
Use ONLY the facts in the fact sheet. Every version must state the
same dates, amounts and causes. Do not add facts, reassurance or blame.

FACT SHEET: [paste]
AUDIENCE NOTES: [paste the table from Step 2]
CHANNEL FOR EACH: [e.g., sponsor: email before a call; team: message
before stand-up; vendor: email to account manager]

DRAFT three messages:
1. SPONSOR: lead with the change and its impact, then the options and
   a recommendation, then the decision needed and its deadline.
2. TEAM: lead with what changes for them, then why, then what happens
   next and how they'll be involved. Acknowledge the extra effort.
3. VENDOR: lead with the facts of the impact and the dependency on
   their delivery, then the recovery commitment needed with dates.
   Factual and firm, not accusatory.

THEN produce a CONSISTENCY TABLE: every date, number and causal claim,
and how each version states it. Flag any difference.

RULES: No adjectives that assign blame ("unacceptable", "failed to").
No promises not in the fact sheet. Plain language. Keep each message
under 200 words.

The consistency table is the safeguard. Read it before you read the messages.

Step 4

Review for tone, then sequence the sends

Read each message as its recipient would, on a phone, between meetings, already stressed. Then check:

  • Does the first sentence say what changed? Burying the news under context makes people suspicious.
  • Is there exactly one ask, with a deadline?
  • Would you be comfortable if the message were forwarded? Especially the vendor one. Assume it will be.
  • Is anything in it better said in person? If a message would land as a shock, call first and send the written version as follow-up.

Then decide the order. The usual rule: the sponsor hears it first, before anyone they might hear it from. Then the team, then external parties. Nobody should learn about a change affecting them from someone else's forwarded email.

Step 5

Worked example: the four-week slip

Fictional project. A CRM migration's go-live moves from 3 March to 31 March. The integration vendor delivered the interface build three weeks late, and testing needs four weeks that can't be compressed. The fact sheet also records that the budget impact is about 6% for extended vendor and contractor time, still being confirmed.

A model given only "tell the sponsor, team and vendor about the delay" produces a sponsor email that opens with "Unfortunately, due to circumstances beyond our control…", a team message that says "this is not a reflection on anyone," and a vendor email that calls the delivery "unacceptable." Each one has a slightly different explanation for the delay.

With the fact sheet and the prompt above, the sponsor version opens:

Go-live moves to 31 March: decision needed by Friday

The CRM go-live can't hold 3 March. The integration build arrived three weeks late, and testing needs four full weeks; compressing it would mean going live with untested payment interfaces. I recommend 31 March. The budget impact is around 6% for extended vendor and contractor time, which I'll confirm by Wednesday. I need your approval of the new date by Friday so we can tell the sales team before their March planning. I've put 20 minutes in your calendar tomorrow to go through the options.

The consistency table shows all three versions giving the same dates, the same cause, and "around 6%, confirming by Wednesday." The project manager notices the vendor version mentions the budget figure. That's a commercial detail they'd rather discuss on a call, so they remove it, and the table is checked again.

Step 6

Send, then follow up

Send in the order you decided, close together so nobody hears second-hand. Then follow up: confirm the sponsor's decision in writing, update the plan and status report the same day, and log the change in your change record.

Change communication fact sheet
Change ID / date:          [ID] — [date]
What changed:              [plain statement]
Confirmed cause:           [facts]
Working explanation:       [labelled as such, if any]
Impact:                    dates [old → new] | budget [amount or %,
                           confirmed or estimate] | scope [items] | people [who]
Recovery plan:             [actions — owner — date]
Asks:                      sponsor [decision, by date] | team [input] |
                           vendor [commitment, by date]
Unknowns:                  [what — when we'll know]
Send order and channel:    1. [audience, channel, time]  2. [...]  3. [...]
Said in person, not in writing: [items]
Reviewed by:               [name] — [date]

What stays with you: the timing, the ask, the relationship, and anything you'd only say in person.

Esc

Saved in this browser

Reading list

Contents

Reference

Keyboard shortcuts

/ or Ctrl K
Search the manual
↑ ↓
Move through search results and index entries
Enter
Open the selected result
← →
Switch discipline tabs; previous / next entry in a workflow card
Esc
Close any dialog
?
Show this list