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
- Review Queue
Review Queue
Record independent decisions to approve, reject or return each submitted event and breakout session.
OverviewMy Review Decisions×
Virtual Event Platform · Review Queue
New
My Review Decisions
Review decisions
| Parent | Source revision | Decision | Reason | Decided at | |
|---|---|---|---|---|---|
| EVN-71047 | 160 | Approve | Approve rd-449 | 11 Oct | |
| EVN-18581 | 170 | Return | Reject rd-740 | 16 Oct | |
| EVN-92232 | 360 | Approve | Return rd-781 | 25 Oct | |
| EVN-97961 | 850 | Return | Approve rd-516 | 27 Oct | |
| EVN-35999 | 190 | Approve | Reject rd-135 | 19 Oct |
6 of 6 records
Approve rd-449Review decisions · RD-58992
ApproveParentEVN-71047
Source revision160
Decided at11 Oct
What you can do
Decide the version that was submitted
An event or breakout should go live only after someone other than its owner has checked it. A review decision records the decision (Approve, Reject or Return), the reason, the reviewer, the time and the version number it applies to. The reviewer must be an active team member in the same organization and independent of the owner.
If the event changes after submission, the decision on the earlier version no longer applies, and the new version waits for its own review. A repeated approval returns the original decision. A conflicting one is refused.
How the work is organized
- Approve. The event or breakout moves forward, and the decision is kept with its reason.
- Return. The work goes back to its owner with a reason, for a revised version.
- Reject. The work stops, with the reason recorded.
What to agree during setup
Name the reviewers and their deputies, and keep the list of eligible reviewers current. Agree what a reviewer checks on an event: capacity against the venue’s limits, timing across time zones and supporting files. Agree what a breakout review checks: host confirmation, start time and capacity. Decide the turnaround for reviews in the final week before an event.
Check the handoff on an actual case
A coordinator submits a product launch webinar for Tuesday at 09:00 Pacific with a capacity of 5,000. The Event Reviewer opens Events Awaiting Review, reads the venue’s eligibility note, which limits the webinar plan to 3,000 attendees, and returns the event with that reason.
The coordinator lowers capacity to 3,000 and resubmits. The reviewer approves the new version, and the decision records the version number, reason and time. When someone retries the earlier return, it is refused because it belongs to an older version.
What your team sees
- Events Awaiting Review — Events submitted for review with owner, venue, start, capacity and version.
- My Review Decisions — Decisions the signed-in reviewer has recorded.
- Eligible Reviewers — Active team members with their role names, used to assign reviews.
Follow the work through
- Event approval to close: See where event approval sits in the lifecycle.
- Breakout session approval: Review a breakout before it opens.
Rehearse access with a coordinator account before go-live.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against a frozen event revision.
- Events
- Virtual events moving through draft, review, approval, open and completion.
- Breakout sessions
- Breakout session extensions submitted for independent review before opening.
- Team members
- Authenticated platform identities with an operational role inside an organization.
Who uses it
Permissions- Event Reviewer
- , Event Coordinator, Program Manager.
- The Event Reviewer decides.
- The Event Coordinator and Program Manager prepare and resubmit work.
Set up Virtual Event Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.