QA scoring redesign archive context checklist: what to confirm at each milestone before the old scorecard is retired

Short answer

Check three milestones in order: before the redesign is announced, before cutover to the new scorecard, and before the old form or platform is switched off. At each one, confirm a short list of facts, name the person who owns each, and know what is lost if the item is skipped. The thread running through all three is whether initial scores and adjudicated decisions are both retained. Every date comes from the company's own plan, never from an assumption.

Visual briefFull-size diagram
A countdown timeline with three milestones, announcement, cutover and switch-off, where checklist items tick off one by one before the old scorecard is retired.
The checklist as a countdown. Milestones follow the company's own documented dates; none are assumed.

This checklist belongs to the QA scoring redesign guide. If you need the conversation itself, use the 30-minute meeting agenda; this page is the follow-through that keeps the answers from going stale.

How the countdown works

A countdown only helps if the clock is real. Before you fill in a single item, write down the three dates as the company has documented them, and who set each.

MilestoneWhere the date usually comes fromIf there is no date yet
AnnouncementThe redesign project charter or the QA lead's rollout noteTreat the checklist as early; work through milestone one calmly
CutoverThe configuration plan for the new formAsk who owns the go-live decision and record that name
Switch-offA platform contract end, a retirement ticket or an admin's planLeave it open; the item becomes "find out who decides"

Mark every item with one of three states: confirmed (someone with authority said so), unknown (nobody knows yet, with a name for who will find out) or at risk (the current plan loses it). Do not mark anything confirmed because a dashboard suggests it. An item marked unknown with an owner is progress; an item marked confirmed on a guess is a liability.

Keep the record yourself in a simple sheet, one row per item, and share it only with the people who answered. It describes configuration and ownership, never content: no scores, names, transcripts or recordings go into it.

Milestone one: before the redesign is announced

This is the cheapest moment to ask, because nothing has been decided about the old history yet and nobody is defending a plan.

ConfirmOwnerWhat happens if it is skipped
Which scorecard versions exist and which years each coversQA leadLater scores cannot be matched to the form that produced them
Whether first evaluations and final decisions are separate recordsAnalytics owner or platform adminThe team learns too late that only the latest score exists
Whether agent disputes are structured records or free-text commentsQA leadThe disagreement is invisible to any later review
Who owns QA records for each program, in-house or clientOwner or account directorRights questions surface only after an introduction is made

In Genesys Cloud, agents can dispute completed evaluation scores and the scorecard updates when the dispute is resolved. Whether the pre-dispute state is kept depends on the configuration, which is exactly why the second row needs a person to confirm it rather than a screenshot.

Milestone two: before cutover to the new form

Once the new scorecard is configured, the old one starts to look like clutter. The items here protect the meaning of the history, not just its existence.

ConfirmOwnerWhat happens if it is skipped
The retired form definition, criteria and weights are archivedQA leadA score of 3 on criterion 14 can no longer be interpreted
Calibration sessions and the expert scoring index are keptQuality adminEvidence of evaluator drift disappears from reporting
The reporting migration includes first scores and disputes, not only finalsAnalytics ownerThe new dashboard shows one number per call and the gap is gone
A mapping from old criteria to new criteria is written downQA leadTrends across the change cannot be read honestly

Genesys Cloud calibration measures each evaluator against a scoring index set by an expert evaluator. That comparison is one of the clearest records of how reviewers disagree, and it is easy for a reporting rebuild to leave out.

Milestone three: before the old form or platform is switched off

Switch-off is final. Items left open here are usually lost for good.

ConfirmOwnerWhat happens if it is skipped
How long recordings and transcripts are retained, under which named policyContact center or IT adminScores lose their link to the interaction they graded
Whether a new retention policy changes anything for past interactionsPlatform adminTeams assume old calls are covered when they may not be
Where the archived evaluations will live and who can access themAnalytics ownerThe history exists but nobody can find or read it
Who can authorize a licensing discussion about the archiveOwner or CEOAn interested company has no one able to say yes

The retention row needs care. Genesys Cloud recording policies can retain indefinitely, retain for a set period or delete automatically, and a newly published policy applies only to interactions after it is published. Ask what the company's own policy says. The Genesys Cloud recording export page covers that platform in more depth, and the system decommissioning guide describes what usually happens to retired instances. Items still at risk can go on the company's own risk register.

Turning the finished checklist into a decision

Illustrative. A 410-person healthcare support provider completed the checklist across its three milestones. The summary it read back to its owner looked like this:

AreaStateNote
Form versions, five yearsConfirmedDefinitions archived before cutover
First scores and final decisionsConfirmedSeparate records for in-house queues
DisputesPartialStructured since year three, comments before
Calibration resultsUnknownAdmin to confirm after the reporting rebuild
Recording retentionConfirmedNamed policy, set period
OwnershipPartialTwo client programs excluded by contract

A summary like that is a sound metadata-level description. If the owner then wants to explore licensing, three things come next.

Disclosure. Tell the owner you are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward that is funded separately and never deducted from the company's payout. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout.

Fit. 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. Demand, the rights review result and any offer stay unknown until SourceX reviews the application.

Introduction. Use the annotated introduction email and send it only to the authorized contact. Sign the Channel Partner Agreement first. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only: a USD 100,000 qualifying payout to the company would mean a USD 55,000 default reward on its first qualifying transaction. The rewards page lists every condition, and the QA scorecard data type explains which scorecard records tend to matter.

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 checklist shows both scores survive the switch-off and the owner wants to talk, register as a partner, check who qualifies, and read the program terms before making the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

What if the company has no switch-off date for the old form?

Then the third milestone is open, and the checklist item is to find out who decides it. Do not substitute a date of your own; an assumed deadline creates pressure the company has not agreed to.

Should the advisor do the archiving?

No. The company's QA and platform teams decide what to keep. The advisor's job is to ask the questions in time and record the answers at metadata level.

Does finishing the checklist mean the company qualifies?

No. It describes what the company holds. Eligibility, rights and any offer are decided only after the company applies and SourceX reviews it.

Sources

  1. refer.sourcex.si/terms
  2. help.mypurecloud.com
  3. help.mypurecloud.com/releasenote/january-31-2024
  4. help.mypurecloud.com

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment