Student progress tracking
Student progress tracking software fed by the work itself
Every progress tracker has the same failure: somebody has to feed it. This one fills itself from the tutoring sessions that were already happening.
01 Why trackers go stale
The data entry is the product
Almost every progress tracking system in a school is technically excellent and practically empty by November. Not because the software is bad, but because the input is a human act that competes with teaching for the same finite hour.
The moment tracking requires a separate assessment window, a spreadsheet, or a teacher typing a rubric score per student per skill, the system degrades to whatever gets entered in the week before a data meeting. Which is a snapshot of that week, not a record of a year.
Fix the input and the rest of the problem disappears.
Conventional tracker
- Input: a teacher entering scores
- Cadence: whenever there is time
- Granularity: per assessment
- Evidence: a number, sometimes a comment
- Cost: an assessment window plus admin
Fed by the session
- Input: the work the student already did
- Cadence: every session
- Granularity: per skill, per session
- Evidence: the student's own reasoning, quoted
- Cost: none, it is a by-product
02 What a record looks like
One student, one skill, eight sessions
Every point on the series links to the session it came from and to the sentence the student wrote. That is what turns a growth claim from something to be trusted into something to be checked.
It is also what makes it usable in an MTSS meeting, where the question is never "did they improve" but "show me".
Choosing the base of a percentage
Says the 20s cancel out.
Applies the second percentage to the original number.
Asks which number the percentage is of, then guesses.
Writes the base under each step but slips on the reverse case.
States the base before calculating, unprompted.
03 Getting it out
A record you cannot export is a record you do not own
CSV, every tier
Per student, per skill, per session, with the evidence line. Open it in whatever your reporting already runs on.
Scheduled reports
School tier and above. A recurring export to a named address, so the data meeting has the data before the meeting.
SIS and LMS export
District tier. Mapped to your standards so the numbers arrive in the shape your systems expect.
On the way out
If you leave, you export first and then we delete. Ownership is not conditional on staying a customer.
Retention and deletion detail is in the privacy policy; the tier breakdown is on pricing.
04 For the person who signs off
Two things a curriculum director asks first
Evidence you can present
Per-skill mastery per student, exportable, with the student's own reasoning attached. It survives a board slide and an MTSS meeting because the wording came from the student, not from a summary.
A privacy posture built for minors
Student work is not used to train models. No advertising, no data resale, deletable on request. Designed around FERPA and COPPA obligations, and our security page states plainly which formal attestations we do and do not hold.
Rollout, procurement and the full sign-off checklist are on the pricing page, alongside the cost-per-student estimator.
05 Pricing
Priced per program, not per seat
Annual billing is about 17% lower. There is no free tier, and the privacy posture is identical on every plan.
Classroom
$89/mo
One teacher, up to 60 students, CSV mastery export.
School
$349/mo
Up to 10 educators and 600 students, roles, SSO, scheduled reports.
District
$1,290/mo
Up to 75 educators and 5,000 students, standards mapping, SIS export, PO billing.
More AI tools for teachers
Generate the first data point
Run a piece of student work through the demo. What comes back is one session of the series above.
Student work is never used to train models. No card required to try the demo.