Who is invited.Who approved it.Who walked in.What that proves.
One system for all-hands, summits, workshops, client seminars, and the compliance training nobody may skip. Private by default: a company event never appears on public BumpJive unless you list it there, and a client-facing one borrows the whole consumer ticket machine the moment you do.
Six kinds of company event, one way to run them.
Each format keeps its own guest list, approvals, door and record, and they all behave the same way underneath. An organiser learns it once, and the person who inherits the job next year does not start over.
Compliance training
Mandatory means mandatory: nobody opts out, there is a pass mark, and the certificate is issued the moment somebody meets the attendance criteria. Your compliance officer can prove who sat through it, months later, without asking anyone to go searching a mailbox.
All-hands and town halls
Everyone in every office is included without anyone building a list, and a question typed from home joins the same queue as a hand raised in the room.
Multi-track summits
Tracks, rooms and per-session seats, each with its own capacity and waiting list, under one agenda that cannot contradict itself.
Workshops and cohorts
Fixed seats over fixed weeks. Prerequisites are checked when somebody asks for a seat, rather than apologised for on the day.
Client seminars
A guest opens a sealed invitation, accepts the NDA once, and attends without creating an account. Their pass stays tied to the colleague who invited them.
Offsites
Every seat request carries a cost centre, so finance gets one clean report instead of a thread with fourteen replies.
The audience is your org chart, not a mailing list.
Invite all of Engineering in Berlin, or every manager appointed this year, and the list stays true as people join, move and leave. Nobody maintains a spreadsheet of who counts as a manager.
Invite by department, team or location
Those are real things here, not tags somebody invented for one event. An audience is a rule about your organisation, so it is still right next quarter.
Hand a seat to a colleague
Allowed exactly where your policy allows it: same team, same event, and never two working passes for one seat.
Bring in people from outside
A guest arrives on a sealed invitation rather than an open link, claims their seat without creating an account, and stays tied to the host who invited them.
Elias Kiptoo, travel to the Engineering Summit
Gaborone to Berlin. Cost centre CC-2189.
- ManagerApproved
- Budget codeApproved
- Final sign-offPending
Example data, written for this page. Your stages, your approvers and your cost centres.
The two things that go wrong at a door.
A pass gets forwarded into a group chat. The venue wi-fi drops halfway through arrivals. Front desk staff should not have to work around either.
A pass that cannot be forwarded
What an attendee sees on their phone is good for about a minute, and only good for them. Screenshot it, forward it, and the person holding the screenshot is turned away at the door.
A door that works when the network does not
Your staff keep scanning through the outage and the queue keeps moving. Every scan taken while the connection was down is confirmed the moment it comes back, and not one of them is quietly lost.
It is the same door BumpJive already runs for public events, pointed at identity and approvals instead of ticket sales.
A remote seat is still a seat.
A join link belongs to one person. Forward it and it stops working, the same way a pass does at the door. Any session can be in the room, online, or both, and a question from the stream joins the same queue as a question from the floor.
Reschedule once, and every invitation follows. Calendar invitations for Google, Microsoft 365 and anything that reads ICS are generated from the event itself, so there is no second copy of the date to drift out of step.
The record still stands a year later.
Attendance, certificates, seat transfers and every administrative action are written once and cannot be quietly edited afterwards. A correction is a new entry saying what changed and who changed it, which is the only version of this that survives being asked about long after everyone has gone home.
| Written | Source | Entry |
|---|---|---|
| 24 Jul 09:12:41 | Door 4 kiosk | Arrival verified, Amara Okafor |
| 24 Jul 09:31:08 | Door 4 kiosk | Arrival verified, Tobias Renner |
| 24 Jul 11:47:19 | Scanned offline, confirmed later | Arrival verified, Nadia Halvorsen |
| 24 Jul 16:02:55 | Attendance criteria met | Certificate issued, Compliance 2026 |
24 Jul 09:12:41 · Door 4 kiosk
Arrival verified, Amara Okafor
24 Jul 09:31:08 · Door 4 kiosk
Arrival verified, Tobias Renner
24 Jul 11:47:19 · Scanned offline, confirmed later
Arrival verified, Nadia Halvorsen
24 Jul 16:02:55 · Attendance criteria met
Certificate issued, Compliance 2026
These particular entries are examples written for this page. A real record belongs to one company and is readable only inside it.
All of this is live. Go and use it.
Create a workspace, link the events you organise, add colleagues by email, then ask for a seat with a cost centre on it and watch it clear both approvals and land in the record. That is the product, not a preview of it.