Generally available
From a rule change to a ranked list of who must act
Impact Analysis
- 4 weeks to 4 days
- typical impact assessment cycle
- 2.7x
- more downstream impacts identified vs. workshop baseline
- 92%
- of assessments completed within SLA
The expensive question is never "did something change?". It is "which of our eleven sites does this land on, and who owns the response?"
The problem
What this module exists to fix
Impact assessment is a multi-week exercise
The standard approach is to convene subject-matter experts across sites, circulate the notification, collect opinions in a spreadsheet and reconcile them. It is slow, inconsistent between assessors, and produces no reusable asset.
Nobody has the site model written down
The knowledge of which state, category and headcount applies to which plant lives in the heads of a handful of people. When they are unavailable, assessment stalls.
Second-order impact is invisible
A change to a hazardous waste threshold touches procurement, EHS, finance and legal. Manual assessment reliably finds the first and reliably misses the last three.
Capabilities
What it does
Organisational graph
A living model of legal entities, sites, states, functions, licences, processes, systems, controls, policies and third parties — with the relationships between them.
Automated impact propagation
An obligation change traverses the graph: obligation to site to control to process to owner. Direct and downstream impact are distinguished and scored for materiality.
Heat maps by any dimension
View exposure by entity, site, state, domain, deadline or severity. Drill from a red cell straight to the obligations and owners behind it.
Gap and readiness assessment
For each impacted obligation, capture current state, target state, gap, remediation plan, owner and target date — with structured templates so assessments are comparable across sites.
Effort and cost estimation
Estimate change effort using your own historical actuals, so a remediation business case is grounded in what similar changes cost you last time rather than a finger in the air.
Scenario modelling
Model a proposed rule at draft stage against your footprint, and quantify the difference between the draft position and the likely notified position before it takes effect.
How it works
Step by step
- 01
Model
Build the organisational graph — imported from your HRMS, ERP, product master and entity registers, then refined.
- 02
Link
Obligations attach to controls, processes and licences, giving the graph its regulatory edges.
- 03
Propagate
A change event traverses the graph and produces a scored, ranked impact set within minutes.
- 04
Assess
Impacted owners receive a structured assessment task with the provision, the delta and the current-state evidence already attached.
- 05
Plan
Confirmed gaps become remediation items with owners, dates and dependencies, pushed to your delivery tooling.
Questions
The things people actually ask
Including the ones where the answer is a limitation.
- How much work is it to build the organisational graph?
- A first usable model typically takes three to five weeks with a part-time working group, and most of it is imported rather than typed. You do not need it complete to get value — the graph earns its keep from the first site you model.
- Can impact analysis run without the full graph?
- Yes. With only entities and sites modelled you get site-level impact immediately. Depth of the graph determines depth of the answer, and you can deepen it incrementally.
- Does it replace our internal risk assessment?
- No. It feeds it. Impact analysis tells you which sites and controls a regulatory change disturbs; your own risk assessment remains the judgement of how well those controls work.
See Impact Analysis against your own footprint
A two-week scoped pilot on your real entities and jurisdictions. You compare the output against what your team found in the same period.