Skip to main content

Forms: Building Custom Forms (Field Types, Sections and the AI Builder)

Build forms visually with 18 field types, repeatable sections and QA sign-off flags, or let the AI convert an existing paper form. Every save is versioned.

Written by Support Superfood

Admins build and edit forms under Form builder in the sidebar. Everything is visual — no coding — and every published change is versioned in the Amendment register.


Two ways to start

  • Build from scratch — name the form, set its category and completion frequency, add sections and fields.

  • AI import — upload the form you already use on paper (PDF, Word, Excel, CSV or even a photo) and the AI extracts its sections, field labels and field types into a ready-to-edit draft. Adjust anything, then publish.


Field types

Type / anywhere in the builder to insert a field from the slash menu (the same pattern as the Docs editor). Available types:

  • Answers: text, long text, number (with a unit like °C or kg), date, time, email, phone

  • Choices: dropdown, radio buttons, checkboxes, rating, linear scale

  • Evidence: signature capture, photo upload, file upload (photos can be handed off to a phone by QR code at fill time)

  • Live data: staff selector and product selector, both pulled from your company's own lists

  • Structure: tables with custom column headings, and text blocks for instructions (supporting dynamic date and user variables)


Field and section options

  • Required — the form won't submit without an answer.

  • QA sign-off — flag a field so a reviewer must individually sign it off before the submission can be approved in the QA queue.

  • Repeatable sections — staff can log multiple numbered records (say, ten batches) inside one submission instead of filling the form ten times.


Scheduling

  • Set how often the form must be completed: hourly (with an interval), daily, weekly, monthly, or on demand.

  • The dashboard computes due dates from the schedule and the last submission — overdue forms surface themselves; nobody has to remember.


Versions and the amendment trail

  • Saving a change shows exactly what's about to be recorded — a human-readable change list — with room for a note about why.

  • The version number bumps on every save, and the entry lands in the Amendment register with who changed it and when.

  • From the register you can open any historical entry and restore it as a new copy — the original is never overwritten.

Did this answer your question?