Skip to content

Know what keeps the doors open

Build a one-page technology register

Create a useful operating inventory without turning the project into a months-long asset-management exercise.

TARGET OUTPUT

What this field note should leave behind

A named owner can see the critical accounts, devices, services, data, renewal dates, recovery paths, and outside contacts on one maintained page.

SEQUENCE / 04

Work the problem in this order

  1. 01

    Start with business jobs, not product names. List how you take orders, collect money, schedule work, communicate, store records, and deliver the service.

  2. 02

    For each job, name the primary system, accountable business owner, administrator, billing owner, information held, renewal timing, and fallback.

  3. 03

    Mark the five systems whose loss would stop or materially disrupt the business today. Give those systems a recovery contact and an offline reference.

  4. 04

    Set a short monthly review. Update the register after a purchase, cancellation, staff departure, major permission change, or vendor change.

CHECK BEFORE CLOSE

Evidence worth seeing

  • The register does not contain passwords, recovery codes, private keys, or full payment details.
  • Every critical system has both a business owner and an administrative owner.
  • The billing contact, renewal date, export path, and cancellation path are visible.
  • A second trusted person can find the register during an outage or absence.
ESCALATION BOUNDARY

Know when general guidance stops

Use qualified help when the inventory reveals unknown administrators, inaccessible accounts, unsupported systems, regulated information, or no workable recovery path.