When an email becomes a cable — and when silence becomes risk
What this artifact is
This is a multi-day escalation timeline exercise designed to train judgment about:
- when to communicate,
- how to communicate (email vs cable),
- when to escalate, and
- how risk accumulates when nothing changes — or when too much is said too early.
It reflects how many real embassy issues unfold:
- not as single crises,
- but as slow-burn situations with accumulating signals.
Who this is for
- FSOs (especially POL, PD, ECON)
- LES staff who surface early warning signs
- Supervisors deciding when to formalize reporting
- Trainers running tabletop or onboarding exercises
How to use this exercise
Participants should work day by day.
At each stage, they must decide:
- What is known vs unverified?
- What instrument is appropriate now?
- Who needs to be looped in?
- What must be documented to protect the institution later?
There is no single “correct” outcome — but there are clearly unsafe paths.
Scenario Overview (Day 0)
Underlying issue:
Growing online allegations link a planned protest to a U.S.-funded NGO.
At the outset:
- no mainstream media coverage,
- no verification,
- no official inquiries,
- but clear political sensitivity.
DAY 1 — Initial Signal (Low Visibility)
What happens
- PD receives a phone call from a journalist probing embassy awareness.
- Allegations remain confined to social media.
- No deadline is given.
Correct institutional response
Primary instrument:
✅ Internal email to supervisor
Purpose:
- Document contact
- Protect institution by recording what was said
- Enable supervisory awareness
Actions taken
- PD emails supervisor with specifics
- No external response
- No cable yet
Common failure modes
- Ignoring the call
- Responding casually without documentation
- Drafting a cable prematurely (over-escalation)
DAY 2 — Signal Reinforcement (Still Limited)
What happens
- A second journalist asks a similar question.
- A local activist reposts allegations.
- Still no mainstream coverage.
Decision point
Is this noise, or pattern?
Correct institutional response
Primary instruments:
✅ Follow-up internal email
✅ Section-level coordination (PD ↔ POL ↔ Program)
Purpose:
- Identify pattern
- Share awareness internally
- Prepare, not react
Still no cable, but supervisors should be aware this may escalate.
Common failure modes
- Treating each inquiry as isolated
- Over-reassuring internally (“this will go away”)
- Drafting holding language too early
DAY 3 — Media Breaks (Threshold Crossed)
What happens
- A mid-tier national outlet publishes a story.
- Social media amplification increases.
- Embassy is named indirectly.
Decision point
This is no longer just internal awareness.
Correct institutional response
Primary instruments:
✅ Holding language drafted (not necessarily released)
✅ First reporting cable
Purpose of the cable
- Alert Washington
- Preserve institutional memory
- Explain why this matters now
Cable characteristics
- Neutral tone
- Clear distinction between allegation and verification
- Assessment of trajectory
Common failure modes
- Waiting for “better facts”
- Issuing a public denial without review
- Sending an email summary to Washington instead of a cable
DAY 4 — Escalation Pressure (Authority Tested)
What happens
- Washington asks: “What is the embassy’s position?”
- Local officials reference the story.
- Journalists seek confirmation or denial.
Decision point
Authority and attribution are now central.
Correct institutional response
Primary instruments:
✅ Updated cable with assessment
✅ Internal authority clarification
✅ Controlled external holding language (if required)
Key requirement
- Explicitly note what is interim
- Name authority gaps if leadership unavailable
Common failure modes
- Manufacturing certainty
- Letting PAO absorb all risk
- Treating silence as neutral
DAY 5 — Resolution or Reframing
What happens (two possible paths)
Path A — Allegations fade
- Coverage drops
- No new facts emerge
Path B — Allegations deepen
- New claims
- Political actors engage
- Congressional or interagency interest
Correct institutional response
Either path requires:
- Final cable documenting outcome
- Clear internal record of decisions taken
- Assessment of lessons learned
Silence without documentation is still failure.
Summary Table: Instrument by Day
| Day | Situation | Cable | Public Language | |
|---|---|---|---|---|
| 1 | First probe | ✅ | ❌ | ❌ |
| 2 | Pattern forming | ✅ | ❌ | ❌ |
| 3 | Media coverage | ⚠️ | ✅ | Draft only |
| 4 | Attribution pressure | ⚠️ | ✅ (update) | Possibly |
| 5 | Resolution | ❌ | ✅ (final) | If needed |
What this exercise teaches
- Escalation is cumulative, not binary
- Emails protect today; cables protect tomorrow
- Waiting too long and speaking too early are equally dangerous
- Institutions fail when signals are treated as noise
What not to assume / not to do
- Do not assume one quiet day resets risk
- Do not treat emails as substitutes for cables
- Do not let uncertainty justify inaction
- Do not let urgency justify fabrication
Bottom line
Most embassy crises are not explosions.
They are missed transitions.
This exercise trains the judgment to recognize:
- when a situation has crossed a threshold,
- and when the institution must change how it speaks.
Member discussion: