Assessment appeal resolution across systems: a system map of the records, linking keys and owners

Short answer

To reconstruct an assessment appeal across systems you need four joins: candidate to attempt, attempt to the version of the marking scheme (the rubric) in force, attempt to the appeal case, and the appeal decision back to the revised score. Each join depends on an identifier that both systems recorded, such as an attempt ID or case ID. The scheme-version join is the one most often missing, because many setups keep only the latest scheme. An advisor maps these at metadata level and never handles the records.

Visual briefFull-size diagram
A system map with four nodes, assessment platform, rubric repository, case manager and gradebook history, joined by four linking keys: attempt ID, rubric version, case ID and score audit entry, which travel along the links to assemble one appeal case in the center.
Illustrative: the IDs that join one fictional appeal. The rubric version link is the one most often missing.

This system map is part of the assessment appeal resolution guide. The main guide explains why appeal records matter; this page shows where each record lives and what holds a case together.

The systems that hold one appeal, and who runs each

Most organizations that mark written or practical assessments split appeal handling across three to five systems. The table is the map in list form: one row per system, the record it holds, the key it shares with its neighbors, and the team that administers it.

SystemRecord it holdsLinking key it sharesUsual owner
Assessment platformCandidate response, attempt, sitting date, per-criterion scores, marker commentsCandidate ID, attempt IDAssessment operations or exams team
Scheme or content repositoryScheme versions, examiner instructions, effective dates, change notesScheme ID and version numberAssessment design or standards team
Appeal case manager or ticketing toolAppeal form, stated reasons, filing date, board minute, decision letterCase ID, plus the attempt ID if the form asked for itAcademic operations or quality team
Gradebook or score historyRevised score, who changed it, whenAttempt ID with an audit entryPlatform administrator
Email or shared driveSecond-examiner notes, board papers, candidate correspondenceWhatever people typed: candidate number, name, dateIndividual staff, unless filed

The owner column matters for two reasons. It tells the advisor who can describe each system accurately, and it shows that nobody on the list owns the whole case. Scheme design, platform administration and the appeal process often sit in different teams.

The linking keys, join by join

A key is only useful if it was recorded on both sides at the time. Here is what each join depends on and what happens without it.

JoinKey on one sideKey on the other sideIf the key is missing
Candidate to attemptCandidate ID in the platformCandidate ID or email on the appeal formAppeals cannot be matched to the sitting they dispute
Attempt to scheme versionScheme ID and version stored with the scoresVersion number in the repositoryNobody can show which criteria were in force when the mark was given
Attempt to appeal caseAttempt ID, if captured on the formCase ID in the case managerAppeal outcomes float free of the scores they changed
Decision to revised scoreScore change with grader and timestampBoard decision and minuteA changed score looks unexplained, or a decision looks unapplied
Scheme change to causeChange note on the new versionBoard recommendation in the minuteThe revision cannot be traced to the appeal that prompted it

Score history is the easiest join to check, because some platforms document it. Moodle, for example, has a Grade history report that filters grading changes by student, grade item and grader, can show only revised grades, and downloads as CSV or a spreadsheet. The same documentation notes that administrators can switch grade history off or keep it only for a set period, so whether the history exists for older sittings is a configuration question, not a given.

The scheme-version join is harder. Moodle documents its rubric total as the sum of the level picked on each line, which makes the point general: a number of points is meaningless once the lines behind it have been edited. Products differ on whether an old version stays attached to the attempts it scored, so confirm with the vendor's own documentation instead of assuming it.

One fully joined appeal case (Illustrative)

A fictional 260-person IT training and certification company runs a practical lab exam. Each candidate's lab is scored on three tasks, 3 points per task, 9 in total, with 6 needed to pass. Every ID below is invented to show the shape of a joined case, not a real record.

StepSystemRecordKey that carries the join forward
1Assessment platformAttempt A-2291 for candidate C-58014, lab sat on Feb 9Attempt A-2291
2Assessment platformTask 2 scored 1 of 3 under scheme R-12 version 3; total 5 of 9Scheme R-12 v3
3Scheme repositoryR-12 v3 task 2 names one configuration method onlyScheme R-12 v3
4Case managerAppeal case AP-0417 filed Feb 23, claiming an alternative method also meets the requirement; form cites A-2291Case AP-0417 citing A-2291
5Email, filed to caseSecond examiner's note supporting the alternative methodCase AP-0417 in the subject line
6Case managerBoard minute, Mar 8: method accepted; task 2 rescored 3 of 3Case AP-0417
7Gradebook historyA-2291 revised from 5 to 7 of 9, pass; grader and timestamp recordedAttempt A-2291
8Scheme repositoryR-12 v4 adds "or an equivalent configuration method"; change note cites AP-0417Scheme R-12 v4 citing AP-0417

Read down the last column and the case holds together: every step names a key that the next step also recorded. Remove step 8's citation and the scheme change has no recorded cause. Remove the attempt ID from the appeal form at step 4 and someone has to match the appeal to the attempt by name and date, by hand.

Where the keys usually break

Most appeal histories are partly joined. The breaks tend to fall in the same places, and naming them helps an advisor describe the history honestly.

  • Typed identifiers. If staff copied candidate numbers into a ticket by hand, a share of them will be wrong or missing. Ask whether the case tool pulls IDs from the platform or relies on typing.
  • Overwritten schemes. A repository that edits in place keeps today's lines and loses the ones a disputed score was based on.
  • Board papers outside the case tool. Minutes saved to a personal drive or sent by email are often the only record of reasoning.
  • Score edits without an audit entry. A revised score with no grader or timestamp cannot be tied to the board decision.
  • A second request type for U.S. schools. The federal education records rule (34 CFR 99.20) gives families and eligible students a route to request a correction, with a hearing offered if the school declines. A vendor that tests on behalf of such schools may hold those correction requests next to ordinary appeals; give them their own node on the map.

None of these rules a company out. A history with three solid joins and one weak one is still a clear thing to describe.

Mapping questions for the head of academic operations

The head of academic operations can usually answer these without opening a single record. Keep every question at metadata level: what exists, how much, how long, which system, who owns it.

  1. Which systems hold attempts, marking schemes, appeals and score changes, and since when?
  2. Does the appeal form capture the attempt ID, or only the candidate's name and number?
  3. Are superseded scheme versions kept, with effective dates?
  4. Is score history switched on, and for how many years does it go back?
  5. Roughly how many appeals are filed a year, and how many change a mark?
  6. Who administers each system, and who owns the appeal process overall?

The answers become the system map in a referral brief. Who can approve a licensing discussion is a separate question, covered in who can license assessment appeal records. A data audit uses the same metadata as its starting point, and more context for the sector is on the education and training page.

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Partners sign the Channel Partner Agreement before submitting introductions. What stays unknown until SourceX reviews it: whether the records can be licensed under candidate terms and privacy law, how much de-identification is needed, and whether any buyer wants them.

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 head of academic operations can name the systems and confirm that at least the attempt and case IDs join, register as a partner, check the company on who qualifies and read the program terms before you make 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

Does the partner need to see any IDs to build this map?

No. The partner asks which systems hold which record types and whether a shared identifier exists. The head of academic operations or the platform administrator answers from what they know; no attempt, case or candidate ID changes hands.

What if the appeals were handled in email rather than a case tool?

Then email is a node on the map and the linking key is whatever people typed in the subject line or body, often a candidate number. That is a weaker join, and it is worth saying so honestly in the introduction.

Sources

  1. refer.sourcex.si/terms
  2. docs.moodle.org/402/en/Rubric
  3. docs.moodle.org/403/en/Grade_history
  4. ecfr.gov/current/title-34/subtitle-A/part-99/subpart-…

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