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.
- Theme Park Management
- Features
- Review and evidence
Review and evidence
Independent decisions and inspection files.
OverviewReview decision log×
Theme Park Management · Review and evidence
New
Review decision log
Review decisions
| Id | Parent | Reviewer | Source revision | Decision | Decided at | |
|---|---|---|---|---|---|---|
| IDD-218 | EVN-91683 | 430 | Approve | 09 Oct | ||
| IDD-510 | EVN-10015 | 870 | Return | 18 Oct | ||
| IDD-831 | EVN-91102 | 300 | Approve | 27 Oct | ||
| IDD-723 | EVN-79165 | 920 | Return | 11 Oct | ||
| IDD-359 | EVN-68499 | 900 | Approve | 15 Oct |
6 of 6 records
IDD-218Review decisions · RD-18796
ApproveParentEVN-91683
Source revision430
Decided at09 Oct
ReasonApprove rd-137
What you can do
Keep the inspection and the decision together
Review decisions record who decided, which revision they reviewed, whether they approved, rejected or returned it, when and why. They are kept on the event as their own records, so the history of a day shows every release and return in order.
Evidence files sit beside the decisions: inspection checklists, maintenance sign-offs, operating notes. Each file has a title, evidence type, who uploaded it and when, and whether it is internal or shareable. A ride session cannot be released without inspection evidence attached to the same event, so the evidence is always there when an inspector or insurer asks.
How the work is organized
Ride operators upload evidence; supervisors decide.
- Decision with revision. Each decision names the revision it applied to.
- Evidence on the event. Files are attached to the event they support.
- Shareable when needed. Internal notes stay internal; shareable files can go to inspectors.
What to agree during setup
Agree what evidence each ride needs before release, and how long files are kept. Agree who may mark evidence shareable. Prepare examples of a release, a return for a missing sign-off and a rejection.
Check the handoff on an actual case
A safety inspector visits a month later and asks how the coaster was cleared on a particular day. The operations manager opens that day’s event and finds the coaster’s readiness record, the supervisor’s return for a missing brake test, the operator’s uploaded sign-off and the final release at 09:20. Everything the inspector needs is on one record.
The checklist was marked shareable when it was uploaded, so the manager can hand it to the inspector directly. The operator’s internal note about the brake test stays internal.
Evidence that is not tied to a ride session can still be attached to the event, such as crowd control plans for a night event or a contractor’s sign-off for new lighting. It sits on the same record as the rides and admissions for that day.
What your team sees
- Review decision log — Releases, returns and rejections with reasons.
- Evidence files — Inspection and operating files by event.
Follow the work through
- Ride session release: Where decisions are made.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Record attachments
- Inspection and operating evidence files attached to an event.
- Events
- Park operating events with capacity, lifecycle and revision control.
- Team members
- Park staff with organization membership and platform identity.
Who uses it
Permissions- Ride Operations Supervisor
- , Ride Operator.
- Supervisors decide; operators upload evidence.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.