Practical software guides
A rollout is not complete because a new screen opens. Define how failed imports, missing attachments, duplicate records and confused users will be recovered before changing the live system.
| Item | Impact | Action and verification |
|---|---|---|
| R-01: missing attachment | One test order cannot be checked | Re-import from approved source; open and match attachment |
| R-02: duplicate customer | Risk of duplicate communication | Hold sends; authorised merge with retained history |
| R-03: wrong role | Unauthorised view possible | Revoke access; check logs and retest permissions |
| R-04: unclear status | Staff cannot finish a task | Correct mapping; user repeats the task successfully |
Set severity by impact, not by which ticket arrived first. Restrict evidence containing personal data. The person marking an item repaired should attach a reproducible check; a second reviewer verifies consequential access or financial changes.
Choose the recovery action
Rollback restores the previous release or configuration. Repair fixes an isolated problem while retaining the new release. Replaying an import can create duplicates unless identifiers and idempotency rules are correct. Do not replay an external payment or message as though it were a local database operation.
Agree a stop threshold and a rollback owner. Track unresolved items and verified closures separately. No launch-success rate or customer deployment is claimed by this specimen.