Preptics
← All features
Available now

Score band and ranking

Digital SAT score band and skill breakdown

A score range you can trust, not a number we made up.

A projected Reading and Writing score, a projected Math score and a total, each reported as a range with a stated confidence — ±60 on the total after one mock, ±45 after two, ±40 after three or more, and ±30 / ±25 / ±20 on each section. Underneath: where your points actually went skill by skill, where your time went question by question, which second module you were routed into, and what your wrong answers have in common. And once you have sat the real thing you can tell us what you scored, which is how we find out whether our ranges were any good.

The first chapter of a report card, “How did I do?”: the projected total as a range of about 120 points marked low confidence, drawn as a shaded band on a 400 to 1600 scale with a dashed flag at the student's target and a dashed outline where the previous mock landed, above separate ranges for Reading and Writing and for Math.
A sample account, not a real student's results.
How a projected score band narrows with more mocksA horizontal score axis from 1100 to 1500. After one mock the reported range is 1230 to 1350, described as low confidence. After two it is 1245 to 1335, moderate confidence. After three or more it is 1250 to 1330, good confidence. The centre of every range is 1290.11001200130014001500estimate 1290After 1 mock±60low confidenceAfter 2 mocks±45moderateAfter 3 or more±40good
The band stops narrowing at ±40. What remains at that point is calibration error, and watching you sit a fourth mock does not reduce it.
What you get today
  • Section and total bands with a stated confidence, never a fake-precise number
  • Every attempt charted as a band rather than a point, with your target as a fixed line
  • Per-skill loss analysis — points lost, not accuracy percentage
  • An estimate of what you know in each skill, shown as a range and updated by every answer that counts
  • A written debrief of each mock — wording drafted by AI, every figure from your own results
  • Time-per-question pacing measured against the real module limits
  • A routing map showing which second module you were sent to, and why that matters
  • Report your real SAT score and see how often our band actually contained it
Coming to this
  • Bands tightened by real response data rather than conservative defaults
  • Published calibration once enough real scores have been reported

Where this actually stands

Live. Section and total bands with stated confidence, every attempt charted as a band rather than a point, per-skill loss analysis, skill estimates shown as ranges, pacing against the real module clocks, a routing map, an error profile, a written debrief, and your rank this season. The bands stay deliberately wide until there are enough real responses to narrow them honestly, and the calibration check exists so that narrowing can be earned rather than announced.

Bands, and the numbers behind them

Every score on this platform is a range. The total carries ±60 points after your first mock, ±45 after your second and ±40 after three or more; each section carries ±30, ±25 and ±20 across the same progression.

Those are wider than the real SAT's own standard error of roughly ±40 on the total — deliberately, because the real test has genuine equating behind it and we do not. Converting a raw count to the 400–1600 scale needs the College Board's equating data, which is not published. An uncalibrated practice form deserves a wider band than the real test, not a narrower one, so the single-mock case starts above that figure and tightens towards it as evidence accumulates.

Scores are reported in ten-point steps, as the real test does. A practice platform that shows you a 1247 is telling you something about itself.

The trend chart draws bands, not points

Every mock you have sat appears as a band, with your target as a fixed line you set yourself. The obvious version of this chart is a bar per attempt with the number printed under it, and that version breaks the one rule the product is built on in the largest type on the page — exactly where a student goes looking for progress.

It also does not extrapolate. A line curving towards your goal is the most persuasive thing this screen could draw and the least honest one: two mocks do not establish a gradient and three do not either. The bands are drawn where they were measured, the target sits where you put it, and the space between them is left alone. If the gap is closing, overlapping bands say so without anyone having to claim it.

The score trend chart in Analytics: each mock drawn as a vertical band rather than a point, rising from about 900 in July to about 1350 in August, with the target of 1400 as a dashed line.
A sample account, not a real student's results.

We check our own accuracy, in public

After you sit the real SAT you can tell us what you actually scored. That number is compared against the band we projected, and the result is aggregated: how often our range contained the real score, and the mean size of the error when it did not.

Almost nothing in this category does this, and the reason is obvious — it is the one measurement that can prove a scoring claim wrong. It is here because a claim of honesty that cannot be checked is just a nicer kind of marketing, and because it is the only mechanism by which the bands could ever be narrowed on evidence rather than on confidence.

Until enough scores have been reported, the page says what the current basis is rather than showing a rate computed from a handful of people.

The “How close were we?” panel in Analytics, with a field for the official SAT total and a Report it button beside the band that was projected for it.
A sample account, not a real student's results.

Where the points and the minutes went

The score is a summary. The screens underneath it are what produce a study plan.

Per-skill loss analysis sorts by points lost rather than by accuracy percentage, because a skill you got 60% right across twenty questions cost you more than one you got 40% right across five, and sorting by accuracy hides that. Pacing measures your time per question against the real module limits and shows where in each module your wrong answers cluster — the difference between running out of time, not knowing the content, and burning the clock early is three different problems with three different fixes, and the score distinguishes none of them.

There is also a routing map showing which second module you were sent to, which is the single most misread thing on any adaptive score report, and an error profile that looks for what your wrong answers have in common.

The report card chapter “Where did my time go?”: one bar per question across a module, a dashed line at that module's time budget for one question, and missed questions drawn as red striped bars.
A sample account, not a real student's results.

What you know, not only what you scored

Alongside the score, each skill carries an estimate of how well you know it: a probability, from Bayesian knowledge tracing, that moves with every answer that counts — practice tests once submitted, lessons and drills on your first attempt of the day. It is shown as a range, and the range narrows as evidence builds.

Answers given too quickly to have been read are left out of those estimates. They still count on your score, exactly as on test day — the point is only that a lucky or unlucky click should not distort what the platform believes you know.

A written debrief, with the figures left to us

Each results page opens with a short written debrief: what capped the score, which kind of mistake cost the most, what to do next. The wording is drafted by an AI model; every figure in it is filled in from your own results by our software, and a draft that states a number of its own is rejected. It is labelled as drafted by AI.

What the model receives is a summary of numbers we have already calculated, with nothing that identifies you, sent only to providers that keep nothing. When no such provider is available, or the daily limit is reached, the same debrief is written from our standard wording instead.

Common questions