Skip to main content

Parent demo prep

The Day-5 last hour. Here's how to make it land.

The day before​

  • Save every student's project. Use the platform's save, share, export, or account workflow before students leave.
  • Email parents a reminder. Include time, room, and what they'll see.
  • Plan room flow. If parents rotate between siblings or classmates, budget about 5 minutes per student.

Morning checklist​

  • Every project opens on the right device.
  • Every student has run through the part they plan to show.
  • Every student has rehearsed a short explanation.
  • Chairs are arranged so parents can stand or sit behind students.
  • Snacks/water are ready if your site provides them.
  • Sign or board: "Welcome to [Camp name] Demo".
  • Code Coach has a student list and one note about each project.
  • Backup plan is ready if a project will not load: screenshots, saved exports, or a coach-led walkthrough.

What each student presents​

Students pick 3 favorite moments from their project. For each:

"This part is [X]. I built it by [Y]. The hardest part was [Z]."

Three short explanations usually land better than a complete walkthrough.

For older or faster students, encourage them to show one piece of code or logic:

"This is the part that controls [feature]. I changed [value or block] so it would [result]."

Parents love seeing the connection between a visible feature and the thinking behind it.

Sample student script​

Print this and place it near screens if students want support:

Hi! My name is _________ and I built this project this week.

[Run or open the project]

This first part is __________.
I built it by __________.
The hardest part was __________.

My favorite feature is __________ because __________.

One thing I would add next is __________.

That's it. Any questions?

Students who finish early can also show:

  • A visual theme or design choice.
  • A stretch challenge or custom feature.
  • A bug they fixed and how they found it.

Code Coach role during the demo​

You're a backup memory and a calm guide.

  • If a student freezes, prompt them: "Show your favorite part first."
  • If a parent asks a hard technical question, help the student answer in plain language.
  • Take photos if your site has permission.
  • Note early departures and offer a short re-show before parents leave.

What the demo is NOT​

  • Not a tech support session for parents.
  • Not a sales pitch for the next session.
  • Not a full line-by-line explanation of every step.

After parents leave​

  • Send a thank-you email with a Creator Hub link.
  • Include 2-3 group photos if you have permission.
  • Save your notes for next session: common stuck points, pacing tweaks, and what worked.