A form for every participant category

A speaker does not fill in the guest form, and the press does not fill in the partner form. Every category has its own fields, its own rules and its own form address — public or closed by link.

Seven event forms — one per participant category
01

An event starts from a ready scenario

The wizard opens with one question: “What are you creating?”. Pick “Conference” and the event already has a programme, partners, a desk, handouts and ticket sales. Then the “Setup” guide shows what is still missing before opening: team contacts or a published form.

  • 10 presets — from “Meeting” and “Training” to “Match” and “Private event”
  • A guide step closes by itself once the data is in place; one you don’t need is marked “Not needed”
  • After creation the event is an ordinary one: anything changes in its settings
The event wizard: the “What are you creating?” step with preset tiles in four groups
02

A form of its own for every category

Attendee, VIP, speaker, media, partner, staff, organizer — seven categories, seven forms. A speaker is asked for a bio and technical needs, the press for their outlet and beat, a partner for the company and their booth role.

  • Categories are a builder per event, not a fixed list
  • Conditional fields: a question appears only when it is relevant
  • Sections, hints and the questions themselves — in any languages
The form editor: sections, fields, display conditions
03

Public forms and forms closed by link

The attendee and media forms are visible to everyone. The VIP, speaker, partner and team forms are published but unlisted — only the link you sent opens them.

  • A closed form is not a way around approval: you still decide on the application
  • Versions: draft → published → history
  • Every application remembers which form version it was submitted on
The list of forms with versions and publication state
04

Before you publish, you see what will change

The readiness panel compares the draft with the published version: which fields were added, removed or changed. A gap in the primary language or a broken display condition stops publication. Fields with documents carry their own protection level: the passport number is masked in the list of applications.

  • A “File / photo” field: PDF, DOCX, JPG, PNG and more, up to 5 files of 10 MB each
  • A “Consent” field — one per form and always required; the consent text is one per organization
  • Field sensitivity: “Work data”, “Contacts” or “Documents”; a passport can’t go below “Documents”
Publishing the speaker form: what changes against v1 — a “Long text” field added, the “Readiness” checklist with no gaps, 30 earlier applications staying on their version
05

A participant reads the form in their own language

An event has as many languages as it needs: English, Ukrainian, German. A participant sees the text in their language if the event has it, otherwise in the event’s primary language. A single-language event shows no language switches and no translation marks at all.

  • A content language can be any ISO 639-1 language
  • DeepL machine translation — a single string or a whole language at once, marked “MT”
  • Change the primary text and machine translations update; manual ones stay as they are
Event languages of the summit: English as the primary and Ukrainian; all required texts are filled in
06

Quotas, a registration window, a waitlist

Registration opens and closes on schedule. A quota limits a category or an approver entity. When seats run out, an application can go to the waitlist instead of being refused.

  • A quota per category, country or approver entity
  • Quota fill is visible on the event dashboard
  • The registration window runs in the event’s time zone
Event quotas and their fill
07

Missing data — you request it instead of emailing back and forth

The participant gets a link and completes only the fields you asked for. An operator can correct a contact or a category themselves — and it stays in the application history.

  • A completion request — with an expiry and a repeat
  • The application history: who changed what and when
  • Duplicates and repeat applications — as a separate list
The application card: profile, form answers, history
08

The form lives on your site

Forms are headless: the event site fetches the form schema over the API and posts the application back. The design is yours, the data lands in the application catalogue at once.

  • An open API: OAuth2, an OpenAPI specification
  • Search, filters and saved views in the catalogue
  • All categories and events — in one organization database
The application catalogue with filters and statuses

We’ll show forms on your event

Your categories, your questions, your languages — we show it on a 30-minute demo call.

A 30-minute demo

Tell us about your event — we’ll show it on yours

A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.

  1. Fill in the form: event type, number of participants, a few words about it
  2. Within one business day we email you to agree a time
  3. On the call we show Aditum configured for your event and answer your questions
Or write directly [email protected]
Phone
We’ll call if the email gets lost
By submitting you agree to the privacy policy.