# ACAR workflow from signal to closure AI Change Accountability & Reauthorisation · 30 September 2026 · CC BY 4.0 1. Prepare scope and authority. Name the event owner, authority and record system. 2. Record and classify the signal. Establish the baseline, proposed or observed change, evidence and applicable triggers. 3. Apply §6.4.4. If all R0 conditions are met, document the routine-change basis, O0 confirmation, interim position and standing review in the short record. Otherwise select R1, R2 or R3, record interim permission, obtain required inputs and record the authorised final outcome. 4. Implement and evidence the decision. Assign actions, owners and deadlines; retain implementation and verification evidence. 5. Apply the route-specific closure requirements in §10.4. If they are not met, retain open issues with owners and due dates and complete the required work. If met, record the closure confirmer and evidence, preserve history and set ongoing review. 6. A new trigger or missed required review opens a linked current review. Reassess the route and interim position while preserving the historical closure. Urgent protection and parallel response processes take priority. A review route does not predetermine the final outcome. The reference guide controls all routing and closure requirements. Original materials © 2026 Maja Kurek · RuleBridge Advisory. CC BY 4.0. https://creativecommons.org/licenses/by/4.0/