A corporate event where HR does not merge lists by hand

A closed form for employees, approval by department, merch in the right size by quota, and the programme in the app. Who has not collected their kit is visible at the end of the day.

  • closed forms
  • approval by department
  • merch by size and quota
  • the programme in the app
The Handouts section: who is entitled to a kit, how many received it, a breakdown by category
What hurts the organizer

Four things HR merges by hand

A list from HR, not registration

Participants don’t need attracting — they need collecting: who is coming, from which office, with whom, what T-shirt size.

Several offices and countries

Every department has its own coordinator and its own spreadsheet. Merging them is a week’s job of its own.

Merch with sizes

Ordered by guesswork, M ran out before lunch, and who has already got a kit is unknown.

Internal confidentiality

Employee data must not sit in a contractor agency’s open spreadsheet.

How Aditum is configured

Not a template. A corporate event configuration

The same blocks as for a summit: approver entities become departments, delegations become offices.

Categories
  • Employee
  • Management
  • Guest
  • Contractor

The category defines the badge, the access and the kit a person gets at the desk.

Approval
  • Delegated: an approver per department
  • or the organizer

A department coordinator sees and approves only their own. The overall list assembles itself.

Forms
  • A closed form by link
  • A form per department

The link goes out by internal mail. Fields: office, T-shirt size, dietary preferences, transfer.

Venue
  • Halls
  • Management area
  • Contractors’ technical area

A contractor enters the technical area on build-up day, an employee enters the halls on the event day.

On site
  • Desks by office
  • A kit by size and quota
  • “Not collected yet” as a list

Everyone gets one kit in their size, management a different one. A second kit can’t be issued by accident.

Communications
  • Campaigns by department
  • The programme in the app
  • Apple + Google Wallet

Logistics go to each office’s segment. The programme and its changes are in the participant app.

Event day

What it looks like from the inside

  1. −21 d
    Console · forms

    Every department gets its own link

    The form is closed and bound to the department. An application goes straight to its coordinator.

    Registration →
    Event forms: public ones and those closed by link
  2. −10 d
    Console · applications

    One list instead of five spreadsheets

    Filter by office, category, status. T-shirt sizes go straight into the merch order, nobody asked twice.

    Approvals & delegations →
    The application catalogue with filters and saved views
  3. 09:00
    An office desk

    A badge and a kit in the right size

    The desk sees what a person is entitled to and what they have already received. The size comes from the application, stock is live.

    On-site accreditation →
    A participant card at the desk: the badge and handouts due
  4. 14:00
    Participant app

    A session moved — the programme is already different

    The change was made in the console. The app shows the new time, nobody posts to the all-hands chat.

    Programme, speakers, partners →
    The event schedule by room
  5. 18:00
    Console · handouts

    Who hasn’t collected a kit is visible at once

    Numbers by category and office: entitled, received, not yet. The remaining kits go out by post — addressed.

    On-site accreditation →
    Handout figures: entitled, received, not received

We’ll show it on your corporate event

Your offices, your departments, your merch — we’ll set the demo up for a real scenario.

Request a demo
Request a demo

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

Not slides — your scenario: categories, approvals, zones, desks. We’ll set the demo up for your event.

Or write directly [email protected]
By submitting you agree to the privacy policy. We reply within one business day.