Solution
The operations file
The question isn’t only whether IT works, but whether an authorised third party can perform priority tasks with the available access and dependencies. The record becomes evidence when another person actually uses it.
The knowledge written down nowhere
Operating continuity increases
Holidays, illness or departure become scenarios that can be rehearsed. Continuity still depends on the documented access, suppliers, skills and systems.
The insurer and the auditor get their answer
A diagram, inventory, dependencies and procedures provide factual material for some questionnaires. Scope and acceptance remain with the insurer or auditor.
The next provider starts faster
Including if you replace me. The handover test measures what the record actually enables and what still requires discovery.
The hidden dependencies surface
The scheduled task on a server nobody watches, the service account with an eternal password, the certificate expiring in eleven months. Writing it down reveals them.
In practice
- An architecture diagram readable by someone meeting the environment for the first time
- An inventory of hardware, software, licences and access, with their dates
- A dependency map: what falls over if a given machine stops
- Operating procedures per task, written to be followed without you
- Contacts and contracts: suppliers, support numbers, renewal dates
- A versioned, dated document, with a review scheduled rather than hoped for
Systems involved
- Inventory and asset management tools already in place
- The directory and the password manager, for the access list
- Backup systems, for what is genuinely protected
- A Git repository or an internal knowledge base, to hold it
- Contracts and supplier portals, for the renewal dates
Service lineServers and hosting →
Which environments
The same work, against each sector’s own constraints. Every card opens the full sector.
Energy and utilities
Handing over operations
Diagram, inventory, dependencies and procedures written for an operator taking over without having followed the project, remote sites included.
Healthcare and life sciences
Governance and traceability
Who has access to what, what was processed, what is kept and for how long, written down and kept current.
How it runs
Survey
The survey takes as long as the systems, suppliers, access paths, exceptions and sources demand. The scope gets set before any console opens.
Writing
Diagram, inventory and dependencies, written for a reader who has never seen the environment.
Test
One procedure is followed by somebody else, to the letter. What is missing shows up immediately.
Upkeep
A dated review, and the simple rule that an architecture change gets written down as it happens.
Test the fit: The operations file
Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.
Describe the situation