Audience: Front Office (FO), section leadership, officers, and LES
Status: Internal reference / training document

I. A Shared Preface for Front Office and Staff

This document is written for both Front Office (FO) and staff, intentionally and explicitly.

It assumes:

  • good faith on all sides;
  • professional judgment exercised daily at multiple levels;
  • and a shared interest in getting the work right without unnecessary friction.

It does not assume:

  • that confusion reflects incompetence;
  • that one side holds the “correct” view;
  • or that alignment requires new rules, approvals, or controls.

Why Both Perspectives Are Included

Front Office and staff operate under different but overlapping risk profiles.

  • Front Office carries ultimate responsibility for decisions, signaling, and institutional accountability. FO risk tends to be retrospective: how a choice will be interpreted later, by Washington, OIG, Congress, or external actors.
  • Staff carry responsibility for analysis, execution, and responsiveness. Staff risk tends to be immediate: acting with incomplete information, under time pressure, with local consequences.

Neither perspective is more legitimate than the other. Both are rational responses to where authority and accountability sit.

Many frictions around decision memos, escalation, and format choice arise not from disagreement about substance, but from misaligned assumptions about risk, authority, and expectation.

What This Document Is (and Is Not)

This document is:

  • a shared reference for how common written instruments function in practice;
  • a way to surface implicit norms and make them discussable;
  • a tool for alignment and training, not enforcement.

This document is not:

  • policy;
  • a checklist;
  • a performance standard;
  • or a critique of existing practice.

The goal is not fewer memos or more memos, but clear authority, appropriate altitude, and mutual understanding.

II. The Core Written Instruments of Daily State Department Operations

Despite variation in format and routing, daily State Department work relies on a small set of recurring written forms. Each exists to solve a distinct institutional problem.

1. Action / Decision Memoranda

What they are
Formal memoranda that explicitly request a decision or approval from a principal (COM, D‑COM, DAS, A/S, Secretary).

Why they exist
To concentrate authority at a clear decision point and create an inspectable record that a decision was requested and made.

How they are used

  • Washington: policy decisions, legal authorities (e.g., Circular 175), resource allocation, deviations from guidance.
  • Embassies: COM/D‑COM approval for sensitive actions, messaging, or resource shifts outside delegation.

When they are appropriate
When explicit approval is required and silence cannot safely be treated as consent.

Key signal
“Decision requested.”

2. Information / Analytic Memoranda

What they are
Concise syntheses of facts, reporting, and analysis that do not request a decision.

Why they exist
To inform leadership, shape situational awareness, and support later decisions without forcing action.

How they are used

  • To brief FO on developments.
  • To surface risks, divergence, or uncertainty early.

Common failure mode
Being treated as de facto decision records through repetition or silence.

Key signal
“For information only.”

3. Briefing Memoranda

What they are
Preparatory documents for meetings, calls, travel, or public engagements.

Why they exist
To ensure message discipline and prevent improvisation under pressure.

How they are used
For Ambassador meetings, senior host‑government engagements, delegations, and public appearances.

What they are not
They are not policy‑setting documents unless paired with an explicit decision memo.

Key signal
“For preparation.”

4. Administrative / Internal Memoranda

What they are
Routine internal correspondence for operational, HR, or administrative actions.

Why they exist
To document actions clearly and reduce reliance on informal or verbal approvals.

How they are used
Everywhere—this is the plumbing of the institution.

5. Memoranda of Conversation (MemCons) / Memoranda to File

What they are
Factual records of conversations or events, capturing participants, dates, and substance.

Why they exist
To preserve institutional memory and protect both individuals and the institution.

What they avoid
Analysis, recommendation, or interpretation.

6. Directives / Policy Memoranda

What they are
Formal instructions establishing or modifying policy (less common at State than DoD, but present via ALDACs, Secretary‑level guidance, etc.).

Why they exist
To standardize behavior and eliminate ambiguity.

7. Cables (State’s Distinctive Instrument)

What they are
Official, archivable communications between posts and Washington that may report, recommend, request, or instruct.

Why they exist
To connect the global Department securely while creating a formal record.

Common risk
Cables being treated as policy or decisions when authority is not explicit.

III. Why Confusion Persists

Confusion arises not because staff or principals misunderstand these tools, but because:

  • multiple tools can describe the same issue from different angles;
  • time pressure incentivizes the fastest format;
  • authority is sometimes inferred rather than stated;
  • accountability risk is asymmetric (especially for LES and junior officers);
  • AI‑generated drafts compress analysis and obscure provenance if not labeled carefully.

Over time, these factors lead to decision inflation, decision avoidance, or format substitution.

IV. Common Failure Modes (Descriptive)

Decision Inflation

Everything becomes a decision memo to avoid later blame.

Decision Avoidance

No decision memo is used; silence or repetition substitutes for approval.

Format Substitution

Analytic briefs, emails, or cables are treated as decision records.

Principal Over‑Correction

Front offices demand memos for issues previously delegated.

Staff Over‑Correction

Staff escalate unnecessarily due to unclear delegation or past experience.

None of these imply bad faith; all are rational responses to risk.

V. A Practical Decision Tree (Shared Diagnostic)

Step 1: Is a Decision Required?

  • Does this require explicit approval?
  • Would acting without written approval create risk?

If no → do not use a decision memo.

Step 2: Who Has Authority?

  • Is authority delegated at section or post level?
  • Is FO or Washington required?

Unclear authority may itself justify a decision memo.

Step 3: What Format Fits the Purpose?

  • Decision required → Action / Decision Memo
  • Information only → Information Memo / Cable
  • Preparation → Briefing Memo
  • Reporting → Cable
  • Documentation → MemCon

Step 4: What Is the Risk of Not Documenting a Decision?

If you would struggle to explain the decision path six months later, escalation may be appropriate.

VI. One‑Page FO–Staff Alignment Summary

Decision Memos Are For:

  • Non‑routine decisions
  • Policy or reputational risk
  • Resource allocation outside delegation

Decision Memos Are Not For:

  • Routine operations
  • Information updates
  • Defensive paperwork

Front Office Values:

  • Clear decision questions
  • Honest uncertainty
  • Appropriate altitude of escalation

VII. Training Scenarios: Typical Embassy Situations and Format Selection

The following scenarios are designed for training and discussion, not as quizzes. Their purpose is to help FO and staff practice format judgment—deciding when escalation is necessary, at what level, and in which written form.

These scenarios reflect common embassy realities where confusion about memos and authority often arises.

Scenario 1: Sensitive Media Inquiry

Situation
A major international outlet contacts the embassy requesting comment on an unfolding political development. Reporting is incomplete, Washington guidance has not yet arrived, and the issue is likely to attract attention.

Appropriate Handling

  • Prepare an Information / Analytic Memo to the COM/D-COM summarizing facts, known unknowns, and possible implications.
  • Include draft talking points only if clearly labeled as not yet approved.
  • Escalate to a Decision Memo only if the COM is being asked to approve a public position or messaging line.

FO Perspective

  • Concerned about reputational signaling and second-order effects of public statements.
  • Needs clarity on what is known vs. uncertain to avoid premature positioning.
  • May prefer early awareness even when no decision is required.

Staff Perspective

  • Operating under time pressure with incomplete information.
  • Concerned that silence or delay may be interpreted externally.
  • Often unsure whether draft language will later be treated as approved.

Common Failure Mode
Treating draft talking points or an analytic summary as an approved policy position.

Scenario 2: Ambassador Meeting with Host-Government Minister

Situation
The Ambassador has a scheduled meeting with a senior host-government official. The agenda includes a sensitive bilateral issue but no obvious policy change.

Appropriate Handling

  • Prepare a Briefing Memo with background, objectives, and talking points.
  • Use a Decision Memo only if the meeting requires approval of a new position, commitment, or concession.

FO Perspective

  • Focused on consistency with existing policy and prior commitments.
  • Wants to avoid being surprised by commitments made in-meeting.

Staff Perspective

  • Aware that conversations can evolve unpredictably.
  • Often tempted to embed guidance implicitly rather than escalate formally.

Common Failure Mode
Embedding a policy shift inside a briefing memo without explicitly flagging it as a decision.

Scenario 3: Resource Reallocation at Post

Situation
A section proposes shifting funds, personnel time, or access from one activity to another due to changing conditions on the ground.

Appropriate Handling

  • If within delegated authority: document internally and inform FO as appropriate.
  • If outside delegation or precedent: prepare an Action / Decision Memo for COM/D-COM approval.

FO Perspective

  • Responsible for overall resource balance and equity across sections.
  • Sensitive to precedents that may affect future allocations.

Staff Perspective

  • Closest to operational realities and immediate tradeoffs.
  • May perceive escalation as slowing necessary adaptation.

Common Failure Mode
Relying on informal email approval that later becomes contested.

Scenario 4: Divergent Section Assessments

Situation
Political and Economic sections interpret the same development differently and recommend different courses of action.

Appropriate Handling

  • Prepare an Analytic Information Memo that explicitly notes divergence and uncertainty.
  • Avoid forcing consensus unless a decision is required.

FO Perspective

  • Needs to understand the range of views before deciding or briefing Washington.
  • Often values transparency about disagreement more than premature alignment.

Staff Perspective

  • Concerned that disagreement may be seen as disorganization.
  • May default to smoothing differences to appear coherent.

Common Failure Mode
Collapsing disagreement into a single narrative for simplicity.

Scenario 5: Ambiguous Guidance from Washington

Situation
Washington sends a cable that suggests a direction but does not clearly instruct post to act.

Appropriate Handling

  • Send a clarifying cable requesting guidance, or
  • Prepare an internal memo documenting post’s interpretation and rationale.
  • Use a Decision Memo only if post proposes to go beyond or reinterpret guidance.

FO Perspective

  • Concerned about alignment with Department intent and interagency equities.
  • Often wary of post-level improvisation being misread.

Staff Perspective

  • Operating under local pressure to act.
  • May read tone or context as implicit approval.

Common Failure Mode
Treating tone or implication as formal instruction.

Scenario 6: External Engagement Opportunity with Reputational Risk

Situation
An external organization invites the Ambassador or D-COM to participate in a high-visibility event that touches on sensitive political themes.

Appropriate Handling

  • Prepare an Action / Decision Memo if acceptance implies endorsement or policy signaling.
  • Prepare a Briefing Memo if participation is already authorized.

FO Perspective

  • Focused on signaling effects and how participation will be interpreted.
  • Sensitive to precedent and external perception.

Staff Perspective

  • May view the invitation as routine or relationship-maintaining.
  • Less attuned to cumulative signaling risk.

Common Failure Mode
Assuming attendance is routine when signaling effects are non-trivial.

Scenario 7: Internal AI-Generated Analytic Draft

Situation
An AI-generated analytic brief is widely circulated internally due to its clarity and speed. No factual errors are identified.

Appropriate Handling

  • Treat the draft as an analytic input, not a decision record.
  • Ensure any adoption of its language into decision documents is explicitly owned by a human role.

FO Perspective

  • Values speed and synthesis but remains accountable for decisions.
  • Concerned about authority being attributed to tools rather than people.

Staff Perspective

  • Appreciates efficiency gains and reduced drafting burden.
  • May assume widespread use implies endorsement.

Common Failure Mode
Allowing repetition to substitute for approval.

These scenarios can be used in onboarding, section meetings, or FO–staff discussions to surface assumptions about authority and escalation.

VIII. Closing Perspective

Decision memos are not a measure of seriousness or trust. They are tools for placing authority at the right moment, in the right format, at the right level.

Effective embassies are not those with more memos or fewer memos, but those where:

  • authority is explicit,
  • formats signal purpose,
  • and staff judgment operates confidently within clear boundaries.

This document is intended to make implicit norms visible—not to impose new ones.