ADM-E7 — A new policy starts while earlier cases remain open

• Situation: A service owner is introducing an allowance while receipt-based journeys, unsettled payments and disputed claims remain.

• Question: How can the authorized change become usable without losing the conditions that still govern earlier cases?

• First useful result or blocker: A decision by the authorized policy owner and usable handling for the affected cases, or the missing policy, provider or evidence contribution; adequate evidence may instead support retaining the arrangement.

• Start with: ADM.16 - Decide Whether and How to Change an Administrative Arrangement Without Losing Open Cases, using the actual retention or change question and one case whose treatment could differ.

• Stop or return: Finish the selected change with the promised provision and continued support for the earlier cases that still need it; identify any unresolved cases and their next responsible action. A new form, successful data import or quiet old queue does not settle a grant, obligation or required historical use.

1. Use consequences to select the change, not merely a closure count. ADM.15 - Judge Administrative Consequences separates usable provision, correct and mistaken refusal, unresolved effects and work shifted to applicants. Its access-service case has 70 closures among 80 registered requests, but only 60 confirmed provisions; twenty additional requests failed before registration. Such an account can justify correcting an established defect without waiting for a general effectiveness study. A proposed policy change still needs its own grounds and competent decision.
2. Apply the adopted transition to the fact that selects the regime. In ADM.16’s constructed allowance case, journeys authorized before 1 November retain receipt-based terms; later authorizations use the allowance. A journey authorized on 28 October, performed on 3 November and claimed on 6 November therefore keeps the earlier terms. A recorded election before disbursement can select the permitted variant only with the confirmation required by the adopted rule. Unknown authorization or election facts remain specific questions, not guesses from the form version.
3. Turn that decision into usable handling. ADM.5 - Design Reusable Instructions for Administrative Requests consumes the policy and transition conditions to specify the minimum request, necessary checks, competent decision, provider action, completion evidence and exceptions. ADM.11 obtains the provider contributions and resolves their joins. If a control gives the wrong response, ADM.14 - Connect an Administrative Control to Its Purpose and Competent Decision distinguishes a defective test or implementation from a policy requiring authorized change.
4. Establish usable handling and preserve unresolved effects. For the changed provision, perform the bounded trial or rehearsal required before widening reliance: include an old-regime case, a new-regime case and the consequential election or unknown-payment branch. The recipient must obtain the promised result; a converted record is only one input. For an unchanged use, reuse adequate existing observations. A new staff exercise is needed only if its result can change the assignment or support decision. ADM.9/.10 recover an earlier payment effect before another payment or conversion that could duplicate it. ADM.13 retains the grounds needed for active disputes and legitimate historical use. Ending new requests through an old form does not by itself authorize disposal of those records.

The Preface explains the common boundaries and the wider provider relationships. When ordinary handling cannot resolve a missing rule, authority or effect, ADM.6 - Resolve an Administrative Exception sends an answerable question to the competent participant while preserving independent permitted work.