When awareness becomes action, and action becomes institutional risk


What this appendix is

This appendix is a mechanical escalation reference for Public Diplomacy staff.

It answers a narrow but critical question:

At what point does “keeping an eye on something” become an obligation to escalate, coordinate, or formalize reporting?

It does not replace judgment.
It exists to prevent hesitation, normalization, and risk drift under pressure.


Who this is for

  • PD FSOs and LES
  • PD supervisors
  • Front Office staff reviewing PD workflow
  • Trainers and mentors

How to use this appendix

Use this as a tripwire system, not a checklist.

If any one threshold is crossed:

  • pause informal handling,
  • document,
  • and escalate to the appropriate level.

Multiple thresholds crossed simultaneously = do not improvise.


Core Escalation Principle

Escalation is not about severity.
It is about trajectory, attribution, and ownership.

Most failures happen because staff wait for certainty that never arrives.


Threshold Category 1: Repetition

Trigger

  • The same question, allegation, or topic arises more than once.
  • Different contacts raise the same issue independently.

Why this matters

Repetition signals:

  • narrative formation,
  • coordination,
  • or testing of embassy response.

Required action

  • Document in email (if not already).
  • Loop in supervisor.
  • Assess whether pattern exists.

Do not assume coincidence.


Threshold Category 2: Attribution Language Appears

Trigger

Contacts use phrases like:

  • “the embassy believes…”
  • “U.S. officials say…”
  • “according to diplomatic sources…”

Why this matters

Attribution language:

  • creates perceived authority,
  • hardens narratives,
  • and can precede misquotation.

Required action

  • Stop informal engagement.
  • Clarify what has not been said.
  • Coordinate with supervisor and POL.
  • Consider holding language.

Threshold Category 3: Platform Shift

Trigger

An issue moves:

  • from social media → mainstream media,
  • from local outlet → national outlet,
  • from private inquiry → public reporting.

Why this matters

Platform shifts dramatically increase:

  • audience size,
  • reputational exposure,
  • and speed of escalation.

Required action

  • Flag immediately to supervisor.
  • Assess whether cable threshold is met.
  • Loop in Front Office if sensitivity is high.

Threshold Category 4: Cross-Sectional Relevance

Trigger

The issue touches:

  • consular cases,
  • political actors,
  • security forces,
  • economic actors,
  • or U.S.-funded programs.

Why this matters

Cross-sectional issues:

  • distribute risk unevenly,
  • require shared ownership,
  • and fail when siloed.

Required action

  • Identify all implicated sections.
  • Initiate coordination explicitly.
  • Do not allow PD to absorb substantive risk.

Threshold Category 5: Time Compression

Trigger

  • External deadlines are imposed.
  • “We need a response today.”
  • “Washington is asking.”

Why this matters

Time pressure:

  • encourages premature certainty,
  • bypasses clearance,
  • and manufactures authority.

Required action

  • Slow language, not response.
  • Use provisional framing.
  • Name authority gaps explicitly.

Threshold Category 6: Requests for Confirmation

Trigger

Contacts ask:

  • “Can you confirm…?”
  • “Is it true that…?”
  • “Are you aware of…?”

Why this matters

“Confirmation” is often treated as validation.

Required action

  • Distinguish awareness from verification.
  • Avoid repeating unverified claims.
  • Coordinate before responding.

Threshold Category 7: Internal Discomfort

Trigger

You feel:

  • uneasy about responding,
  • unclear about authority,
  • pressure to reassure,
  • or fear of overstepping.

Why this matters

Discomfort is often the first signal of misaligned risk.

Required action

  • Pause.
  • Escalate internally.
  • Document concerns.

Instinctive hesitation is information.


Threshold Category 8: Washington Interest

Trigger

Washington asks:

  • “What is post’s view?”
  • “What’s the embassy position?”
  • “Do you recommend X?”

Why this matters

This is a shift from observation to institutional representation.

Required action

  • Clarify authority.
  • Move from email to cable if not already done.
  • Ensure Front Office awareness.

Threshold Category 9: External Actors Invoke the U.S.

Trigger

Local actors say:

  • “The U.S. supports…”
  • “The embassy agrees…”
  • “Washington is concerned…”

Why this matters

False invocation creates reputational and diplomatic exposure.

Required action

  • Document immediately.
  • Coordinate corrective language if needed.
  • Assess need for formal reporting.

Threshold Category 10: Silence Becomes Interpretable

Trigger

Lack of response is framed as:

  • agreement,
  • indifference,
  • or confirmation.

Why this matters

Silence is not neutral once narratives harden.

Required action

  • Evaluate whether silence still protects.
  • Coordinate whether limited response is safer.

Quick Reference: Escalation Ladder

SignalInstrumentAudience
First probeEmailSupervisor
Pattern formingEmail + coordinationSection leads
Media coverageCableWashington
Attribution pressureCable + FOInstitution
Authority gapDocument + pauseProtection

What Not to Do

  • Do not wait for proof to escalate awareness.
  • Do not escalate emotionally; escalate structurally.
  • Do not allow PD to become sole risk holder.
  • Do not improvise language under pressure.

Bottom Line

Escalation is not failure.
Delayed escalation is.

This appendix exists to give PD staff:

  • permission to pause,
  • language to escalate,
  • and structure to protect themselves and the institution.

If escalation feels awkward, that is often because it is necessary.