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.
- Exhibition / Trade Show
- Features
- Review and evidence
Review and evidence
Record independent decisions and supporting attachments against the event.
OverviewDecisions by event×
Exhibition / Trade Show · Review and evidence
New
Decisions by event
Review decisions
| Id | Parent | Reviewer | Source revision | Decision | Reason | |
|---|---|---|---|---|---|---|
| IDD-991 | EVN-46989 | 320 | Approve | Approve rd-230 | ||
| IDD-232 | EVN-13616 | 790 | Return | Reject rd-115 | ||
| IDD-217 | EVN-83888 | 410 | Approve | Return rd-917 | ||
| IDD-260 | EVN-98509 | 710 | Return | Approve rd-424 | ||
| IDD-593 | EVN-36078 | 220 | Approve | Reject rd-247 |
6 of 6 records
IDD-991Review decisions · RD-99390
ApproveParentEVN-46989
Source revision320
ReasonApprove rd-230
Decided at09 Oct
What you can do
Make the decision traceable
A reviewer decision belongs to an event and names the reviewer, source revision, decision, reason, time and operation key. Those details matter when the event or a booth assignment changes after submission. Event Reviewer should examine the current source record and its linked evidence, then decide against that revision. A decision on an older revision should not silently authorize a changed date, venue, capacity or booth allocation.
Attachments live under the same event. They include a title, file, evidence type, upload time, uploader and visibility. Internal and shared scopes help the operating team distinguish working evidence from material intended for broader use. Decide access carefully: shared visibility is an explicit classification, not a substitute for checking the recipient’s role or organization. Keep a record of the underlying decision even when the attached file changes.
How the work is organized
- Collect the evidence. Event Owner adds event documents and classifies their visibility before asking for review.
- Decide independently. Event Reviewer records approval, rejection or return with a reason and the source revision.
- Resolve changed scope. Event Owner prepares a correction; the reviewer considers the new scope and any compensation for executed work.
What to agree during setup
Agree which attachments are necessary for an event review and which are necessary for a booth assignment. Define an independent reviewer for each operating organization and the boundary between a return for correction and a rejection. Decide who can classify an attachment as shared and how the team handles a file uploaded to the wrong event. The operation key and source revision should be stable enough to connect a review decision to the action it authorizes.
Check the handoff on an actual case
Event Owner prepares a show with venue and capacity details, attaches the supporting information and sends it for review. Event Reviewer compares the current revision and attachment evidence, then records an approval with a reason. After booths have been assigned, the organizer asks to reduce capacity. Event Owner examines admission and booth records before requesting the change. Because existing work may already be executed, the reviewer evaluates a compensating action carrying the original source identity and reason. An older approval cannot simply be reused. The resulting operation receipt remains attached to the event so the team can inspect any discrepancy before calling the correction complete.
What your team sees
- Events awaiting review — Current event records and revisions needing a decision.
- Decisions by event — Review outcome, reviewer and reason beside the source revision.
- Shared event evidence — Attachments classified for shared visibility under their parent event.
Follow the work through
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.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Team members
- Staff membership linking a platform user to an organization and role.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
Who uses it
Permissions- Event Reviewer
- Owns the independent decision.
- Event Owner
- Prepares and corrects the work.
- Admin
- Governs access and evidence visibility.
- Finance Reviewer
- Checks resulting operation exceptions.
Set up Exhibition / Trade Show your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.