№ 07  ·  Brief Template Peninsula School District

Continuation Brief

For a bet that's not done yet — one more cycle to know.

Template· One of three: Adoption · Decommission · Continuation· Drafted by The Logbook

A Continuation Brief is what a team publishes when a six-week bet needs another cycle to know. The original hypothesis is still alive but the evidence isn't yet conclusive. The team is sharpening the question and going again.

§ I  ·  Shared backbone, evolving questionSix fields, one of three patterns

The Continuation Brief follows the same six-field backbone as Adoption and Decommission. What's distinctive: the Decision is "continue" + a revised hypothesis. The "What others should know" field becomes "What we're testing next," and that revised hypothesis carries forward into the next cycle's Bet Brief.

  1. Header strip — Continuation Brief · ID · cycle · team
  2. Hypothesis — the original bet from the cycle's Bet Brief
  3. What we did — moves, dates, surprises
  4. What we learned — including what is still unknown and why
  5. Decision — "Continue into Cycle [N+1]" + the revised hypothesis
  6. What we're testing next — what changes about the bet in the next cycle

§ II  ·  A worked exampleWhat a published Continuation Brief looks like

Continuation Brief Logbook 0014 · Cycle 01 · 14 Oct 2026

AI-assisted Tier 2 reading intervention notes for K–3 teachers

Team · Elementary Principal Team

Hypothesis

If we give K–3 teachers an AI tool that drafts intervention notes from short audio recordings of reading sessions, we expect teachers to recover 60+ minutes per week and to have richer notes for MTSS data conversations. Success means measurable time recovery, no reduction in note quality (judged by reading specialists), and willing weekly use by at least eight of the twelve teachers we pilot with.

What we did

Twelve teachers across three elementary buildings piloted the tool starting Week 02. The tool records a five-minute reading session, transcribes it, and drafts an intervention note in the format our MTSS coordinator expects. Teachers reviewed and edited the draft before saving. By Week 05 we had 84 sessions logged.

Surprise: teachers used the tool in unexpected ways — several used it as a self-reflection tool ("I want to hear how I did") rather than as a notes-drafting tool. That changed our measurement.

What we learned

  • Time recovered per teacher was 35 minutes per week — below target. The bottleneck wasn't note-drafting; it was the data entry into our MTSS system, which the tool doesn't yet touch.
  • Reading-specialist judgments of note quality were positive — the drafts captured nuance teachers would have skipped under time pressure.
  • Adoption was strong: 10 of 12 teachers used the tool weekly by Week 04. Two stopped due to mic quality issues in older classrooms.
  • The "self-reflection" use case was unexpected and may be the more important value — teachers said it changed how they listened during sessions.
Decision
Continue into Cycle 02 — revised hypothesis

The original time-recovery target is the wrong measurement. We are going again with a sharpened bet focused on instructional quality and teacher growth, not just time saved. We will also expand to mic-quality remediation for the two stopped teachers.

Revised hypothesis for Cycle 02 If K–3 teachers use the AI-assisted intervention tool weekly, we expect teacher-reported instructional growth (measured by short pre/post self-assessment) to increase, and reading-specialist judgments of teacher note quality to remain at or above the Cycle 01 baseline. Success means a measurable shift in teacher self-assessment, sustained note quality, and continued voluntary use by at least 10 of 12 teachers — now expanded to 18.

What we're testing next

  • New primary metric — teacher-reported instructional growth, not time saved.
  • Expand pilot from 12 to 18 teachers, adding two buildings.
  • Address mic-quality issues in older classrooms before Cycle 02 launch.
  • Begin scoping the MTSS data-entry integration as a separate Cycle 03 bet (different team).

§ III  ·  The discipline of continuing wellWhat makes this brief useful

Sharpen the question. A Continuation Brief is not a "we need more time" admission. It is a more precise question than the one the team started with. State the new hypothesis explicitly.
Be honest about what you don't know. The "What we learned" field for a Continuation should be the most uncertain of the three brief types. List what is still unknown and what evidence would resolve it.
Don't continue forever. A bet that has run two full cycles without sharpening is probably a Decommission in disguise. The Logbook's accountability layer flags these patterns to the cabinet.
Carry the revised hypothesis forward. The new hypothesis becomes the next cycle's Bet Brief, verbatim. That is how the chain stays coherent.

§ IV  ·  How the Logbook helpsFrom open question to sharpened bet

The Logbook drafts the Continuation Brief from the team's Google Chat Space and then helps the team sharpen the revised hypothesis. It can pull patterns from how other teams have refined bets cycle over cycle, and it can flag when a "continuation" is starting to look like avoidance.

A note on cycles in series The corpus over time becomes a sequence: an early Bet Brief, a mid-cycle check-in, a Continuation Brief, a revised Bet Brief, and eventually an Adoption or Decommission. That sequence is one of the most useful things districts will be able to fork from us — the actual trajectory of figuring something out, not just the answer.