HORIZON SCAN / EMERGING THREATS REPORT
[SUBJECT / SECTOR / REGION - SCAN TITLE - ENGAGEMENT REF]
The Horizon Scan / Emerging Threats Report is the wide-aperture, structured sweep for emerging, novel, and over-the-horizon issues that could materially affect the client’s interests, operations, or strategic position over a defined future period. It is the early-warning / weak-signal product of the Strategic Forecasting & Early Warning node and answers a different question from its neighbours: not “how is this situation most likely to develop” (the Strategic Forecast & Estimate - calibrated probabilistic forecast of a known situation, consumed here as an input for baseline trajectory), not “what are the distinct, internally-consistent alternative futures” (the Alternative Futures Analysis - full 2×2 / cone-of-plausibility scenario set, commissioned when a scan-identified issue warrants deep scenario development), not “what is the standing signpost-monitoring cadence” (the Indicators & Warning (I&W) Program - retained service that operationalises the scan’s watch items into ongoing monitoring), and not “what is the live scoring/tracking surface” (the Probabilistic Forecasting Dashboard - system). This product delivers a structured, methodical, and transparent scan - it identifies, categorises, and prioritises emerging issues, weak signals, and nascent threats, assesses their potential impact and plausibility, and recommends which to watch, escalate, or ignore. It is not a prediction, a forecast, a risk rating, or a statement of certainty about what will emerge; it is a systematic early-warning sweep designed to reduce strategic surprise. Where a scan-identified issue warrants deeper treatment, it is routed to the appropriate sibling product via the recommendations in §16.
Document Control
| Field | Value |
|---|---|
| Report Reference | [REF-YYYY-###] |
| Date of Report | [YYYY-MM-DD] |
| Scan As-Of Date | [YYYY-MM-DD - the date through which evidence is assessed] |
| Scan Horizon | [e.g., 2–5 years / 5–10 years - the forward-looking aperture of the scan] |
| Classification / Handling | [CONFIDENTIAL - CLIENT EYES ONLY / TLP:AMBER] |
| Client | [CLIENT NAME] |
| Requesting Party | [CONTACT - ENGAGEMENT REF] |
| Scan Subject / Aperture | [The sector, region, domain, or strategic question being scanned - e.g., “Emerging threats to [client’s] supply chain in [region] through [horizon]“] |
| Engagement Purpose | [Decision the scan informs - e.g., strategic early-warning, risk-identification, horizon-scanning capability, investment-thesis challenge, posture-setting] |
| Scope / Depth | [Wide-aperture structured scan - see §2 scope] |
| Prepared By | [ANALYST NAME / ID] |
| Reviewed By | [REVIEWER NAME / ID] |
| Approving Officer | [APPROVER NAME / ID] |
| Version | [1.0] |
| Distribution | [NAMED RECIPIENTS] |
Handling & Legal Caveat
Handling: [Classification/TLP]. Disseminate only to the named authorized recipients. Reproduction or onward sharing prohibited without originator approval. Where the scan references named individuals, it may contain personal data - store and transmit per the client data-processing agreement and applicable data-protection frameworks (GDPR, CCPA, and local equivalents).
Nature of this product (READ FIRST): This is a structured horizon scan for emerging issues, weak signals, and nascent threats - a systematic early-warning sweep designed to reduce strategic surprise, not a prediction, a forecast, a risk rating, or a statement of certainty about what will emerge. Issues identified here are potential developments, not certainties; their plausibility and impact are assessed on the evidence available at the scan as-of date, and the scan is explicitly designed to surface low-probability / high-impact and novel issues that would be missed by narrower analytic methods. The scan is the firm’s independent, policy-neutral analytic judgment; it is not adjusted to suit a client-preferred answer or to avoid uncomfortable findings. This is not legal advice, investment advice, security or travel advice, or a credit opinion. It is one analytic input; the client’s legal, security, financial, and in-country advisers should be relied on for operational and transactional determinations.
Analytic independence & policy neutrality (ICD 203): Findings here are the firm’s independent analytic judgment, reached on the evidence and free of policy advocacy, a client-preferred conclusion, or any government’s or party’s line. Reporting is distinguished from analyst judgment throughout; uncertainty drivers and change indicators are stated explicitly; alternative explanations and outcomes are tested, not suppressed; and the scan is not adjusted to suit a preferred answer.
Weak-signal & novelty caveat: Horizon scanning by design surfaces issues that are poorly evidenced, novel, or at the fringe of current discourse. Many identified issues will not materialise; some will prove to be noise. The scan’s value is in systematic coverage and transparent prioritisation, not in the accuracy of any single item. Issues are graded by plausibility and evidence quality (§6–§7) so the client can calibrate attention. The absence of an issue from this scan does not mean it will not emerge.
Sourcing & legality: Findings derive from open, licensed, and lawfully accessed sources - public record, official statistics, reputable media, academic and institutional research, grey literature (conference proceedings, working papers, think-tank reports, patent filings, grant databases), specialist and trade publications, social-media and forum monitoring (where lawfully accessed and within terms of service), and (where commissioned) discreet in-country human sourcing and expert elicitation - current as of the as-of date and graded (Annex A). No classified, proprietary-without-licence, or unlawfully obtained material is used; copyright and database-licence terms are respected. Official statistics and state-controlled media are treated as potentially self-interested and corroborated against independent sources.
Perishability: This is a point-in-time scan. New events and information will surface issues not captured here and may invalidate or re-prioritise those that are. The scan decays as the horizon advances and as the environment evolves - re-scan before any consequential or time-critical decision, and commission an Indicators & Warning Program for standing monitoring of the watch items identified here.
Reliance: Reliance is limited to the named client for the stated purpose; no third-party reliance without originator consent.
Scan Snapshot
| Field | Value |
|---|---|
| Scan Subject / Aperture | [The sector, region, domain, or strategic question being scanned] |
| Scan Horizon | [Period covered] |
| Scan As-Of Date | [YYYY-MM-DD] |
| Scan Methodology | [Structured horizon-scanning method used - e.g., STEEP-V / PESTLE-based driver taxonomy, signal-hunting protocol, expert elicitation, Delphi, patent/grant analysis, media-frequency tracking - see §5] |
| Baseline Product(s) Used (if any) | [Reference to Regional Study or Strategic Forecast & Estimate used as input for baseline trajectory, or note if none] |
| Total Issues Identified | [Number of discrete issues surfaced by the scan] |
| High-Priority Watch Items | [Number of issues rated High priority - see §7] |
| Highest-Impact / Lowest-Probability Item | [The single most impactful issue that is plausible but unlikely - the classic horizon-scan find] |
| Most Novel / Surprising Finding | [The issue that most departs from current mainstream discourse] |
| Coverage Confidence | [HIGH / MODERATE / LOW - aperture breadth, source diversity, domain expertise, currency - see §17] |
Table of Contents
- BLUF
- Executive Summary & Scope
- Key Judgments
- Priority Intelligence Requirements (PIRs)
- Scan Methodology & Framing
- Emerging Issues Register
- Issue Prioritisation & Heat Map
- Weak Signals & Novel Indicators
- Cross-Cutting Themes & Driver Synthesis
- Discontinuities, Wildcards & Black-Swan-Adjacent Issues
- Key Findings Summary
- Analysis of Competing Hypotheses (ACH) - [on a selected high-stakes issue, if warranted]
- Key Assumptions Check (KAC)
- Premortem / Red-Team Check
- Collection Gaps & RFIs
- Assessment & Recommendations
- Annex A - Sources & Methodology
- Annex B - Appendices
(Page numbers populate on export to Word/PDF.)
1. BLUF
2–3 sentences. Lead with the most decision-relevant finding from the scan - the highest-priority emerging issue, the most novel weak signal, or the cross-cutting theme that most challenges current assumptions - then the aperture and horizon, and the most important implication for the client with the recommended posture or next step. Written so the decision-maker can act on this line alone.
[BLUF]
2. Executive Summary & Scope
Triggering requirement and engagement purpose; why this horizon scan is being conducted and for what client decision-horizon. Scope in/out stated explicitly - the subject/aperture, the scan horizon, the domains/drivers in scope (e.g., STEEP-V categories), and what is deferred to sibling/downstream products (calibrated forecast → Strategic Forecast & Estimate; full scenario development → Alternative Futures Analysis; standing I&W monitoring → Indicators & Warning Program; dashboard → Probabilistic Forecasting Dashboard; deeper bounded estimate → Intelligence Estimate; environmental baseline → Regional Study). Narrative synthesis of the scan’s most important findings - the highest-priority issues, the most novel weak signals, the cross-cutting themes, and the overall coverage and confidence. State the headline finding used in the BLUF and Snapshot here.
[EXECUTIVE SUMMARY & SCOPE]
3. Key Judgments
The analytic bottom line of the scan - the most important emerging issues, cross-cutting themes, and coverage assessments, ordered by decision-relevance. Each judgment carries a plausibility (ICD 203 band - the likelihood that the issue will materialise or become significant within the horizon) and analytic confidence as separate columns (never combined - ICD 203; plausibility is about the issue, confidence is about the evidence base behind the assessment) and a change-indicator stating what would shift the assessment. Note that plausibility in a horizon scan is a weaker epistemic claim than a forecast probability - it expresses how credible the issue is on current evidence, not a calibrated probability of occurrence.
| # | Key Judgment (Emerging Issue / Theme) | Plausibility | Analytic Confidence | Change Indicator (what would shift the assessment) |
|---|---|---|---|---|
| KJ-1 | [e.g., [Issue X] is the highest-priority emerging threat within the horizon] | [e.g., likely] | [HIGH/MOD/LOW] | [ ] |
| KJ-2 | [e.g., [Weak signal Y] is novel and potentially high-impact but poorly evidenced] | [e.g., unlikely - but high-impact if true] | [ ] | [ ] |
| KJ-3 | [e.g., The dominant cross-cutting theme is [theme]; it is under-discussed in current client planning] | [n/a - analytic statement] | [ ] | [ ] |
| KJ-4 | [e.g., Coverage is strongest in [domain] and weakest in [domain]; the scan’s principal gap is [gap]] | [n/a - coverage assessment] | [ ] | [ ] |
| KJ-5 | [e.g., No single issue warrants immediate escalation, but [issue] should be placed under structured monitoring] | [ ] | [ ] | [ ] |
4. Priority Intelligence Requirements (PIRs)
The collection-management spine for a horizon scan: PIRs drive the aperture - what domains, drivers, and signal types the scan systematically sweeps. Each PIR is tied to a driver category and a signal-hunting protocol. Summarise in the matrix.
- PIR-1 - Geopolitical / security emerging issues: What nascent geopolitical, conflict, or security developments could materially affect the client’s interests within the horizon? [ ]
- PIR-2 - Technological / cyber emerging issues: What emerging technologies, cyber threats, or digital-domain discontinuities are on the horizon? [ ]
- PIR-3 - Economic / financial emerging issues: What nascent economic, market, or financial-system developments could disrupt the client’s operating environment? [ ]
- PIR-4 - Environmental / resource emerging issues: What emerging environmental, climate, or resource-scarcity developments carry material risk? [ ]
- PIR-5 - Social / demographic / health emerging issues: What nascent social, demographic, public-health, or workforce developments could shift the operating context? [ ]
- PIR-6 - Regulatory / legal / compliance emerging issues: What emerging regulatory, legal, or compliance developments could affect the client’s licence to operate? [ ]
- [Add engagement-specific PIRs - e.g., sector-specific, region-specific, client-specific.]
| PIR | Driver Category | Signal-Hunting Protocol | Key Findings | Confidence | Key Gap |
|---|---|---|---|---|---|
| PIR-1 | [Geopolitical / security] | [ ] | [ ] | [H/M/L] | [ ] |
| PIR-2 | [Technological / cyber] | [ ] | [ ] | [H/M/L] | [ ] |
| PIR-3 | [Economic / financial] | [ ] | [ ] | [H/M/L] | [ ] |
| PIR-4 | [Environmental / resource] | [ ] | [ ] | [H/M/L] | [ ] |
| PIR-5 | [Social / demographic / health] | [ ] | [ ] | [H/M/L] | [ ] |
| PIR-6 | [Regulatory / legal / compliance] | [ ] | [ ] | [H/M/L] | [ ] |
5. Scan Methodology & Framing
The load-bearing methodology section for a horizon-scan product - state the rules before any finding appears so the scan is transparent and repeatable. Define, in order:
- Scan aperture & horizon. The subject, sector, region, or domain being scanned; the forward-looking horizon; and the rationale for the aperture (why this scope, what is excluded).
- Driver taxonomy / framing framework. The organising framework used to structure the scan (e.g., STEEP-V, PESTLE, PMESII-PT, or a custom taxonomy); the categories swept and the rationale for the choice.
- Signal-hunting protocol. The systematic method used to identify weak signals and emerging issues - the source types swept (academic, grey literature, patent/grant databases, specialist media, social-media/forum monitoring, expert elicitation), the search terms and filters, the frequency and recency criteria, and the novelty/divergence threshold for inclusion.
- Issue identification & triage. How identified issues are captured, categorised, and triaged - the initial screening criteria, the elimination of false positives and noise, and the threshold for inclusion in the register (§6).
- Plausibility & impact assessment. The scales used to assess each issue’s plausibility (ICD 203 band - a weaker epistemic claim than a forecast probability) and potential impact (qualitative or scored); how the two combine into the prioritisation matrix (§7).
- Techniques applied. The structured techniques used (structured brainstorming, expert elicitation / Delphi, media-frequency / trend analysis, patent/grant landscaping, Key Assumptions Check §13, premortem §14, and - where commissioned - quantitative or model-based methods); note any model and its uncertainty.
- Relationship to other products. This consumes the Regional Study baseline and/or Strategic Forecast & Estimate forecast as input for baseline trajectory; identifies issues that may warrant deeper treatment via the Alternative Futures Analysis (scenario development), Indicators & Warning Program (I&W monitoring), or Intelligence Estimate (bounded estimate); feeds the Probabilistic Forecasting Dashboard.
- Principal coverage constraints. Aperture breadth vs. depth trade-off, source-language bias, publication-lag bias, novelty-detection limits, expert-elicitation calibration, and reflexivity (the scan or client action altering the emergence of an issue).
| Framing Element | Content |
|---|---|
| Scan aperture & horizon | [ ] |
| Driver taxonomy / framing framework | [STEEP-V / PESTLE / PMESII-PT / Custom - state categories] |
| Signal-hunting protocol | [Source types, search terms, frequency/recency criteria, novelty threshold] |
| Issue identification & triage | [Screening criteria, noise elimination, inclusion threshold] |
| Plausibility & impact assessment | [Scales used - see §7] |
| Techniques applied | [Structured brainstorming / Delphi / media-frequency / patent landscaping / KAC / premortem / model - note model uncertainty] |
| Relationship to other products | [Consumes Regional Study / Strategic Forecast & Estimate / routes to Alternative Futures Analysis / Indicators & Warning Program / Intelligence Estimate / Probabilistic Forecasting Dashboard] |
| Principal coverage constraints | [Aperture depth, language bias, publication lag, novelty detection, reflexivity] |
Plausibility scale (the load-bearing scale of this product - ICD 203 bands applied to emerging issues, a weaker epistemic claim than a forecast probability):
| ICD 203 band | Interpretation for horizon scan |
|---|---|
| almost no chance / remote | Issue is speculative; evidence is absent or contradictory; inclusion is for completeness |
| very unlikely | Issue is possible but improbable on current evidence; low signal strength |
| unlikely | Issue is not the most plausible path but is credible enough to note |
| roughly even chance | Issue is as plausible as not; evidence is mixed or ambiguous |
| likely | Issue is the most plausible path on current evidence; moderate-to-strong signal strength |
| very likely | Issue is strongly indicated by converging evidence from multiple source types |
| almost certain | Issue is near-certain to emerge or become significant within the horizon |
State plausibility as a band, not a point probability - horizon-scan issues rarely support calibrated numeric probabilities. Keep plausibility separate from analytic confidence - a “likely” issue can be held at LOW confidence if the evidence base is thin but convergent.
6. Emerging Issues Register
The analytic spine of the product - the full register of discrete emerging issues, weak signals, and nascent threats identified by the scan. Each issue is described, categorised by driver domain, assessed for plausibility and potential impact, graded by evidence quality and novelty, and assigned a priority. The register is the raw output of the signal-hunting protocol; the prioritisation matrix (§7) distils it for decision-makers.
| # | Issue / Signal | Driver Domain | Description | Plausibility (ICD 203) | Potential Impact | Evidence Quality | Novelty | Priority | Source Grade |
|---|---|---|---|---|---|---|---|---|---|
| 1 | [ ] | [e.g., Geopolitical / Tech / Economic / Environmental / Social / Regulatory] | [Brief description - what the issue is, how it would manifest, the mechanism by which it would affect the client] | [ ] | [Critical / High / Moderate / Low] | [Strong / Moderate / Weak / Speculative] | [Novel / Emerging / Known-but-escalating / Mature] | [High / Medium / Low / Watch] | [A–F/1–6] |
| 2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 4 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 5 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 6 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 7 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 8 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 9 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 10 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
Priority definitions: High = issue warrants immediate attention and structured monitoring; Medium = issue is credible and potentially significant but not yet urgent; Low = issue is plausible but low-impact or poorly evidenced; Watch = issue is speculative or low-probability but would be high-impact if it materialised - the classic horizon-scan find.
7. Issue Prioritisation & Heat Map
A visual or tabular distillation of the §6 register - the issues plotted on a plausibility × impact matrix to identify the highest-priority items. The heat map is the decision-maker’s quick-reference tool: which issues to act on, which to watch, and which to ignore.
| Impact ↓ \ Plausibility → | Remote / Very Unlikely | Unlikely | Roughly Even | Likely | Very Likely / Almost Certain |
|---|---|---|---|---|---|
| Critical | [Issue # - Watch / Escalate] | [ ] | [ ] | [ ] | [ ] |
| High | [ ] | [ ] | [ ] | [ ] | [ ] |
| Moderate | [ ] | [ ] | [ ] | [ ] | [ ] |
| Low | [ ] | [ ] | [ ] | [ ] | [ ] |
Heat-map interpretation: [The issues in the top-right quadrant (high plausibility × high impact) are the highest-priority items - they warrant immediate attention and structured monitoring. The top-left quadrant (low plausibility × high impact) contains the classic horizon-scan finds - low-probability / high-impact issues that should be watched but not acted on without further evidence. The bottom-right quadrant (high plausibility × low impact) contains known issues that are unlikely to be strategically significant. The bottom-left quadrant can be ignored.]
8. Weak Signals & Novel Indicators
The specific weak signals, early indicators, and novel data points that triggered the identification of the emerging issues in §6 - the raw material of the scan. Each signal is described, its source and strength noted, its diagnostic value assessed, and its relationship to the issue it signals stated. This section is the audit trail for the scan’s findings and the hand-off to the I&W Program.
| # | Weak Signal / Indicator | Source | Signal Strength | Diagnostic Value | Issue(s) Signalled | Current Status | Disposition |
|---|---|---|---|---|---|---|---|
| 1 | [ ] | [ ] | [Strong / Moderate / Weak] | [High / Moderate / Low - how diagnostic this signal is of the issue’s emergence] | [Issue # from §6] | [Not present / Emerging / Confirmed / Disconfirmed] | [Watch / Escalate / Route to I&W Program / Close] |
| 2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 4 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 5 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
9. Cross-Cutting Themes & Driver Synthesis
The patterns, themes, and interactions that emerge across the individual issues in §6 - the synthesis that the register alone does not reveal. Identify the cross-cutting themes (issues that share a common driver, affect the same client asset, or would compound each other), the dominant drivers and their interactions, and the implications for the client’s strategic posture. This is the bridge from the raw issue register to the assessment and recommendations (§16).
| Cross-Cutting Theme | Issues Involved | Common Driver(s) | Interaction / Compounding Effect | Implication for Client |
|---|---|---|---|---|
| [ ] | [Issue s] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] |
Driver synthesis: [The dominant driver(s) across the scan, the most significant interaction or compounding effect, and the cross-cutting theme that most challenges current client assumptions or planning.]
10. Discontinuities, Wildcards & Black-Swan-Adjacent Issues
The low-probability / high-impact issues that are plausible enough to warrant mention but too speculative to include in the main register - the “black-swan-adjacent” items that horizon scanning is designed to surface. Each is described, its potential impact assessed, its leading indicators noted, and a recommendation made for whether and how to monitor it. This section is the hedge against the scan’s own blind spots.
| # | Discontinuity / Wildcard | Description | Potential Impact | Plausibility | Leading Indicators | Recommendation |
|---|---|---|---|---|---|---|
| 1 | [ ] | [ ] | [Critical / High] | [Remote / Very unlikely] | [ ] | [Watch / Escalate / Ignore - with rationale] |
| 2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
Wildcard note: [The most credible wildcard, the most impactful one, and the threshold at which a wildcard should be promoted to the main register or routed to the Alternative Futures Analysis.]
11. Key Findings Summary
Consolidated register of the load-bearing findings behind the scan, each graded by evidentiary status and confidence so the reader can see what is established vs. assessed vs. contested. Materiality flags the findings that most drive the prioritisation and recommendations.
| # | Finding | Status | Confidence | Materiality |
|---|---|---|---|---|
| 1 | [ ] | [Established / Assessed / Contested / Speculative] | [H/M/L] | [ ] |
| 2 | [ ] | [ ] | [ ] | [ ] |
| 3 | [ ] | [ ] | [ ] | [ ] |
| 4 | [ ] | [ ] | [ ] | [ ] |
| 5 | [ ] | [ ] | [ ] | [ ] |
12. Analysis of Competing Hypotheses (ACH) - [on a selected high-stakes issue, if warranted]
Apply ACH to a single high-stakes issue from §6 where the evidence is ambiguous and the consequences of mis-prioritisation are significant - e.g., “Is [emerging issue] a genuine emerging threat or noise?” / “Is [weak signal] a leading indicator or a false positive?” Array the competing interpretations as hypotheses, marshal the diagnostic evidence for/against each, and identify the most consistent interpretation and the evidence that would overturn it. Omit this section if no single issue warrants ACH-level treatment - say so and close.
| Evidence / Indicator | H1: [Interpretation A - e.g., genuine emerging threat] | H2: [Interpretation B - e.g., noise / false positive] | H3: [Interpretation C - e.g., different issue entirely] |
|---|---|---|---|
| [ ] | [C/I/N] | [C/I/N] | [C/I/N] |
(C = consistent · I = inconsistent · N = neutral.) Most consistent interpretation: [ ] - [rationale + the diagnostic evidence that would overturn it].
13. Key Assumptions Check (KAC)
The assumptions underpinning the scan - about the aperture and horizon, the driver taxonomy, the signal-hunting protocol, the novelty-detection threshold, the reliability of the source base, the absence of systematic bias, and the continuity of the current environment - each with its basis, confidence, and the impact on the scan’s findings if it proves wrong. Linchpin assumptions (those that, if wrong, materially change the prioritisation) are flagged.
| # | Assumption | Basis | Confidence | Impact on Scan if Wrong | Linchpin? |
|---|---|---|---|---|---|
| 1 | [e.g., The STEEP-V taxonomy captures the relevant driver domains] | [ ] | [H/M/L] | [ ] | [Y/N] |
| 2 | [e.g., The signal-hunting protocol is broad enough to detect novel issues] | [ ] | [ ] | [ ] | [ ] |
| 3 | [e.g., The source base is not systematically biased toward [language/region/perspective]] | [ ] | [ ] | [ ] | [ ] |
| 4 | [e.g., The current environment is sufficiently stable that the scan’s baseline is valid] | [ ] | [ ] | [ ] | [ ] |
| 5 | [e.g., No major exogenous shock intervenes within the horizon that invalidates the scan] | [ ] | [ ] | [ ] | [ ] |
14. Premortem / Red-Team Check
A structured premortem to surface the ways the scan could fail. Imagine it is the end of the horizon and the scan missed the most consequential emerging issue: what most plausibly happened, which assumption broke, which driver domain was under-swept, which signal was dismissed as noise, and what bias (availability, confirmation, anchoring, groupthink, cultural/professional blind spot) most likely contributed. Capture the corrective - the signal or domain that would have caught it - and feed it back to §8 and §16.
| # | Failure Mode (scan missed [issue] because…) | Assumption/Domain That Broke | Likely Bias | Corrective / Early Catch (→ §8 / §16) |
|---|---|---|---|---|
| 1 | [ ] | [ ] | [Availability / Confirmation / Anchoring / Groupthink / Cultural blind spot / Professional blind spot] | [ ] |
| 2 | [ ] | [ ] | [ ] | [ ] |
Premortem note: [The most credible failure mode and the single corrective most worth installing against it - e.g., a domain that should be added to the sweep, a source type that should be included, a signal that should be promoted to watch.]
15. Collection Gaps & RFIs
Where coverage is thin or contested, the impact on the scan’s findings, the collection that would close the gap, and where to escalate. Horizon-scan gaps are typically domain under-coverage, source-language bias, publication-lag blind spots, novelty-detection limits, or a specific issue that warrants deeper treatment via a sibling product.
| Gap | PIR / Domain | Impact on Scan | Recommended Collection | Escalation Target | Priority |
|---|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [Strategic Forecast & Estimate / Scenario Analysis / I&W Program / Expert elicitation / In-country HUMINT / Patent/grant landscaping] | [H/M/L] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
16. Assessment & Recommendations
16.1 Scan Assessment
Overall assessment - the scan’s most important findings, the highest-priority issues and cross-cutting themes, the most novel weak signals, the coverage and confidence caveats that bound the findings, and the implications for the client’s stated purpose and decision horizon. State the headline finding used in the BLUF and Snapshot. Be explicit about what the scan does and does not claim - it is a structured sweep for emerging issues, not a prediction or a forecast.
[ASSESSMENT]
16.2 Recommendations
- For decision-makers / principals: [What the scan’s findings mean for the client’s strategic posture; the issues that warrant immediate attention; the no-regret moves robust across plausible emerging scenarios; the conditions under which the scan should be refreshed.]
- For planners / risk owners: [Which issues to place under structured monitoring; which weak signals to track; the watch items that should trigger escalation; the cross-cutting themes that should inform planning assumptions.]
- For analysts (next intelligence steps): [Which issues warrant deeper treatment via the Strategic Forecast & Estimate, Alternative Futures Analysis, or a bounded Intelligence Estimate; which signals should be operationalised into an I&W Program; the recommended re-scan cadence.]
- Escalations / downstream products: [Items routed to the Strategic Forecast & Estimate, Alternative Futures Analysis, Indicators & Warning Program, Probabilistic Forecasting Dashboard, or a bounded Intelligence Estimate.]
- Conditions for reliance / refresh: [The perishability window and the events/signals (per §8) that should trigger a re-scan before reliance on these findings.]
17. Annex A - Sources & Methodology
Collection methods and scope; the source register graded with the Admiralty two-axis code; the reference scales (below); statement of the plausibility-vs-confidence separation and the horizon-scanning method (structured sweep with STEEP-V / PESTLE / custom driver taxonomy, signal-hunting protocol, plausibility × impact prioritisation); the techniques applied (structured brainstorming, expert elicitation / Delphi, media-frequency / trend analysis, patent/grant landscaping, KAC, premortem, and any model with its uncertainty); coverage and currency limitations (aperture breadth vs. depth, source-language bias, publication-lag bias, novelty-detection limits, expert-elicitation calibration, reflexivity); and the treatment of official statistics and state-controlled media as potentially self-interested and corroborated against independent sources.
Source reliability (Admiralty, A–F): A Completely reliable · B Usually reliable · C Fairly reliable · D Not usually reliable · E Unreliable · F Reliability cannot be judged.
Information credibility (Admiralty, 1–6): 1 Confirmed by other sources · 2 Probably true · 3 Possibly true · 4 Doubtful · 5 Improbable · 6 Truth cannot be judged. (Each sourced datum carries a two-character grade, e.g., B2.)
Estimative probability / likelihood (ICD 203): almost no chance / remote (01–05%) · very unlikely (05–20%) · unlikely (20–45%) · roughly even chance (45–55%) · likely (55–80%) · very likely (80–95%) · almost certain (95–99%).
Plausibility (horizon-scan application - a weaker epistemic claim than a forecast probability): The ICD 203 bands are applied to emerging issues to express how credible the issue is on current evidence, not a calibrated probability of occurrence. See §5 for the full mapping.
Analytic confidence (evidence base - kept separate from plausibility): HIGH (multiple independent reliable sources, converging evidence from multiple source types, no significant contradiction) · MODERATE (some corroboration, gaps, minor unresolved inconsistency) · LOW (single/uncorroborated source, weak or speculative evidence, significant gaps, plausible alternatives open). Never combine a plausibility term and a confidence level in the same sentence - a “likely” issue may be held at HIGH or LOW confidence.
Risk scoring (where a discrete risk is quantified - e.g., the impact of a §10 wildcard or discontinuity): Likelihood (1–5) × Impact (1–5) = 1–25; key: 1–5 Low · 6–10 Moderate · 11–15 Elevated · 16–20 High · 21–25 Critical. (Conditional - the horizon-scan spine is plausibility × impact prioritisation, above; this scale applies only where a discrete risk is scored for impact.)
Coverage confidence (product-level): HIGH (broad aperture, diverse independent sources across all driver domains, strong domain expertise, current coverage) · MODERATE (adequate coverage with gaps in specific domains or source types, some reliance on secondary sources) · LOW (significant aperture or source-base limits, weak domain expertise, currency degraded, high risk of missed issues).
Analytic-framework note: The scan is built on a structured horizon-scanning methodology - a systematic sweep for emerging issues, weak signals, and nascent threats using a defined driver taxonomy and signal-hunting protocol. Issues are identified, categorised, assessed for plausibility and impact, and prioritised transparently. The scan is designed to surface low-probability / high-impact and novel issues that would be missed by narrower analytic methods; many identified issues will not materialise. The scan is independent and policy-neutral per ICD 203 and is not adjusted to suit a client-preferred answer.
Searched sources (record source type, provider/title, as-of date, coverage scope, limitations, and any self-interest/reliability caveat): [TABLE]
18. Annex B - Appendices
- Appendix A - Full Emerging Issues Register: the complete §6 register with all issues, descriptions, assessments, and grades.
- Appendix B - Weak Signal & Indicator Log: the full §8 log with all signals, sources, strengths, and dispositions.
- Appendix C - Cross-Cutting Theme Analysis: the detailed §9 synthesis with interaction maps and compounding-effect assessments.
- Appendix D - Wildcard & Discontinuity Register: the full §10 register with all wildcards, assessments, and leading indicators.
- Appendix E - ACH / KAC / Premortem Workpapers: the structured-technique workings behind §12–§14.
- Appendix F - Source Taxonomy & Search Protocol: the full signal-hunting protocol - source types, search terms, filters, frequency/recency criteria, and novelty thresholds.
- Appendix G - Expert Elicitation Record (if used): the elicitation method, participants, questions, and results.
- Appendix H - Full Source Register: every source, Admiralty grade, access date, reference, and any coverage/limitation note.
- Appendix I - Glossary & Abbreviations.
- Appendix J - Revision History.
END OF REPORT.
Verification disclaimer: This horizon scan is a point-in-time, structured sweep for emerging issues, weak signals, and nascent threats based on open, licensed, and lawfully accessed sources current as of the as-of date; it is not a prediction, a forecast, a risk rating, or a statement of certainty about what will emerge. Issues identified here are potential developments, not certainties; many will not materialise, and the scan may miss issues that do. The scan is the firm’s independent, policy-neutral analytic judgment and is not adjusted to suit a client-preferred answer. Plausibility assessments are a weaker epistemic claim than forecast probabilities - they express how credible an issue is on current evidence, not a calibrated probability of occurrence. The scan decays as the horizon advances and as the environment evolves - re-scan before any consequential or time-critical decision. Official statistics and state-controlled sources were treated as potentially self-interested and corroborated where possible. No classified, unlawfully obtained, or out-of-licence material was used in the production of this report.
Document control footer: [REF-YYYY-### · Version · Classification/TLP · Prepared/Reviewed/Approved · Distribution].
Model wiring
Generated from cell frontmatter at publish time.