Back to Report Blocks

ScoreChampionVersionTimeline

Optimizer
Report block

Shows score champion-version changes during a requested time window, with per-score timelines, optimizer cost, SME context, diffs, and feedback/regression evaluation metrics.

What It Answers

  • Which scores changed champion versions during this window?
  • Did champion feedback and regression metrics improve?
  • What changed between the prior champion and the latest champion?

Use When

  • Reviewing optimizer impact after score improvement work.
  • Explaining production champion changes across a whole scorecard.
  • Auditing manually promoted score versions.

Avoid When

  • You need every optimizer candidate; use procedure optimizer views.
  • You want scores with no champion change; unchanged scores are hidden unless explicitly requested.
  • The score predates championHistory metadata and has no recorded transitions.

Run From The CLI

Direct report commands are the simplest path for one-off usage. Saved report configurations use `plexus report config create` and `plexus report run`.

plexus feedback report score-champion-version-timeline \
  --scorecard "Customer Service QA" \
  --days 30

# Limit to one score.
plexus feedback report score-champion-version-timeline \
  --scorecard "Customer Service QA" \
  --score "Medication Review: Dosage" \
  --days 30

# Use an explicit date range instead of a trailing day window.
plexus feedback report score-champion-version-timeline \
  --scorecard "Customer Service QA" \
  --start-date 2026-03-01 \
  --end-date 2026-03-31

# Add --include-unchanged to include initial champion entries with no previous champion.
return plexus.report.score_champion_version_timeline{
  scorecard = "Customer Service QA",
  days = 30,
  sync = true
}
plexus report config create --name "ScoreChampionVersionTimeline Example" --file score-champion-version-timeline.md
plexus report run --config "ScoreChampionVersionTimeline Example"

Minimal Configuration

# Scorecard-wide trailing window.
class: ScoreChampionVersionTimeline
scorecard: "Customer Service QA"
days: 30
include_unchanged: false

# Or limit to one score.
class: ScoreChampionVersionTimeline
scorecard: "Customer Service QA"
score: "Medication Review: Dosage"
days: 30
include_unchanged: false

# Or use an explicit date range.
class: ScoreChampionVersionTimeline
scorecard: "Customer Service QA"
start_date: "2026-03-01"
end_date: "2026-03-31"
include_unchanged: false

Live Rendered Example

Rendered with the same dashboard component used by generated reports.

ScoreChampionVersionTimeline Example

Customer Service QA

March 11, 2026 to March 31, 2026

Scores With Changes
1
Champion Changes
2
Optimization Cost
$2.42
Procedures
1
Evaluations
4
Score Results
600
Medication Review: Dosage
score-dosage
2 champion changes
Procedures
1
Evaluations
4
Score Results
600
Optimization Cost
$2.42
Feedback AC1
Regression AC1
Feedback Accuracy
Regression Accuracy
Champion Entered
Version
Feedback AC1
Regression AC1
Previous Champion
3/12/2026, 2:20:00 PM
version-101
0.710
0.680
version-100
3/26/2026, 9:10:00 AM
version-102
0.780
0.720
version-101
Champion Diff
version-100toversion-102
SME Information
procedur
Status: COMPLETEDUpdated: 3/26/2026, 10:30:00 AMGenerated: 3/26/2026, 10:35:00 AM
Agenda

Review dosage exception wording with SME.

Worksheet

Confirm whether ambiguous dosage mentions should be excluded.

How To Interpret It

  • By default, initial champion entries with no previous champion are omitted because they are not changes; set include_unchanged to true to show them.
  • Only versions with championHistory enteredAt values inside the requested window are included.
  • The displayed date range is narrowed to one day before the earliest champion activity when the request window is much broader than the activity.
  • Missing feedback or regression evaluations are shown as unavailable instead of suppressing the champion point.
  • Procedure, evaluation, score-result, and procedure cost totals summarize optimizer work during the window.
  • SME agenda and worksheet content comes from the most recent optimizer procedure for each score.
  • Diffs compare the previous champion before the first in-window transition to the latest in-window champion.