Architecture Portal

Organisation and process templates

Roles, handovers and readiness.

Adrian Sutherland · Version 1.0 · · © 2005–2026

Using the records

These editable records develop the cancellation handover. Each Markdown template has a completed example with the same headings. The comma-separated values (CSV) responsibility table opens in a spreadsheet. Use the questions that help and map them to records your team already maintains.

Roles and authority

Record what a role does, what it can decide, required skills and access, capacity, cover and escalation. Distinguish roles from named assignments.

Handover and exceptions

Describe the trigger, information, acceptance, waiting work and failure paths. Include the current owner, receiving role, effective transfer and history.

Change and readiness

Record the proposed change, affected people and records, training, access, capacity, checks and the decision to start or stop a trial. Include work performed by supporting services, delegated actions and the responsibilities for an interrupted handover.

Diagram sources

The diagrams are newly authored illustrations. Mermaid text and structured JSON retain their labels and connections for adaptation.

Methodology configuration

A team charter may already describe authority and cover; an operating procedure may contain handover rules. Link the records needed to understand the decision, using your method’s terms and review steps. See configuration guidance.

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.

About this edition

Refreshed for the September 2026 website update. This edition develops the earlier Architecture Portal and ASAF material; the fictional worked example was added in 2026.

Scope, limitations and next checks

Status and accountability

Read this page with its boundaries visible

Status

In development

Last reviewed

Intended users

  • Architects adapting an existing approach to organisation and process

Non-goals

  • A prescribed organisation structure or automation platform

Limitations

  • Guidance illustrated by a fictional example; proposed checks and benefits require application.

Next evidence sought

  • Review responsibilities and try the records with an existing method.