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.
- Live Event Streaming
- Features
- Review and evidence
Review and evidence
Keep decisions, receipts and attachments with the event.
OverviewEvent Review Decisions×
Live Event Streaming · Review and evidence
New
Event Review Decisions
Review decisions
| Source revision | Decision | Decided at | Reason | Reviewer | Parent | |
|---|---|---|---|---|---|---|
| 870 | Approve | 20 Oct | Approve rd-299 | EVN-24590 | ||
| 740 | Return | 09 Oct | Reject rd-511 | EVN-79761 | ||
| 580 | Approve | 22 Oct | Return rd-485 | EVN-92497 | ||
| 270 | Return | 16 Oct | Approve rd-784 | EVN-20353 | ||
| 70 | Approve | 03 Oct | Reject rd-215 | EVN-23749 |
6 of 6 records
Approve rd-299Review decisions · RD-16853
ApproveSource revision870
Decided at20 Oct
ParentEVN-24590
What you can do
Make the decision traceable
A Review Decision records an approve, reject or return decision against a source revision of an Event. The reviewer, time and reason make the decision explainable after the event has changed. The source revision matters: a favorable decision on an earlier schedule or capacity must not be treated as approval of a changed event. The Event Reviewer owns that decision, distinct from the person preparing the record.
Operation Receipts keep a stable operation key, expected revision and result state for guarded actions. A receipt may be pending, completed, failed or need review. The receipt gives the team a place to investigate an uncertain result without repeating an external effect. Record Attachments keep event evidence with a visibility scope and uploader. Shared and internal visibility are distinct choices during review.
How the work is organized
- Decision. review decisions ties a reviewer and reason to the source revision.
- Operation. operation receipts tracks the action key and observed result.
- Evidence. record attachments stores files and visibility beside the parent Event.
What to agree during setup
Choose the decision authority for an event and a participant registration. Decide which evidence type is required for each review, and who may see internal versus shared attachments. Establish a rule for stale decisions after a revision changes. Also define who investigates a receipt that remains pending or needs review and which provider reference is authoritative for that action.
Check the handoff on an actual case
An Event Manager changes capacity after the event was submitted. The Event Reviewer compares the submitted revision with the current one before deciding. A return decision includes the reason, allowing the owner to correct and resubmit. Later, a payment operation receives an uncertain provider response. The Operation Receipt retains its key and expected revision. Finance Reviewer checks the linked local effect and provider reference, records the discrepancy and resolves the receipt only when the evidence matches. The event’s attachment history remains available for the reviewer who handles closeout.
A reviewer receiving a case mid-shift can start with the current event revision, then read the decision history and attachments in order. A completed receipt means the expected effect was observed; a failed receipt and one needing review call for different follow-up. Keep the reason concrete so the next person can determine whether the issue was source data, provider evidence or access scope.
What your team sees
- Event Review Decisions — Decisions, reviewers and revisions for the selected event.
- Open Operation Receipts — Pending or disputed actions that need investigation.
Follow the work through
See review and evidence and event closeout.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against a source revision.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Record attachments
- Uploaded evidence files linked to an event with visibility scope.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Team members
- Staff membership linking a platform user to an organization and role.
Who uses it
Permissions- Event Reviewer
- , Event Manager, Finance Reviewer, Admin.
Set up Live Event Streaming your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.