Skip to content

Field Types

The form builder offers a range of field types to collect different kinds of information. You will find them in the left panel of the Fields tab, organized into three groups: Existing Fields (synced to your system data), One-Off Fields (collected in this form only), and Layout elements.

Before choosing individual field types, it is important to understand the fundamental distinction between synced fields and one-off fields — every field you add to a form is one or the other, and the difference affects how data flows through your system.

Synced fields are connected to family, camper, or enrollment records in your system. When a parent fills out a form with synced fields, their responses automatically update the corresponding record — no manual data entry needed. These fields can also pre-fill with the data already on file, so parents see what you already have and can correct or confirm it.

In the form builder, synced fields appear under Existing Fields in the left panel and show a Synced badge on the canvas. For the full list of available synced fields and how they work, see Linked Fields.

One-off fields collect information that lives only in the form’s submissions. They are not connected to any record in your system — responses are saved with the submission and nothing else is updated. You define the field type, label, and options yourself.

In the form builder, one-off fields appear under One-Off Fields in the left panel.

Use synced fields when the information belongs on the family or camper record and you want it to stay up to date in your system. Use one-off fields when you need to collect something specific to this form that does not need to live anywhere else.

Here are some common scenarios:

  • Health form — Use synced fields for allergies, medications, and doctor information (these belong on the camper’s record and should stay current). Use a one-off signature field for a seasonal liability waiver that only applies to this form.
  • Trip permission slip — Use synced fields for emergency contact phone numbers (so any updates from the parent flow back to their record). Use one-off fields for trip-specific questions like “Does your child get motion sickness?” or “Preferred seat on the bus?” that do not belong on a permanent record.
  • Interest survey — Use all one-off fields. Questions like “Which electives interest your camper?” or “Any feedback from last summer?” are form-specific and do not correspond to any system field.
  • Contact info update — Use all synced fields. If the goal is for parents to review and update their phone numbers, emails, and addresses, every field should write back to the family record.

If you are unsure, ask yourself: “Would I want this answer to show up on the family or camper profile?” If yes, use a synced field. If the answer only matters in the context of this specific form, use a one-off field.

A single-line text field for short answers like names, titles, or brief responses. You can set a placeholder to give the person a hint about what to enter.

A multi-line text area for longer answers like descriptions, notes, or detailed explanations.

A field that only accepts numeric input. Useful for quantities, ages, or counts.

A text field that validates the input is a properly formatted email address. If someone enters something that is not an email, they will see an error when they try to submit.

A phone number field with formatting built in.

A menu that opens when clicked, showing a list of options. The person picks one. Define the options in the field settings by typing each one and pressing Enter.

A set of options displayed as buttons. The person picks one. Similar to a dropdown, but all options are visible at once — better when there are only a few choices.

A set of options where the person can pick multiple answers. Each option appears as a checkbox. Use this when more than one selection should be allowed (for example: “Which activities is your camper interested in?”).

A dropdown that allows picking more than one option. Works like a regular dropdown, but multiple selections are possible. Use this instead of checkboxes when you have many options and want to save space.

Lets the person upload a file. You can restrict which file types are accepted:

  • All supported — PDF, Word documents, images, and audio files
  • Images only — JPG, PNG, GIF, HEIC, WebP
  • Documents — PDF and Word files
  • Audio only — MP3, WAV, M4A

The maximum file size is 25 MB per upload.

A single yes/no checkbox — not to be confused with the Checkboxes field above, which offers multiple options. Use this for agreement statements like “I authorize…” or “I have read and agree to…”

A drawing pad where the person signs with their finger (on mobile) or mouse (on desktop). They can clear and re-sign if needed.

These do not collect any data — they help organize and explain your form.

A section title that breaks the form into logical groups. Use headings to separate your form into parts like “Emergency Contact,” “Medical History,” and “Permissions.”

A paragraph of text for instructions, context, or important information. Good for explaining what a section is about or providing guidance before a group of fields.

A horizontal line that visually separates sections. Lighter than a heading — use when you want a subtle break without a title.

  • Every field can be set to Required in the field settings panel. Required fields show an asterisk (*) on the form and must be filled out before the person can submit.
  • You can place up to four fields side by side on the same row. When you drag a field to the left or right of another, they share the row and their widths adjust automatically.
  • File upload fields accept a single file per field. If you need multiple files (for example, front and back of an insurance card), add two separate file upload fields.
  • On the canvas, synced fields display a small Synced badge so you can tell them apart from one-off fields at a glance.
  • You can mix synced and one-off fields freely on the same form. Many forms use both — synced fields for data that belongs on the record, and one-off fields for everything else.