Contingency priorities
- Most critical mechanism: Mechanism: Region A to Country X (stops 3 items).
- For the scenario: none stops none.
Global Compliance · Expanded Global Compliance
Map obligations across countries, states, regions and local jurisdictions, including overlapping or conflicting requirements and uncertainty about which applies.
Demonstration: Osterley Components GmbH (fictional) · Industrial manufacturing. Fictional data and a scripted answer.
If the transfer mechanism for one country stops being valid, which of our data flows and services are affected?
Fail one or more items and see what stops and what only degrades, worked out by following the dependencies.
Choose what loses its transfer mechanism. Hard dependencies stop with it; soft ones carry on, degraded.
Simulated answer. Written for this fictional case, not produced by a live model. Only the figures in it are computed, from what you decided above.
Following the data flows, losing none stops none and degrades none [S1][S2]. The most consequential single mechanism in this map is Mechanism: Region A to Country X, which stops 3 other item(s).
A flow with no lawful route has to stop or be re-papered, and the order matters: payroll is dated, marketing analytics is not. The map shows which dependencies force a deadline.
Relies on: S1 · Data flow mapS2 · Transfer mechanism register
The data protection officer decides. Approving fixes the contingency priorities for transfer mechanisms. It does not stop any flow or sign any clause.
Not ready to approve. Fail at least one item first, to see what depends on it.
In the product this is a different person with the right permission. Here you play that role to see the rule.
The Global Compliance story · This capability in the full register