Review and Evidence

A review decision belongs to an event, identifies the source revision and names a reviewer. Its decision is Approve, Reject or Return, with a decision time, reason and operation key. The reviewer can use the event’s attachments and payment evidence to understand the submission. A decision against an earlier revision does not authorize a changed event or scan. For a scan decision, the reviewer checks the parent event and the submitted scan together before recording the decision for the current revision. That link is the basis for a clear handoff when an owner revises work after review.

Attachments have a title, evidence type, upload time, uploader and visibility of Internal or Shared. These fields help the team find the supporting file and control who should see it. Payment evidence records provider event identity, reference, type, amount in USD, occurrence time and whether it has been verified. The event ties these records together without turning an unverified provider event into a confirmed capture.

• Decision. Record the reviewer, revision and reason for each event or scan action.
• Supporting file. Link an attachment to the event and choose its visibility intentionally.
• Provider event. Separate the provider’s reported event from the team’s verification of it.

Choose reviewers who are separate from the people preparing and executing the event. Agree when to return work for correction and when to reject it. The reason should say what must change, so a new submission can be reviewed against the right revision. Decide which evidence types the team uses for venue confirmation, payment review or a cancellation request. Limit Shared attachments to the people who need them.

Identify the authoritative provider source before reconciling payments. Agree how its event ID and reference are matched to an event and how a refund or void is verified. The reviewer should see a capture as verified only after that source has been checked. An attachment is useful context, but it does not replace provider confirmation.

An event owner submits a revised start time for a sold-out show. The reviewer opens the event, reads the current revision and checks the venue note and attached change request. If the new time is acceptable, the reviewer records Approve with a reason. If the attached information is incomplete, the reviewer records Return. Later, a ticket scan arrives with a provider capture reference. The reviewer checks the separate payment evidence record before approving the scan. The team can then explain both the schedule decision and the admission outcome from records linked to the same event.

• Events awaiting review — Current event revisions needing an independent decision.
• Shared event attachments — Supporting files designated for shared access.
• Unverified payment evidence — Provider events awaiting confirmation.

Read review and evidence for decision handling and event closure for final evidence checks.