What changed
One question
Business Context asks for your major business functions, each with a rough share of revenue and how long it can be down. Pre-filled from your industry and revenue model.
Supplier fields
Adding a vendor asks what stops or slows if it's down, and whether there's a tested backup. Criticality is worked out from the answers.
Connection step
Connecting a cloud account or database asks which functions each discovered system supports, with guesses filled in. Test systems are skipped.
People tag
“Can restore” on a person, with a backup. If only one person can restore a system, the map flags it.
The map
Functions, systems, suppliers and people in one view, with the revenue a day each link carries.
Changes to confirm
Proposed links appear dashed, with what they'd change. Confirm them, or say why they're wrong so they aren't proposed again. Nothing counts until it's confirmed.


Why it matters
Impact analyses start as long questionnaires and go stale within a year. Collecting each answer where the data already enters keeps the map current without anyone owning a spreadsheet.
It's what makes Resilience, Early Warning and the outage losses in Portfolio trustworthy: the revenue at risk comes from what the business said, not what we assumed.
Availability
Intake questions ship today on Business and up. The map and Changes to confirm are on Enterprise.
Open it at Settings → Business Context → How the business runs. Answers given before upgrading carry over.
Known limitations
- Proposed changes are reminded after 14 days and passed to the admin after 30.
- Organization charts are read from a connected identity provider. Without one, add “can restore” tags by hand in People.