# QA scoring redesign: keep both scores | SourceX

Canonical: https://refer.sourcex.si/guides/moment-qa-scoring-redesign-cx-analytics-advisors
Last updated: 2026-11-05

Sometimes, and a QA scoring redesign is when it gets decided. Many contact centers keep a first evaluator score, an agent dispute and an adjudicated or calibrated decision, but a new scorecard often carries forward only final scores, mapped to new criteria. CX analytics advisors can ask the company's authorized owner one metadata question: are initial scores and adjudicated decisions both retained? If yes, and the company wants to explore licensing, introduce its decision-maker to SourceX.

## Are initial scores and adjudicated decisions both retained?

Ask that question directly, because the answer is rarely obvious from a dashboard. Reporting usually shows the current score. Whether the original evaluation, the dispute and the adjudication are stored as separate records depends on the platform's configuration and on choices made years ago.

Most QA platforms support the pieces. Genesys Cloud, for example, lets agents dispute completed evaluation scores, and its calibration feature measures each evaluator against a scoring index set by an expert evaluator. That produces exactly the evidence a redesign can flatten: the first judgment, the challenge, and the settled decision with the person who settled it.

Reviewer disagreement evidence is what makes an archive like this interesting for AI training and evaluation. A scored interaction is already a human judgment; a scored interaction with a recorded disagreement and a reasoned resolution shows how experts converge. The [QA scorecard data type page](/data-types/call-center-quality-assurance-scorecard) covers scorecards in general. This page is about the redesign moment and what to ask during it.

### Score lineage for one evaluated call

Illustrative. A 340-person outsourced support provider is redesigning its scorecard from 20 weighted criteria to 12. One evaluated call carries this lineage today:

| Record | Value | Who created it | What a redesign often does |
|---|---|---|---|
| Form version | Scorecard v3, 20 criteria | QA lead | Retires it without archiving the definition |
| Initial evaluation | 72 out of 100 | QA evaluator | Overwritten by the final score |
| Dispute | Two criteria challenged: verification and resolution | Agent | Kept as a free-text comment, if at all |
| Adjudicated decision | 84 out of 100, with a note | Calibrator | Kept as the only score |
| Calibration result | Evaluator deviation from the scoring index | Quality admin | Dropped from reporting |
| Link to interaction | Recording or transcript ID | Platform | Broken if recordings expire first |

The 12-point gap between 72 and 84 is the useful part. Without the form version, neither score can be interpreted; without the initial evaluation, the disagreement disappears. If the owner can say which of these rows exist and for how many years, you have a sound metadata-level description.

### Why reviewer disagreement evidence is easy to overlook

A redesign is run by the quality team, and its success measures are forward-looking: fewer criteria, faster evaluations, tighter calibration on the new form. Historic scores matter to it only for trend lines, and a trend line needs one number per call. So the migration plan maps old final scores onto the new scale and treats the rest as clutter. Disputes look like noise, calibration sessions look like training material, and old form definitions look obsolete. Each of those decisions is reasonable for reporting, and together they erase the only record of how experts disagreed and resolved it.

The advisor's advantage is timing. You usually see the migration plan before it runs, which is the last point at which the company can decide to keep a read-only copy of the full lineage.

### Four metadata questions after the opener

1. **Since when are evaluations, disputes and adjudications stored as separate records?** The year the dispute workflow was switched on is often the real start date.
2. **How many evaluations a year, and what share were disputed or calibrated?** A rough range is enough.
3. **Are old form versions archived with their criteria and weights?** Without them the historic scores cannot be read.
4. **How long are the linked recordings or transcripts kept?** In Genesys Cloud, for example, recording policies can retain indefinitely, retain for a set period or delete automatically, and they apply only to interactions after the policy is published. A score whose call has expired loses much of its context.

Then one ownership check: for outsourced programs, does the provider or its client own the evaluations? The answer decides whom you would introduce, if anyone.

## Does the company qualify, and who can authorize a licensing discussion?

Check fit first. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

| Question | Typical answer in a QA redesign | Unknown until SourceX reviews |
|---|---|---|
| Which records exist? | Evaluations, disputes, calibrations, linked interactions | Whether buyers need that record type |
| Who owns them? | The company, or its client for outsourced programs | The rights review result |
| Who can authorize? | CEO, often the owner | Dataset scope and de-identification needs |
| How much and how long? | Rough evaluation count and years covered | The company's offer and any reward |

Customer conversations contain personal information, which is why partners never touch them. Stay with what, how much, how long, which system and who owns it. The [CX consultant partner page](/for/cx-consultant-referral-program) and the [partner hub](/for) cover the wider practice.

### Reward disclosure and owner permission

Sign the Channel Partner Agreement before submitting an introduction, and tell the owner up front that you may receive a referral reward that SourceX pays separately, so it never reduces the company's payout. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application; one partner per company. The default reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap. Illustrative reference only: if the company were paid $400,000 for a qualifying completed handoff, the default reward would be $70,000. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) explains.

A short introduction is enough: the redesign date, the years of lineage the owner described, one sentence on SourceX licensing approved operating records directly from companies, and the disclosure. Send it only to the decision-maker who agreed to it.

## Go deeper on QA scoring redesigns

- [QA scoring redesign introduction email](/resources/qa-scoring-redesign-introduction-email): a template for introducing the decision-maker before old evaluations are flattened, with the disclosure included.
- [QA scoring redesign meeting agenda](/resources/qa-scoring-redesign-meeting-agenda): a timed agenda for the first owner conversation about score history.
- [QA scoring redesign archive context checklist](/resources/qa-scoring-redesign-archive-context-checklist): a checklist of form versions, retention settings and ownership facts to confirm before the new scorecard goes live.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the owner confirmed that both initial and adjudicated scores survive the redesign and wants to explore licensing, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://help.mypurecloud.com/?p=380404
- https://help.mypurecloud.com/releasenote/january-31-2024
- https://help.mypurecloud.com/?p=17591
