Advanced form rules

Use advanced form settings to make questions relevant, control eligibility, and preserve useful reporting information.

Conditional questions and eligibility

Skip logic changes the sections or fields shown after an answer. Eligibility rules determine whether a response meets configured intake criteria. Test both the qualifying and non-qualifying paths in preview.

Set clear messages for people who do not qualify. Avoid making a hidden question required on a path where the person cannot answer it.

Access and dates

Published status is only one condition for access. User type, cohort, working group, and opening or closing dates can also restrict discovery and submission. Verify the intended combination using representative accounts.

Field limits and data sources

Use the supported validation controls for word counts, numeric ranges, files, and required values. Dynamic option sources can offer current programme data instead of maintaining duplicated lists.

Personal data and reporting

Where capability settings are available, distinguish personal information from reportable demographic information. These classifications affect anonymisation and travel with exported templates. Unclassified answers are cleared by applicant anonymisation rather than retained by default.

Questions can also be marked for filtering or AI review where the workflow supports it. Review these settings before publishing a new version.

Module-owned forms

Project report and other module forms can have protected question keys and types. Edit only what the builder permits. These constraints keep the form compatible with summaries and the surrounding workflow.