All docs
Evaluation policyRe-score past answersdashboard

Re-score past answers

Judge stored answers again with a published policy version; earlier verdicts are kept.

When you publish a better policy, the answers already in were scored with the old one. A re-score judges stored answers again with a published version. The earlier verdicts are kept: each answer gains a new verdict in its history, and the newest is the one lists and averages use.

When to use it. You added a business rule and want to know how many of last week's answers broke it. You fixed a code list and want last month's "Right version of the source" failures re-checked. You put back an earlier version and want the last day scored with it again.

Start a re-score

Re-score answersRe-score answers

There are three ways in:

  • Re-score recent answers… on the card that appears right after you publish.
  • Evaluation policy › Versions & audit › Re-score answers…
  • In Live events, tick answers and click Re-score… (only those answers).

Then:

  1. Choose the Policy version. Only published versions can re-score; a draft can't.
  2. Choose Answers from (The last 24 hours, The last 7 days, The last 30 days or The last 90 days) and an Environment (or All environments). From Live events, the selected answers are used instead.
  3. Add a Note (optional): why you are re-scoring, kept in the audit log.
  4. Click Start re-score.
  5. Watch the Re-score table: Started, Version, Answers, Progress, State (Queued, Running, and then done, Cancelled or Failed). Cancel stops a running job.

Starting a re-score needs the Policy admin role.

The limits, and why

  • At most 1,000 answers per job, one job at a time per project. Re-scoring runs the full scoring again, so a job has a size you can wait for. Choose a shorter range or one environment if you have more.
  • Re-scores run behind live scoring, so your live answers are never delayed by one.
  • An answer is never scored with less than it had. If the documents or rows an answer was scored with are no longer stored, it is listed under Why it was not re-scored, with the reason, and keeps its verdict.
  • Sampling doesn't apply. Every answer you choose is re-scored, even one outside its rule's sample.

What you'll see

Open a re-scored answer and its History tab: the On arrival verdict and a new Re-score row with the job and version. The new one is Shown now; the old one is kept in history. Averages for that period change to use the new verdicts. The audit log records who started the job and the note.

Common mistakes

You seeWhyFix
"Publish a version first: only a published version re-scores."A draft was chosen, or nothing is publishedPublish first
"Choose a shorter range or one environment."More than 1,000 answers matchNarrow the range or the environment
Re-score answers… is greyed outYour role is not Policy adminAsk a Policy admin
A new job is refused while one runsOne job at a time per projectWait for it to finish, or Cancel it
Averages for last week changedA re-score replaced the shown verdictsCompare the verdicts in each answer's History