Blog
Why the EEAS-FIMI weekly brief needs a strict structure
A weekly EEAS-FIMI format brief is not a research paper; it’s a decision-support product. The director’s desk expects a document that is consistent week to week, easy to scan in minutes, and precise about what matters: what happened, why it matters, what you assess, and what should happen next. A predictable structure reduces cognitive load and builds trust—readers know where to find the headline judgement, the supporting evidence, and the implications.
This guide walks you through a practical structure you can reuse every week, plus tips for writing, prioritizing, and quality-checking under time pressure.
Step 1: Start with the “director view” (top lines that can stand alone)
Put the most important content at the top. Assume the reader may only read the first section.
Include:
- One-sentence headline: the week’s dominant development in FIMI terms.
- 2–4 key judgements: concise, testable assessments (not a list of events).
- Immediate implications: what this means for EU interests, narratives, or operational posture.
- Confidence language: keep it simple (e.g., high/medium/low), tied to evidence quality.
Practical writing tip: Each key judgement should fit on one line. If it can’t, it’s likely two judgements.
Step 2: Define scope and timeframe (so readers know what you covered)
A short scope block prevents confusion and reduces follow-up questions.
Include:
- Time window covered (e.g., last 7 days, with exceptions noted)
- Geographic focus (EU-wide, specific member states, neighbourhood, global)
- Platforms/environments (main social platforms, messaging apps, traditional media, offline signals)
- What’s excluded (and why) if relevant
Keep this to a tight paragraph or bullets. The goal is clarity, not caveats.
Step 3: Provide a compact “week-at-a-glance” overview
This section is your bridge between the top-line judgements and the deeper analysis. Use a scannable format that highlights what changed.
Recommended elements:
- Key narratives (3–6 max), each with a short descriptor
- Primary targets (institutions, communities, policy areas)
- Main channels/tactics (e.g., amplification, impersonation, coordinated posting, cross-platform seeding)
- Notable shifts vs. previous week (new narrative emergence, intensified targeting, tactical pivot)
Actionable structure: Use bullets with consistent labels each week, so comparisons become effortless.
Step 4: Deep-dive on narratives using a repeatable template
For each narrative, use the same sub-structure. This is where your brief becomes operationally useful.
Narrative block template (copy/paste each week)
1) Narrative statement (what is being pushed)
Write it as the disinformation claim or framing, not as your rebuttal.
2) Context (why now)
Tie to real-world events, policy decisions, crises, or media moments that explain timing.
3) Audience and objective (who it’s for, what it tries to achieve)
Focus on intended effect: erode trust, polarize, suppress turnout, undermine support, distract, justify actions, etc.
4) Spread and delivery (how it moved)
Summarize:
- Key platforms/environments
- Use of influencers or pseudo-media
- Cross-posting patterns
- Language variants
- Signs of coordination (be careful: describe observable behavior)
5) Assessment (what you believe is happening)
This is where you interpret. Keep it bounded:
- What you assess about intent and likely impact
- Confidence level and why (quality/coverage of observations)
6) Implications and watchpoints (what to monitor next week)
Convert analysis into forward-looking value:
- Likely next iterations of the narrative
- Potential triggers that could spike volume
- Vulnerable audiences or events
Discipline rules:
- One narrative block should typically be short and complete, not sprawling.
- If you have more than six narratives, you likely need prioritization (see Step 6).
Step 5: Add a “tactics and techniques” section (pattern recognition over content)
Directors often need to know not only what is being said, but how the information environment is being manipulated. This section supports operational planning and resilience measures.
Structure it as:
- Observed tactics (this week):
- Amplification patterns (e.g., rapid reposting, coordinated timing)
- Credibility hacking (impersonation, forged branding, false experts)
- Laundering (moving claims through multiple layers to appear organic)
- Harassment or intimidation dynamics
- What’s notable about these tactics now
- What changed vs. baseline
- What suggests experimentation or adaptation
- Operational implications
- Where monitoring should be strengthened
- Which stakeholders may need a heads-up
Keep it evidence-led and concrete: describe behaviors and patterns, avoid over-claiming attribution unless your mandate and evidence support it.
Step 6: Prioritize ruthlessly (a weekly brief is not a catch-all)
A frequent failure mode is trying to include everything. The director’s desk needs what is most consequential, not what is most abundant.
Use three filters:
- Impact potential: Does it affect public trust, policy space, security, or social cohesion?
- Novelty or escalation: Is this a new narrative, a surge, or a tactical shift?
- Decision relevance: Will someone act differently after reading it?
If something is worth recording but not spotlighting, place it in a short “Other notable items” section at the end.
Step 7: Translate analysis into action (clear takeaways and next steps)
Your brief should end with a section that helps leadership decide what to do.
Include:
- Recommended actions (2–5 items), phrased as verbs:
- “Coordinate messaging on…”
- “Alert relevant teams to…”
- “Increase monitoring of…”
- “Prepare lines on…”
- Risks if no action is taken (brief)
- Dependencies (what you need from others: data access, partner inputs, comms alignment)
Keep recommendations realistic for the week ahead. Avoid generalities like “raise awareness” without specifying who should do what.
Step 8: Use a consistent writing style that signals confidence and restraint
EEAS-FIMI briefs live or die by clarity. Apply these style habits:
- Lead with verbs and assessments: “We assess…”, “This suggests…”, “Indicators point to…”
- Separate observation from inference:
- Observation: what you saw
- Inference: what it likely means
- Avoid jargon unless it reduces ambiguity; if you must use a term, use it consistently
- Keep paragraphs short; directors scan
- Prefer precise qualifiers over hedging:
- Good: “Limited evidence,” “Multiple independent indicators”
- Avoid: “Maybe,” “Perhaps,” “It seems”
Step 9: Build a quick quality-check before you send
Use this checklist to prevent common brief failures:
- Can the top section stand alone as a one-minute read?
- Do key judgements match the body (no orphan claims)?
- Are narrative labels consistent (same naming across sections)?
- Are you overloading with examples instead of synthesis?
- Is confidence stated where it matters (especially on high-impact judgements)?
- Is there a clear “so what” for each narrative?
- Did you avoid implying attribution without sufficient basis?
- Is the document scannable (bullets, headings, limited clutter)?
If time is tight, prioritize alignment: top-line judgements must be supported by what follows.
A reusable weekly outline (copy-ready)
Use this as your standard structure:
- Headline
- Key Judgements (2–4)
- Implications (immediate)
- Scope and Timeframe
- Week-at-a-Glance
- Key narratives
- Targets
- Channels/tactics
- Notable shifts
- Narrative Deep Dives (3–6)
- Narrative statement
- Context
- Audience/objective
- Spread/delivery
- Assessment + confidence
- Implications/watchpoints
- Tactics and Techniques (cross-cutting)
- Other Notable Items (brief)
- Recommendations / Next Steps
Consistency is a force multiplier. When the structure stays stable, leadership spends less time deciphering your product and more time absorbing your judgement—exactly what a director’s desk expects.