Back to Report Blocks

ScorecardHistory

Stakeholder
Report block

Summarizes starred score-version changes over a time window, with champion coverage, high-level change bullets, and optional evaluation gauge context.

What It Answers

  • What changed across this scorecard in the requested window?
  • Which changes were champion-related (all, some, or none)?
  • What stakeholder/SME questions should we ask next?

Use When

  • Preparing a weekly client update.
  • Reviewing optimizer-driven changes across many scores.
  • Explaining changes in stakeholder language before deep diff review.

Avoid When

  • You only need champion transitions; use ScoreChampionVersionTimeline.
  • You need item-level feedback rows; use RecentFeedback.
  • No starred versions were created in the window; unchanged scores are intentionally omitted.

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 scorecard-history \
  --scorecard "Customer Service QA" \
  --days 10

# Single-score scope on the same scorecard.
plexus feedback report scorecard-history \
  --scorecard "Customer Service QA" \
  --score "Medication Review: Dosage" \
  --days 10

# Explicit date range (instead of days).
plexus feedback report scorecard-history \
  --scorecard "Customer Service QA" \
  --start-date 2026-03-01 \
  --end-date 2026-03-31
return plexus.report.scorecard_history{
  scorecard = "Customer Service QA",
  days = 10,
  sync = true
}
plexus report config create --name "ScorecardHistory Example" --file scorecard-history.md
plexus report run --config "ScorecardHistory Example"

Minimal Configuration

# Scorecard-wide scope
class: ScorecardHistory
scorecard: "Customer Service QA"
days: 10

# Single-score scope
class: ScorecardHistory
scorecard: "Customer Service QA"
score: "Medication Review: Dosage"
days: 10

# Explicit date range
class: ScorecardHistory
scorecard: "Customer Service QA"
start_date: "2026-03-01"
end_date: "2026-03-31"

Live Rendered Example

Rendered with the same dashboard component used by generated reports.

ScorecardHistory Example

Customer Service QA

March 1, 2026 to March 31, 2026

History Summary
Some promoted
  • What changed
    • Three starred updates changed policy handling in dosage and transfer workflows.
  • Guideline / rubric changes
    • Dosage now requires explicit numeric dosage confirmation before a pass.
  • Scoring behavior changes
    • Transfer routing is stricter for unresolved medication risk scenarios.
  • Questions for SMEs / stakeholders
    • Should implied dosage ever qualify when no number is restated?
  • Rollout and evidence
    • Champion coverage is some; both recent-feedback and regression gauges are available for the latest included versions.
Scores Changed
2
Starred Versions
3
Champion Related
1
Champion Coverage
Some promoted
Medication Review: Dosage
2 starred versions | 1 champion-related
score-dosage
  • Overview
    • 2 starred versions were created in the window.
    • Champion coverage: 1 were champion-related.
  • Guidelines
    • 2 included versions changed guideline text.
  • Code / configuration
    • 1 included version changed score configuration.
  • Evaluations
    • Gauge data is available for recent feedback and regression.
  • Change notes
    • Tightened dosage confirmation criteria.
    • Clarified edge cases for inferred dosage language.
Guidelines
1
1 starred version changed rubric guidance.
Code
0
No code/config diff was detected in the included versions.
Champion
0
0 champion-related versions in this window.
Evaluations
2
Gauge data available for recent feedback and regression.
Change Notes
  • 3/21/2026, 10:00:00 AMTightened dosage confirmation criteria.

How To Interpret It

  • Only starred versions created inside the requested window are included.
  • Scores with no in-window starred versions are intentionally omitted.
  • Champion coverage is reported as all/some/none across included versions.
  • Summary bullets are stakeholder-focused; use expanded diff panels for technical details.
  • If both recent-feedback and regression evaluation data exist, gauges are shown with tabs.