It is part of the appeal-to-course-correction records guide. The record chain page explains the identifiers this scorecard tests.
Scoring rules
Each check earns 2 points for a pass, 1 for a partial and 0 for a fail, so the maximum is 12. Score with the assessment lead and the person who maintains course templates together; each knows half the answers.
- Pass means the practice holds across the years in scope and someone can name when it started.
- Partial means it holds for some programs, some years or some teams.
- Fail means it does not hold, or no one can say. Unknown is a fail with a name beside it for who could find out.
Write the starting year beside every pass and partial. A practice that has held since 2023 and one that has held since 2017 are very different descriptions, even with identical points.
The scorecard
| Check | Metadata question | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Identifier | Starting from a scoring-guide change, can staff trace back to the panel decision and ticket behind it? | Ticket number on the panel decision, panel decision number on the change | One of the two references exists | Neither; challenges retyped, changes unreferenced |
| 2. Release | Is the course release named both in the panel decision and in the change? | Named in both | Named in one | Title only; release guessed from dates |
| 3. Propagation | After a change, how do staff know each delivery copy received it? | Guides locked in templates; push exceptions reviewed | Locked in some programs | Unknown; copies edited freely |
| 4. Regrading | When a criterion changes, are earlier marks revisited, and is that choice written down? | Flag or register records it | Recorded for major changes only | Never recorded either way |
| 5. Timing | Is the panel decision a dated system entry made before the change? | System entry, dated first | Dated meeting minutes | Written up afterward, or not at all |
| 6. Outcome | Are challenges counted per criterion after an update? | Counted by criterion over time | Counted per course only | Not counted |
Checks 1 and 2 decide whether the trail can be joined at all. Checks 3 and 4 decide whether the fix's reach can be described. Checks 5 and 6 decide whether the order of events and the result can be trusted.
Some notes on scoring specific checks:
Check 1. In Zendesk, ticket audits are a read-only history of every update, so the ticket side of the link usually survives. The question is whether the appeal record carries the ticket ID, which depends on the appeal form, not the support desk.
Check 3. Instructure's documentation says a Canvas blueprint sync overwrites locked objects in associated courses, while unlocked items are left to instructors, later syncs are manual, and edits made in an associated course before a sync can produce exceptions. A company that locks rubrics and reviews sync exceptions can pass; one that leaves rubrics unlocked cannot know without comparing copies.
Check 4. Moodle's documentation describes a platform-level answer: after a significant grading form change, existing assessments may be flagged "Needs review" for re-assessment against the new version. A company using a feature like that has a recorded re-review; a company that edits rubrics in place usually does not. Ask which describes the client, and from which year.
The wrong-version test
Run one scenario through checks 2 and 4 before you total the card. Illustrative: an appeal from the March intake of a spoken-English course is upheld because the fluency band descriptor is vague; the curriculum team rewrites the descriptor in the September template; March speaking scores are left as they were.
Ask the client: "In a case like that, would your records show the fix went to September on purpose, and that March scores were deliberately left?" Three answers are possible, and they score differently:
| Client's answer | Check 2 | Check 4 | How to describe it |
|---|---|---|---|
| Both versions are named, and the decision to leave past grades is logged | Pass | Pass | A recorded policy choice |
| Versions are named, but the re-review decision is not written down | Pass | Fail | Traceable fix, unknown follow-up |
| Only course names appear, and nothing records the choice | Fail | Fail | Cannot tell decision from oversight |
The third answer is common and still describable. What matters is that the description says so plainly rather than implying a clean trail.
A scored example and what the total means (Illustrative)
A fictional 520-person language-teaching company, scored with its head of assessment and curriculum director.
| Check | Mark | Points | Note |
|---|---|---|---|
| 1. Identifier | Partial | 1 | Ticket ID on appeals since 2022; edits unreferenced |
| 2. Release | Partial | 1 | Cohort code on appeals; edits name the blueprint only |
| 3. Propagation | Partial | 1 | Rubrics locked in two of five programs |
| 4. Regrading | Fail | 0 | No record either way |
| 5. Timing | Pass | 2 | Panel decisions are dated system records |
| 6. Outcome | Partial | 1 | Tracked per course, not per criterion |
| Total | Sum of points | 6 of 12 | Joinable from 2022 with known gaps |
Only one check passes outright, and that is fine. Five honest marks with years beside them say more than a confident total. The one-line description for a reviewer: "Appeals and decisions joinable from 2022; rubric edits not tied to appeals; reach of fixes known only for locked programs; no re-review record." The ERP replacement handoff checklist shows the same habit of stating gaps before a migration removes them.
Who answers, and what the score leaves open
The head of assessment answers checks 1, 4, 5 and 6; the curriculum director or LMS administrator answers 2 and 3. The CEO, usually the owner in an owner-run company, authorizes a licensing discussion; a COO or chief academic officer may sponsor it internally. The education screening worksheet helps confirm fit.
The company needs 50+ full-time employees at peak (contractors excluded, which usually includes freelance instructors), documented operating history, rights to license its curriculum and rubrics, 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.
The score leaves open how learner identities would be removed, whether student-record rules apply (the FERPA vendor data use guide covers U.S. schools), whether a buyer wants this history, and what the company would be paid. SourceX settles those under the company's agreement. Partners never handle learner work, appeal letters or grades.
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 scorecard shows a trail the client can describe honestly, wrong-version cases included, register as a partner, check who qualifies, and read the terms before you introduce the sponsor.