Choosing a record
Start with the decision, information or handover you need to record. Each collection pairs blank records with completed fictional examples in Markdown, a plain-text format. Several also provide comma-separated values (CSV) files that open in a spreadsheet, and editable diagram sources. Map useful fields into your team’s existing records.
| Subject | Collection |
|---|---|
| Blueprint | Cover, views and linked records |
| Business architecture and Purpose | Outcomes, information and change |
| Process and Structure | Responsibilities and accepted handovers |
| Information | Definitions, records, lifecycle and processing |
| Systems | Interfaces, components, business rules and recovery |
| Technology | Environments, release and technical recovery |
| Security | Risk, access and continuing controls |
| Management | Direction, decisions and exceptions |
| Finance | Options, assumptions and commitments |
| Metrics | Definitions, observations and decisions |
| Customer | Roles, needs and research |
| Supplier | Responsibilities, dependencies and exit |
| Channel | Journeys and accepted service meaning |
| Deployment and operations | Readiness, support and recovery |
Use and editions
The records use version 1.0, September 2026. Each collection links its edition information; keep this with adaptations. Completed examples distinguish proposed checks from actual results. Keep that distinction when using them.
Use the worked example to follow their connections and Methodology configuration to map terminology and review steps. The review questions help prepare a discussion or examine a record.