Write a status map with explicit exits
For every status, record meaning, authoritative source, permitted next steps and the customer's possible action. Define paused, cancelled and reopened separately. A numerical sequence is insufficient when a case can legitimately return to active work.
Fictional service example: received may become scheduling or declined; in progress may become waiting or closed; closed may reopen after an approved decision. This is a discussion model, rather than a universal workflow for every business.
Exercise delayed and repeated events
Replay the same test event and deliver an older update after a newer one. Define which version or ordering evidence governs the change. Arrival time alone can mislead when transfer is delayed.
Check that an old event does not unintentionally move the customer from closed to in progress. A legitimate reopening must still be possible when the right source authorises it. Always selecting the highest status number does not solve both problems.
| Exercise | Question | Customer-view check |
|---|---|---|
| Normal transition | Was the decision saved on the right case? | Correct stage with clear meaning |
| Same event again | Does an unintended repeat occur? | No false new activity or notification |
| Older event arrives late | Which version may change state? | No unintended regression |
| Approved reopening | Is there a valid path to an active case? | Reopening is clear without a false completion promise |
| Notification fails | Are storage and sending separate? | Saved status remains; delivery failure can be followed up |
Trace the notification to a saved change
Simulate notification failure after state is saved. Check how an operator finds it and how a retry remains associated with the same change. Do not repeat the business action simply because its message was not delivered.
Test two rapid status changes too. An older email must not present an outdated fact as a new definitive commitment. Wording, event time and the route to current portal status need to fit the real process.
Check clarity and report the limits
Review the status on mobile and with a keyboard. Where content updates without navigation, important feedback must be perceivable without sight; avoid announcing every background fetch. Manual assistive-technology testing is needed beyond automated checks.
Record event ordering, source version, saved state, visible wording, notification and exception owner. A passing exercise establishes this sample in this environment. It is not a guarantee of future operation or a confirmed delivery forecast.