Using the records
These editable records develop the case-service proposal. Each Markdown template has a completed fictional example with the same headings. Link existing records where they already answer the question.
Environment and dependencies
Connect requirements to execution, storage, connections, identity, capacity, responsibilities and support life. Record the actual version and configuration when a choice is made.
Recovery and continuity
Distinguish an application restart from recovery after lost or restored data. Connect technical restoration to the checks and decisions needed to resume work.
Release and readiness
Identify the change, versions, migration, checks, recovery path and support handover. The comma-separated values (CSV) inventory separates expected and actual results and opens in a spreadsheet.
- Blank release record — Markdown
- Completed release record — Markdown
- Blank readiness checks — CSV
- Completed readiness checks — CSV
Diagram sources
Methodology configuration
Map these fields into the platform, service and change records used by your team. Keep the service requirement and its operational owner connected to the configuration. See Methodology configuration.
Edition and reuse
Version 1.0 · September 2026 · © 2005–2026 Adrian Sutherland.
Refreshed for the September 2026 website update. Keep the edition note with the files and identify adaptations by their source asset, version and filename. The completed examples are fictional; proposed checks need actual results before they can support a service decision.
Read the edition note for authorship and version history.
The Portal-authored downloads use CC BY 4.0: reuse and adapt them with credit, a licence link and changes identified. The edition note records the scope and any separate notices.