Evidence · for school leaders

What we measure, and what we don’t.

Most PD evidence fails in one of two directions: it measures the workshop instead of the classroom, or it measures the classroom with instruments that cannot reach it and dresses the result up as proof. This page is the inventory — every kind of evidence this product produces, labeled honestly, with the claims we will not make listed alongside.

Every number carries a type

Internally, every metric and report element is tagged with what kind of evidence it is. Those labels are visible on the leader’s dashboard and in the report, next to the sections they describe, because a number whose provenance is invisible invites the reader to assume the strongest possible reading.

Evidence typeWhat it meansExampleStatus
Product telemetryWhat happened in the application — check-ins completed, teachers active.A check-in was completedIn use
Teacher-reportedWhat teachers say they tried or experienced. Self-report, not observation.“I used wait time today”In use
Shared by teachersContent a teacher explicitly chose to share with the school.A shared classroom winIn use
Leader-enteredObservation or artifact entered by a school leader.A walkthrough countLater release
Verified outcomeExternally validated result. Not currently offered.—Not offered

The bottom row is the important one. Nobody in this category of product can currently give you externally validated outcomes from a 30-day cycle, and we would rather say so on a public page than let the word “proof” do quiet work in a sales conversation.

What gets captured, and when

Day 1 — the baseline. One goal in the teacher’s own words, how often they report having used the practice in the prior five teaching days, a confidence rating on a stable five-point scale, and a sentence of classroom context. Only what will actually be used later. Without this, nothing that follows is movement.

Days 2–29 — the record. Whether each check-in happened, what the teacher reported trying, whether they adapted the practice or set it down, whether they asked for help, an optional weekly confidence rating, and anything they chose to share.

Day 30 — the close. The same behavior-frequency and confidence questions asked at baseline, so the comparison is like-for-like; whether the practice was refined, retained, replaced, or abandoned; whether the coaching was useful; whether the teacher would continue; and an optional comment.

The report map — which source feeds which section

Participation

Product telemetry

Invited, activated, and active teachers, week by week — what happened in the application, counted, with its denominator shown.

Practices tried

Teacher-reported

What the cohort reports trying and adapting — each theme shown with how many teachers' entries support it (never fewer than three, within a cohort of at least five). Self-report, labeled as such.

Friction & support

Teacher-reported

Where teachers report friction or ask for support — the input for your next staff-meeting agenda, not a compliance list.

Next cycle

Interpretation

A recommendation: what to sustain, adjust, or support next — drawn from the labeled evidence above it and marked as interpretation.

Interpretive sections — next-cycle recommendations, theme summaries — are AI-assisted drafts reviewed against the rules on this page, and they are labeled Interpretation wherever they appear: judgment drawn from the labeled evidence above them, never a measurement of their own.

How the report is allowed to talk

The reporting language is constrained, and the constraint is enforced in the software rather than left to whoever writes the summary.

We sayWe never say
“Teachers reported trying…”“Instruction improved by…”
“Participation remained…”“The initiative caused…”
“The most common implementation pattern was…”“The data proves…”
“Confidence increased from X to Y among N respondents.”“Teachers resisted…”
“This report does not include classroom observation or student outcomes.”“Practice changed” with no evidence source attached

The right-hand column is not a list of things we find distasteful. Each one is a claim this data cannot support: an inference about a classroom nobody observed, a causal claim with no counterfactual, a judgment of teachers dressed as a finding. And low engagement is never reported as resistance — it may as easily be workload, absence, a poor fit, or a teacher quietly deciding the goal was wrong.

Where a number is withheld

  • Below five contributing teachers, no themes and no confidence trend. A pattern drawn from so few is those people, identifiable to anyone who knows the staff. Within a qualifying cohort, each theme additionally needs at least three teachers’ entries behind it, and every draft is checked for re-identification before a leader sees it.
  • No direct quotation unless a teacher explicitly chose to share those words.
  • A count that would re-identify someone is withheld entirely — never rounded or estimated. The report says a number is missing rather than showing a smaller one, and a small-group number that moves by a single teacher from one day to the next is held back that day.

Each of these makes the report less impressive and more trustworthy, which is the trade we would make every time. A blank section says the floor held.

The honest limits, stated plainly

  • Self-report is not observation. A teacher telling you she used wait time is evidence that she believes she did, gathered in the moment rather than recalled at year-end. It is the same instrument a coach uses in a sit-down. It is not a rubric score and should never be presented as one.
  • Confidence is direction, not attainment. A rating that moves from 2 to 4 says something changed in how a teacher reads her own practice. It does not convert into a skill level.
  • Thirty days is thirty days. One cycle is one month of implementation learning. A trend needs a second month; a defensible picture needs a third.
  • Student outcomes are out of scope — not because they don’t matter, but because a 30-day report claiming them would be lying, and the claim would be untraceable to anything in the data.

The report shows product activity and what teachers report trying, adapting, and needing. It does not verify classroom practice or student outcomes. Every report section names its evidence source.

What this is good for

Within those limits the evidence answers the question a leadership team actually asks, at the level it can honestly be answered in a month: teachers engaged with follow-up at this rate, here is what they reported working on, here is how their confidence on their own goals moved, and here is what they chose to share about it. That is a real answer about the weeks after the workshop, which is more than an attendance sheet has ever offered.

Methodology as described: v2 · September 2026. The boundary itself, in one sentence: The platform records participation and synthesizes teacher-reported implementation patterns. It does not observe classrooms, score teachers, or claim student-outcome impact.

Two questions people ask here

What evidence does the report contain?

Product activity (what happened in the application) and teacher-reported implementation (what teachers say they tried, adapted, and need). Every section names its evidence source. It does not claim classroom practice or student outcomes changed.

Is this teacher evaluation?

No. Nothing here scores a teacher, observes a classroom, or feeds an evaluation system. Leaders see participation under the privacy mode the school chose, and anonymous group themes — never anything a teacher wrote, unless they choose to share it. Themes are summarized only once five teachers have contributed, with at least three behind each one.

Judge the evidence yourself.

The interactive sample includes the whole Day-30 report, populated, every section labeled — or read it as a PDF.