Portable planetarium operators benefit from a calm post-event review process when something did not go as expected. The goal is to preserve useful lessons, protect private details, and separate public patterns from sensitive event records.
This checklist is a general review workflow. Incident-specific legal, insurance, medical, school-policy, venue-policy, equipment-repair, emergency, safety-threshold, or reporting decisions should come from operator records, qualified guidance, manufacturer documentation, venue rules, school rules, insurer or legal review where applicable, or direct submitted evidence.
Separate Private Records From Public Lessons
Keep the operator's incident, near-miss, equipment, venue, host, school, medical, accommodation, payment, security, and contact notes private.
Convert only anonymized, permissioned, or aggregate lessons into public PortaDome guides, Dispatch ideas, training notes, or demand-signal summaries.
- Do not publish identifying event details unless the owner of those details has directly approved the use.
- Avoid treating one private event as a public trend.
- Keep public examples focused on general workflow lessons rather than sensitive records.
Capture The Basic Review Fields
Useful private review notes often start with what was noticed, where in the event workflow it occurred, and whether it involved equipment, venue access, communication, scheduling, accessibility, host coordination, teaching materials, or follow-up.
Label what needs private follow-up, qualified review, manufacturer review, host review, or internal operator review before turning any lesson into a reusable checklist item.
Preserve Evidence Without Overclaiming
Photos, messages, forms, equipment notes, and host communications should stay in the operator's own records when needed.
Label whether each note came from direct observation, host report, equipment documentation, submitted correction, or later review.
Feed Safe Patterns Back Into Operations
Repeated anonymous patterns can inform setup checklists, site survey questions, event-day communication, teacher and host prep, troubleshooting triage, maintenance routines, and future Dome Guide topics.
Analytics, demand-signal reports, and community notes should stay limited to aggregate or non-sensitive patterns until approved instrumentation and consent routes exist.
Useful PortaDome Companions
Pair this checklist with the safety guide, site setup checklist, school site survey checklist, event-day communication checklist, troubleshooting triage guide, post-event review checklist, maintenance routine guide, load-in and venue access checklist, moderation queue template, and Demand Signals report template.