SPES Operational Handbook — Section 4

Data, Monitoring, and Institutional Intelligence

Purpose of this section:
Define how SPES uses data and monitoring to support judgment, not to replace it—and to prevent the recurring institutional failure of acting on anecdotes, pressure, or the loudest voice in the room.

This section explicitly distinguishes:

  • decision intelligence from
  • performance measurement and
  • surveillance.

SPES does the first and explicitly avoids the latter two.


4.1 What SPES Data Is (and Is Not)

What SPES data is

  • A way to see patterns over time
  • A way to test assumptions
  • A way to flag risk early
  • A way to ground leadership conversations

What SPES data is not

  • A staff evaluation tool
  • An audience targeting system
  • A sentiment “scorecard”
  • A substitute for policy guidance
  • A predictive engine

If data is used to judge individual performance or justify predetermined conclusions, SPES disengages.


4.2 Core Data Domains SPES Tracks

SPES maintains visibility across six data domains. No single system covers them all; integration is the point.


4.2.1 Media Environment (Traditional & Digital)

What is tracked

  • Major local print and electronic outlets
  • High-impact online platforms
  • Key social accounts that routinely shape narratives
  • Media pickup of Embassy statements

What matters

  • Who quotes us
  • How our words travel
  • Which issues activate coverage
  • When silence is filled by others

Artifacts

  • Daily media digest (lightweight)
  • Press pickup log (when Embassy statements are externalized)
  • Periodic media landscape map (ownership, alignment, reach)

What SPES does not do

  • Rank outlets by favorability
  • Blacklist or label journalists
  • Assign political affiliation

4.2.2 Social Media & Digital Platforms (Embassy-Owned)

Includes:

  • Facebook
  • X (Twitter)
  • Instagram
  • YouTube
  • Any platform used under Embassy branding

Tracked structurally

  • posting frequency
  • topic distribution
  • engagement baselines
  • activation outliers
  • comment dynamics

Tracked qualitatively

  • interaction types (information, grievance, rumor, hostility)
  • escalation patterns
  • casework spillover
  • policy attribution risk

SPES rule

Engagement volume is less important than interpretation risk.

4.2.3 American Spaces (Centers, Corners, Shelves)

SPES tracks

  • Location
  • Programming themes
  • Partner institutions
  • Audience types (students, professionals, general public)
  • Event visibility and amplification

Key SPES concern
American Spaces are often perceived locally as:

“semi-official U.S. platforms”

This creates:

  • endorsement risk,
  • favoritism risk,
  • and politicization risk.

SPES role

  • Ensure programming themes align with Mission priorities
  • Flag events likely to be misinterpreted
  • Track cumulative narratives across spaces (not isolated events)

4.2.4 Exchanges & People-to-People Programs

Includes:

  • Fulbright (students, scholars, TEA, DAI)
  • IVLP
  • Short-term exchanges
  • Alumni networks

SPES tracks

  • program type
  • cohort size
  • thematic focus
  • visibility (public vs quiet)
  • alumni prominence over time

What SPES does not do

  • Measure “impact” in causal terms
  • Evaluate individuals
  • Assign political orientation

Why SPES tracks this
Exchanges shape:

  • elite networks,
  • long-term narratives,
  • and attribution claims (“the U.S. trained X”).

SPES ensures:

  • messaging does not overclaim,
  • alumni prominence does not imply endorsement,
  • exchange narratives align with Mission posture.

4.2.5 Programmatic Signals (Econ, Security, Agriculture, Governance)

SPES maintains awareness of:

  • major program launches,
  • large grants,
  • commercial milestones (e.g., aircraft, agriculture exports),
  • security cooperation announcements.

SPES is not the program manager, but tracks:

  • what is publicly said,
  • what is implied,
  • how it fits into broader narratives.

Failure mode SPES prevents
Isolated announcements that, in aggregate, tell a story the Mission did not intend.


4.2.6 External Policy Environment

SPES tracks:

  • ICS priorities
  • NSS/NDS alignment
  • major Washington statements affecting host country
  • travel advisories and alerts
  • election calendars and political cycles

This allows SPES to:

  • flag misalignment early,
  • anticipate sensitivity spikes,
  • prevent outdated framing.

4.3 Key Systems and Tools (Reality-Based)

4.3.1 MATS (Mission Activity Tracking System)

What MATS is

  • A State Department system for logging PD activities
  • Focused on what happened, not what it meant

What MATS contains

  • event descriptions
  • dates
  • locations
  • audiences (broad categories)
  • resources used

What MATS does well

  • institutional memory
  • reporting consistency
  • accountability to Washington

What MATS does poorly

  • narrative coherence
  • cross-platform analysis
  • risk detection
  • interpretation

SPES role vis-à-vis MATS

  • Use MATS as input, not as analysis
  • Identify gaps between MATS reporting and public narratives
  • Flag when MATS success ≠ reputational safety

4.3.2 Social Platform Analytics (Meta, X, etc.)

SPES uses

  • native analytics exports
  • time-series trends
  • aggregate audience data (high level)

SPES avoids

  • micro-targeting logic
  • demographic inference beyond aggregates
  • sentiment automation

4.3.3 External Reference Data (Selective)

SPES may draw from:

  • publicly available polling
  • academic research
  • media ownership databases
  • think-tank reporting

Only when:

  • sources are credible,
  • limitations are stated,
  • data is used contextually.

4.4 Data to Decision Translation (The Critical Step)

SPES never forwards raw data alone.

SPES always translates data into:

  • What it suggests
  • What it does not prove
  • Why it matters now
  • What decision it affects

Example:

“Engagement on visa-related posts has doubled, but comment quality indicates confusion rather than hostility. Clarification may reduce rumor amplification.”

4.5 Documentation & Continuity

SPES maintains:

  • lightweight logs
  • periodic snapshots
  • annotated datasets (where needed)

Purpose:

  • continuity across rotations,
  • protection against hindsight blame,
  • institutional learning.