Back to Insights
Event Nightsparent teacher conference schedulingconference night checklistschool conference software

The conference night runbook

A practical checklist for the week before, the night of, and the morning after parent-teacher conferences — written for the admin holding the duct tape.

4 min read
347 words

Free: AI Integration Starter Guide

A practical roadmap for integrating AI into your business operations.

Why conference night still breaks

Three hundred families. One shared sheet. A form that worked in September and dies at 8pm in November. If you have lived that night, you already know the failure mode: too many people editing the same thing, confirmations that never arrive, and a front desk answering the same “am I booked?” question until 9:30.

This runbook is the version we use with schools on SchoolConferenceGo. Steal it even if you keep your current tool.

Seven days out

  • Freeze the schedule shape. Teacher blocks, blackout times, and specials should stop changing daily.
  • Send one booking path. Not three links in three emails. One URL in the newsletter, the classroom app, and the reminder text.
  • Name the human on watch. Who is the escalation contact the night of? Put a cell number in the staff brief — not buried in a PDF.
  • Test confirmation email/SMS to a personal account. If parents do not get receipts, you will get phone calls.

Forty-eight hours out

  • Pull the open-slot report by teacher. Chase the thin rooms, not the full ones.
  • Brief volunteers: check-in location, late arrivals, interpreters, and what “we cannot find your booking” actually means.
  • Print a backup roster only if your network is unreliable — and treat paper as backup, not the system of record.

Night of

  • Keep one live dashboard open. Refresh habits beat screenshot habits.
  • Do not open a parallel spreadsheet “just in case.” Parallel systems are how double-books happen.
  • Log issues in one place (a shared note is fine). Patterns matter more than heroics.

Morning after

  • Export attendance and no-shows while the night is fresh.
  • Send a short thank-you and a “how did booking go?” pulse — three questions max.
  • Write down what broke. That note becomes next semester’s week-one checklist.

The product version of this runbook

SchoolConferenceGo exists because we kept watching the same night fail the same way. One booking path for families, live dashboards for staff, and someone watching launch. If your runbook still depends on a hero admin and a fragile sheet, that is the duct tape talking.

Related Articles

More Articles

Ready to retire the shared spreadsheet on conference night?

See SchoolConferenceGo

Ready to Build Your Competitive Advantage?

Let's discuss how custom technology can drive measurable results for your business. No sales pitch -just a strategic conversation about your goals.

We typically respond within one business day. Your information is never shared with third parties.