System end-of-life planning begins during architecture design and executes when the system reaches the end of its operational life. The regulatory basis establishes the AI Act obligations that survive decommissioning. End-of-life triggers define the events that initiate the decommission process: planned retirement, regulatory withdrawal, performance degradation, and organisational change. End-of-life planning covers the decommission plan, stakeholder notification, transition planning, and timeline. Seven decommission workstreams address system shutdown, data disposition, model archival, documentation preservation, deployer transition, regulatory notification, and knowledge transfer. Post-decommission obligations cover the ten-year documentation retention, ongoing regulatory response, and liability management. The section concludes with artefacts.

Note: This section corresponds to the End-of-Life section and feeds primarily into AISDP Module 12 (Post-Market Monitoring) and Module 10 (Record-Keeping).