Plan how to reverse a faulty automation change

What this means for your practice

Ask the supplier to demonstrate restoring the previous working setup. Separately agree who reviews enquiries, tasks or messages affected by the faulty rule, because restoring settings does not undo actions already taken.

A practical conversation with your supplier

Rehearse a change that misroutes fictional requests, then return to the previous version. Which records still need correction and who owns them? Agree who decides to reverse the change. A successful rollback should leave a manageable list of affected work rather than imply that changing settings repaired everything.

Plan the first improvement

Prepare a practical decision route for reversing a change. Name the person authorised to act, the previous accepted version and the circumstances that should prompt review. The supplier should explain which parts can be restored directly and which actions already taken require separate correction. A rule that sent a message cannot be made harmless merely by restoring its earlier settings. Identify the period and records affected by the faulty version so the practice can review them through the appropriate process.

Include a change that partly works in the rehearsal, not only one that fails immediately before handling anything. Ask how pending work is paused or managed during the reversal and how staff know which arrangement is active. After restoration, verify the intended workflow and assign any remaining exceptions. Keep the reason for reversing the release with the change record. This helps future decisions and makes clear that the recovery addressed both the configuration and the work processed under it.

How to check the result

Track affected work that remains unresolved after the previous setup is restored.