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
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.
The Aditum configuration for a corporate event
The same blocks as for a summit: approver entities become departments, delegations become offices.
- Employee
- Management
- Guest
- Contractor
The category defines the badge, the access and the kit a person gets at the desk.
- Delegated: an approver per department
- or the organizer
A department coordinator sees and approves only their own. The overall list assembles itself.
- A closed form by link
- A form per department
The link goes out by internal mail. Fields: office, T-shirt size, dietary preferences, transfer.
- 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.
- Desks by office
- A kit by size and quota
- “Not collected yet” as a list
- Rooms from a hotel block
- Lunch and dinner by badge
Everyone gets one kit in their size, management a different one. A second kit can’t be issued by accident. The host scans the badge and sees the portion allowance, and the hotel reception checks people in with the same badge.
- Campaigns by department
- The programme in the app
- Apple + Google Wallet
- A survey after the event
Logistics go to each office’s segment. The programme and its changes are in the participant app. After the event everyone gets a survey by email.
What it looks like from the inside
-
−21 dConsole · forms
Every department gets its own link
The form is closed and bound to the department. An application goes straight to its coordinator.
Registration →
-
−10 dConsole · 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 →
-
−1 dStation · run to the hotel
The office arrives by train — the coach is already waiting
Each person’s train sits in their trip; the run has a code, a vehicle and a driver. The driver boards people by badge scan and taps “Driver is waiting” — passengers get a push. Whoever didn’t board lands on the “Missed run” list.
Logistics →
-
09:00An 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 →
-
14:00Participant 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 →
-
18:00Console · 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 →
What runs at a corporate event
Questions and answers
Can we handle employee accommodation?
Yes. A room block at the hotel for the event dates, bookings whose occupants can only be participants, and a grid of nights that warns when the block is exceeded. You set the payer for the room, the tourist tax and surcharges separately: the company, the employee or a third party. The hotel gets an XLSX rooming list.
How do we run transfers from the station or airport?
Each person’s train or flight sits in their trip; runs carry a code, a vehicle, a driver and a seat count. The driver gets the manifest as a PDF and a live link, and the employee sees their transfer in the app. Who needs a transfer but has no run shows up on a separate list.
How do we count meals?
Lunch and dinner are slots with time windows. You set who is entitled by category or badge group — management, say, also gets the dinner. The host scans the badge and can cancel a mistaken serving with a comment, and the restaurant gets an XLSX statement to reconcile the bill.
What do drivers, the hotel and the restaurant see?
Only their own part. A driver sees their carrier’s runs, reception sees their hotel’s bookings without prices, a restaurant sees its own meals. The manifest and the rooming list carry no emails or documents.
How do we find out what employees think of the event?
A survey after the event: NPS, ratings, open questions. The default mode is confidential — you see who answered, but not what a specific person said, and cuts with fewer than five answers are hidden. Results can be broken down by category, country and language.
We’ll show it on your corporate event
Your offices, your departments, your merch — we show it on a 30-minute demo call.
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.
- Fill in the form: event type, number of participants, a few words about it
- Within one business day we email you to agree a time
- On the call we show Aditum configured for your event and answer your questions