Create useful questionnaires and forms

Ask for the information you will actually use. Explain unfamiliar questions and keep optional information optional.

Choose fields deliberately

The documented builder supports short and long text, email, number, date, dropdown, upload and informational fields, with additional table and matrix options. Use the field types offered in your current builder. Give every question a meaningful label, state the expected format and mark only essential answers required.

Use defaults carefully

A default can be a literal value, a supported variable, or a compatible client custom-field binding. A client-field binding can prefill from the portal profile and save the completed answer back. A prefilled value is not a submitted answer. Verify what the intended client sees and remove private or inappropriate defaults.

Check conditions

If a step depends on an answer, test both a matching and a non-matching case. Check that a required field is reachable in the intended branch. Variables should come from the current builder's available list; never guess a token name.

Verify the result

Preview the form, submit only an authorized test record when needed, and inspect the saved response. Do not ask clients to place passwords, authentication codes or payment-card details in ordinary text fields. See responses and exports.