Field Events
Using Field Events to show conditional follow-up questions. Fields controlled by Field Events are completely hidden when their condition isn't met, keeping the form clean and straightforward.
Field Events let you show or hide follow-up questions based on how an applicant answers a previous question. For example, if an applicant selects "Yes", they can be shown (and required to complete) a "Yes" follow-up field — while the "No" follow-up remains hidden, and vice versa.
Setting up your fields
Before configuring any Field Events, add all the fields you need to your form template — including any follow-up fields you only want to show conditionally. They will all be visible in the editor, but Field Events will control when applicants see them.
Creating Field Events
Click the main question field (the one whose answer will trigger the conditional logic).
In the left-hand panel, open Field Events and click Create new Event.
Set the Condition — for example, If equals Yes.
Set the Action — either:
Show element — the follow-up field appears but applicants are not required to fill it in, or
Require element — the follow-up field appears and must be answered.
Set the Target — select the follow-up field you want to show or require.
Repeat for each answer option. For example, a Yes/No question would typically have up to four events if the follow-up question is to be mandatory:
If Yes → Show the Yes follow-up
If Yes → Require the Yes follow-up
If No → Show the No follow-up
If No → Require the No follow-up
Tip: If you want a follow-up to be mandatory, you'll need two events for that answer — one to Show the field and one to Require it. If you only need the follow-up to be optional, a single Show event is all that's required.

What applicants see
Applicants only ever see the follow-up question relevant to their answer. The screenshots below show this in action:
No answer selected — only the main question is shown, with no follow-ups visible.
"Yes" selected — the Yes follow-up field appears and is marked as required.
"No" selected — the No follow-up field appears instead, also marked as required.



Duplicating pages, sections or fields
Field Events are not carried over when you duplicate a page, section, or individual field. If a field controlled by a Field Event (or a field that triggers one) is duplicated, the conditional logic is left behind on the original — the duplicate will need its Field Events recreated from scratch.
This applies whether you're duplicating a page/section within the same template, or duplicating an entire template (see Application Templates, Assessment Templates, or Milestone Templates). After duplicating, check any fields that relied on conditional show/hide or require logic and re-create the Field Events on the copy.
Last updated
Was this helpful?