# Appeal records retention timeline before renewal | SourceX

Canonical: https://refer.sourcex.si/guides/preserve-assessment-appeal-resolution-records
Last updated: 2026-11-04

Before a platform renewal changes what is kept, list five facts for each appeal record class: what the class is, the years it covers, which system and team hold it, what the vendor documents as exportable, and the real date access ends. Then add the company's existing retention rule for that class. A renewal carries active candidates, current rubrics and open appeals. Closed appeals, superseded rubrics and marker comments on old sittings are the history most often left behind, and grade history can be trimmed earlier still.

This timeline is part of the [assessment appeal resolution guide](/guides/workflow-assessment-appeal-resolution). It is written for assessment systems advisors who learn about a renewal, migration or vendor exit months before it happens.

## The timeline from renewal notice to lost access

A renewal or migration runs to a contract date. Working back from it gives the order in which to ask questions. The schedule below is **Illustrative**: a fictional 140-person professional certification body changing assessment platforms, not a real case.

| When | What happens | What the advisor asks about |
|---|---|---|
| Month -12 | Renewal notice or decision to change platform | Which record classes exist and where |
| Month -9 | Migration scope drafted | What the plan says moves: open appeals only, or closed history too |
| Month -6 | Vendor export options confirmed | Whether comments, rubric versions and score history export with scores |
| Month -3 | Data load to the new platform | What was left on the old instance |
| Month 0 | New platform live; old platform read-only | How long read access lasts |
| Month +3 | Old platform access ends under the exit clause | Nothing new; the inventory should already exist |

The useful moment for an inventory is month -9, while the scope is still a draft. By month -3 the decisions about what moves have been made, and the inventory only records what was left out.

## What disappears first, record class by record class

Record classes leave the old platform in a rough order, set by migration scope, configuration and the company's own schedule. This order is a pattern to check, not a rule.

| Order | Record class | Why it tends to go early | What survives if it is lost |
|---|---|---|---|
| 1 | Grade history and score audit entries | May be switched off or trimmed by a cleanup setting long before renewal | Final scores, with no record of who changed them |
| 2 | Superseded rubric versions | New platforms usually load the current rubric only | Today's criteria, not the ones a disputed mark used |
| 3 | Marker and second-marker comments | Exports often carry scores, not free-text comments | Numbers with no reasons |
| 4 | Closed appeal files and panel minutes | Held in a separate case tool or drive outside migration scope | The decision letter, sometimes |
| 5 | Candidate responses | Usually under the most explicit retention rule | Depends on the schedule |

Grade history is first for a documented reason. In Moodle, for example, administrators can turn grade history off or keep it only for a set period under the server cleanup settings, which means the trail of revised scores may already be shorter than the score records themselves. Ask how the setting has been configured over time.

## How long each class is kept: ask, do not assume

There is no standard retention period for appeal records. Each company sets its own, based on its purposes, its regulators and its contracts, so the inventory records the company's rule rather than proposing one.

Where personal data is involved, data protection law pushes in one direction. The UK regulator's guidance on storage limitation says personal data must not be kept longer than needed, that organizations should be able to justify retention periods by their purposes, and that a retention policy or schedule should set standard periods where practical. A company that deletes candidate responses after a set period is following that principle, and the inventory reports the rule; it does not argue against it.

U.S. school records can push the other way. FERPA's inspection rule says a covered institution may not destroy education records while a request to inspect and review them is outstanding. Where a company assesses on behalf of covered schools, open requests are a fact for the inventory and a question for counsel.

## The inventory sheet: six facts per class, no copies

The inventory holds metadata only. Partners never ask for appeal files, candidate responses or comments.

| Fact | What to write down | Who usually knows |
|---|---|---|
| Record class | Responses, rubric versions, marking instructions, comments, appeal files, panel minutes, reissued results | Head of academic operations |
| Time coverage | First and last sitting held; whether comments go back as far as scores | Platform administrator |
| System and owner | Platform, case tool or drive, and the team that runs it | Platform administrator, appeals officer |
| Export path | What the vendor documents as exportable, and in what format | Platform administrator, vendor documentation |
| Access deadline | The date in the renewal or exit clause | Contract owner |
| Retention rule | The company's existing schedule for that class | Records or data protection lead |

The sheet is also the starting point of a [data audit](/proof/what-is-a-data-audit), and the record classes match the joins on the [system map](/guides/assessment-appeal-resolution-records-across-systems).

## Who approves keeping anything beyond the plan

Changing what is kept is an executive decision, not an operational one. The platform administrator can configure retention; they cannot decide it. The head of academic operations can recommend; counsel or the data protection lead checks the recommendation against the law and candidate terms; the chief executive or a delegated executive approves. The [who-can-say-yes tree](/questions/who-can-license-assessment-appeal-resolution-records) shows the same people for a licensing discussion.

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. Whether any preserved history can be licensed, and whether a buyer wants it, stays unknown until SourceX reviews it. For sector context see [education and training](/industries/education-and-training), and if the renewal is part of a sale, the [exit readiness assessment](/tools/business-exit-readiness-assessment) frames the wider timetable.

## 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 inventory shows years of closed appeals and rubric versions with a real access deadline ahead, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you raise it with the head of academic operations.

## Sources

- https://refer.sourcex.si/terms
- https://docs.moodle.org/403/en/Grade_history
- https://www.ecfr.gov/current/title-34/subtitle-A/part-99/subpart-B/section-99.10
- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/
