Appeal-to-course-correction record chain: the keys that join a support ticket, an appeal decision and a versioned rubric change

Short answer

A company connects appeal-to-course-correction records by passing a reference number forward at every hand-off: the help desk ticket number onto the appeal, the appeal number onto the marking-scheme change, and a named version onto all three. Ticket and appeal numbers are often present. The version is the identifier most companies skip, storing a course title and leaving the edition implied by a date. Once that happens, nobody can later prove which wording a learner challenged, or whether the repair reached them.

Visual briefFull-size diagram
Four records, ticket, appeal, rubric edit and section copy, click together as chain links; the link keyed only by course name glows as weak, then turns green once a course version key is added.
Illustrative chain. The weak link is the course version, which most companies leave implied by the date.

This page is part of the appeal-to-course-correction records guide. It does one job: list the identifiers that hold the chain together and show where they snap. For what a single export loses, see the missing context page.

The chain at a glance: step, record, key, system

Four steps, four records, three systems. Think of the key column as a foreign key in a database: it is the value a later record must hold for anyone to find the earlier one.

StepRecordKey it should carrySystem
1. Challenge receivedHelp desk ticket with tags and routing historyTicket number; course title and intake codeSupport desk
2. Ruling madeAppeal entry with outcome and reasoningTicket number from step 1; assessment number; scheme edition usedAssessment platform
3. Scheme amendedChange to the marking scheme on a template courseAppeal number from step 2; new edition; target course editionLMS
4. Amendment arrivesDelivery copies after a push from the templateTemplate edition; lock flag on the schemeLMS

Read across each row. Steps 1 and 2 share a number someone must copy by hand. Steps 2 and 3 share a number someone must remember to type. Steps 3 and 4 are joined by the platform itself, but only under conditions explained below.

Ticket to ruling. The first key is a number generated by the help desk. In Zendesk, ticket audits keep a read-only history of each update, so tagging and routing a dispute to assessment staff leaves a dated trace on the desk side. That trace only becomes a join when the appeal entry stores the same number in a field of its own, not pasted into a free-text summary. Ask whether the field is mandatory, optional or absent, and when it was added.

Ruling to amendment. This is the decision join, and no platform makes it automatically. The designer who rewords a criterion is rarely the person who sat on the panel, often weeks apart. The key here is the appeal number written into whatever records the amendment: a change request, a version comment, a release note. If the company keeps change requests in a project tracker, that tracker is a fourth system and belongs in the chain.

Amendment to edition. Both the ruling and the amendment concern a specific edition of the assessment. The key is an edition label stored on both entries, in the same format. A company that labels editions "Spring 2024" in one system and "24-1" in another has the key in principle and a translation table in practice, which is worth noting.

Edition to delivery copies. Here the platform does the joining, within limits. Instructure documents that a Canvas blueprint sync overwrites locked objects in associated courses, leaves unlocked items to instructors, needs manual syncs after the first, and can raise exceptions when a copy was edited beforehand. The lock setting is therefore part of this key: a push alone does not prove that every copy now carries the amended wording.

Where the chain usually snaps

LinkTypical breakWhat it looks like laterRepair a company can describe
Ticket to appealAppeal re-typed from the ticketTwo records, no shared numberAppeal form has a ticket ID field, since a known year
Appeal to scheme changeChange made with no referenceCriterion reworded for no visible reasonChange note or version comment cites the appeal ID
Change to editionEdition implied by dateCannot tell which intake the fix was forEdition named in both records, same format
Edition to copiesScheme unlocked in some copiesOld wording survives after a pushLocking policy; sync exceptions reviewed
Back to earlier gradesNo re-review recordedUpheld appeal with no follow-up on othersRe-review flag or log, as some platforms provide

The last row extends the chain backward. Moodle's documentation describes one way platforms handle it: when a grading form changes significantly after use, existing assessments may be flagged "Needs review" for re-assessment against the new version. A company with a feature like that has a recorded fifth link; most do not.

Key coverage by year: one provider's matrix (Illustrative)

Keys are rarely all present or all absent. They arrive one at a time, usually after a process change, so the useful question is "since when?" for each link. Below is a fictional 520-person accountancy exam-prep provider, described by its operations team from memory and system settings. No records were opened. Every value is Illustrative.

Link2019-20202021-20222023 onwardWhat changed
Ticket number on the appealAbsent: appeals arrived by emailOptional fieldMandatory fieldHelp desk web form replaced the appeals inbox
Appeal number on the scheme changeAbsentAbsentPresent in version commentsPanel chair asked designers to cite rulings
Edition label on both recordsAbsent: schemes edited in placeExam-session code on rulings onlySession code on both, e.g. AUD-23.2Marking schemes moved into a versioned template
Lock setting on copiesNot trackedNot trackedSchemes locked by defaultTemplate policy introduced with versioning
Re-review of earlier gradesNot recordedAd hoc emailsLogged as a panel actionQuality audit finding

Read down the last column and a pattern appears: each key came from one decision, by one owner, in a known year. That makes the chain describable in honest terms. For this provider, roughly the last three years can be traced end to end; the two years before have the ruling but not its reach; anything earlier begins with an email thread, which counts as a gap rather than a link.

The company can then test the matrix itself. Its assessment manager picks twenty upheld appeals from 2023 onward and checks, for each, whether the next record can be found by key alone. In this Illustrative run, 19 of 20 carry a ticket number, 15 of 20 scheme changes cite the appeal, and 20 of 20 name the session code. The partner hears those counts, not the appeals.

Testing the chain in one question, and who can answer it

Ask the client one joining question: "When an appeal changes a rubric, where do you write down which course version the appeal came from and which version you changed?" A specific answer with a start year means the chain can probably be described end to end. "We'd know from the dates" means the version link is inferred and should be marked that way.

Each link has its own owner: the learner support manager for tickets, the head of assessment for appeals, the curriculum director for the LMS. None of them authorizes licensing; the CEO does, usually the owner in an owner-run provider, with a COO or chief academic officer as a likely sponsor. For the support desk side, see Zendesk records; for what a structured review of record quality involves, see what a data audit is; for sector context, education and training companies and the systems hub.

Confirm the basics before an introduction: 50+ full-time employees at peak (contractors excluded, which usually includes freelance instructors), documented operating history, rights to license the 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.

What stays unknown until SourceX reviews it: how learner identities would be removed, whether student-record rules apply, which histories a buyer would want, and what the company would be paid. The partner never handles tickets, appeals or grades. SourceX does not claim a connector for Canvas, Moodle or Zendesk.

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 client can name the key at each link, including the course version, and an officer will take the call, register as a partner, check who qualifies, and read the terms before you introduce them.

  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

Is a course name ever enough as a key?

Only when a course has a single version at a time and cohorts never overlap. Most training companies run several cohorts on different rubric versions at once, so a name alone cannot say which wording applied to which learner.

Should the partner build the joined table for the company?

No. The partner asks whether each key exists and since when. If a licensing discussion goes ahead, the company does the joining under its agreement, and SourceX reviews it.

What if appeals arrive by email instead of a support desk?

Then the first link has no system key, and the chain starts at the appeal record. Record that as a gap. It does not stop the rest of the chain from being described.

Sources

  1. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  2. community.instructure.com/en/kb/articles/628548-blueprint-sync-functio…
  3. docs.moodle.org/36/en/Advanced_grading_methods
  4. refer.sourcex.si/terms

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