Published

A financial application team adds an independent evidence check before final approval. Twelve application files are already waiting for review, correction or a final decision. Changing the route for tomorrow's applications leaves a practical question: which of those twelve need the new check?
Approve the treatment of existing work alongside the new approval rule. Identify the affected files, decide whether they can continue or need further review, and give every unresolved file an owner. Preserve earlier decisions and record what authorises the next action.
State the reason for the change and its effective time. Then define its scope: new submissions only, all unresolved applications, a particular document class, or a named set of files. A received date and a final-approval date select different populations. Make the chosen boundary explicit.
Use the same assessment for department processes, separate business use cases and customer tenants. An independent check introduced for one programme should affect the files covered by that programme's decision. An urgent correction may require an immediate hold on affected work; assign someone to resolve that hold and its business deadlines.
List the files, current stages, recorded decisions and pending actions affected by the change.
Choose what may continue, what needs another check and which actions must wait.
Check the changed process in use and resolve every file left outside the intended route.
| Treatment | When it can fit | What to establish |
|---|---|---|
| Continue under the earlier process | The authorised change applies only to later submissions, and earlier work may finish under the old requirements. | The eligible files, reason, responsible reviewers and permission to complete remaining actions. |
| Add or replace a review | A new check applies to unresolved files, while some completed work remains relevant. | The evidence each reviewer must see, earlier work that still counts and the prerequisite for proceeding. |
| Start a fresh review | Changed scope or evidence requires a new decision rather than a continuation of the earlier review. | The reason, connection to the earlier review, new assignments and treatment of outstanding tasks. |
| Hold affected work | The owner has not resolved the transition or a defect makes further action inappropriate. | The blocked actions, owner, review point and conditions for resuming work. |
A recorded approval establishes what that reviewer accepted at the time. If the revised process asks a materially different question, record the additional decision it needs. Keep the earlier approval visible without treating it as an answer to a check that did not yet exist.
For each affected file, retain the reviewed document revision, current stage, accepted decisions, pending corrections and next action. Include messages or external requests that have already been sent. A change of review route should not accidentally send the same agreement, notification or downstream instruction again.
Give staff a useful explanation: “Independent evidence check required before final approval” tells them more than a generic changed status. Clear obsolete assignments through the approved process and show who now owns the work. Review access separately when responsibilities change; assignment alone does not grant permission to the documents.
The concurrent-review guide covers competing decisions and concerns raised after completion. The document-action retry guide covers uncertain or repeated downstream actions. Use those controls within the agreed transition rather than assuming that restarting a process is harmless.
This fictional change extends the FIN-1042 review workflow. The process owner requires an independent evidence check for every application still awaiting final approval at the changeover time. Seven files await initial review, three await corrected evidence and two await final approval. Four previously completed files are outside this transition's scope.
The owner approves the new check, effective time and twelve-file list. FIN-1042 is one of the two files awaiting final approval. The record identifies the independent reviewer and the documents that person must assess.
The seven initial reviews and three correction cases retain their necessary work, with the independent check required before final approval. The two files already at the final stage wait for that check. Existing reviews and corrections remain connected to their files.
Using representative test files at all three stages, the team verifies that the intended reviewers can act, incomplete checks prevent final approval and earlier actions are not repeated. It also tests a submission that arrives during the changeover and an outstanding correction returned afterwards.
Staff see FIN-1042 awaiting its independent check. The earlier review remains visible. If the new reviewer finds missing evidence, the application returns to the appropriate correction route; the earlier approval does not satisfy the new requirement.
The owner checks each file against the approved list. A completed check permits the next authorised stage; a correction, hold or unresolved assignment retains an owner. The four completed files remain outside the change, with their earlier decisions preserved.
If a revised procedure also changes the work people must learn, the document-change and retraining guide covers that separate readiness decision.
A process change is ready when staff can explain which files it covers, what each file still needs and why earlier decisions remain relevant. Release the new route with an approved treatment for existing work, then verify the result against the affected-file list.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.