Autosave protects work; deliberate submission marks a process transition. Use both. Save entries as the client works without interrupting them, show the save status and ask for a reviewable confirmation at the end before staff treat the response as submitted.
A form without autosave penalises connection problems and distractions. A form without a final submission step leaves it unclear when the client has finished. The two functions solve different problems.
Make drafts and submissions visibly different
Yindle Portal uses a draft response followed by a submitted or confirmed status. Answers can be saved while the form is being completed; the final step shows a review summary. Use wording such as ‘Saved as draft’ and ‘Submit final response’, rather than two versions of ‘Save’.
Also explain whether a submitted form can still be changed. If a change requires help, show the correct route and the current version of the submission.
Design autosave for unreliable connections
Do not send an unlimited stream of save requests with every keystroke. Use a short delay, prevent overlapping requests and show three states: saving, saved and not saved. If an error occurs, keep the entries on screen and give the client an option to retry.
Check on the server whether the user still has access and whether the form is still open. An old browser tab must not silently turn a confirmed submission back into a draft.
Worked example: a fictional moving service
In this fictional example, moving coordinator NieuweStart asks about rooms, large furniture and special requirements. Customer Bo enters the living room details on a phone while travelling; the train connection drops. The page shows ‘not yet saved’ and retries when reception returns.
At home, Bo opens the questionnaire again and sees the draft. After the final room, a summary shows quantities and points to note. The task only appears for the planner after ‘Submit inventory’ is selected. The planner therefore does not see a half-completed list as ready.
Test the states
| Situation | What the client sees | What administrators see |
|---|---|---|
| New | Not yet started | Open task |
| Partially completed | Draft saved | In progress; do not use the content as final |
| Connection error | Not saved, with a recovery action | Latest valid draft |
| Submitted | Receipt and summary | Ready for review |
| Confirmed | Outcome and date | Completed process step |
Test every transition with two tabs and two devices. Also have a staff member publish or archive the form while a client is working on it. The error message must explain what has been retained and how to continue.
Measure lost work and uncertainty
Track failed saves, repeated submission attempts and support questions such as ‘did you receive it?’. These signals tell you more than the percentage of submitted forms alone. Do not add more pop-ups before you know the actual cause.
Keep the confirmation available in the case record. An email can supplement it, but must not be the only place where the client can see what was submitted.
Test conflicts between devices. Bo may have an old tab open at home while a newer answer has been saved on the phone. Decide whether the latest change wins, the form is temporarily locked or the user receives a conflict message. Silent overwriting is the least understandable outcome.
Make the autosave indicator accessible. A brief green flash alone is not enough. Use text that a screen reader can announce without interrupting every letter. Keep the last saved time in a fixed position so it does not jump around while someone types.
Limit what a draft triggers internally. A half-completed form must not initiate an order, final document or external task. If staff may view draft information to offer help, clearly mark it as incomplete and do not treat it as consent or a decision.
Set a retention policy for abandoned drafts. An endless collection of old entries makes case records unclear and can retain unnecessary data. Consider sending one targeted reminder, archive according to agreed periods and tell the user what will happen to the draft. Have those periods reviewed appropriately.
Include a browser crash, expired session and server error in the release check. After signing in again, users must know which parts were safely saved. Confidence in that recovery is the real value of autosave.
Explore the form and case management features of Yindle Portal or read the guide building a customer portal. To work out your draft and submission states, test one form with Yindle.