SPES Operational Handbook — Section 3
Core Workflows (What SPES Actually Does, End-to-End)
Purpose of this section:
Define the repeatable workflows SPES uses to stabilize public engagement across the Mission—especially when multiple sections, platforms, and incentives collide.
These workflows are cross-cutting. They do not belong to PAO alone, nor to any single section.
3.1 Workflow A — Press Incident / Allegation / Media Shock
Trigger Conditions
This workflow activates when any of the following occur:
- A media outlet publishes allegations involving U.S. funding, programs, partners, or policy.
- A journalist requests confirmation or comment on an unverified claim.
- Social media amplification precedes traditional media pickup.
- Local partners signal nervousness or reputational risk.
- Washington asks, “What’s going on?”
Step 1 — Immediate Intake (0–30 minutes)
SPES actions:
- Capture the allegation verbatim (headline, quote, link).
- Identify:
- who is named,
- what is alleged,
- what is implied but not stated,
- what timeframe is referenced.
- Identify the first decision deadline (journalist deadline, Washington call).
Artifact produced:
- Incident Snapshot (½–1 page)
- Allegation summary (neutral language)
- Known facts (sourced)
- Unknowns
- Immediate risks
Failure mode SPES prevents:
Relying on secondhand paraphrase (“they’re saying misuse”) instead of precise claims.
Step 2 — Authority & Ownership Mapping (parallel, 0–30 minutes)
SPES explicitly asks:
- Who owns program facts?
- Who owns press engagement?
- Who owns legal exposure?
- Who owns decision authority right now?
If authority is unclear → SPES flags a risk vacuum.
Artifact produced:
- Authority Map (can be embedded in the snapshot)
- Decision authority
- Risk owners (program, reputational, legal)
- Interim owner if Ambassador unavailable
Mandatory escalation rule:
If no owner is identified within 30 minutes, SPES escalates to DCM with a proposed interim owner.
Step 3 — Claim Discipline Pass (30–60 minutes)
SPES enforces strict separation between:
- verified facts,
- allegations,
- inferences,
- denials,
- unknowns.
SPES blocks language such as:
- “There is no misuse” (unless verified)
- “This is false” (unless disproven)
- “We deny the allegations” (unless authorized)
Artifact produced:
- Claims vs Non-Claims Ledger
- What we can say
- What we must not say
- What we can say later
Step 4 — Holding Language & Silence Analysis (60–90 minutes)
SPES prepares two parallel paths:
- Holding language (if asked)
- Silence justification (if choosing not to respond)
Each includes:
- rationale,
- risks,
- re-evaluation trigger.
Example holding language (generic):
“We are aware of the report and take any allegations seriously. We are reviewing the matter and will provide information when appropriate.”
SPES explicitly notes:
- how this may be interpreted locally,
- how it might be screenshot or quoted,
- how it could conflict with later findings.
Step 5 — Washington Brief (if required)
SPES produces a confidence-safe brief:
- concise,
- caveated,
- non-defensive.
Required structure:
- What happened
- What we know
- What we don’t
- What we’re saying (or not)
- What could change
Failure mode SPES prevents:
Overconfident cables or calls that later require retraction.
3.2 Workflow B — Social Media Escalation
Trigger Conditions
- A post generates disproportionate engagement.
- Comments shift from information requests to allegations.
- Media outlets cite Embassy social posts as official statements.
- Hostile narratives begin clustering.
Step 1 — Post Classification
SPES classifies the post:
- service information,
- public diplomacy narrative,
- policy-adjacent,
- partner-facing,
- commemorative.
Each category carries different risk.
Step 2 — Interaction Quality Scan
SPES reviews:
- top comments by reactions,
- reply depth,
- repeated grievance patterns,
- misinformation vectors.
This is not sentiment scoring; it is interaction typology.
Step 3 — Escalation Decision
SPES advises one of:
- continue monitoring,
- clarify with pinned comment,
- pause engagement,
- coordinate with press guidance,
- remove or edit (with documentation).
Key rule:
Deletion/editing without documentation is institutional risk.
Step 4 — Externalization Check
SPES checks whether:
- local media are quoting the post,
- phrasing is being reinterpreted as policy,
- partner reputations are implicated.
If yes → escalate to PAO/DCM.
3.3 Workflow C — Program Launches, Grants, Agreements, and Events
Trigger Conditions
- Launch of a funded program.
- Announcement of grants, exchanges, purchases, or agreements.
- High-visibility events (especially with politically connected partners).
Step 1 — Narrative Pre-Flight
SPES reviews draft messaging for:
- implied endorsements,
- partner favoritism,
- financial overstatement,
- policy signaling beyond authority.
Step 2 — Alignment Check
SPES ensures consistency across:
- press release,
- social posts,
- speeches,
- American Spaces programming,
- partner messaging.
Misalignment here is a predictable failure mode.
Step 3 — “What This Is / Is Not” Framing
SPES ensures messaging includes:
- what the activity is,
- what it is not,
- what it does not imply.
This protects against later reinterpretation.
3.4 Workflow D — Speeches & Public Remarks
Trigger Conditions
- Ambassador/DCM speeches.
- Remarks at sensitive events.
- Commemorative or values-based statements.
SPES role
SPES does not write speeches by default.
SPES:
- reviews for claim discipline,
- checks against current risk environment,
- flags lines likely to be excerpted.
SPES provides:
- “safe paragraphs,”
- lines to avoid,
- alternate phrasing for sensitive sections.
3.5 Workflow E — Ongoing Monitoring & Pattern Detection
SPES maintains structural awareness, not constant reaction.
Tracked over time:
- topic dominance,
- engagement volatility,
- repeated risk themes,
- silence periods that precede crises.
Artifacts:
- monthly snapshot,
- quarterly pattern memo,
- ad hoc alerts.
Member discussion: