# QA scoring redesign meeting agenda (30 min) | SourceX

Canonical: https://refer.sourcex.si/resources/qa-scoring-redesign-meeting-agenda
Last updated: 2026-11-04

Run a 30-minute meeting in five blocks, with the question for each block assigned to the person who can actually answer it. The second block asks the core question outright: are initial scores and adjudicated decisions both retained? The meeting ends with one recorded decision: introduce the company's authorized contact to SourceX now, revisit after the new scorecard goes live, or stop. Everything stays at metadata level; nobody opens an evaluation or a recording.

This agenda is part of the [QA scoring redesign guide for CX analytics advisors](/guides/moment-qa-scoring-redesign-cx-analytics-advisors), which explains why reviewer disagreement evidence matters. Use this page when you need the meeting itself: the invite, the run sheet, the timekeeping and the close.

## Before you send the calendar invite

A short meeting only works if the logistics are settled in advance. Book it as its own slot rather than squeezing it into a build stand-up, and keep the invite list small.

- **Purpose line in the invite.** "Thirty minutes on what the old QA history contains before the new form goes live. Description only; no files." That sentence tells every attendee they will not be asked to export anything.
- **Pre-read.** None, or a one-line list of the five block questions. Long pre-reads turn into debates before the meeting starts.
- **Chair and timekeeper.** You chair. Ask the QA lead to keep time, because they know which block tends to overrun.
- **Notes.** Take notes yourself in a plain table: block, answer, who gave it, open item. You will need it for the decision at minute 30.
- **Parking lot.** Anything about the new scorecard design itself goes on a list for the redesign workstream. This meeting is about the history the old form leaves behind.
- **Timing.** Hold it after the redesign scope is agreed but before the new form is configured, when people can still describe the old setup from memory and the plan for it is not yet fixed.

If the owner cannot attend, run blocks one to four with the others and book a separate ten minutes with the owner for block five. Never treat an absent owner's silence as consent.

## Who needs a seat for the 30 minutes

Four roles cover every question. If one is missing, the block that depends on that role turns into a follow-up item rather than an answer.

| Role | Why they are needed | Blocks they answer |
|---|---|---|
| QA lead or quality manager | Owns the scorecard, its versions and the dispute process | 1 and 3 |
| Analytics owner or platform admin | Knows what the QA platform stores as separate records | 2 and 3 |
| Contact center or IT admin | Knows recording and transcript retention settings | 4 |
| Owner or CEO | Can say who owns the records and can authorize a licensing discussion | 4 and 5 |

For an outsourced provider, add the account director for the client program in question. Client contracts often decide who owns evaluations and recordings, so block four cannot be closed without them.

## The five blocks, with the question and the answer you want

Illustrative. A 260-person insurance contact center is cutting its scorecard from 18 criteria to 10. The advisor runs this agenda in the week before the new form is configured.

| Block | Question for the block | Who answers | What a good answer sounds like |
|---|---|---|---|
| 0-5 min: scope | What changes on the scorecard, and on what date does the new form go live? | QA lead | "Version 4, 18 criteria, retires on the go-live date; version 5 has 10." |
| 5-12 min: both scores | Is the first mark kept alongside the final ruling? | Analytics owner | "Yes. The first evaluation, the dispute and the final score are separate records back to 2021." |
| 12-18 min: calibration and old forms | Are calibration results kept, and will retired form definitions be archived with the scores? | QA lead and platform admin | "Calibration sessions are stored against the expert's scoring index; we will export the v4 definition before go-live." |
| 18-24 min: ownership and recordings | Who owns the evaluations and the linked recordings, and how long are recordings kept? | Owner and IT admin | "We own them for in-house queues. Recordings are kept for a set period under a named policy." |
| 24-30 min: decision | Does the company want to hear how licensing of approved records works, and who would lead that? | Owner | "Yes, I can authorize it. Our COO is the working contact." |

### Block 2 is the reason for the meeting

The current dashboard usually shows one number per evaluation. What you need to learn is whether the platform also keeps the first judgment and the challenge. In Genesys Cloud, for example, agents can dispute completed evaluation scores and the scorecard updates when the dispute is resolved, so the question is whether the earlier state is kept as its own record or only the latest one. Ask the analytics owner to describe the configuration, not to prove it with data.

### Block 3 decides whether the scores can be read later

Calibration in Genesys Cloud measures every evaluator against a scoring index set by an expert evaluator. That comparison is direct evidence of how reviewers disagree, and it is easy to drop from reporting. The retired form definition matters for a different reason: a score of 7 on criterion 12 means nothing once nobody knows what criterion 12 asked.

### Block 4 is where ownership gets settled

Retention is a second clock alongside the go-live date. 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](/systems/genesys-cloud-recording-export-bulk) covers that platform in more depth.

## Answers that should change the plan

Not every answer is yes. These are the common ones and what each should change about the meeting.

| What you hear | What it usually means | What to do next in the meeting |
|---|---|---|
| "The dashboard shows final scores only." | The answer to block 2 is not yet known | Name the admin who can check the configuration; move on |
| "Disputes are a comment field." | The challenge exists but is not structured | Note "partial" and ask how many years it covers |
| "We are deleting old forms at go-live." | Older scores may become unreadable | Flag it for the [archive context checklist](/resources/qa-scoring-redesign-archive-context-checklist) |
| "The client owns the evaluations." | The company may not hold rights to license | Ask which programs are in-house; stop for the rest |
| "Recordings expire quickly." | Scores may lose their link to the interaction | Record the policy name, not a guessed period |

The point is to leave with a description, not to win every block. A meeting that ends with "partial, two programs, owner to confirm" is a good result.

## What the owner hears before block five

Three things must be said before the decision, in plain words.

**What SourceX does.** SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Nothing is shared by attending this meeting.

**Your interest.** You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward under the [terms](/terms). It is funded separately and is never deducted from the company's payout. A meeting or an introduction alone does not trigger payment.

**Whether the company can qualify.** The introduced 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.

What stays unknown until SourceX reviews it: demand for this record type, the rights review result, any de-identification needed for customer conversations, any offer, and any reward. Partners never ask for or handle evaluations, transcripts or recordings.

## The decision the meeting has to produce

Close the meeting by reading out one of three outcomes and the name attached to it. Write it in the meeting notes the same day.

| Outcome | When it fits | Recorded by | What happens next |
|---|---|---|---|
| Introduce now | Block 2 is yes or partial, ownership is clear, the owner opted in | Advisor | Send the [introduction email](/resources/qa-scoring-redesign-introduction-email) to the named contact |
| Revisit after go-live | Answers depend on the new configuration or an admin's check | QA lead | Agree a date tied to the documented go-live, not an invented one |
| Stop | The owner declines, or the client owns the records | Advisor | Note the reason; the redesign work continues unchanged |

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. Sign the Channel Partner Agreement before submitting. Illustrative only: if a company were paid $250,000 for a qualifying completed handoff, the default reward would be $62,500; the [rewards page](/rewards) lists every condition. For a broader sense of which QA records matter, see the [QA scorecard data type](/data-types/call-center-quality-assurance-scorecard) and the [CX consultant partner page](/for/cx-consultant-referral-program). The [portfolio review agenda](/resources/portfolio-review-meeting-agenda-private-equity) shows the same time-boxed method in a different setting.

## 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 meeting ended with "introduce now," [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the introduction.

## Sources

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