Judgment, escalation, and clarity under routine pressure

What this artifact is

This is a hands-on training exercise that uses a realistic embassy email scenario to practice:

  • eliminating ambiguity,
  • making escalation explicit,
  • clarifying next steps,
  • and protecting the institution through ordinary communication.

Unlike cables, emails:

  • move faster,
  • are less reviewed,
  • and are more likely to create silent failure.

That makes them higher risk than they look.

Who this is for

  • FSOs (especially new officers)
  • LES drafting or summarizing contact calls
  • Supervisors coaching communication discipline
  • Anyone who sends emails “just to inform”

Scenario Context (Given to the Drafter)

You are a PD staff member.

You receive a phone call from a trusted journalist contact.
The contact mentions:

  • an upcoming protest,
  • possible embassy mention in local coverage,
  • and rumors involving a U.S.-funded NGO.

The contact is not hostile, but clearly probing.

You draft a quick email to your supervisor before leaving for another meeting.

❌ The Weak Email (Original)

Subject: Call with media contact

Hi,

I spoke earlier today with one of our media contacts who mentioned there may be some developments coming up related to a protest this weekend. He also said there could be some mention of the embassy in connection with an NGO we’ve worked with before. It’s not clear yet how serious this is, but I told him thanks and we'll be keeping an eye on things.

Thanks,
[Name]

Step 1: Diagnose the Failures (Before Rewriting)

Ask these questions:

  • Who called? When?
  • What protest? Where? Why?
  • What does “mention of the embassy” mean?
  • What was actually said to the contact?
  • Who needs to know?
  • What happens next?

Identified failures

  • Vague subject line
  • No time anchor
  • No identification of the contact’s influence
  • Passive language (“may be,” “could be”)
  • Unclear what was said on behalf of the embassy
  • No escalation or next step
  • No indication of risk or urgency

This email creates awareness without responsibility, which is dangerous.

Step 2: Clarify the Purpose

Purpose of the email:
To inform a supervisor of a potentially sensitive media probe and enable timely decision-making about escalation and messaging.

The email should allow the supervisor to decide:

  • whether to loop in POL, FO, or others,
  • whether to prepare holding language,
  • whether follow-up is needed now.

Step 3: Rewrite the Subject Line

❌ Weak

Call with media contact

✅ Improved

Media Contact Flags Potential Embassy Reference in Upcoming Protest Coverage

Why this works

  • Signals relevance
  • Indicates risk
  • Encourages prompt reading

Step 4: Rewrite the Body (Step-by-Step)

A. Add Time, Source, and Context

Replace vague opening with:

This afternoon (March 7), I received a phone call from [Outlet]-affiliated journalist [Name], a regular embassy contact with national reach.

Why:

  • Time matters
  • Credibility matters
  • Scope matters

B. State What Was Actually Said (Precisely)

Replace “mentioned there may be developments” with:

He said his outlet is preparing coverage of a planned protest this weekend and asked whether the embassy was aware of claims circulating online linking the protest organizers to a U.S.-funded NGO.

Why:

  • Removes ambiguity
  • Distinguishes rumor from reporting
  • Protects against misremembering later

C. Clarify What You Said (Institutional Protection)

Replace “I told him we were aware and keeping an eye on things” with:

I responded that I had no information to confirm those claims and that the embassy does not comment on unverified reports.

Why:

  • Documents what was said
  • Avoids implying acknowledgment or endorsement
  • Protects the institution if quoted later

D. Surface Risk and Next Steps Explicitly

Add:

Given the potential for media attribution and political sensitivity, this may warrant coordination with POL and preparation of holding language if coverage materializes.

Why:

  • Moves from “FYI” to decision support
  • Makes escalation optional but visible

✅ Revised Strong Email (Complete)

Subject: Media Contact Flags Potential Embassy Reference in Upcoming Protest Coverage

Hi [Name],

This afternoon (March 7), I received a phone call from [Outlet]-affiliated journalist [Name], a regular embassy contact with national reach.

He said his outlet is preparing coverage of a planned protest this weekend and asked whether the embassy was aware of claims circulating online linking the protest organizers to [a U.S.-funded NGO] we have previously worked with.

I responded that I had no information to confirm those claims and that the embassy does not comment on unverified reports.

Given the potential for media attribution and political sensitivity, this may warrant coordination with POL and consideration of holding language if coverage expands. Please advise on next steps or if you would like me to loop in other sections.

Best,
[Name]

Step 5: What Changed (Explicitly)

  • Ambiguity → specificity
  • Passive voice → active documentation
  • “Flagging” → decision support
  • Personal reassurance → institutional discipline

Common Email Failure Patterns This Exercise Exposes

  • “Just flagging” without ownership
  • Using vagueness to avoid responsibility
  • Failing to document what was said externally
  • Not signaling escalation pathways

How to Use This Exercise in Training

  • Give only the weak email to participants.
  • Ask them to rewrite just the subject line first.
  • Then rewrite the first paragraph.
  • Stop before “next steps.”
  • Compare versions and discuss escalation clarity.

Bottom line

Most institutional failures do not start with bad policy.
They start with emails that hide risk behind politeness.

A good operational email:

  • documents facts,
  • protects the institution,
  • and enables decisions.

If the email does not help the reader decide something,
it is not finished.