Graduation operation · Operations room
On event day nobody browses menus. The Operations Room brings together on a single screen the audience that has entered, the crew that checked in, the checklist for the current time, open incidents and the team board, with a big-screen mode for the production room and a retrospective that answers, the next day, what time the venue filled up.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
On event day the information is spread across five screens and nobody has time to open any of them.
One screen brings together attendance, posts, the current checklist, incidents and board, and it opens straight to today's event without asking anything.
The operations checklist is a sheet of paper on someone's clipboard.
Checklist per post with times calculated from the event start, checked off on the phone by whoever is on their feet, with delays highlighted.
The day's problems turn into group chat messages and get lost.
Incidents opened with a short form, with an owner and severity, saved to the same Issues Board that Event Production already uses.
An important message needs to reach the entire field crew at the same time.
Board with priority, target audience and expiration, because a notice for the day dies with the day and a board full of old messages stops being read.
The next day nobody can say what time the venue filled up.
While open, the Room records periodic snapshots of the metrics, and the retrospective shows the attendance curve, the checklist completed on time and incidents hour by hour.
If a module isn't subscribed, the whole event day screen breaks.
Each card reads from a different source and fails on its own: whatever isn't available shows the reason and the rest of the dashboard stays up.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
Entry was bottlenecking and production couldn't see how big the problem was.
The dashboard showed the hourly entry curve and the number of posts with check-in done, making it clear the main gate was short on ticket validators.
Two freelancers were moved to the front gate, and the curve was back to normal in twenty minutes.
The bar always opened late because each stand depended on someone remembering what to do.
A checklist per post was applied to the event, with items already converted to real clock time from the start.
The Room showed what was behind while there was still time, and the bar opened on schedule for the first time that season.
The company couldn't justify the size of the crew hired for the next event.
The retrospective showed peak attendance with the time, incidents by severity and the percentage of the checklist completed on time.
Crew sizing started being discussed with numbers instead of gut feeling, and the next proposal was approved without any scope cuts.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
6 modules and 34 features on this page, all running on the same class, graduate and event records.
Everything about the event on one screen, updating on its own.
The same information in full screen, for the production room.
Templates reused across events, applied with the right times.
The day's problem recorded where the company already records problems.
The message that reaches everyone at the same time.
The next day, with numbers instead of gut feeling.
Compare the modules and choose the setup that fits your operation.