Dashboard Guide

Understanding your results.

A single reference for every score, indicator, and recommendation in Sophurion Horizon. Use it to interpret dashboards, share results with stakeholders, and build shared vocabulary across leadership, legal, regulatory, and operating teams.

LowModerateElevatedHigh
score

Executive Risk Score

A 0–100 measure of overall organizational risk exposure across Horizon's intelligence domains.

What it measures

The combined exposure and preparedness signals across climate, geopolitical, supply chain, regulatory, and infrastructure domains, weighted for industry and organizational profile.

Why it matters

Gives leadership a single, comparable number for board conversations, resource prioritization, and tracking risk posture over time.

How to interpret results
0–25
Low Risk
Overall risk exposure appears contained. Existing preparedness signals are aligned with the risk profile.
26–50
Moderate Risk
Notable exposure exists in one or more domains but is generally within manageable ranges.
51–75
Elevated Risk
Multiple domains show meaningful exposure. Preparedness gaps may compound impact if left unaddressed.
76–100
High Risk
Concentrated exposure across critical domains. Warrants leadership attention and a coordinated response.
Example scenario

A mid-market manufacturer with concentrated Asia-Pacific suppliers and limited continuity testing may score in the Elevated (51–75) range, triggering executive review and mitigation planning.

Recommended actions
  • Compare current score to the previous period to identify direction of travel.
  • Drill into the highest-scoring domains for driving factors.
  • Use the Recommendations queue to sequence response actions.
index

Emerging Risk Index

A 0–100, forward-weighted index highlighting potential future risks and developing trends.

What it measures

Signals biased toward climate, geopolitical, and regulatory domains, where forward trajectory typically diverges most from current state.

Why it matters

Surfaces issues that current-state scoring understates so leadership can act before risks materialize.

How to interpret results
0–25
Low Risk
Overall risk exposure appears contained. Existing preparedness signals are aligned with the risk profile.
26–50
Moderate Risk
Notable exposure exists in one or more domains but is generally within manageable ranges.
51–75
Elevated Risk
Multiple domains show meaningful exposure. Preparedness gaps may compound impact if left unaddressed.
76–100
High Risk
Concentrated exposure across critical domains. Warrants leadership attention and a coordinated response.
Example scenario

An organization with a low current-state risk score but rising exposure to new disclosure regulations and geopolitical tension may show an Elevated Emerging Risk Index — a leading indicator worth monitoring.

Recommended actions
  • Compare Emerging Risk Index to Executive Risk Score; wide gaps signal trajectory change.
  • Prioritize monitoring in the fastest-moving domains.
  • Fold forward-looking risks into strategic planning cycles.
indicator

Confidence Rating

How much weight to place on Horizon's outputs based on the quality and completeness of available information.

What it measures

Input completeness, geographic specificity, and organizational context provided to the intelligence engine.

Why it matters

Tells decision-makers when to act with confidence and when to gather more information before acting.

How to interpret results
80–100
High Confidence
Strong supporting information and analysis available. Suitable for decision-grade use.
60–79
Moderate Confidence
Some uncertainty or incomplete information exists. Directionally reliable; verify headline calls.
0–59
Low Confidence
Additional information may be required before relying heavily on results. Treat as indicative.
Example scenario

A dashboard built from a partially completed assessment with vague geography will show a Low Confidence rating; completing the assessment and specifying operating regions typically moves it into the High range.

Recommended actions
  • Increase input completeness in the assessment.
  • Provide specific operating and supplier geographies.
  • Verify headline calls against a High Confidence rerun before major decisions.
index

Organizational Confidence Index

A 0–100 measure of the visibility, preparedness, governance maturity, monitoring capability, and awareness an organization appears to have regarding its risks and resilience.

What it measures

The strength of an organization's own information, monitoring, and governance signals — not Horizon's confidence in its outputs.

Why it matters

Highlights whether leadership has the visibility required to interpret risks and respond effectively. A high risk score paired with low organizational confidence usually warrants elevated attention.

How to interpret results
80–100
High Confidence
Organization demonstrates strong visibility, monitoring, governance, and preparedness relative to its risk profile.
60–79
Moderate Confidence
Reasonable visibility is in place, with identifiable areas that would benefit from improvement.
40–59
Limited Confidence
Information gaps, monitoring weaknesses, or governance limitations may exist.
0–39
Low Confidence
Significant blind spots may exist. Leadership may not have sufficient visibility to fully understand current and emerging risks.
Example scenario

A regional business that reports strong monitoring and continuity testing but limited visibility into tier-2 suppliers may score in the Moderate range, with supplier visibility flagged as the highest-leverage improvement.

Recommended actions
  • Address highest-impact information and governance gaps first.
  • Formalize ownership for monitoring and reporting processes.
  • Reassess after material governance or reporting changes.
indicator

Blind Spot Indicators

Potential gaps in organizational visibility, monitoring, governance, preparedness, planning, reporting, or information quality.

What it measures

Areas where Horizon detects missing information, weak monitoring signals, or incomplete governance patterns.

Why it matters

Organizations are often impacted by risks they fail to identify rather than risks they already understand. Blind spots quantify the size of what leadership may not yet see.

How to interpret results
Missing information
Gap in inputs
Key assessment areas were skipped, generalized, or unavailable.
Limited monitoring
Weak signal capture
The organization does not appear to track a domain at the required cadence.
Weak governance processes
Unclear ownership
Roles, escalation paths, or approval processes for a risk area appear underdeveloped.
Incomplete reporting
Reporting gap
Internal or external reporting does not fully cover the risk domain or its material drivers.
Lack of contingency planning
Resilience gap
Response plans, playbooks, or continuity tests are absent or untested.
Emerging risks not being tracked
Foresight gap
Forward-looking risks are not part of current monitoring or planning cycles.
Limited organizational awareness
Awareness gap
Leadership or key functions may not be actively engaged with the risk area.
Inconsistent data quality
Data quality gap
Underlying inputs vary in accuracy or completeness, reducing confidence in downstream outputs.
Example scenario

A firm may have strong climate exposure signals but no formal governance owner for supply-chain risk. Horizon would flag a governance blind spot even if its supply-chain risk score is currently low.

Recommended actions
  • Improve monitoring in flagged domains.
  • Collect additional information where inputs were sparse.
  • Strengthen governance ownership and escalation paths.
  • Conduct additional assessments in weakly covered areas.
  • Improve internal reporting cadence and coverage.
  • Review strategic assumptions against emerging-risk signals.
signal

Opportunity Signals

Potential business opportunities identified through Horizon's analysis of the organization's exposure profile and context.

What it measures

Positive patterns such as underused strengths, favorable market or regulatory conditions, or capabilities that could be extended.

Why it matters

Risk intelligence is not only defensive — the same signals often reveal where an organization can differentiate or grow.

How to interpret results
Strategic
Strategic opportunity
Longer-horizon positioning move.
Operational
Operational opportunity
Efficiency, resilience, or cost improvement.
Market
Market opportunity
Customer, geographic, or product expansion.
Example scenario

A company with strong preparedness in a high-disclosure region may be positioned to differentiate on trust or win regulated-buyer segments.

Recommended actions
  • Prioritize opportunities aligned to current strategic goals.
  • Sequence pursuit alongside risk mitigation to preserve execution capacity.
indicator

Financial Exposure

An order-of-magnitude estimate of potential operational, financial, strategic, regulatory, reputational, or business exposure.

What it measures

Declared revenue band, industry-baseline disruption coefficients, and the overall risk score, combined into a planning anchor.

Why it matters

Gives finance and executive teams a materiality reference for prioritizing mitigation investment.

How to interpret results
Planning anchor
Order of magnitude
Intended as a band for planning conversations, not an actuarial loss estimate.
Example scenario

An organization with elevated exposure across supply chain and infrastructure may see a financial exposure band that justifies investment in continuity testing and supplier diversification.

Recommended actions
  • Compare the exposure band to current mitigation spend.
  • Use it to frame board-level discussions about capital allocation to resilience.
indicator

Resilience Indicators

Measures related to preparedness, adaptability, responsiveness, and organizational resilience.

What it measures

The presence, maturity, and testing cadence of continuity plans, governance mechanisms, and monitoring practices.

Why it matters

Resilience determines how much a given risk actually costs the organization when it materializes.

How to interpret results
Emerging
Emerging
Foundational practices are inconsistent.
Defined
Defined
Practices exist and are documented.
Tested
Tested
Practices are regularly exercised and refined.
Example scenario

An organization with annually tested continuity plans, a defined climate response, and a mapped supplier tier-1 will show stronger resilience indicators than one that only has intent statements.

Recommended actions
  • Move highest-priority practices from Emerging to Defined.
  • Schedule continuity and scenario tests for the coming period.
framework

Recommendations

Prioritized suggested actions generated from Horizon's analysis of the organization's exposure and preparedness signals.

What it measures

Category of action (Executive, Operational, Strategic Planning, Monitoring) and priority level (Low, Moderate, High, Critical).

Why it matters

Turns intelligence into an executable queue leadership can assign, sequence, and track.

How to interpret results
Low
Low priority
Risk score < 40
Moderate
Moderate priority
Risk score 40–59
High
High priority
Risk score 60–74
Critical
Critical priority
Risk score ≥ 75
Example scenario

A Critical-priority Executive action might be scheduling a board-level review of concentrated supplier exposure, while a Moderate Monitoring action might be setting a quarterly review cadence for a stable domain.

Recommended actions
  • Assign an owner and target date to each recommendation.
  • Track completion and re-score on a defined cadence.
framework

Priority Levels

The urgency framework applied to Horizon recommendations.

What it measures

Underlying risk score, with explicit escalation at defined thresholds.

Why it matters

Ensures the highest-impact actions rise to the top of the executive decision queue.

How to interpret results
Low
Risk score < 40
Maintain monitoring.
Moderate
Risk score 40–59
Review trends. Strengthen monitoring.
High
Risk score 60–74
Executive review. Mitigation planning. Additional assessment.
Critical
Risk score ≥ 75
Immediate leadership review. Detailed analysis. Strategic response planning. Executive action plan.
Example scenario

A recommendation tied to a domain risk score of 78 escalates to Critical priority and appears at the top of the decision queue.

Recommended actions
  • Sequence Critical and High actions ahead of Moderate and Low.
  • Confirm ownership before moving down the queue.
framework

Industry Benchmarking

Anonymized comparison of an organization's scores against a cohort of peers in the same industry.

What it measures

Cohort size, industry averages, and p25 / p50 / p75 percentile positioning across overall risk, confidence, and pillar scores.

Why it matters

Grounds internal results in external context so leaders can distinguish company-specific issues from industry-wide dynamics.

How to interpret results
n < 5
Not available
Cohort is too small to publish. No comparison is shown.
Below p25
Better than most peers
Exposure or gap is lower than 75% of the cohort.
p25 – p75
In line with peers
Positioned within the typical range for the industry.
Above p75
Higher than most peers
Exposure or gap exceeds 75% of the cohort — investigate drivers.
Example scenario

An organization with an overall risk score of 62 in an industry where the p50 is 48 and p75 is 58 is positioned above most peers and should investigate the pillars driving the delta.

Recommended actions
  • Focus first on pillars where your score is materially above the industry p75.
  • Use pillar-level deltas to prioritize which domains to strengthen next.
  • Re-run benchmarking after mitigation to confirm movement toward the median.
framework

Percentile Ranking

The position of a value within a distribution, expressed as the percentage of the cohort at or below that value.

What it measures

Where an organization sits inside the industry distribution for a given score.

Why it matters

Percentiles show relative standing more meaningfully than a raw average, especially when distributions are skewed.

How to interpret results
p25
25th percentile
25% of the cohort scores at or below this value.
p50
Median
The middle of the cohort — half score above, half score below.
p75
75th percentile
75% of the cohort scores at or below this value.
Delta vs. average
Delta vs. industry average
Your score minus the cohort mean. Positive means higher exposure than typical peers; negative means lower.
Example scenario

If the industry p75 for supply-chain risk is 60 and your score is 68, you sit above the top quartile of exposure for peers.

Recommended actions
  • Read p50 as the peer baseline and p25 / p75 as the typical range.
  • Treat a positive delta on a risk score as an area to investigate.
  • Treat a negative delta on a confidence score as an area to strengthen.
framework

Monitoring Frameworks

Structured schedules and assignments that keep Horizon intelligence current between full assessments.

What it measures

Assigned owners, review cadence, review-due status, and monitoring coverage across risk domains.

Why it matters

Risk profiles drift. Monitoring frameworks turn Horizon from a point-in-time snapshot into a continuous decision-support surface.

How to interpret results
Scheduled
Scheduled review
A cadence is set and the next review date is in the future.
Due
Review due
The scheduled review window has arrived — action required.
Overdue
Overdue
The review window has passed. Refresh the assessment to keep intelligence reliable.
Example scenario

A quarterly monitoring assignment on a critical supplier ensures the executive team is prompted to refresh exposure data before the next board meeting.

Recommended actions
  • Assign an owner to every active monitoring framework.
  • Address 'Review due' items promptly to prevent stale intelligence.
  • Escalate 'Overdue' items into the next executive review cycle.
signal

Executive Alerts

Prioritized notifications generated when Horizon detects a material change, review-due event, or intelligence match relevant to the organization.

What it measures

Alert type, severity, source (assessment, monitoring, industry intelligence), and recommended executive action.

Why it matters

Ensures leadership sees what matters without needing to monitor the platform manually.

How to interpret results
Informational
Informational
Awareness-level signal. Review during the next intelligence cycle.
Advisory
Advisory
Meaningful development — consider updating monitoring or planning.
Priority
Priority
Direct executive attention warranted. Coordinate a response.
Critical
Critical
Immediate leadership review and response planning required.
Example scenario

A new industry intelligence item tagged to your sector may generate a Priority alert with a link to the underlying context and a suggested next step.

Recommended actions
  • Triage alerts weekly at minimum.
  • Convert Priority and Critical alerts into recommendations with owners.
  • Close out alerts once action is taken so the queue reflects reality.
framework

Executive Intelligence Reports

Structured PDF briefings that consolidate scores, findings, recommendations, benchmarks, and methodology for executive audiences.

What it measures

Executive summary, key risk areas, strengths, priority recommendations, strategic outlook, next steps, methodology, industry benchmarks, and glossary.

Why it matters

Provides a portable, board-ready artifact that captures Horizon intelligence at a moment in time.

How to interpret results
Executives
Executives
Use as the anchor document for leadership discussions and prioritization.
Boards
Boards
Reference the summary, risk areas, and recommendations for governance oversight.
Advisors
Advisors
Use benchmarks and methodology sections to frame client conversations.
Example scenario

A quarterly Executive Intelligence Report becomes the shared reference for the executive committee to align on the current risk posture and the actions in motion.

Recommended actions
  • Circulate reports ahead of executive and board meetings.
  • Track recommendations from each report to closure.
  • Regenerate after material changes so the archive reflects the current posture.
framework

Strategic Foresight & Scenario Intelligence

Structured exploration of possible future conditions, risks, opportunities, and resilience implications relevant to the organization.

What it measures

Scenario configuration (risk category, severity, time horizon, industry) and the resulting analytical brief.

Why it matters

Improves executive readiness by pressure-testing assumptions before conditions change. Foresight is not prediction.

How to interpret results
Near-term
Near-term (0–12 months)
Scenarios most useful for operational planning.
Mid-term
Mid-term (1–3 years)
Scenarios most useful for strategic planning.
Long-term
Long-term (3+ years)
Scenarios most useful for structural and capital planning.
Example scenario

A moderate-severity, mid-term supply-chain scenario helps leadership stress-test sourcing strategy before the next planning cycle.

Recommended actions
  • Treat outputs as possible futures — not forecasts.
  • Use scenarios to inform planning, resilience, and advisory conversations.
  • Save briefs for reference and re-run as conditions evolve.
framework

Digital-to-Digital Intelligence

The forward-looking capability for Horizon to exchange structured intelligence with other enterprise systems and platforms.

What it measures

Structured, machine-readable intelligence artifacts that can be produced, consumed, and acted on across systems.

Why it matters

Reduces manual re-entry, accelerates response, and lets Horizon intelligence flow into workflows leadership already uses.

How to interpret results
Foundation
Foundation
Structured intelligence framework established inside Horizon.
Expanding
Expanding
Integration ecosystem being built out with enterprise platforms.
Example scenario

A monitoring alert in Horizon could be routed directly into an enterprise workflow tool so the accountable executive receives it in their existing environment.

Recommended actions
  • Plan integrations against the enterprise platforms already in use.
  • Prioritize systems where Horizon intelligence changes decisions.
Executive Risk Score

How to read the Executive Risk Score

Low Risk
025

Overall risk exposure appears contained. Existing preparedness signals are aligned with the risk profile.

  • Maintain current monitoring cadence.
Moderate Risk
2650

Notable exposure exists in one or more domains but is generally within manageable ranges.

  • Review trends.
  • Strengthen monitoring in the highest-exposure domains.
Elevated Risk
5175

Multiple domains show meaningful exposure. Preparedness gaps may compound impact if left unaddressed.

  • Enhanced monitoring.
  • Executive review.
  • Mitigation planning.
  • Additional assessment where information is thin.
High Risk
76100

Concentrated exposure across critical domains. Warrants leadership attention and a coordinated response.

  • Immediate leadership review.
  • Detailed analysis of driving factors.
  • Strategic response planning.
  • Executive action plan with owners and timelines.
Example
15
Low RiskModerate RiskElevated RiskHigh Risk
Example
38
Low RiskModerate RiskElevated RiskHigh Risk
Example
62
Low RiskModerate RiskElevated RiskHigh Risk
Example
84
Low RiskModerate RiskElevated RiskHigh Risk
Organizational Confidence

How to read the Organizational Confidence Index

High Confidence
80100

Organization demonstrates strong visibility, monitoring, governance, and preparedness relative to its risk profile.

  • Continue current practices.
  • Focus on emerging-risk scanning.
Moderate Confidence
6079

Reasonable visibility is in place, with identifiable areas that would benefit from improvement.

  • Close the highest-leverage information or governance gaps first.
Limited Confidence
4059

Information gaps, monitoring weaknesses, or governance limitations may exist.

  • Strengthen reporting.
  • Expand monitoring.
  • Formalize governance ownership.
Low Confidence
039

Significant blind spots may exist. Leadership may not have sufficient visibility to fully understand current and emerging risks.

  • Prioritize information collection.
  • Establish baseline monitoring.
  • Introduce or formalize risk governance.
Example
92
High ConfidenceModerate ConfidenceLimited ConfidenceLow Confidence
Example
70
High ConfidenceModerate ConfidenceLimited ConfidenceLow Confidence
Example
48
High ConfidenceModerate ConfidenceLimited ConfidenceLow Confidence
Example
22
High ConfidenceModerate ConfidenceLimited ConfidenceLow Confidence
Confidence Rating

How confident is Horizon in its own outputs?

The Confidence Rating tells you how much weight to place on the numbers based on the quality and completeness of available information.

80–100
High Confidence

Strong supporting information and analysis available. Suitable for decision-grade use.

60–79
Moderate Confidence

Some uncertainty or incomplete information exists. Directionally reliable; verify headline calls.

0–59
Low Confidence

Additional information may be required before relying heavily on results. Treat as indicative.

Blind Spot Analysis

Blind spots are what leadership can't yet see.

Blind Spot Indicators highlight areas where Horizon detects potential gaps in visibility, monitoring, governance, preparedness, planning, reporting, or information quality. Organizations are often impacted by risks they fail to identify rather than risks they already understand.

Missing information
Limited monitoring
Weak governance processes
Incomplete reporting
Lack of contingency planning
Emerging risks not being tracked
Limited organizational awareness
Inconsistent data quality
Recommended actions
  • Improve monitoring in flagged domains.
  • Collect additional information where inputs were sparse.
  • Strengthen governance ownership and escalation paths.
  • Conduct additional assessments in weakly covered areas.
  • Improve internal reporting cadence and coverage.
  • Review strategic assumptions against emerging-risk signals.
Action Framework

Recommended actions by risk level

Low
Risk score < 40
  • Maintain monitoring.
Moderate
Risk score 40–59
  • Review trends.
  • Strengthen monitoring.
High
Risk score 60–74
  • Executive review.
  • Mitigation planning.
  • Additional assessment.
Critical
Risk score ≥ 75
  • Immediate leadership review.
  • Detailed analysis.
  • Strategic response planning.
  • Executive action plan.
Risk Legend

The colors used across dashboards

The same four-level palette appears beside charts, heat maps, scorecards, and risk visualizations throughout Horizon.

LowModerateElevatedHigh
Legal Disclaimer

Horizon is an executive decision-support platform designed to assist organizational planning, risk identification, resilience assessment, and strategic decision-making. Results, scores, indicators, analyses, and recommendations should be used alongside professional judgment, organizational policies, regulatory requirements, and applicable expert advice.