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.
| Milestone | Where the date usually comes from | If there is no date yet |
|---|---|---|
| Announcement | The redesign project charter or the QA lead's rollout note | Treat the checklist as early; work through milestone one calmly |
| Cutover | The configuration plan for the new form | Ask who owns the go-live decision and record that name |
| Switch-off | A platform contract end, a retirement ticket or an admin's plan | Leave 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.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| Which scorecard versions exist and which years each covers | QA lead | Later scores cannot be matched to the form that produced them |
| Whether first evaluations and final decisions are separate records | Analytics owner or platform admin | The team learns too late that only the latest score exists |
| Whether agent disputes are structured records or free-text comments | QA lead | The disagreement is invisible to any later review |
| Who owns QA records for each program, in-house or client | Owner or account director | Rights 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.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| The retired form definition, criteria and weights are archived | QA lead | A score of 3 on criterion 14 can no longer be interpreted |
| Calibration sessions and the expert scoring index are kept | Quality admin | Evidence of evaluator drift disappears from reporting |
| The reporting migration includes first scores and disputes, not only finals | Analytics owner | The new dashboard shows one number per call and the gap is gone |
| A mapping from old criteria to new criteria is written down | QA lead | Trends 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.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| How long recordings and transcripts are retained, under which named policy | Contact center or IT admin | Scores lose their link to the interaction they graded |
| Whether a new retention policy changes anything for past interactions | Platform admin | Teams assume old calls are covered when they may not be |
| Where the archived evaluations will live and who can access them | Analytics owner | The history exists but nobody can find or read it |
| Who can authorize a licensing discussion about the archive | Owner or CEO | An 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:
| Area | State | Note |
|---|---|---|
| Form versions, five years | Confirmed | Definitions archived before cutover |
| First scores and final decisions | Confirmed | Separate records for in-house queues |
| Disputes | Partial | Structured since year three, comments before |
| Calibration results | Unknown | Admin to confirm after the reporting rebuild |
| Recording retention | Confirmed | Named policy, set period |
| Ownership | Partial | Two 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.