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.
- Photo Booth / Activation
- Features
- Review Decisions
Review Decisions
Record an independent decision on the submitted version of activation work.
OverviewReturned for Correction×
Photo Booth / Activation · Review Decisions
New
Returned for Correction
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| EVN-83125 | 40 | Return | 12 Oct | Return rd-437 | ||
| EVN-82805 | 460 | Return | 07 Oct | Return rd-878 | ||
| EVN-80322 | 380 | Return | 20 Oct | Return rd-236 | ||
| EVN-47372 | 200 | Return | 22 Oct | Return rd-900 | ||
| EVN-19553 | 430 | Return | 17 Oct | Return rd-119 |
6 of 6 records
Return rd-437Review decisions · RD-61858
ReturnParentEVN-83125
Source revision40
Decided at12 Oct
What you can do
Decide the version in front of you
A review decision records a source revision, reviewer, decision, reason and decision time against an event. This lets the team explain what was approved, rejected or returned, even when the activation session later changes. Independent Reviewer inspects the submitted session and its supporting event evidence before recording a decision.
The submitted revision is essential. A prior approval should not silently apply to a changed consent template, brand or delivery record. When the operator makes a correction, the reviewer evaluates that new version. The decision reason should help the operator understand a return or rejection without guessing what to change.
How the work is organized
- Inspect submitted work. The reviewer starts from the activation session waiting for a decision and checks its event and organization context.
- Record an outcome. Approval, rejection and return are distinct decisions with a reviewer, time and reason.
- Keep the trail. The source revision and operation key connect a decision to the version and action the team later audits.
For example, a reviewer may return a session when the consent template is inconsistent with the client agreement. The Media Operator can correct the record and submit it again. The original return remains useful evidence; the next approval must point to the corrected submitted revision.
What to agree during setup
Choose who can review events and who can review media release, and define how independent the reviewer must be from the preparer. Establish concise reasons for returning work and how a decision is communicated to the operator. Decide which event attachments the reviewer must inspect before approving media. The team should also know when a corrected or cancelled event scope requires a compensating decision instead of a direct edit.
Set a clear standard for a final decision: the reviewer checks the current revision, the event and organization match, and any required consent and delivery evidence is available. Record the person who decided and the time. Keep the decision visible to the Event Manager when event completion is discussed.
Check the handoff on an actual case
Submit a media session and ask one Independent Reviewer to return it with a reason. Confirm the return appears in the correction list. Revise and resubmit, then ask for approval against the new source revision. Check that a stale revision cannot be approved and that the preparer cannot sign off their own work under the team’s role policy. Use a second case that is rejected and confirm it does not appear as approved media. Trace each decision back to its event and reviewer before accepting the pilot.
What your team sees
- Returned for Correction — Decisions that sent work back, with reason, revision and reviewer visible.
- Activation Sessions Awaiting Review — Submitted sessions awaiting the next independent decision.
Follow the work through
Use media review for the release decision and scope correction when accepted event work must change.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on an exact submitted revision.
- Activation sessions
- Activation sessions that release approved media after consent and delivery evidence.
- Events
- Scheduled photo booth and activation events with capacity and lifecycle.
- Team members
- Staff members with organization membership and operational role scope.
- Record attachments
- Uploaded evidence files linked to an event.
Who uses it
Permissions- Independent Reviewer
- , Media Operator, Event Manager, Admin.
Set up Photo Booth / Activation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.