App

Build a form template

The field palette, sections, conditional logic, scored questions, and signatures — everything the form builder can do.

Updated Jul 26, 2026

Clients → Forms → New form

A form template is built once and sent as many times as you need. This page covers authoring; Send forms and consents covers sending and tracking.

Simple mode and the full palette

The builder starts in simple mode, showing only the everyday field types. Most intake forms never need more than that.

Switch out of simple mode when you want the advanced types — date-and-time, rating, address, file upload, and calculated fields.

The field palette

Layout

FieldUse it for
SectionA heading that breaks a long form into readable chunks
ParagraphExplanatory text with no input — instructions, a disclaimer

Text inputs

Text, Long text, Email, Phone, Number.

Email and phone validate what's typed, so you get a usable address rather than a typo.

Date and time

Date, Time, Date and time.

Selection

FieldBehaviour
CheckboxA single yes/no tick
Checkbox groupPick any number from a list
Radio buttonsPick exactly one, all options visible
DropdownPick exactly one from a longer list
RatingA star rating
Use radio buttons when there are five or fewer options and you want the client to see them all — a medical yes/no/unsure. Use a dropdown when the list is long enough that showing it all would bury the rest of the form.

Advanced

FieldWhat it does
AddressA structured address, not a free-text box
SignatureDrawn on screen. This is what makes a consent a consent.
InitialsA lighter-weight acknowledgment, for initialling individual clauses
File uploadThe client attaches a document or photo
CalculatedA score derived from other answers — see below

Required fields

Mark any field as required and the form can't be submitted without it.

A required field inside a section that's hidden by conditional logic is not enforced while it's hidden. That's correct behaviour — you can't require an answer to a question the client was never shown — but it means "required" alone doesn't guarantee you'll get an answer. Check your conditions.

Conditional logic

Any field can be shown only when other answers meet a condition — "if the client ticked pregnant, show these three questions".

You can combine several conditions and choose whether all of them must match or any of them.

The same rules are evaluated on the server when the form is submitted, so a client can't bypass a condition by fiddling with the page.

Calculated fields

A calculated field produces a score from other answers. It's how you turn a questionnaire into a triage signal.

How the total is built:

  • Radio and dropdown — the selected option's score
  • Checkbox group — the sum of every selected option's score
  • Rating and number — the value itself

You then map the total onto bands — a label for each range, with the total falling into the lowest band whose maximum it fits under. A total above every band lands in the highest one.

Scoring is deliberately bounded to summing option scores and mapping to bands. There is no general formula engine — that's a safety decision, not an omission. If you need something more elaborate, calculate it outside the form.

The live preview computes the score exactly the way the server does, so what you see while authoring is what the client's submission will record.

Form settings

  • Category — how the form is grouped in lists and in a client's documents
  • Signature — whether a signature is captured
  • Expiry — the default number of days a sent link stays live

Versions

Every form has version history. A form already sent keeps the version the client was sent — editing a template never rewrites a submission somebody has already completed.

Attaching a form to a service

A service can require a form, set on the service's Forms tab.

A service that requires a signed clinical form will block checkout until the form is signed. Test the whole path — send, complete, sign, check out — before you put a required form on a service you sell every day.

Starter templates

The builder ships with starter templates. Starting from one and cutting what you don't need is usually faster than starting from an empty form, and you're less likely to forget a standard question.

Archiving

Archive a form you no longer send rather than deleting it. Deleting orphans the submissions that reference it.

Keep reading

Related

2
Send forms and consentsBuild a form once, send it to one client or many, and track it from sent to signed.Services and pricingBuild the catalog that drives booking and checkout — durations, prices, who can perform what, and per-location overrides.