GO TO A SECTION

↑ ↓ to navigate · Enter to openExplore all sections →
FDEInterviews logo
arXiv preprint

Rubrics as Rewards: Reinforcement Learning Beyond Verifiable Domains

Turn task-specific criteria into RL feedback, compare explicit and implicit rubric rewards, and learn why a high aggregate score cannot replace required checks.

Breakdown by FDE Interviews · 9 min read · Updated

About the original · 2025
AUTHORS
Gunjal, Wang, Lau, Nath, He, Liu, Hendryx
FROM
Scale AI
PUBLISHED
Jul 2025 · arXiv preprint
IN THIS BREAKDOWN · 10 SECTIONS

You can read 18% of this breakdown.

01

The paper in one minute

Rubrics as Rewards trains a model using criteria tailored to each task. Instead of asking a judge for an unstructured overall rating, it supplies a rubric describing what the answer should accomplish and which mistakes matter. The resulting feedback becomes the reward in an on-policy reinforcement-learning loop.

The paper compares two aggregation methods. Explicit aggregation scores criteria separately and combines them with chosen weights. Implicit aggregation gives the rubric to a judge and asks for a combined quality score. The latter performs best overall in the reported medicine and science experiments, while explicit aggregation provides more direct control over the arithmetic.

The approach depends on the quality of both rubric and judge. Most training rubrics are generated from reference answers, which serve as a proxy for expert guidance. Making criteria visible helps inspection, but it does not make model judgments infallible or transform subjective requirements into mathematically verified facts.

The useful idea extends beyond training: write down what a good response must satisfy before scoring it. Applying that idea to an enterprise evaluation is reasonable; claiming the paper proves a production agent is safe would go beyond its experiments. The released RaR-Medicine and RaR-Science datasets document the authors' training materials.

THE IDEA, VISUALLY
A GOOD AVERAGE CAN HIDE A REQUIRED FAILURE Synthetic enterprise example using the category weights in section 4.4. CRITERION WEIGHT RESULT Task addressed 1.0 PASS Evidence included 0.7 PASS Clear wording 0.3 PASS Permitted disclosure 0.9 FAIL Weighted score: 0.690 2.0 / 2.9; threshold = 0.65 Required check: BLOCK Score cannot override this check The hard release gate is our deployment extension, not a result of RaR training. A rubric judge supplies evidence for review; it does not grant permission to disclose data.
Our synthetic enterprise example uses section 4.4's positive category weights. A separate required-condition gate prevents a good average from hiding a disclosure failure. That gate is deployment advice, not a mechanism or measured result claimed by the paper.
Research notes: the problem, approach and results
31.2

RaR-Implicit HealthBench score, Figure 2

25.5

Direct-Likert HealthBench baseline, Figure 2

2 methods

explicit and implicit aggregation, section 2.2

THE PROBLEM

Many useful answers need several judgments and cannot be checked by one exact answer or executable test.

THE IDEA

Generate task-specific rubrics from reference guidance and use a judge's rubric-based assessment as an RL reward.

THE RESULT

The reported experiments favor instance-specific rubrics, while leaving judge reliability and reward specification as core dependencies.

02

Why it matters to an FDE

A customer may reject an answer that is factually correct but incomplete, unsupported or unsuitable for the requested workflow. A single “good answer” score hides those distinctions. A rubric makes the disagreement inspectable and gives the team a more useful starting point for evaluation or adaptation.

For example, a support-response rubric could distinguish identifying the issue, citing the relevant policy and avoiding disclosure of another tenant's data. Those conditions require different evidence. A model judge may help assess explanation quality, while authorization must remain enforced by the application.

Start with LLM-as-a-judge and a reviewed set of examples before attempting RL. If the rubric cannot reliably distinguish acceptable from unacceptable answers offline, using it as a training reward will not repair that weakness. It may instead teach the policy to satisfy the judge's mistakes more consistently.

THE FULL BREAKDOWN

Understand the mechanism. Try it on a real problem.

Unlock this breakdown and 199 more papers.

Premium opens every paper in full, plus every answer, concept, course and guide on the site. One payment for six months of access.

6 months · One payment · No auto-renewal

Get Premium · ₹2,000 / $25
  • ◇1 architecture diagram
  • </>2 runnable code blocks
  • ▦3 results tables
  1. 03Key takeaways

    Six choices that determine whether a rubric gives useful supervision or a misleading score

    Free account
  2. 04How it works

    Build the rubric, choose an aggregation rule and close the training loop

    Premium
  3. 05The numbers that matter

    Recompute the main comparisons and keep the ablation populations separate

    Premium
  4. 06Try it yourself

    Test weighted scoring, required-condition gating and the published comparison arithmetic

    Premium
  5. 07Where it breaks

    Anticipate incomplete rubrics, correlated judges and rewards that hide serious failures

    Premium
  6. 08Using it on a deployment

    Start with an evaluation contract and adopt training only after the reward is trustworthy

    Premium
  7. 09Interview angles

    Explain why transparent criteria can still produce an unreliable reward

    Premium
Back to the paper library →