The release quality loop
Give a finding an owner, investigate the source and review a compatible follow-up result. Keep the remaining findings with the handover.
What changed after the correction?
Two findings resolved. No new findings. Review the comparison, then play the complete recorded path from Browse to the report.
The stored runs from 22 September check the same twelve synthetic Patients before and after correcting identifier use at the source. Two terminology findings resolve, no new findings appear and 24 information occurrences remain. Current resource findings can differ from these recorded results.
A closed task is not itself a verified correction. Check completion, review remaining findings and confirm that the scope and recorded inputs support the comparison. Investigate a new finding against a baseline.
Where the loop shows up
Apply the workflow to the decision your team needs to make.
Release & CI
Release Safety
Run the loop before a promotion and decide from the delta, not from the absence of incidents.
Change & comparison
Drift Detection
Run it on a schedule and separate a real regression from pre-existing debt.
Release & CI
CI/CD Quality Gate
Run it in the pipeline so the exit code carries the decision.
Quality & evidence
Validation Reports
Keep the last step — the exported evidence — as the artifact an auditor receives.
Apply the loop to your next delivery.
Bring a permitted test delivery, the change to verify and the person responsible for reviewing the result. Saved runs, comparisons and reports use a Records workspace.