Two features keep long forms friendly: drafts let someone leave and come back, and edits let them fix an answer after they have submitted. Both are off until you turn them on under Settings > Access & limits.
Saved drafts
Turn on Save partial responses and Autosave while typing. Answers are saved as people type, and a short notice tells them how long an unfinished draft is kept.
- Closing and reopening restores the fields that belong to the form. Anything else is dropped.
- Retention is yours to set from 1 to 365 days (30 by default). Older drafts are deleted automatically.
- Abandoned drafts are those with no activity for a set time, 24 hours by default (1 to 720). The label is informational: it never sends anything by itself.
- Email me a link is optional. The respondent ticks a consent box, confirms the address from a link, and receives one message with a single-use link to finish. The message never contains their answers.
A draft is not a response. It does not count towards your monthly total or your response cap, and it never sends a notification, webhook, integration, automation or autoresponder. All of that happens once, when the respondent finishes the form.
Tracking choices do not affect drafts
Saving a draft uses only the storage needed to save it. If a visitor declines optional analytics or marketing tracking, drafts still work. The only difference is that the page that referred them is not kept with the draft unless they accepted marketing tracking.
Letting respondents edit
Turn on Let respondents edit their submission via a link. From a response in your inbox you can then create an edit link; it expires (30 days by default), you can revoke it any time, and it works for that one response only.
Each field has Respondent can change this answer later under More options. Switch it off to lock a field after submission, for example a reference number. Calculated and payment fields are always locked. A file field can be replaced by uploading a new file; the old file is deleted.
Two edits at once
Every response has a revision number. If two people edit the same revision, the first save wins and the second is told: "This response changed while you were editing. Review the latest version before saving." The second person keeps what they typed and can choose Show the latest version before saving again.
History
Nothing is overwritten. Every version is kept with who made the change (the respondent, or a named team member), where it came from and which fields changed. Open a response in the inbox to read the history. Files that were added or replaced are listed with their revision.
Over the API and MCP
PUT /api/v1/forms/{form}/submissions/{submission}with apayloadrecords a new revision. Sendexpected_revision(therevisionyou read) and a stale value answers409witherror: "revision_conflict"and the latest answers.GET /api/v1/forms/{form}/submissions/{submission}/revisionsreturns the full history.GET /api/v1/forms/{form}/submissions?state=draft|abandoned|acceptedfilters by lifecycle; every submission carriesstateandrevision.get_submission(withinclude_revisions),update_submission(withexpected_revision),list_submissions(withstate) andupdate_formcover the same ground for agents.
What's next
- Restricted access → - decide who may respond
- Editing submissions → - staff edits
