Decide where the work belongs
Rank work at risk
Describe lost text, selections, repeated rows, files, or relationships and whether the user can reconstruct them accurately. Give higher priority to long or consequential submissions.
Rank recovery quality
Check browser back, refresh, duplicate tabs, or manual reconstruction and record which paths work consistently. A hidden server draft or accidental browser cache is not a clear user recovery path.
Set a correction checkpoint
Choose a review after form, validation, nested-parameter, or error-rendering changes. State which representative draft must survive and which invalid field should remain highlighted.
What to carry forward
The queue result should name the lost draft scope, blocked workflow, recovery quality, owner, and checkpoint. Keep priority high when meaningful work disappears or corrections require re-entry; lower it only with reliable retention evidence. Raise priority when users lose substantial text, repeated inputs, relationships, or attachments and must reconstruct them; a single harmless default reset can stay scoped.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow