Forms
The Forms module collects structured information from your teams: tech specs, contact sheets, requirement forms — anything one response per team should answer. You build a form from flexible blocks, target it at the right teams, notify their contacts, and review what comes back.
Forms is always available in the event dashboard (it isn’t a toggleable module).
Forms vs Inductions: Forms collect one response per team, completed by the team’s managers. Inductions collect one completion per person. Use Forms for “tell us about your team”, Inductions for “every individual must complete this”.
Creating a form
Forms → All Forms → Add Form:
- Set the form name, description, and an optional deadline.
- Choose the audience:
- No limits — every manager team on the event is eligible.
- Limit to groups — all teams in the selected groups.
- Limit to teams — specific teams, even outside those groups.
- Both — teams matching either are eligible.
- Configure emails: a notification template for invites, an optional completion template for the team (or Do not send email), and comma-separated internal addresses to alert when a team submits.
- Toggle Needs review if you want to review submissions (on by default).
Building the content
The form builder uses the same block palette as inductions:
| Block | Purpose |
|---|---|
| Input | Text, numbers, email, dates, times. |
| Options | Checkboxes, radio buttons, dropdowns. |
| Quiz | Questions with scored answers. |
| Upload | File uploads (riders, stage plots, insurance…). |
| Headshot | Photo capture. |
| Text / Video / Slideshow | Display-only content to inform, not collect. |
A form made only of display blocks is labelled Information Only and can’t be submitted — add at least one answerable block to collect responses.
Notifying teams
Press Notify to email every eligible team contact a secure link to their team’s copy of the form. The link is team-specific — no login needed — and any of that team’s contacts can use it.
How teams respond
Each team has one shared response per form. Multiple managers can open the same link, and later submissions update the team’s existing answers rather than creating duplicates — the latest submission is the source of truth, with earlier versions kept as revisions for reference.
Deadlines are enforced: once passed, the form no longer accepts submissions.
When a team submits, your internal notification addresses are emailed.
Reviewing responses
Forms → Responses shows each form’s progress — eligible teams, submitted, reviewed, and completion rate — with a team-by-team detail view.
With Needs review enabled, each submission can be:
- Marked as Reviewed — you’re happy with it.
- Sent back with requested changes — with a note to the team.
If a reviewed team resubmits, the response flips to Updated After Review so you know to look again. Teams removed from the audience later keep their historical response visible as Previously Eligible, but drop out of the counts.
Settings
Forms → Settings picks the forms information page shown in the team portal (edit its content under Settings → Pages).
Quick reference
| I want to… | Go to |
|---|---|
| Collect a tech spec from every production supplier | Add Form, limited to the Production Suppliers group |
| Ask three specific teams a question | Add Form → Limit to teams |
| Chase teams to fill it in | The form → Notify |
| See who’s submitted | Forms → Responses |
| Ask a team to correct something | Response detail → request changes with a note |
| Share info without collecting answers | Display-only blocks (Information Only) — or consider the Knowledge Base |