Save-and-resume on long forms

Long applications often need more than one sitting. Save-and-resume is useful when someone needs to find a document, check an answer, or return from another device.

The draft is only half the workflow. The person also needs a usable return link, clear expectations about what is saved, and a way to finish before it expires.

Enable draft saving deliberately

Open the form’s Settings → Save & resume section:

1. Enable Drafts to allow saving and returning through a unique link.
2. Set Draft expiry to a retention period appropriate for the form. The default is 30 days.
3. Treat Partial entries as a separate choice. Enable unfinished lead capture only when you intend to retain that data and have explained it to visitors.
4. Save the form and test recovery before promising it to applicants.

A short newsletter signup rarely needs this. Applications, project intake, and questionnaires that require research are better candidates. Field count alone is not a useful cutoff.

What Core Forms saves

Drafts are stored in the WordPress submissions table, normally wp_cf_submissions with your site’s table prefix. They contain field data, a draft token, and the current step.

The current frontend saves after a pause in input, using a five-second debounce. Multi-step navigation also triggers draft saving when enabled. Closing the page immediately after typing can happen before the latest save completes.

The draft endpoint processes submitted field values; it does not implement persistent file-upload recovery. Do not promise that a selected file will still be attached after someone returns. Test uploads separately and ask visitors to reselect files when necessary.

A return link needs an explicit delivery path

The draft-save response includes a resume_url. The return link uses cf_resume:

https://yoursite.com/your-form/?cf_resume=YOUR_DRAFT_TOKEN

The token placeholder above represents the actual token returned by Core Forms. Keep the link pointed at the page containing the same form.

The built-in frontend retains the draft token, but it does not automatically email the return link or present a complete copy-link workflow. Enabling Drafts alone does not deliver that link to the visitor. A custom integration must expose or send it before you can offer a dependable leave-and-return experience. See the save-and-resume documentation for the underlying workflow.

If you add a reminder email, explain what was saved and when it expires. A subject such as “Continue your application” is clearer than an unsupported claim that the form is a particular percentage complete. Ordinary data variables do not automatically add a resume-link delivery feature.

Treat the link as access to the draft

Core Forms generates a cryptographically random, 64-character hexadecimal token. Anyone holding a valid return link can access its draft while resuming is enabled and the draft remains available.

• Share the link only with the intended recipient.
• Avoid placing it in analytics events or public pages.
• Do not rely on an email-verification toggle: the current save-and-resume settings do not provide an OTP verification step.
• Collect only the information the form needs and choose an appropriate retention period.

Cleanup removes old drafts according to the configured expiry period. A draft is not a completed submission, and a saved answer does not reserve stock, a booking slot, or an application place.

Test the complete recovery path

Use a separate test form with harmless sample data:

1. Enter text, select choices, and move between steps.
2. Confirm a draft-save request succeeds after input settles.
3. Obtain the return link through the delivery mechanism you configured.
4. Open it in another browser and check the restored values and step.
5. Check checkboxes, radio groups, multi-select fields, and uploads individually.
6. Complete the form and confirm the final submission and intended actions.
7. Verify what a visitor sees after the draft expires.

For a multi-step form, also go backward and change an answer that controls later fields. Recovery needs to remain coherent when the person’s answers change.

Measure recovery without promising a lift

Compare completed submissions from comparable audiences and track how often people successfully return to drafts. More stored drafts do not necessarily mean more useful applications.

Start with a form that people have a reason to pause. Finish the return-link workflow, test it across devices, and then decide whether it improves completion for your audience.

Save-and-resume is bundled in Core Forms.