Form Builder

Default fields — always collected

These five fields are locked and always appear first on every registration form. They cannot be removed, renamed, or reordered — they're foundational to how Tikxz works.

Tikxz uses these fields to send registration confirmation emails, SMS reminders, assign delegates to committees, and generate QR check-in codes. Without them, the core platform workflows break. Your custom fields appear below these defaults.

Adding custom fields

Navigate to Dashboard → Your MUN → Form Builder. The interface shows the locked defaults at the top, followed by your custom fields.

1. 1

   Click Add Field to open the field configuration panel.

2. 2

   Select a field type from the dropdown (see the full breakdown in the next section).

3. 3

   Write a clear label — this is what delegates see above the input. Be specific: "School / College Name" is better than "Institution."

4. 4

   Optionally add placeholder text — hint text that appears inside the field before the delegate types. Use it to show an example: "e.g. Delhi Public School, R.K. Puram."

5. 5

   Toggle Required / Optional. Only mark a field Required if you genuinely won't process the registration without it.

6. 6

   Drag to reorder custom fields using the handle on the left. Custom fields cannot be moved above the locked defaults.

7. 7

   Click Save Form. Changes take effect immediately for all new registrations. Existing registrations keep the form data from when they submitted.

Field types and when to use each

Choosing the right field type reduces data quality problems and makes your form easier to fill out. Here's a practical guide:

Required vs. optional — getting the balance right

Every required field is a commitment the delegate must make before they can register. That's fine for genuinely necessary information. It's a problem when you mark everything required "just in case."

• Mark Required when: you cannot process the registration without this information, and collecting it later is operationally impractical (e.g. government ID for age verification, dietary restriction for catering).
• Mark Optional when: the information is useful for planning but not blocking (e.g. t-shirt size for extras, LinkedIn for networking).
• Don't add the field at all when: you're collecting it because it seems like something you should have, but you don't have a specific use for it before or during the event.

Field visibility — public form vs. internal only

Custom fields can be set to Public (shown on the registration form) or Internal (visible only in the organizer dashboard). Internal fields are useful for adding manual notes to a registration without cluttering the delegate-facing form.

• Public fields are filled in by the delegate at registration time.
• Internal fields can be filled in by organizers after the fact — for example, marking a delegate as a scholarship candidate, noting who referred them manually, or flagging a registration for review.
• Internal fields don't appear in the delegate's confirmation email or their registration view. They are included in your CSV export.

Downloading form responses

All registration form responses — both default fields and every custom field you've added — are included in the CSV export from Dashboard → Your MUN → Registrations → Export CSV.

• Each custom field appears as its own column in the CSV.
• File Upload fields show the filename (not the file itself) in the CSV — download files individually from the registration detail view.
• Delegates who registered before a custom field was added will have blank values for that column.
• The export includes all registration statuses (active, pending, cancelled) — filter by status in your spreadsheet tool if needed.