Guide · 5 min read
Save and resume: letting people finish a form later
Updated 2026-09-17
TL;DR
A save-and-resume option emails the respondent a link that reopens the form with their answers already filled in, so a long form doesn't have to be finished in one sitting.
Some forms just take longer than one sitting to fill out — a detailed application, a multi-page survey, anything that asks someone to go dig up a document or a number they don't have on hand. Forcing a single unbroken session on those forms is where a lot of drop-off happens. Save-and-resume fixes that by letting a respondent leave and come back to exactly where they stopped. This guide covers when it's worth adding, how the flow works for the respondent, and what keeps a resume link secure.
When a form needs save-and-resume
The signal is length and friction, not field count alone. A 15-field form that's all quick multiple-choice can usually be finished in one go; a 6-field form that asks for a tax ID or a document upload someone has to go find cannot. If you notice partial completions in your response data, or the form realistically takes more than five minutes, save-and-resume is worth adding.
It's less useful for short, low-friction forms — adding a save step there is one more click before people can leave, without much benefit.
How the flow works for a respondent
Partway through the form, the respondent enters their email and asks to save their progress. They get an email with a link; opening it later reopens the form with everything they'd already answered filled back in, starting from where they left off.
Because the state is tied to a specific link rather than a login, there's nothing to remember beyond checking that one email — no separate account or password.
What makes a resume link safe to use
A resume link should not be a guessable URL. The token in the link should be long, random, and checked against a stored, hashed value rather than compared in plain text, and it should expire rather than stay valid forever.
It's also worth tying the saved answers to a specific version of the form. If the form changes materially after someone saves progress, resuming against a stale schema can produce confusing or broken results — reject the link instead of silently mismatching.
Setting expectations for respondents
Tell people up front, near the save option, roughly how long the link stays valid so they don't sit on it indefinitely and then find it's expired. A short note like "this link works for 30 days" avoids a support email later.
If a resume link does expire, the form should fail clearly — a plain message that the link is no longer valid, not a blank or broken page.
How YeetForm handles it
In YeetForm, a respondent partway through a form can save progress by email: it sends a resume link and stores a hashed token that's valid for 30 days and tied to the specific form version they were filling out, so opening the link later hydrates the form exactly where they left off.