The app for training events and workshops
A training day lives and dies on room capacity. Twenty seats, twenty-eight people who want them, and a facilitator discovering the mismatch at the door is the failure mode this page is about.
A planning figure: a cohort large enough to need parallel workshops and small enough that every seat is accounted for.
Why capacity is the whole problem
A training event app manages the sessions, room capacities and sign-ups for a workshop programme, and collects feedback while each session is still fresh. event67's workshop RSVPs are enforced on the server with automatic waitlist promotion, which is the part most event apps get wrong, and it collects per-session ratings and written suggestions that go straight to the organizer. It does not track continuing-education credits or issue certificates.
Capacity that is real, not advisory
Most event apps let anyone tap join and sort out the overflow at the door. event67 enforces workshop capacity on the server: when the twentieth person takes the twentieth seat, the twenty-first joins a waitlist and is promoted automatically the moment someone drops. The facilitator's list is therefore true at 09:00 and still true at 14:00.
A schedule that reflects the actual rooms
Training programmes reshuffle constantly: a facilitator is delayed, two small groups merge, a room floods. The live schedule with rooms and tracks means the change propagates to every device at once, and the personal agenda means each learner sees only their own path through it.
Feedback per session, not one survey at the end
The end-of-programme survey measures how people felt about lunch. Session feedback and ratings collected inside each session tell you which module worked, and the written suggestions come back attributed and specific enough to act on.
Materials and messages that land
Announcements push to the cohort and deep-link to the post, so a pre-read or a room change reaches everyone. Sponsor pages carry partner or awarding-body information where a programme has one.
A training day, session by session
Enrolment
Import the cohort
The learner list arrives from wherever enrolment happens: a learning management system export, a spreadsheet, a registration tool. Import it as CSV, send branded invites, and check delivery per recipient before day one.
Uses the branded app.
The week before
Open workshop sign-ups
Publish the workshop grid with real capacities and let learners choose. The waitlist does the allocation work that a coordinator would otherwise do by email, and it keeps doing it as people change their minds.
Uses the schedule and RSVPs.
Morning of
Who is here, per room
Check-in at the door with a QR scan, and the arrivals count tells you whether to hold the first session. A repeat scan returns already checked in, so a learner who steps out for a call does not create a support ticket.
Uses check-in.
In session
Questions and polls inside the room
Live polls check comprehension in thirty seconds, which is the fastest formative assessment available to a facilitator. Q&A with upvoting lets a quiet cohort ask what it is actually confused about.
Uses polls and Q&A.
At the end of each session
Rate it now
A rating and a free-text suggestion, collected while the session is still in the room. That is the data a training team can act on between cohorts rather than between years.
Uses session feedback.
Setting up a workshop programme
Five steps. Step three is the one people skip and then regret.
Create the event
One event per programme or per cohort. Separate cohorts as separate events keeps the feedback comparable.
Build the workshop grid
Sessions with rooms, facilitators and time slots. Use tracks where learners follow distinct paths.
Set true capacities
Enter the room's real seat count, not the number you hope to fit. The server enforces it, so an optimistic number becomes a real problem at the door rather than a soft one.
Import the cohort and invite
CSV in, branded invite out, delivery tracked.
Turn on session feedback
Decide before day one which sessions collect ratings. Collecting on all of them is usually right for a first cohort.
What a 90-learner training day costs
Ninety learners activate. Fifty are free, so forty are billable, once, for the whole programme however many days and workshops it spans.
- activated attendees
- 90activated attendees
- billable, after the first 50 are free
- 40billable, after the first 50 are free
- for the whole event, at $5.00 each
- $200for the whole event, at $5.00 each
A cohort of fifty or fewer costs nothing at all, which covers a great many training days outright.
What a training programme needs that we do not have
This is the honest boundary, and for regulated training it is decisive.
- No continuing-education credit tracking. No CEU, CME or PDH, no attendance-duration verification and no certificate generation. If your programme awards credits, event67 cannot be the system of record for them.
- No learning management system features: no course content hosting, no assessments, no scoring, no completion records.
- No integration with your LMS or HR system. The cohort is a CSV import.
- No paid registration. Forms collect responses, not money.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Does event67 issue CEU or CME certificates?
No. There is no credit tracking, no attendance-duration verification and no certificate generation of any kind. For accredited training this is a hard gate, and you would need a separate system of record for credits with event67 handling the schedule, capacity and feedback around it.
How does the waitlist actually work?
Capacity is checked on the server when someone RSVPs, so the seat count cannot be beaten by two people tapping at once. When an attendee drops out, the next person on the waitlist is promoted automatically and notified. The facilitator's list is always the current list.
Can learners see only their own workshops?
Yes. Each learner stars the sessions they are in and their own day pins to the top of the schedule screen. The full grid stays browsable underneath it.
Is it worth it for a single 40-person workshop?
Financially it is free at that size, so the only question is whether the overhead of setting it up is worth the capacity control and the feedback. For a one-room, one-session day, probably not. For a day with four parallel workshops, the RSVP enforcement alone justifies it.
Can we reuse the setup for the next cohort?
Create a new event for each cohort. That keeps ratings and attendance separate, which is what you want when you compare how a module performed across groups. Each event carries its own free fifty attendees.
Keep reading
Other kinds of event
The features this leans on
Give every workshop a real seat count
Server-enforced capacity, automatic waitlists, and feedback collected in the room. Free up to fifty learners.