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.
- Award / Competition Mgmt
- Features
- Review and evidence
Review and evidence
Retain event decisions, attached evidence and operation outcomes.
OverviewReceipts needing review×
Award / Competition Mgmt · Review and evidence
New
Receipts needing review
Operation receipts
| Operation key | Parent | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| OK-195 | EVN-66282 | ACT-665 | 50 | Needs review | Cut to length | |
| OK-164 | EVN-50376 | ACT-738 | 910 | Needs review | Weld frame | |
| OK-181 | EVN-79149 | ACT-877 | 690 | Needs review | Drill and tap | |
| OK-226 | EVN-52776 | ACT-603 | 570 | Needs review | Deburr | |
| OK-958 | EVN-85794 | ACT-989 | 110 | Needs review | Assemble |
6 of 6 records
OK-195Operation receipts · OR-76868
Needs reviewParentEVN-66282
ActionACT-665
Expected revision50
Failure reasonCut to length
External referenceER-994
What you can do
Keep a decision with its source
A review decision links to an event and records the source revision, reviewer, decision, time, reason and operation key. Approve, Reject and Return are different outcomes. The reviewer should be able to explain which version of the event was considered and why it was accepted or sent back. For a registration under review, the team checks its own status and revision and the current parent event scope.
Attachments carry a title, evidence type, upload time, uploader and visibility setting. Internal and Shared are explicit scopes. The team can attach an event plan, venue confirmation or provider correspondence, subject to its access rules. An attachment helps explain a decision, but the decision record still needs its own reviewer and reason.
How the work is organized
- Decision. A named person records a result against a source revision and gives a reason.
- Attachment. A file is tied to the event and labeled for internal or shared visibility.
- Operation outcome. A receipt keeps the action, expected revision, result state and linked effects for follow-up.
What to agree during setup
Decide which people may submit an event and who can decide it independently. Define when Return is used for revision and when Reject ends the proposed scope. Set the attachment visibility policy before adding files that contain personal or payment context. Agree who checks receipts marked needs review or Failed and where the authoritative external reference is found. Train staff to preserve an earlier decision when a later revision changes the event; the new revision needs its own review rather than quietly inheriting the older approval.
Check the handoff on an actual case
An Event Owner changes the venue and capacity for a planned ceremony after the first review. The Event Reviewer opens the revised event, checks the venue evidence, and records a new decision with the current revision and a reason. The earlier decision remains part of the record. Later, a payment-related operation receipt is marked needs review because its expected provider effect is unclear. Finance Reviewer compares the receipt’s external reference and linked effect references with payment evidence before recording a resolved outcome. The team can explain the event change and financial follow-up without treating an attachment or a local receipt as a substitute for the underlying decision or provider confirmation.
What your team sees
- Event decisions — See reviewer, source revision, decision and reason by event.
- Receipts needing review — Find uncertain operation effects and their failure reason.
- Events awaiting review — Open event plans waiting for an independent decision.
Follow the work through
Use event planning and review for the approval handoff and event closeout for outstanding receipts. Review roles when assigning access.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against a source revision.
- Record attachments
- Uploaded evidence files linked to an event with visibility scope.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- People
- People records for award and competition operations: a platform user's membership in the hosting organization with role title, time zone and active state.
- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
Who uses it
Permissions- Event Reviewer
- , Event Owner, Finance Reviewer, Admin
Set up Award / Competition Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.