Messy search page
What do I call it when a form loses progress?
If users refresh, leave, return later, or hit a failed step and their work disappears, the problem is not just a bad form. It needs state and recovery vocabulary.
Use these terms
Draft persistence
Saves unfinished work safely after meaningful changes so refreshes and failed steps do not erase progress.
Resumability
Lets users come back later and continue from a safe point instead of starting over.
Checkpoint
Names the safe save points where the product can resume without replaying risky side effects.
State reconciliation
Resolves disagreements between UI state, server state, saved drafts, and URL state.
Recovery path
Defines what users see and how they continue after a failure.
Source of truth
Decides which system owns the real current state when the browser, server, and draft disagree.
Prompt pattern
Weak ask
My form loses progress. Fix the save issue.
Exact Terms ask
Audit this form for draft persistence, resumability, checkpoints, state reconciliation, recovery paths, and a clear source of truth across browser, URL, server, and saved drafts.
Common questions
Is this autosave?
Autosave is one tactic. The better vocabulary is draft persistence plus resumability, because the product also needs safe restore and recovery behavior.
What should I ask a coding agent to return?
Ask for ownership of draft state, save points, failure modes, resume rules, and acceptance tests for refresh, back/next, failed save, and return visits.