What could be affected?
Identify the relevant sites, people, suppliers, places, and business systems.
Connect infrastructure, communities, services, and economic activity to plan for complex, cascading disruption.
Identify the relevant sites, people, suppliers, places, and business systems.
Trace direct, indirect, delayed, and cross-sector pathways.
Compare intervention points, trade-offs, and uncertainty.
Match external events to the assets, suppliers, routes, markets, and portfolios that matter to your organisation.
See what may happen first, what could follow, and when—from the next day to the next three months.
Turn evidence and scenarios into clear trigger indicators, priorities, and decision options.
A useful scenario shows what happened, which parts of the business depend on it, how the effects could spread, what the consequences may be, and which actions could change the outcome.
Bring event, environmental, operational, and proprietary data into a continuously updated view of emerging risk.
Learn more MapMap suppliers, infrastructure, places, assets, and economic relationships as one queryable network.
Learn more SimulateCompare what may happen next, when effects could arrive, where they could accumulate, and which actions could change the outcome.
Learn more PrioritiseCompare the possible operational, financial, and wider consequences so teams can focus attention and resources where they matter most.
Learn moreThe framework keeps data provenance, model validation, uncertainty, research, and decision outcomes visible as evidence is verified and published.
An upcoming framework for examining connected exposure, propagation, and intervention.
Read moreA forthcoming practice note on turning signals into decision-ready context.
Read moreAn upcoming briefing on how dependency mapping supports resilience planning.
Read moreThese answers describe the current operating principles. Product-specific sources, controls, integrations, and documentation will be published as they are confirmed.
DominoRisk is designed to combine organisation-authorised data with appropriately licensed public and commercial sources. Sources, refresh cadence, provenance, permissions, and permitted uses will be documented for each deployment.
Validation is proportionate to the decision context. Documentation will identify assumptions, uncertainty, data limitations, applicable back-testing or sensitivity analysis, expert review, and the conditions under which a model should not be used.
Implementation begins with the decision, users, data permissions, and required outputs. Available integrations and export formats will be documented as they are released rather than implied in advance.
Sensitive or confidential information should not be submitted through the public website. Production security and privacy controls will be documented in the Trust Centre before they are relied upon for protected data.
We can shape a focused deployment around your exposure data, operating decisions, and the time horizons your team manages.