One click can become two records
A resident submits an application, sees a timeout and tries again. Both requests may reach the server, creating duplicate cases or charges. The gold standard is a service that can handle uncertainty and retries without unfair consequences.
Define transaction identity
A service should distinguish a new legitimate request from a repeated attempt to complete the same action.
Use appropriate technical controls
Idempotency keys, unique constraints and controlled retry logic can help where suitable. Implementation depends on the service and its systems.
Coordinate payments and applications
A payment confirmation, application record and case status may be held in different systems. Their relationships must remain traceable.
Make user feedback clear
Explain when a submission is pending and provide an appropriate status-checking route before encouraging another attempt.
Reconcile exceptions
Duplicate or uncertain records need responsible teams and authorised correction procedures.
Break-test: a batch is replayed after an outage
Can the service prevent repeated effects and identify any cases that still require manual review?
Connected knowledge
See Transaction Reconciliation, Service Restoration Verification and GovTech.