What if the new application form fails after launch?
A public service deploys a revised form, then discovers that saved drafts cannot be submitted. Rollback readiness helps the agency restore a safe service without corrupting applications or creating duplicate payments.
Define rollback conditions
Identify failures that justify reversal, correction or controlled suspension under authorised procedures.
Preserve data compatibility
A new form may introduce fields that an older version cannot interpret. Plan how records will be handled safely.
Protect transaction state
Payments and accepted submissions should not be duplicated or silently lost during rollback.
Test recovery paths
Use representative drafts, submitted cases and exceptional situations before deployment.
Assign decision authority
Technical and service owners need clear roles for initiating rollback and communicating impact.
Verify after recovery
Check that users can complete valid applications and that existing records remain consistent.
Break-test: some users submit under the new version before rollback
Can the agency preserve those legitimate cases while restoring the service?
Connected knowledge
See Form Migration Safety, Draft Version Reconciliation and GovTech.