Surfaces
Feedback Form
Configure, preview, schedule, and publish the event-specific attendee feedback form.
First created Last updated
Overview
Feedback Form configures one form for the selected event. A new draft starts from the CebuFurs-derived standard template: Event Feedback, Concern, Suggestion, Issue / Bug Report, Compliment, General Comment, and Other. The event comes from the route, so attendees are never asked which event they mean.
Draft saves and publishing are separate. Saving preserves operator work without changing the attendee form. Publishing creates a new numbered, immutable version and makes that version available according to its Enabled, Opens, and Closes settings.
Operator steps
- Open EMS → current event → Setup → Feedback Form.
- Confirm title, introduction, success message, safety notice, and official incident-report URL.
- Choose Anonymous, Anonymous with optional contact, or Verified attendee identity.
- Enable, reorder, duplicate, or remove categories and edit their questions.
- Use Open real regosite preview and check both desktop and 390 px views.
- Save the draft. Resolve any update-conflict warning by reloading before overwriting another operator’s work.
- Select Publish form. Verify the published version badge and the public
/:eventSlug/feedbackroute.
Use Restore standard template only after confirming the replacement. It replaces the draft, not a historic published version or response snapshot.
Identity and safety
| Mode | Stored identity |
|---|---|
| Anonymous | No attendee account and no contact email. |
| Optional contact | Anonymous unless the attendee checks follow-up consent and enters a valid email. |
| Verified attendee | A signed-in attendee account is required and may be linked to the response. |
Feedback is not an emergency or safety-report channel. Keep the safety notice visible and configure the official report link. A feedback response can later be handed off explicitly by an authorized operator, but the system never creates a safety report automatically.
Version behavior
Every publication appends a form-version snapshot. Each response stores the published version, normalized answers, and its category schema snapshot. Later edits do not rename, reorder, or delete the labels needed to read older responses.