AdaptEd for Schools

Teachers keep their own lessons, sequence, and materials. The campus gains standards-level evidence across every classroom that connects, drafted reteaching for the students below mastery, and a record that can be printed and defended. No adoption cycle, no IT project, no district sync.

What it does

A teacher authors a lesson — or uploads one they already teach — and AdaptEd builds the checkpoints and exit assessment around it. As students work, every first-try, unaided answer lands in a per-standard, per-sub-skill mastery record. When a student struggles, the lesson can reteach the slide they missed with a simpler version the teacher has reviewed; when a group falls below mastery on a standard, one click drafts a targeted reteach lesson from the material those students worked. Missed content returns on a spaced schedule until it holds. Teachers approve every lesson before students see it.

The record a campus can stand behind

• Per-standard, per-sub-skill mastery with a written admissibility rule: only unaided, first-try, summative work counts toward a claim.
• A 95% confidence range and an evidence gate on every score. The top band requires at least five admissible attempts and a lower bound clearing 70 — a thin sample is reported as thin, not as a verdict.
• A printable evidence record for any student on any standard: which attempts counted, which were excluded and under which rule, every band change with its date and cause, and the reteaching delivered in between.
• Claims that can be revoked. A failed spaced review folds back into the evidence and moves the band down. The record shows the movement.
• An accelerated-instruction documentation aid that collects, per student and standard, what reteaching AdaptEd delivered and whether the standard moved — a time-saver for the district's own HB 1416 documentation, not a substitute for it.

The full method — including what AdaptEd deliberately does not claim: no national norms, no percentiles, no predicted state-test scores, and an evidence base that is currently a logic model (ESSA Tier 4) — is published at How We Measure Mastery.

The trust model

• Campus leadership access is teacher-authorized: you issue a campus code, each teacher connects in about thirty seconds, and any teacher can disconnect at any time.
• A campus leader cannot edit a teacher's lessons, grades, or classes, and cannot open an individual student's answers — that stays with the teacher of record.
• The one write a leader can make into student data is a campus benchmark import — attributed, deletable, and it can fill a blank student ID on a roster but never overwrite one.
• Grades flow to Google Classroom, which remains the gradebook of record. AdaptEd does not replace the SIS, the LMS, or the district assessment platform.
• AI is disclosed and controllable: teachers review AI-drafted lessons before publishing, AI-drafted reteach content sits in a review queue, and the student AI tutor can be switched off per lesson.

Privacy posture, sub-processors, retention, legal hold, and the audit trails — including what we do not yet have (no SOC 2, no third-party penetration test) — are stated plainly at the vendor compliance summary.

Assessment posture in Texas

An AdaptEd pod is a classroom examination a teacher designs or adopts and administers — the category of assessment that Texas' benchmark limits (TEC 39.0263, effective 2027-28) expressly do not restrict. AdaptEd is not a benchmark product, does not offer district-required practice testing, and does not predict STAAR scores. Campus reporting is a roll-up of each teacher's own classroom results, not a campus-administered common assessment.

Pricing

• Every teacher can start on the free tier today — no card, no expiry — so a campus decision can follow classroom evidence rather than precede it.
• The Campus Command Center is free and is not behind a paid tier. The Campus plan buys teacher capacity, not leader features.
• At a typical single-campus purchase, the total stays far under district competitive-procurement thresholds and clears as a campus purchase order.

What a rollout looks like

• Week one: teachers create free accounts and run their first pods. No installation — it runs in the browser on district devices, and rosters can come from Google Classroom.
• Week two: you issue the campus code; connected classrooms appear in the Command Center with band distributions and standards to watch.
• Any time: import a campus benchmark and see it matched against every connected roster at once.