Why we'd rather show you no number than a wrong one
The exam-prep category has a reputation for shipping wrong answers and false confidence. Here's the design that makes both hard for us to do quietly.
Two numbers decide whether an exam-prep product is worth trusting: whether its questions are correct, and whether it tells you the truth about how ready you are. Most of the category gets at least one of them wrong — and the reviews are merciless about it. So we built CutScore so that getting them wrong is hard to do quietly.
A question has to earn its way in
Every CutScore question is authored from exactly two kinds of source: the public exam blueprint and official vendor documentation. No real exam content. No brain-dump sites. No scraped competitor banks. That boundary isn't a policy page — it's enforced in the data model.
Before a question can reach you, it passes a fail-closed gate. It has to trace to a real blueprint task, ground every claim in a cited source, be independently authored, be technically correct against a human-authored golden standard, and carry a named human's sign-off. Miss any one and it cannot publish. The absence of a check counts as a failure. That's what "fail-closed" means: silence is not consent.
The readiness number under-claims on purpose
The most consequential thing a prep tool ever says is "you're ready — book it." Say it wrong and you watch someone fail on your word.
So we never read readiness off the middle of the estimate. We read it off the lower bound of the confidence band, and we only say "ready" when that lower bound clears the pass mark with margin and every domain is covered. On thin data we show no number at all — because a confident number you haven't earned is the one thing we won't print.
A wide band on a new account isn't a bug. It's us telling the truth about what we don't yet know.
When we're wrong, you'll see it
We will be wrong sometimes. When a question is reported and the report is valid, we correct or retire it, notify the people who saw the old version, and log the fix in a public correction log. Turning an error into a visible demonstration of reliability is the entire point.
That's the whole pitch: the audit trail is the product. Come find out what you don't know — honestly.