Skills Quality assurance
Scorecard migration
Scorecards change. Products change, policies change, regulators change, and the first version was wrong. The failure mode is treating a rubric change like a wording tweak while continuing to plot one trend line — agents, leadership, and auditors then draw conclusions from data that crossed an unmarked cliff.
npx rulebase-skills install cx-scorecard-migrationWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “we're updating the scorecard”
- “how do we migrate to a new rubric”
- “can we compare scores before and after the change”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Step 1: Version before you edit
Every scorecard needs: Version id (semantic, Effective date, Owner, Changelog.
Step 2: Classify the change
If two or more rows in the "No" column apply, this is a major migration, not a tweak.
Step 3: Build old-to-new criterion mapping
For every retired or changed criterion, document.
Step 4: Run a parallel / dual-score window
Before cutover, score a sample with both versions: Sample size large enough to see per-criterion shift, Duration long enough to catch channel-specific effects.
Step 5: Define the cutover
Pick one: Hard cutover, Gradual grader cutover, Channel-by-channel.
Step 6: Communicate the break point
Stakeholders will compare across the line unless you stop them. Provide: What remains comparable, What is not comparable.
Step 7: Historical data policy
Three legitimate positions — pick explicitly: Frozen history, Re-score sample, Mapped aggregate.
Step 8: Re-validate after migration
Four to eight weeks post-cutover: Re-measure grader agreement on v2 gold set, Check score distribution, Re-check correlation with outcome metrics named at scorecard design, Compare auto-fail actioning.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
