Audience questions and host feedback can help a portable planetarium operator improve programs, follow-up materials, event checklists, and future content planning. The useful habit is to capture those notes carefully while keeping private people, schools, hosts, and events out of public materials unless permission is documented.
This checklist separates private notes from public examples. It does not assume PortaDome has measured audience demand, survey results, traffic, search, filter, download, submission, Dispatch signup, or outreach-reply behavior unless a future approved data route supplies that evidence.
Separate Questions, Feedback, And Permission
Treat audience questions, teacher comments, host feedback, testimonials, photos, case-study interest, Dispatch interest, listing corrections, and operator observations as different kinds of records.
Do not treat a good comment, successful visit, booking relationship, or audience participation as permission to publish a name, quote, photo, school, logo, classroom detail, or case-study detail.
Capture Useful Private Notes
Record recurring questions, requested subjects, grade-level fit, vocabulary confusion, host-prep gaps, setup friction, room-flow issues, accessibility questions, follow-up material requests, and listing corrections as private operational notes.
Keep private participant, host, school, teacher, student, medical, accommodation, security, payment, contract, incident, and contact details outside public PortaDome content.
- Do not invent survey results, question frequency, satisfaction scores, learning outcomes, repeat-booking rates, referral rates, conversion rates, or market trends.
- Do not publish direct quotes, photos, school names, student work, host names, organization logos, or classroom details unless permission is documented from the appropriate source.
- Do not label hunches, one-off impressions, or uninstrumented site behavior as measured demand.
Label The Source Of Each Signal
Mark whether a note came from an audience question, direct host request, teacher feedback, operator observation, public submission, listing correction, outreach reply, or internal review.
Keep source labels plain so later demand-signal reporting can distinguish direct submissions, operator notes, host feedback, public REST/manual milestone evidence, and any future approved analytics route.
Decide What Can Become Public
Use public examples only when identifying details are removed, permission is documented, or the item is already safe as aggregate or anonymized planning context.
When permission is unclear, keep the note private and use it only to improve internal checklists, toolkit worksheets, show-finder gaps, or future article planning.
Feed The Right PortaDome Lane
Repeated subject questions can inform Show Finder gaps and Dome Guide topics. Host-prep friction can improve toolkit worksheets and event checklists. Permissioned stories can support Operator Spotlight or Dispatch planning.
Until analytics or counters are approved, use only approved aggregate or manual evidence in PortaDome Demand Signals reports.
Useful PortaDome Companions
Pair this checklist with the Operator Toolkit, post-event review checklist, follow-up materials checklist, photo and testimonial permission checklist, repeat-booking and referral follow-up checklist, weather and backup planning checklist, and Operator Spotlight intake template.