These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Virtual Event Platform
- Features
- Event Command
Event Command
See the live state of the program and resolve every operation receipt that failed or needs review.
OverviewUnresolved Operation Receipts×
Virtual Event Platform · Event Command
New
Unresolved Operation Receipts
Operation receipts
| Parent | Action | Operation key | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| EVN-58426 | ACT-209 | OK-434 | Pending | 24 Oct | Cut to length | |
| EVN-53557 | ACT-617 | OK-724 | Failed | 08 Oct | Weld frame | |
| EVN-60891 | ACT-619 | OK-197 | Needs review | 05 Oct | Drill and tap | |
| EVN-27324 | ACT-119 | OK-944 | Pending | 21 Oct | Deburr | |
| EVN-88809 | ACT-566 | OK-517 | Failed | 23 Oct | Assemble |
6 of 6 records
ACT-209Operation receipts · OR-18274
PendingParentEVN-58426
Operation keyOK-434
Occurred at24 Oct
Failure reasonCut to length
What you can do
Run event day from one worklist
On event day the team needs one place to see what needs attention. The Event Command Dashboard shows events by status, breakouts awaiting review, admissions, unresolved operation receipts and payment evidence gaps, with a ranked worklist that opens the underlying record.
Behind the dashboard, every guarded action on an event leaves an operation receipt: the action, a unique operation key, the version it expected, the outcome, the time, any external reference, the records it affected and the failure reason. Outcomes are Pending, Completed, Failed or needs review. A repeated action with the same key returns the original receipt and makes no second change.
How the work is organized
- Receipts for every guarded action. Approvals, registrations, admissions, closures and cancellations each leave a receipt.
- Unresolved receipts in one queue. Pending, Failed and needs review receipts sit together for the Finance Coordinator.
- Reconciliation that never repeats an action. Receipts are compared with the admissions, payments and decisions they should have produced, then marked Completed or needs review.
What to agree during setup
Agree who watches the dashboard during an event and who resolves receipts afterwards. Decide when the routine reconciliation runs. Agree what evidence lets a receipt be marked Completed and who signs off a needs review receipt.
Check the handoff on an actual case
Twenty minutes into the user conference, the streaming platform’s join notifications slow down and several admissions are retried. Each retry uses the same operation key, so attendees are admitted once. Two receipts are left Pending when the connection times out.
The dashboard ranks them at the top of the worklist. After the keynote, the Finance Coordinator opens Unresolved Operation Receipts. One Pending receipt has a matching admitted time on its registration and is marked Completed. The other has no admission, so it is marked needs review with the discrepancy, and the Registration Coordinator follows up with the attendee.
What your team sees
- Unresolved Operation Receipts — Receipts waiting for review with action, outcome and failure reason.
- Active Venues — Venues currently in use, with contacts and eligibility notes.
- Active Organizations — The organizations running events, with time zone and currency.
Follow the work through
- Cancellation and reconciliation: Reconcile receipts and payments after a cancellation or correction.
- Registration to admission: See where receipts are left for registrations and admissions.
Map the source records before importing history.
What it keeps track of
Data model- Operation receipts
- Idempotent receipts for every guarded operation executed against an event.
- Events
- Virtual events moving through draft, review, approval, open and completion.
- Admissions
- Reserved and admitted attendee lines belonging to an event.
- Payment evidence
- Provider authorization, capture, refund and void evidence for event payments.
- Organizations
- Tenant organizations that own events, venues and team membership.
Who uses it
Permissions- Finance Coordinator
- , Event Coordinator, Event Reviewer, Admin.
- The Finance Coordinator resolves receipts.
- The Event Coordinator watches the dashboard on event day.
- The Event Reviewer and Admin read the trail when a question arises.
Set up Virtual Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.