Horizon Scanning Team Cadence Report Template

Build a horizon-scanning agenda and report template from a team, cadence, scan areas, and horizon labels.

Description

A horizon-scanning meeting needs areas, horizons and a review cadence.

A horizon-scanning meeting needs areas, horizons and a review cadence. A template can organize that work before any signals are collected.^[1]

The returned values include Agenda items, Agenda completeness percent, Report template, Agenda item count. The How section below explains the calculation, input rules and interpretation.

When to use Horizon Scanning Team Cadence Report Template

Use Horizon Scanning Team Cadence Report Template when you need to evaluate the supplied records under the calculation and evidence rules below. The constant completeness value describes accepted template inputs, not completed scans or actual team performance. No meeting is scheduled.

Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.

How to use Horizon Scanning Team Cadence Report Template and understand its results

Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.
Enter horizonLabels, reviewCadence, scanAreas, teamName using the field table and calculation rules, then run the tool.
Read agendaItems, cadenceCompletenessPercent, reportTemplate, totalAgendaItemCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
horizonLabels	Horizon labels	list of string	Required
reviewCadence	Review cadence	string	Required
scanAreas	Scan areas	list of string	Required
teamName	Team name	string	Required

Trim nonblank team/cadence and nonempty nonblank area/horizon lists. Generate pairs area-major, then horizon order, and return agenda/count plus Markdown report with unfilled sections. cadenceCompletenessPercent is always100 for accepted input.

agenda=scanAreas×horizons

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
agendaItems	Agenda items	list of string
cadenceCompletenessPercent	Agenda completeness percent (%)	number; minimum: 0; maximum: 100
reportTemplate	Report template	string
totalAgendaItemCount	Agenda item count	integer; minimum: 1

json

{
  "input": {
    "horizonLabels": [
      "0-2 years",
      "3-10 years"
    ],
    "reviewCadence": "Quarterly",
    "scanAreas": [
      "Technology",
      "Regulation"
    ],
    "teamName": "Strategy Futures Team"
  },
  "output": {
    "agendaItems": [
      "Scan Technology across the 0-2 years horizon for new signals and implications.",
      "Scan Technology across the 3-10 years horizon for new signals and implications.",
      "Scan Regulation across the 0-2 years horizon for new signals and implications.",
      "Scan Regulation across the 3-10 years horizon for new signals and implications."
    ],
    "cadenceCompletenessPercent": 100,
    "reportTemplate": "# Strategy Futures Team horizon scan\nCadence: Quarterly\n\n## Agenda\n- Scan Technology across the 0-2 years horizon for new signals and implications.\n- Scan Technology across the 3-10 years horizon for new signals and implications.\n- Scan Regulation across the 0-2 years horizon for new signals and implications.\n- Scan Regulation across the 3-10 years horizon for new signals and implications.\n\n## Signals\n[to complete]\n## Implications\n[to complete]\n## Actions\n[to complete]",
    "totalAgendaItemCount": 4
  }
}

Limitations and assumptions

The constant completeness value describes accepted template inputs, not completed scans or actual team performance. No meeting is scheduled.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Core numeric and string lists are limited to 100,000 entries; text entries are subject to the general large-text limit. Follow any smaller calculation limits above. Extremely large text inputs are rejected. Missing fields without a declared default, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Foresight Deliverable Types Report Formats Lookup: A scan, scenario set, strategy, roadmap and monitoring report support different decisions. Format, audience and cadence should follow the purpose of the deliverable. For a complementary task, use Signal Insight Action Pipeline Stage Tracker: A signal-to-action pipeline distinguishes observation, interpretation, action and completion. Stage labels determine the next template prompt.

References

Horizon Scanning Team Cadence Report Template — tool.io

Similar or alternative tools

Foresight Deliverable Types Report Formats Lookup
A scan, scenario set, strategy, roadmap and monitoring report support different decisions. Format, audience and cadence should follow the purpose of the deliverable.
Signal Insight Action Pipeline Stage Tracker
A signal-to-action pipeline distinguishes observation, interpretation, action and completion. Stage labels determine the next template prompt.