Paper Breakdowns  /  Let's Verify Step by Step
Paper 58~11 min read2023worked math + runnable code
Paper Breakdown

Let's verify
step by step.

Ask a model to solve a hard math problem and grade only its final answer, and you reward a lot of lucky nonsense — chains that stumble into the right number through faulty logic. This paper asked a sharper question: what if you graded every step instead? Training a reward model on step-by-step correctness, rather than final outcomes, produced a far better judge of reasoning — and a far better way to pick the right solution from many. Here's the difference between rewarding outcomes and rewarding process, made concrete.

Video breakdown
The animated walkthrough is in production.
Read the full breakdown below in the meantime ↓
01

Outcome vs process

To make a model reason better, you train a reward model to judge its solutions, then use that judge — to rerank many attempts, or to provide a training signal. The question is what the judge looks at. An outcome reward model (ORM) sees only the final answer: right or wrong. A process reward model (PRM) sees every intermediate step and judges each one.

These sound similar but differ profoundly. On a long chain-of-thought solution, the outcome is a single bit at the very end; the process is a rich, step-by-step verdict. And crucially, the final answer is a noisy label for reasoning quality — a chain can be riddled with errors that happen to cancel, landing on the correct number. Grade only the outcome and you teach the model that lucky-but-wrong reasoning is fine. This paper set out to measure how much that matters.

The one-sentence version

Reward every reasoning step, not just the final answer — the denser, per-step signal is a far better judge of whether a model actually reasoned correctly.

02

The process reward model

A PRM assigns each step of a solution a correctness score. To turn per-step scores into a solution-level judgment, the natural rule is strict: a solution is correct only if every step is correct, and its confidence is roughly the product of the per-step correctness probabilities. Contrast the two judges:

ORM(solution) = f(final answer only)
PRM(solution) = i stepi_correct  ·  confidence = i p(stepi correct)

Because the product of many sub-1 probabilities shrinks, a single doubtful step drags the whole solution's score down — exactly the behavior you want. Two things fall out for free: the PRM localizes the first mistake (the step where correctness breaks), and it rejects "right answer, wrong reasoning" chains that an ORM would happily reward. The runnable version below shows a lucky flawed chain passing the ORM but failing the PRM.

03

Why process wins

Beyond catching lucky answers, process supervision helps for reasons that compound:

What each judge can and can't see
Dense signalPRM gives feedback at every step; ORM gives one bit at the end.
Error locationPRM points at the exact failing step; ORM only says "wrong somewhere."
No lucky creditPRM rejects right answer via bad reasoning; ORM rewards it.
Better rerankingScoring candidates by step-correctness picks sounder solutions in best-of-N.

There's also an alignment argument the paper highlights: process supervision directly rewards reasoning a human would endorse at each step, rather than an outcome that might be reached by unfaithful means. Rewarding the process encourages the model to be right for the right reasons — a safer target than rewarding the answer alone, especially as tasks get harder to check.

04

Human labels at scale

To train a PRM you need step-level labels, and the paper collected them at scale: PRM800K, roughly 800,000 human annotations marking each step of model-generated MATH solutions as correct, incorrect, or neutral. That dataset — released with the paper — is what makes step-level supervision possible, and its release fueled a wave of follow-up work on reasoning verifiers.

Collecting per-step human labels is expensive, which is the honest cost of process supervision: it needs finer-grained annotation than "is the final answer right." The paper's contribution was partly to show that this cost pays off — the resulting verifier is good enough that, used to rerank many sampled solutions, it lifts accuracy well past outcome-based selection. Later work has explored generating step labels automatically to reduce the human burden.

RUN IT YOURSELF

Outcome judge vs process judge

The difference between the two reward models is a few lines. This shows an outcome model rewarding a chain purely on its final answer — so a "lucky" chain with a wrong middle step still scores 1 — while a process model checks every step, fails that chain, and even reports which step broke. The process score is the product of per-step correctness, so a sound chain (0.729) beats a flawed one (0.162), and best-of-N reranking by the process model picks the genuinely sound solution. Edit the step correctness and watch the two judges disagree.

CPython · WebAssembly
05

The results

The headline is a clean win for process supervision on hard reasoning:

FindingWhat it showed
PRM beats ORM at rerankingSelecting the best of many sampled MATH solutions, the process reward model chose correct answers far more often than the outcome one.
Large solve-rate liftBest-of-N with the PRM solved a substantially higher fraction of a challenging MATH subset than outcome-based selection.
Holds as you scale samplesThe PRM's advantage grew, not shrank, as more candidate solutions were generated to choose from.
Alignment bonusRewarding faithful step-by-step reasoning is more aligned than rewarding outcomes reachable by unfaithful means.

The reranking result is the practical punchline: sample many chains, score each with the PRM, keep the best. Because the PRM judges reasoning rather than luck, that selection lands on correct, well-reasoned solutions much more reliably than picking by a final-answer verifier.

06

What it seeded

Process reward models became a central tool of the reasoning era. The idea — verify reasoning step by step, and use that verifier to select or train — runs directly into the test-time-compute and reasoning-model wave: sampling many chains and reranking with a process verifier is a core recipe, and step-level rewards feed reinforcement-learning pipelines that push models to reason more carefully. Much subsequent work builds PRMs, often trying to generate the step labels automatically to escape the human-annotation cost.

The deeper lesson is about what you measure. It is tempting to grade the thing you ultimately care about — the answer. But when the answer is a lossy, gameable proxy for the quality you actually want (sound reasoning), a denser signal on the process itself is both more informative and better aligned. "Grade the reasoning, not just the result" turned out to be one of the more consequential ideas for making models reason.

Worth knowing

The product-of-steps scoring means a PRM naturally penalizes longer chains slightly (more steps, more chances for a low score) — a subtle pressure toward concise, correct reasoning that implementations tune with care.

Frequently asked

Quick answers

Process vs outcome supervision?

Outcome rewards only the final answer; process rewards every reasoning step. The paper showed process supervision produces a much better verifier on hard math.

What is a PRM?

A process reward model — it scores each step's correctness. A solution passes only if all steps are correct, and its confidence is roughly the product of per-step probabilities.

Why does it catch lucky answers?

An outcome model can't see a flawed intermediate step if the final answer is right; a process model checks every step and fails the chain regardless of the outcome.

What is PRM800K?

The released dataset of ~800k human step-level correctness labels on MATH solutions, used to train the process reward model.

Let's Verify Step by Step · Lightman, Kosaraju, Burda, Edwards, Baker, Lee, Leike, Schulman, Sutskever, Cobbe · 2023 · read the original paper on arXiv → · Vibe Engines · 2026
Finished this one? 0 / 101 Paper Breakdowns done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Paper Breakdowns