SPES Operational Handbook — Section 1

Role & Boundaries (What SPES Is, What SPES Is Not, and How to Behave When Everyone Wants “More”)

Audience: incumbent SPES; PD leadership; PAO/A-PAO; incoming supervisors; interagency section chiefs
Purpose of this section: stop role drift, stop silent risk transfer, and make the job executable under real mission conditions.

1.1 SPES in one sentence (operational, not aspirational)

SPES is the mission’s public-engagement integration and decision-support function: you take fragmented activity (press, digital, exchanges, spaces, outreach, section events), convert it into usable institutional situational awareness, and provide bounded, claim-disciplined guidance that helps leadership decide what to say, what not to say, and when to escalate.

You are not “the communicator.” You are the coherence layer.

1.2 What SPES “owns” (deliverables and obligations you can be held accountable for)

SPES owns outputs and connective tissue, not program execution.

A) Outputs SPES owns (you are responsible for producing and maintaining)

  1. Leadership Snapshot (1 page, recurring)
  • Scale + cadence: posting rates, engagement baselines, notable spikes
  • Top narrative categories (what we are actually saying repeatedly)
  • Activation outliers (posts/events that generate disproportionate reaction)
  • 3–5 “risk archetypes” observed (patterns, not people)
  • “Claim discipline” flag: where our language is being treated as policy position
  1. Narrative Architecture & Drift Report (quarterly or incident-driven)
  • Topic distribution over time
  • What we amplify vs what we ignore
  • Where silence creates rumor-fill risk
  • Repeating frames that imply policy commitments we do not intend
  • Cross-surface alignment: speeches ↔ posts ↔ press lines ↔ exchange stories
  1. Risk Register + Decision Rules (living document)
  • Predictable failure modes and triggers
  • Escalation thresholds (when to pull in Legal/DCM/Front Office/Washington)
  • Holding language templates by risk type
  • “Never say / don’t confirm” categories for social and press
  • Authority map: who clears what, and who is risk owner for which domain
  1. Interaction Quality Dossier (monthly/quarterly, plus crisis addenda)
  • Comment and engagement taxonomy (info requests / grievance loops / misinformation claims / hostile mobilization / service-queue dynamics)
  • De-identified examples of each pattern
  • Thread escalation curves (how quickly things become brittle)
  • “Brittleness indicators” (repeated claims that recur regardless of response)
  1. Exchanges & American Spaces footprint integration (pulse reports)
  • What programs exist (Fulbright/IVLP/others), what sector mix, what geographies
  • Alumni re-engagement mechanisms (events, speakers, mentorship)
  • Safe “impact signals” (aggregate, non-causal)
  • How Spaces/exchanges contribute to narrative architecture and audience reach
  • Risks: elitism perceptions, favoritism allegations, political labeling risk
  1. Press surface brief (weekly or as needed)
  • What narratives journalists are pushing
  • What outlets treat as “Embassy confirmation”
  • Pickup patterns: what gets quoted from our posts or lines
  • Recommended “attribution-safe” language patterns (3–5)

B) Obligations SPES owns (how you must behave)

  • Maintain claim vs non-claim discipline in any product you circulate
  • Maintain traceability (what you relied on, even if not formally cited)
  • Maintain boundedness: you flag risks and options; you do not decide
  • Maintain integration: your job is to connect, not to perfect one lane
  • Maintain non-attributional handling of internal concerns (especially LES)

1.3 What SPES does not own (and must not quietly absorb)

This is where Missions fail: SPES becomes the “catch-all” for everything public and everyone’s anxiety.

SPES does not own:

A) Program execution

  • selecting participants
  • running events
  • contracting/procurement
  • grant monitoring and compliance
  • partner management
  • implementing exchange logistics
    Owner: program officers / PD sections / grants staff / implementing partners

B) Clearance authority or “approval”

  • final sign-off on public lines
  • legal clearance
  • policy clearance
  • Washington clearance
    Owner: PAO/Front Office/Legal/Washington channels as applicable

You may recommend. You may flag. You do not approve.

C) Individual-level profiling

  • commenter identity analysis
  • political affiliation inference
  • education/profession inference at person level
  • “who our audience really is” as demographic certainty
    Owner: nobody should be doing this without authorized, aggregated tools and purpose. SPES does aggregate-only.

D) Owning contact lists (names, personal data)

You can maintain topology (tiers, beats, outlet categories, relationship status in non-PII terms).
You do not become the human repository of journalist names and personal details.
Owner: press team / PAO systems.

E) Becoming the “social media manager”

You may shape decision rules and risk posture. You do not become the daily poster unless assigned that role separately.
Owner: digital team.

F) Becoming the “writer of everything”

If you become the default drafter for all speeches, posts, press lines, you will lose the integration function.
SPES supports writing discipline and provides templates; others draft their lanes.

1.4 SPES boundary phrases (what to say when people push you to overstep)

These are scripts you can use without sounding evasive.

When asked: “Can you approve this?”

“I can’t approve. I can flag claims, risks, and what needs clearance. Approval sits with PAO/Front Office.”

When asked: “Just give us something confident” (with incomplete facts)

“I can give you a confident structure and a bounded position statement, but I will mark what is not verified. Confidence without verification becomes a liability.”

When asked: “Can you own the fallout if this goes wrong?”

“I don’t hold institutional authority to own fallout. What I can do is make the risk legible and ensure the right risk owner is named before release.”

When asked: “We need a quick one-pager, no caveats.”

“I can deliver a one-page brief, but removing caveats when facts are incomplete creates a false claim. I will keep caveats minimal but explicit.”

When asked: “Track everything across the Mission.”

“I track everything that becomes public, everything that can be quoted, and everything that can trigger allegations. Section owners provide the underlying facts.”

1.5 SPES relationships by actor (who you serve, and how)

This is a practical map of “what they want from you” vs “what you can safely provide.”

A) Front Office (Amb/DCM)

What they want: confidence, speed, simplified story, plausible deniability from uncertainty
What you provide: bounded confidence + explicit unknowns + options + escalation logic
Failure mode: they treat your document as “the embassy position”
Your countermeasure: label “analysis vs decision,” include decision owner line

B) PAO / A-PAO

What they want: message discipline, risk coverage, fewer surprises
What you provide: risk register, claim discipline, narrative drift detection, interaction quality signals
Failure mode: PAO offloads all cognitive load to SPES
Your countermeasure: insist on division of labor (SPES integrates; PAO decides/clears)

C) Press team

What they want: Q&A, holding lines, outlet posture, rapid response scaffolding
What you provide: safe phrasing patterns, “what not to confirm,” escalation thresholds, pickup log
Failure mode: SPES becomes the daily clip writer
Your countermeasure: provide templates + decision rules; press team executes daily products

D) Digital team

What they want: content ideas, risk coverage, analytics, comment handling rules
What you provide: monitoring schema, activation outliers, comment taxonomy, escalation rules
Failure mode: SPES becomes the analyst and the moderator
Your countermeasure: analytics and rules yes; day-to-day moderation no unless assigned

E) Program officers (Exchanges/Spaces/Grants)

What they want: to protect their programs, avoid controversy, highlight successes
What you provide: narrative framing discipline, partner-risk flags, “what can be safely said,” impact signals that are non-causal
Failure mode: defensiveness and fact-minimization (“it’s all bad faith”)
Your countermeasure: insist on verification boundaries; separate “allegations exist” from “allegations true”

F) Other sections (Pol/Econ/DAO/Cons/USG agencies)

What they want: their milestones reflected accurately; no accidental policy signaling
What you provide: a simple intake schema + claim discipline + “quote risk” guardrails
Failure mode: they bypass SPES until crisis then demand instant cleanup
Your countermeasure: routine cadence; minimal intake burden; make value visible

G) LES staff

What they want: safety, realism, avoidance of public/institutional backlash, not being blamed
What you provide: anonymous signal capture (non-attributional), early warning channels, realism in risk registers
Failure mode: their warnings get treated as “gossip” until too late
Your countermeasure: convert warnings into pattern-based risk indicators, never attribution

1.6 The SPES “integration rule” (prevents collapse)

Rule: SPES does not track everything. SPES tracks:

  1. Everything public-facing (anything the embassy or partners publish, post, or say)
  2. Everything quote-able (anything likely to be treated as official position)
  3. Everything allegation-sensitive (anything involving funds, favoritism, misuse, elections, security, rights)
  4. Everything that triggers escalation patterns (comment storms, press deadlines, partner panic)

Everything else is “nice to have” and should not displace core outputs.

1.7 Where SPES sits in the institutional risk chain

SPES is a risk visibility node, not a risk owner.

You are responsible for:

  • identifying where risk exists,
  • showing what it would look like if it escalates,
  • pointing to the decision point and decision owner,
  • and ensuring “silence” or “definitive statement” is treated as a decision with consequences.

You are not responsible for:

  • making the decision,
  • owning legal exposure,
  • or defending a factual claim that was never verified.

1.8 Common failure patterns and how SPES prevents them (practical)

Failure Pattern 1: Diffusion of accountability

Everyone assumes someone else cleared it.
SPES countermeasure: every product includes a “Decision/clearance owner” line.

Failure Pattern 2: Overconfident interim narrative

A “clean story” becomes a trap when facts change.
SPES countermeasure: “interim” labeling + bounded language + explicit unknowns.

Failure Pattern 3: Program defensiveness

Programs equate any acknowledgment with legitimizing allegations.
SPES countermeasure: separate acknowledgment of question from confirmation of wrongdoing; propose holding language that does neither.

Failure Pattern 4: Social media treated as informal

Posts are read locally as official policy.
SPES countermeasure: “policy-sounding phrasing” flags + safe sentence bank.

Failure Pattern 5: MATS substitution

Activity logging is mistaken for situational awareness.
SPES countermeasure: treat MATS as input only; produce narrative + risk outputs separately.

1.9 Minimal “first 30 days” operational posture for a new or overwhelmed SPES

If you are new, understaffed, or inheriting chaos, do this:

  1. Stand up the Risk Register + Decision Rules first (even if rough).
  2. Build a Monthly Leadership Snapshot from existing data (posts cadence, top topics, activation outliers).
  3. Establish a routine intake: one-liner from each section weekly of upcoming public-facing items.
  4. Build a holding language skeleton for common allegation types (funds, favoritism, election violence, citizen services).
  5. Create a “what I need from you” one-pager to reduce ad hoc burdens on sections.

Everything else can follow.