Decision Memos and Briefing Checklists at the U.S. Department of State

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

I. Why Focus Specifically on Decision Memos and Briefing Checklists

Among all State Department written instruments, decision memos and briefing checklists / background papers generate the most friction and confusion.

They are:

closely associated with authority;
often prepared under time pressure;
frequently reused, forwarded, or excerpted;
and easily misused when purpose and structure are unclear.

This document narrows in on these two forms because they sit at the boundary between analysis and authority. Getting them right reduces unnecessary escalation, protects staff judgment, and preserves front office time and clarity.

II. What a Decision Memo Is (and Is Not)

What a Decision Memo Is

A decision memo is a written request for explicit approval, direction, or choice by a named decision owner.

It exists to:

force clarity about what decision is being asked;
surface relevant constraints and tradeoffs;
place responsibility at the correct level;
create an inspectable record that a decision was requested and made.

What a Decision Memo Is Not

A decision memo is not:

a general analytic brief;
a background paper;
a vehicle for surfacing information without a decision point;
a way to transfer responsibility upward without framing a choice.

If no decision is required, a decision memo is the wrong tool.

III. Core Principles of a Strong Decision Memo (FO and Staff Perspectives)

Across State, DoD, DHS, and comparable agencies, effective decision memos share a small set of principles. These principles look different depending on where one sits.

From the Front Office Perspective

Clarity beats completeness. FO time is constrained; unclear decision framing creates delay.
Constraints matter as much as recommendations. FO is accountable for legal, reputational, and political consequences.
Authority must be explicit. FO cannot rely on implication when decisions are later scrutinized.

From the Staff Perspective

Decision framing is a form of protection. A clear memo prevents retrospective reinterpretation.
Surfacing uncertainty is a strength, not a weakness. FO can only weigh what is visible.
Recommendation is optional, clarity is not. Staff judgment can be expressed without presuming approval.

Shared principles:

The decision question is explicit and early.
Authority is clear.
Constraints are surfaced, not buried.
Options are bounded.
Judgment remains human-owned.

IV. A Practical Structure for a State Department Decision Memo

This structure is descriptive, not mandatory. It reflects common practice across bureaus and posts.

1. Header / Routing

TO: Decision owner (COM, D-COM, DAS, etc.)
FROM: Office / section
SUBJECT: Clear statement of the decision

The subject line should already imply a decision (e.g., “Decision on…”).

2. Decision Requested (BLUF)

One short paragraph answering:

What decision is being requested?
Why now?

This is the most important section. If it is unclear, the memo fails.

3. Background / Context (Minimal)

Purpose:

provide only the context necessary to understand the decision;
avoid re-litigating known facts.

Good background answers:

How did this issue arise?
What has already been decided?

4. Key Considerations / Constraints

This section surfaces factors that meaningfully shape the decision:

legal or policy limits;
reputational or signaling concerns;
resource implications;
timing constraints;
interagency or host-government sensitivities.

This is often where FO judgment is most engaged.

5. Options (When Appropriate)

Options need not be exhaustive, but they should be real.

Each option should briefly note:

what it entails;
key pros/cons;
risks or tradeoffs.

Some decisions genuinely have one viable option; stating why alternatives are not viable is sufficient.

6. Recommendation

If staff has a view, it should be stated clearly and respectfully.

The recommendation should:

align with the stated constraints;
not assume approval;
remain separable from the decision itself.

7. Decision Line / Approval Block

A clear space for the decision owner to:

approve;
disapprove;
request modification;
or defer.

This is what converts analysis into authority.

V. Common Decision Memo Failure Modes (Observed)

These are common, rational errors that arise under pressure.

Implied decision: The memo describes action without explicitly asking for approval.
Background creep: Excessive context obscures the decision question.
Hidden constraints: Legal or reputational limits appear only in annexes or footnotes.
Inevitable recommendation: Language suggests the decision has already been made.
Responsibility laundering: The memo shifts risk upward without framing a real choice.

VI. A 60-Second Diagnostic: Is This a Decision Memo?

Before drafting, staff and FO alike can ask:

Is there a specific person who must decide this?
If no, it is not a decision memo.
Would acting without written approval create risk later?
If no, escalation may be unnecessary.
Is there a genuine choice or constraint to surface?
If no, this may be information or briefing.
Can the decision be stated in one sentence?
If not, the issue may not be ready.
Would silence be misinterpreted as approval?
If yes, a decision memo may be protective.

If fewer than two answers are "yes," reconsider the format.

VI. Briefing Checklists and Background Papers

What They Are

Briefing checklists (BCLs), background papers, or info sheets are preparatory tools. They support meetings, calls, travel, or engagements.

They are not decision vehicles unless explicitly paired with a decision memo.

What They Exist To Do

They help principals:

understand the issue quickly;
speak consistently;
avoid surprises;
stay within policy bounds.

VII. A Practical Structure for a Briefing Checklist / Background Paper

1. Purpose of the Engagement

Why is this meeting/call happening?
What does success look like?

2. Key Facts / Context

Essential background only.
Clearly distinguish known facts from interpretation.

3. Objectives

What the principal is trying to achieve.

4. Talking Points

Short, clear, and policy-aligned.
Flag any language that is not yet approved.

5. Sensitive Issues / Watchouts

Topics to avoid or handle carefully.
Likely pressure points or questions.

6. If Asked / Q&A (Optional)

Anticipated questions and safe responses.

VIII. Decision Memo vs. Briefing Checklist: A Simple Distinction

Decision Memo: “Please decide.”
Briefing Checklist: “Please be prepared.”

Confusion arises when one is used in place of the other.

VIII. Annotated Examples (Illustrative)

The following fictional examples illustrate common patterns. They are not templates.

Example A: Strong Decision Memo (Condensed)

Decision Requested: Approval for Ambassador participation in a high-visibility civil society forum.

Why It Works:

Decision is explicit and early.
Reputational and signaling constraints are surfaced.
Recommendation is clear but not presumptive.

FO Lens: Clear authority placement; manageable risk framing.

Staff Lens: Judgment expressed without overreach.

Example B: Misused Decision Memo

What It Looks Like:

Long background on the event.
No explicit decision line.
Action proceeds by default.

What Goes Wrong:

Authority is inferred, not exercised.
Responsibility becomes ambiguous.

Example C: Briefing Checklist That Accidentally Becomes Policy