Questionnaire sections and saved progress

A personal questionnaire can now be completed in sections, with a saved draft between visits. Saving is separate from sending: a draft does not create a response, update the private contact record, or complete a booking step.

Build sections without editing code

Open Forms, edit the questions, then choose Add sections. Give each section a heading and optional introduction. Add another section and use the question-to-section selectors to assign its questions. The interactive preview shows the same headings and question order.

A question belongs to exactly one section. Questions in the earlier section come first, and a conditional question must follow the answer it depends on. Publishing rejects inconsistent ordering; move the dependent question after its controlling answer before trying again. There can be up to 12 sections and 40 questions in a form. Empty sections do not appear to the recipient.

For example, put name and email in Contact details. Put an outdoor-ceremony checkbox and a rain-plan question in Your celebration, with the rain-plan question shown only when the checkbox is selected. A recipient can save contact details now and return to the ceremony questions later.

Save and publish the form when the preview is ready. Already-issued personal requests retain their original published questions. Older one-page forms and their response records keep their existing URLs and answer verification format.

Save progress, then review the final answers

The personal link opens the most recently saved draft. Save progress saves the visible typed answers, including an incomplete value such as an unfinished email address. Save and continue saves and opens the next visible section. Moving between section tabs does not automatically save.

Hidden answers are removed on save. An invalid controlling answer cannot reveal a dependent question. The final review requires all visible required answers and valid email, number, date and choice values.

Choose Review final answers after saving. Review the complete saved answer set across every section, then choose Confirm and send answers. Only this confirmation creates the immutable response and marks the request complete. A booking journey can then verify that response before preparing its next step. Repeating the same confirmed submission does not create a second response.

The private contact record remains separate. Use reviewed response mapping to compare selected submitted answers before changing contact details.

Recover a stale or uncertain operation

If another window has saved a newer revision, this window cannot overwrite it silently. Your unsaved values remain visible. Open Recover or clear progress, use Download my edits if you need a local copy, and choose Load saved draft to replace the current window with the server's saved version. There is no automatic merge between two drafts.

If the app cannot confirm a save or submission, editing is held and Retry the same operation repeats its original request. Loading the saved draft also resolves the current state. Do not change the answers and assume a timed-out submission was unsuccessful.

Clear all saved answers… asks for a separate confirmation. It clears the whole draft, including starting prefills. It does not submit a response or change contact details. Saved draft content is not a revision-by-revision answer archive; only the current draft and operation receipts are retained in this flow.

Control a private request link

A personal link is a capability: someone who possesses it can access that request while it is active. It does not independently verify the recipient's identity. Share it deliberately and avoid entering information that is unnecessary for the planning task.

For a standalone pending request, an owner can revoke the link or replace it. Replacement closes the old link, preserves saved content and shows the new link once; its readable secret is not stored. Copy it then. If the replacement result was lost, reload the request and explicitly replace the link again rather than reusing the previous URL. Expired, revoked, archived-contact and merged-contact requests cannot continue.

Requests bound to a booking journey are managed through that journey. Their direct links recheck the journey's current step and access at the end of each mutation. Pausing or revoking the journey while a submission waits prevents the submission from committing. Completed responses remain retained for the team; an old child link cannot be used to skip forward or reopen the completed questionnaire.

Public anonymous inquiry forms can display sections but do not store returnable drafts. File uploads, repeating groups, arbitrary document fields and offline submission are not part of this questionnaire flow. No email, SMS, payment or provider configuration is required to save an answer draft.

Multiple-choice questions

Choose multiselect for a question such as “Which services interest you?” and enter each option on its own line: Photography, Albums and Video. The client can select more than one. A required question needs at least one selection; the server rejects unknown or duplicate options and retains choices in the published option order.

A following question can depend on one selected option. Set its condition to the earlier question and enter Albums to ask about album priorities only when Albums is selected. Hidden answers are discarded on submission. Saved progress retains multiple selections, and reviewed contact mapping can retain them as a custom answer for the matching project type. Multiple choices cannot overwrite a scalar contact name, email, phone or date.

Automation conditions on a multiple-choice answer match one selected option. The published questionnaire stays unchanged when you edit a new draft.