Inventory
A single register of critical systems, with named owners and review dates that do not quietly expire.
Dependency maps
Upstream and downstream relationships recorded explicitly, including the vendors nobody listed.
Audit evidence
Continuity records exported in a form an assessor will accept, without a fortnight of screenshots.
The problem we built for
Most organisations can tell you what systems they run. Far fewer can tell you what happens when one of them stops. The information exists — it is spread across a spreadsheet somebody maintains, a diagram drawn two reorganisations ago, and the knowledge of three people who have been there long enough to remember why.
That arrangement holds until it is tested. Then the questions arrive all at once: which services depend on this one, who owns it, when was the recovery procedure last checked, and is any of that written down anywhere an auditor would accept.
How teams use the Register
Recording what already exists
Most teams start by importing what they have — an asset spreadsheet, a CMDB export, a list of vendor contracts. The first useful output is usually not a map but a gap list: systems with no owner, owners who have left, dependencies recorded in one direction only.
Making dependencies explicit
A dependency that lives in someone's head is not a record. The Register asks for relationships to be stated: this service requires that database, this process requires that vendor, this recovery plan assumes that backup is current. Stated relationships can be reviewed. Assumed ones cannot.
Keeping evidence current
Continuity documentation tends to be accurate on the day it is written and progressively less so afterwards. Review cycles, ownership confirmations and change records keep the register close to reality, so that preparing for an audit is a matter of exporting rather than reconstructing.