VANKPA
The decision
Session expiry should protect access without unexpectedly erasing work. Decide what can be preserved, how the user is informed, and where they return after signing in again. The behavior should fit the sensitivity of the data and the task.
In practice
A staff member completing a long inspection should not discover at submission that the app silently stopped accepting requests. Warn or recover appropriately, preserve permitted draft data, and make reauthentication understandable.
- Test expiry during editing, upload, approval, and background activity.
- Confirm what remains on the device and what is sent to the server.
- Review shared-device use and avoid restoring private content to the wrong account.
When to take the next step
Review expiry behavior before releasing long forms or field tasks. Use realistic task durations and inspect what happens when the user returns from background activity.
Questions clients ask
Should every draft survive logout?
No. Define draft storage according to the data, device context, and access requirements.
What should happen after login?
Return the user to a valid task state and explain whether a draft was retained.
A worked scenario
Consider a service app used for long inspection forms. The useful outcome is to protect access without losing unfinished work. This is a planning example, not a reported client result. The team needs a decision that can be checked against real work, rather than a feature list that looks complete during a presentation. The starting question is whether the proposed approach changes that particular task in a way the people doing it can recognize.
In this situation, a renewal producing duplicate submissions is the failure to guard against. Ask the responsible person to demonstrate an ordinary case and one difficult case using current records or safe test data. Record what they expect to happen, what actually happens, and where they need another person to intervene. Those observations establish the scope for this example; they do not justify an assumed improvement percentage or a guaranteed business result.
Decision checkpoints
| Checkpoint | Practical action | Evidence to retain |
|---|---|---|
| Prepare | Identify drafts safe to preserve locally. | The approved scope, relevant source records, and unresolved questions. |
| Verify | Explain expiry and restore the task after sign-in. | The test case, expected result, observed result, and correction needed. |
| Operate | Test expiry during submission and attachment upload. | The responsible owner, completion record, and next review trigger. |
Use these checkpoints to protect access without losing unfinished work; they are a sequence of decisions, not a promise of a particular schedule. A completed document or screen is not enough if the underlying action still fails. Keep unresolved items visible and describe which ones prevent progression. The evidence can be a small test record, an approved mapping, or a reviewed example. It should be understandable to someone who was not present when the work happened.
Measure the useful result
A useful check for this topic is expired-session tests recovering the intended task divided by tested expiries. The numerator is expired-session tests recovering the intended task; the denominator is tested expiries. Define the sampling window, exclusions, and source of each count before interpreting the result. If only selected examples can be reviewed, describe them as a sample. Do not present a small reviewed group as a complete picture of the business, and do not assign a target simply because a round number looks persuasive.
The measure helps reveal whether the team can protect access without losing unfinished work, but it does not explain every cause of success or failure. Inspect the underlying cases alongside the summary. If the count changes after explain expiry and restore the task after sign-in, check whether the operating result changed or the counting method changed. Retain enough context to explain the difference. When records are incomplete, state the limitation and use a direct task review instead of manufacturing a precise-looking estimate.
Step 1: Prepare the evidence
The first practical move is to identify drafts safe to preserve locally. Start with the smallest set of examples that covers the important variation in this scenario. Include an ordinary case, a case with missing information, and a case that requires intervention. Describe the intended result before reviewing the current behavior. This keeps the preparation focused on the outcome: protect access without losing unfinished work.
For a service app used for long inspection forms, the person responsible for the source information should take part in preparation. Ask that person to confirm which information is authoritative and which points still need a decision. Record those uncertainties beside the scope instead of hiding them in a general assumption. Preparation is complete when another team member can follow the agreed example and explain what evidence would allow the work to continue.
Step 2: Test the difficult case
The next move is to explain expiry and restore the task after sign-in. Compare expected behavior with observed behavior in the same test, rather than comparing two descriptions written at different times. Pay particular attention to a renewal producing duplicate submissions. A demonstration that works only for its author does not establish that the intended user can complete the task. Let the reviewer attempt the work with the instructions they would normally receive.
For this check, retain the input, the relevant condition, and the final disposition. A screenshot can illustrate the state, but the record also needs to explain what the team expected and why the result matters. If the draft contains material that cannot safely remain on the device, hold the decision open and send it to someone with the authority to resolve it. Retest the changed case after correction; an agreement to fix something is different from evidence that the correction works.
Step 3: Assign operating ownership
The operating move is to test expiry during submission and attachment upload. A successful initial test should lead to a repeatable responsibility, not a permanent dependency on the person who built the solution. Name the person who reviews the result, the person who can change the rule, and the person who responds when the task fails. In this scenario, each responsibility contributes to the same outcome: protect access without losing unfinished work.
Give the operator a short record of what healthy work looks like and what requires intervention. Include the warning case of a renewal producing duplicate submissions, together with the relevant records and support route. The procedure should be usable during normal work, not only during a formal review meeting. Check that an authorized backup person can follow it before treating the approach as ready for broader use.
Handle exceptions deliberately
The specific pause condition is that the draft contains material that cannot safely remain on the device. Make the pause visible to the person doing the work and to the person responsible for resolving it. Preserve the relevant context so investigation does not depend on memory. A stopped case is still part of the process; it needs a status, an owner, and a safe route back into ordinary work after the uncertainty is resolved.
Before restarting, establish whether a renewal producing duplicate submissions affected only this case or indicates a wider rule problem. Correcting one record may be appropriate for an isolated exception. A recurring pattern may require changing the definition, interface, routing, or review procedure. Test the restart against the original case and one related variation. Record the reason for the change so later reviewers can distinguish a deliberate decision from an unexplained workaround.