Four days of decisions become visible in about eleven seconds each. Every boat gets tested with a learner inside it, the sinking ones get the loudest cheer of the day, and the whole week gets named out loud on the way home. Full-day Adventure Day - the normal schedule does not apply.
By pickup today every learner can point at a decision their team made on Monday and say what it did in the water on Friday.
Finished or not, floating or not. A team whose boat doesn't get its run has been robbed of the whole week.
Loudly, and led by the guide the first time it happens. This sets whether failure is safe here for the rest of the year.
Learners can say why the boats and the Spark afternoons were the same week and not two unrelated things.
Every time on this page assumes a thirty-minute journey each way. Adjust the whole day to your actual travel time as soon as transport is confirmed, and give yourself more margin than you think at both ends - the pack-out from a pool with a studio full of wet learners always takes longer than planned.
Different arrival today. Every learner gets checked off a list at the door: swimsuit on under clothes, towel, full change of clothes, water bottle, shoes that can get wet.
Have spares. Someone will forget a towel, and a kid sitting out because of a towel is an avoidable tragedy.
Talking points, not a script. Hit these in your own words - the studio can tell the difference, and the ones that land are the ones you actually mean.
The safety brief first (8 min). Not a formality - the first thing said today, before any excitement is built.
The format (8 min):
The awards (3 min): Read out the categories so teams know what's actually being celebrated. Only one of them is about floating:
The close (1 min):
"Four days ago this was flat cardboard and a drawing. Let's go find out."
Real engineering with real consequences, watched by everyone. The thing that makes this land isn't which boat wins - it's that a team's four days of decisions become visible in about eleven seconds. Run it as an event, with ceremony, and make the cheering non-optional.
Run of play:
The moment to watch for: a team whose boat fails badly. What they do in the next ten seconds is the most important thing that happens all day. If a teammate blames the rider, step in immediately and quietly. If they laugh together, let it run and name it later at Callouts.
Earned, unstructured, guide-supervised. Buddy groups still count each other in and out.
Same protocols as studio lunch, outdoors. Guides eat with the studio. Shade and water pushed hard - nobody notices dehydration at a pool.
12:45–1:15 - second free swim.
1:15–1:30 - the awards, poolside, wet, in the moment. Do these here rather than back at the studio - the ceremony only works while everyone's still soaked.
Tired, sunburnt, and still full of it. Don't over-run this - but don't skip it either, because a day like today evaporates by Monday if nobody names what happened.
Four questions, round the circle:
Then close the week properly, and connect the two halves of it out loud:
"This week you did two things that look completely different. You built a boat with people you didn't pick, and you sat on the floor with a five-year-old who wanted you to read the same page four times. They're the same skill. Both of them are about being useful to someone else on their terms instead of yours. That's what this whole week was."
Then ICEE #3 (10 min) - if the day has any left in it:
Adventure Days don't carry the Friday ritual stack, and this one is a full day out ending in a tired, sunburnt studio. So read the room: if there is genuinely nothing left, run it first thing Monday instead and say so out loud. What must not happen is it quietly disappearing - Week 3 is the hardest week of the quest and the trend chart comes out in Week 5, where a missing point is a hole exactly where the interesting part was.
Share Chair is skipped this week, and say so rather than letting it quietly vanish: "No Share Chair today - we were at a pool. Anything you've written this week gets read next Friday." The 360 is covered by the debrief circle you've just run.
The build zone comes down for good today. Cardboard scraps out, tape stubs binned, tools away, floor swept, space returned to being a studio.
Progress photos from all four sessions go up on the wall alongside the fleet photo. The boats are gone; the record of them shouldn't be.
The best Callouts of the quest so far are available today. Push past "it was fun" toward the specific: who held it together when their boat folded, who cheered loudest for a rival team, who carried someone else's boat, who took the Exploration prediction seriously on Thursday and was right to.
One question: "What's the thing about today you'll still remember in June?" Quick round, no elaboration.
Send-off by name. Families will ask - let the learners tell it. Stand back and let them do the talking at the door.
Talking points for this week's email. Drop these into an AI assistant along with two or three live notes from your actual week - a name, a moment, something that surprised you - and it'll give you a draft in your own voice. The specifics are what make it land; the structure below is just the scaffolding.
The draft underneath is an example of the shape and the tone, not a template to send as-is. A parent who gets the same email as every other parent can tell.
Subject: They floated (mostly)
Hi families,
We took four cardboard boats to a pool today and put a learner in each one. Some floated. Some did not. The ones that did not got, by a considerable margin, the loudest cheers of the day - which was deliberate, and which I'd been building toward all week.
Each boat got a float run with the studio counting to thirty out loud, and before each run the team read out the prediction our Exploration learners had written on a sticky note the day before. Awards went to the longest float, the best boat name, the best crew as voted by the other teams, and - genuinely the most contested category - most spectacular sinking.
On the way back we connected the two halves of the week. Every learner spent one afternoon with a Spark learner during reading time, and four afternoons building a boat with a team they didn't choose. Those look like different activities. They're the same skill: being useful to someone else on their terms rather than yours.
Your learner will be tired and probably slightly sunburnt despite our best efforts. Ask them what their boat was called.
Thank you to everyone who sent cardboard, signed forms on time, and came along to help. None of this works without you.
- [your name]