A practical guide for avoiding surprises, missteps, and unowned risk

What this artifact is

This is a staff-facing operational reference that answers one question:

“Before I act, write, speak, or respond — who else needs to be looped in?”

It is not exhaustive policy, and it does not replace judgment.
It is a default escalation and coordination map designed to prevent:

  • accidental policy signaling,
  • clearance failures,
  • unowned risk,
  • and Front Office surprises.

Who this is for

  • FSOs (all cones)
  • LES staff (especially PD, POL, ECON, CONS)
  • New supervisors
  • Anyone drafting, speaking externally, or responding under time pressure

How the work actually functions (process)

Most embassy failures do not occur because someone made a bad decision.
They occur because someone acted alone when the issue crossed section lines.

This matrix assumes:

  • you start in your home section,
  • you identify the issue type,
  • you loop in the minimum necessary sections early,
  • and you escalate further only if risk increases.

Looping someone in does not mean asking permission — it means preventing surprise.

The Matrix (Use This First)

1. Media, Public Messaging, or External Attribution

Examples

  • Press inquiries
  • Public statements
  • Social media posts
  • Public remarks by embassy officials

Loop in

  • PD (always)
  • POL (if political implications)
  • ECON (if economic, trade, sanctions, labor)
  • RSO (if security implications)
  • Front Office (if sensitive or high-profile)

Why
Public statements create institutional positions, not personal opinions.

2. Host Government, Political, or Sensitive Engagement

Examples

  • Meetings with political actors
  • Election-related issues
  • Governance, human rights, protests

Loop in

  • POL (always)
  • Front Office (if senior, sensitive, or ambiguous)
  • PD (if visibility or messaging risk)

Why
Political signaling is often indirect and cumulative.

3. Economic, Trade, Business, or Sanctions Issues

Examples

  • Investment disputes
  • Business advocacy
  • Sanctions-related inquiries
  • Labor or climate-economic overlap

Loop in

  • ECON (always)
  • POL (if political ramifications)
  • Front Office (if reputational or strategic)

Why
Economic actions can quickly become political or bilateral issues.

Examples

  • Security incidents
  • Defense cooperation
  • Civil unrest
  • Emergency planning

Loop in

  • RSO (always)
  • POL/MIL (if defense or military)
  • Front Office (almost always)
  • PD (if public awareness is possible)

Why
Security failures cascade faster than any other category.

5. Consular or Citizen-Facing Issues

Examples

  • Visa inquiries
  • Arrests or deaths of U.S. citizens
  • High-profile ACS cases

Loop in

  • CONS (always)
  • Front Office (if sensitive, high-profile, or political)
  • PD (if media interest)

Why
Consular matters are legally constrained and highly scrutinized.

6. Programs, Grants, or Allegations Involving U.S. Funds

Examples

  • Program complaints
  • Allegations of misuse
  • Partner disputes

Loop in

  • Program section (PD / USAID / ECA)
  • FMO (financial implications)
  • Legal (if available)
  • Front Office (if public or political)

Why
Program issues combine money, optics, and accountability.

7. Internal Staffing, HR, or Workplace Issues

Examples

  • Performance issues
  • Conflicts
  • Misconduct concerns

Loop in

  • HR
  • MGT
  • Front Office (only if escalation warranted)

Why
Improper handling creates legal and morale risk.

Common Failure Patterns (and Corrections)

Failure

“I didn’t think this was political.”

Correction
If a local actor, journalist, or official is involved, assume POL relevance.

Failure

“It was just a draft.”

Correction
Drafts leak. Drafts signal intent. Drafts require judgment.

Failure

“I copied everyone.”

Correction
CC ≠ clearance. Explicit coordination matters.

Failure

“I didn’t want to slow things down.”

Correction
Early looping prevents later freezes.

Scenario Examples (Realistic)

Scenario 1: Routine Event Goes Public

A cultural event attracts political attention online.

Correct loop-in
PD → POL → Front Office
(not after the story runs)

Scenario 2: Journalist Asks an “Economic” Question

The question involves a politically connected business.

Correct loop-in
PD → ECON → POL

Scenario 3: Program Complaint Appears Online

No facts yet, but accusations involve U.S. funds.

Correct loop-in
Program section → PD → FMO → Front Office

What Not to Assume / Not to Do

  • Do not assume your section “owns” the issue alone.
  • Do not assume silence equals approval.
  • Do not wait until after external contact.
  • Do not treat looping in as a sign of weakness.

Bottom Line

If you are unsure who to loop in, that is usually the sign that you should loop someone in.

Early coordination is not bureaucracy.
It is how institutions protect themselves — and you.