This standard ensures systems are documented in ways that reflect their real-world evolution, not just their initial design. It helps teams onboard faster, make safer changes, and understand system intent over time.
Aligned to our "Architect for Change" policy, this standard reduces knowledge gaps, supports continuous improvement, and ensures documentation stays useful. Without it, teams risk misalignment, rework, and slower delivery.
Level 1 – Initial: Documentation is missing, out-of-date, or only created at the start of a project. System knowledge is tribal and reliant on specific individuals.
Level 2 – Managed: Some teams maintain documentation, but it is updated sporadically. It may reflect intended architecture more than the current or evolving system state.
Level 3 – Defined: Documentation practices are standardised across teams. Living documents reflect system evolution, and updates are part of regular engineering workflows.
Level 4 – Quantitatively Managed: Documentation quality and coverage are tracked. Updates are linked to system changes through tooling and review processes, ensuring traceability and accuracy.
Level 5 – Optimising: Documentation continuously evolves through team feedback and automation. It reflects real-world use and change, accelerates onboarding, and supports architecture decision-making at scale.