1. Community Event Platform
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Keep reviewer decisions, supporting files and operation outcomes traceable.

OverviewReview decisions
Community Event Platform · Review and evidence

Review decisions

Review decisions

New
SourceSource revisionDecisionDecided atReasonReviewer
CE-59190340Approve11 OctApprove rd-778
CE-92144630Return03 OctReject rd-754
CE-65066880Approve15 OctReturn rd-614
CE-10734170Return10 OctApprove rd-116
CE-12520610Approve13 OctReject rd-962
6 of 6 records
Approve rd-778Review decisions · RD-17230
Approve
SourceCE-59190
Source revision340
Decided at11 Oct
Example screen with sample data

What you can do

Keep the operating record clear

Review decisions records who decided an event revision, when, and why. Evidence documents keeps uploaded files with the event and marks their visibility Internal or Shared. Operation runs records guarded attempts, their source revision, stable key and result. Together these records let the team trace a decision or retry to the event it concerned.

How the work is organized

  • Review the exact scope. Independent Reviewer compares the selected event revision with the decision being made.
  • Keep supporting material attached. Event Owner links documents to the event and chooses their visibility.
  • Investigate the result. Reconciliation Lead reads the operation receipt and its linked effects before resolving needs review.

What to agree during setup

Agree what evidence a reviewer needs for an event and for a registration. Assign independent reviewers who can see the relevant organization while avoiding self-approval. Decide when a file is internal or shared. Rehearse an approval on the current revision and a returned decision after a change.

Check the handoff on an actual case

The owner submits an event after adding a supporting document. The reviewer reads the event revision, considers the evidence and records an approval, rejection or return with a reason. When a later correction changes the event, the prior decision stays attached to its original revision. A reconciliation discrepancy appears in the operation queue with the reason for investigation.

For a concrete review, submit an event with a supporting file marked Shared and another marked Internal. The Independent Reviewer reads the permitted evidence and records Approve, Reject or Return with a reason for the current event revision. After the Event Owner changes capacity, inspect the earlier decision and confirm it still describes the old revision. For an operation discrepancy, read the saved failure reason and external reference, compare the linked local effects and leave the receipt for investigation until the evidence agrees. These checks show who made each decision and which scope it covered.

What your team sees

  • Event review queue — Events awaiting a decision on their current revision.
  • Operations needing review — Receipts with a discrepancy reason for the Reconciliation Lead to investigate.

Follow the work through

Check the record definitions before importing active work.

What it keeps track of

Data model
Review decisions
Independent reviewer decisions recorded against a source revision.
Evidence documents
Uploaded evidence files linked to an event with visibility scope.
Community events
Programs, events and sessions with capacity, lifecycle and revision.
Event registrations
Participant registration records submitted for review and completion.
Operation runs
Idempotent receipts for guarded operations with expected revision and result state.
People
Staff membership linking a platform user to an organization and role.

Who uses it

Permissions
Independent Reviewer
Decides submitted scope.
Event Owner
Prepares evidence.
Reconciliation Lead
Investigates operation outcomes.
Admin
Manages access.

Set up Community Event Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started