Forms

What a form is

A form is a configurable set of questions used to collect structured input from a person — a mix of short text answers, long text, numbers, dates, single- and multiple-choice questions, dropdowns, sliders, and ratings. Forms aren’t tied to one place in the product: the same question can be reused across many forms, and the same form can be reused across many programs.

Underneath, a form is built from a library of individual questions (“form items”). A form doesn’t own its questions outright — it composes them, pulling items from a shared library and arranging them in a specific order with its own per-form settings (required or optional, min/max values, custom labels). This means one question — say, “How would you rate this session?” — can appear, and be edited once, across many different forms rather than being duplicated everywhere it’s used.

Forms can also branch: a question’s answer can determine which question comes next, so a form can adapt to what the respondent has already said rather than showing every question to everyone.

The main places forms show up

Forms aren’t a single feature with one entry point — they’re a building block used across several parts of a program:

A step in the program journey. An admin can add a standalone form as its own item in the journey, with its own trigger (e.g. manual, on a milestone date) and its own target role.
The intake / application form when someone requests to join a program. When self-application or manager nomination is enabled for a program, the person applying fills out a configurable request form as part of that process.
The questionnaire behind a session evaluation. By default, session evaluations use a fixed set of built-in questions (what was gained, actions to take, coach rating, NPS, and so on). A program can instead be configured to use full custom forms for these evaluations — separate forms for the receiver’s view of the session, the receiver’s private feedback to the program admin, and the coach’s own notes and feedback to the admin.
The questionnaire behind a 360-degree feedback collection. A 360 program item references a single feedback form that respondents (managers, peers, direct reports, etc.) fill out about the person being reviewed.
Pre-, mid-, and post-program evaluations. A program can attach different forms to fire at the start, midpoint, and end of the program lifecycle, and can require or not require completion at each point.
Structured questions inside other features. Individual form questions can also be surfaced on a person’s profile card — for example, showing a mentor’s answer to “what’s your coaching style?” on their public profile.

What an admin configures

For each form, an admin can configure:

The questions/fields themselves — pulled from the shared question library or created new, with a question type (short text, long text, number, date, single choice, multiple choice, dropdown, multi-select, rating, slider, etc.), a label, optional help text, and any answer choices.
Per-form question settings — whether a given question is required on this particular form, its order, and (for numeric/date questions) minimum and maximum allowed values. The same question can be required on one form and optional on another.
Branching — rules that show or skip later questions based on how an earlier question was answered.
Where and when the form is used — which journey step, role, or program milestone triggers it, and whether completing it is required before someone can move on.
How responses are used and reported — completed forms can be reviewed individually, and for intake/demand forms specifically there is a dedicated results view that lists every invited person alongside their submission status and answers, so an admin can see at a glance who has responded and what they said.

Templating and reuse

Forms support reuse at two levels. First, individual questions live in a shared library and can be dropped into any number of forms — editing a library question, or adding it to a new form, doesn’t require re-creating it. Second, whole forms can be marked as reusable templates and cloned: an admin can take an existing form (its questions and their configuration) and create a new copy under a new name, then adjust it for a different program, rather than building a similar form from scratch each time. Shared, tenant-wide template forms are also available as a starting point across programs.