# Assessment appeal referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/assessment-appeal-resolution-referral-brief-template
Last updated: 2026-11-04

A company introduction about assessment appeal resolution is a one-page brief that describes the appeal history without containing any of it. It names the business task, the record classes, the systems that hold them, the years and rough volumes covered, the open question about how the records join, any access deadline, and who can convene and approve a discussion. It leaves out candidate names, responses, scores, appeal files and any estimate of value. The template below has ten fields; the example fills each one.

This template is part of the [assessment appeal resolution guide](/guides/workflow-assessment-appeal-resolution). Use it after the first conversation with the head of academic operations, once you know enough to fill the fields honestly.

## The fill-in template

Copy the fields and fill each one with a short, checkable statement. Write "unknown" rather than guessing; an honest gap is more useful to SourceX than a confident estimate.

| Field | What to write | Example of a good entry format |
|---|---|---|
| 1. Company | Sector, approximate full-time headcount at peak, country | "Certification body, about 200 full-time staff, Ireland" |
| 2. Business task | The appeal workflow in one sentence | "Appeals against marks on written exams" |
| 3. Record classes | Which kinds of records exist, by name | "Rubric versions, marker comments, appeal files" |
| 4. Systems | Each platform, case tool or repository, by type | "Assessment platform, ticketing tool, shared drive" |
| 5. Coverage | First and last year held, per record class if they differ | "Scores since 2016; comments since 2019" |
| 6. Volume | Rough counts from a report, never from opening records | "About 600 appeals a year" |
| 7. Linkage | Which joins hold and which are unknown | "Case ID cites attempt ID; rubric versions unclear" |
| 8. Deadline | A documented event that changes access, with its source | "Old platform read access ends per exit clause" |
| 9. Authority | Who convenes, who approves, who advises | "Head of academic operations; CEO; counsel" |
| 10. Left out | What the brief deliberately does not include | "No names, responses, scores or files" |

Field 7 is the one that makes a brief worth reading. It tells SourceX whether the history can be followed from a disputed mark to the decision that changed it, which the [system map](/guides/assessment-appeal-resolution-records-across-systems) explains join by join.

## A completed brief (Illustrative)

The values below describe a fictional 210-person professional certification body. They are **Illustrative**, not a real company, case or deal.

1. **Company:** professional certification body, about 210 full-time staff at peak, headquartered in Canada; all candidate records in English.
2. **Business task:** resolving candidate appeals against marks on written case-study exams, including answers that are valid but fall outside the original rubric.
3. **Record classes:** rubric versions with effective dates, marking instructions, first- and second-marker comments, appeal forms and grounds, panel minutes, reissued results.
4. **Systems:** a hosted assessment platform; a ticketing tool used as the appeal case manager; a shared drive holding rubric versions and panel papers.
5. **Coverage:** eight years of sittings on the current platform; marker comments complete for the last six; panel minutes on the shared drive for all eight.
6. **Volume:** roughly 400 to 500 appeals a year, of which about a fifth change a mark, according to the appeals officer's annual report.
7. **Linkage:** appeal tickets cite the attempt ID since year three; earlier tickets cite the candidate number only. Whether superseded rubric versions are tied to the attempts they scored is unknown.
8. **Deadline:** the platform contract renews next year; read access after exit is set by the exit clause, which the contract owner is checking.
9. **Authority:** the head of academic operations will convene; the chief executive approves; the general counsel advises on candidate terms and the platform contract.
10. **Left out:** candidate names and numbers, responses, scores, any appeal file or minute, login details, and any estimate of value.

Notice what the example does with uncertainty. Field 7 says "unknown" about the rubric link instead of assuming it, and field 8 names who is checking the date instead of supplying one.

## Fields that look helpful but do not belong in a brief

Some entries make a brief longer without making it more useful, and some create risk.

| Tempting entry | Why it stays out | What to write instead |
|---|---|---|
| A sample appeal or redacted minute | Moves candidate records before any rights review | The record class and the years it covers |
| An estimate of what the data is worth | Nobody knows until SourceX reviews it | Nothing; leave value out entirely |
| Pass rates or score distributions | Derived from candidate records | Appeal volume from a published or internal summary count |
| Login details or export files | Partners never handle access or records | The system type and who administers it |
| A promise of licensing | Rights and demand are undecided | The open questions in fields 7 and 8 |

## Checks before you send it

Run through these before the brief goes to the head of academic operations:

- **Size:** does the company have 50+ full-time employees at peak, contractors excluded? If unsure, write "unknown" and check with the [screening worksheet for education and training businesses](/resources/a-referral-screening-worksheet-for-education-and-training-businesses-businesses).
- **Geography:** 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.
- **Rights:** have you named the candidate-terms, platform-contract and student-privacy questions without answering them? Where records are education records of a FERPA-covered school, signed written consent naming the records, purpose and recipients is generally required before disclosure, which is a question for counsel, not for the brief.
- **Rubric detail:** if you describe the rubric, describe its structure only, for example "criteria with points per level, summed to a total", as rubric tools document it. For regulated awarding, note that marking procedures are records too; Ofqual defines a marking error partly by reference to them.
- **Authority:** is the person in field 9 able to say yes? The [who-can-say-yes tree](/questions/who-can-license-assessment-appeal-resolution-records) helps check.
- **Paperwork:** have you signed the Channel Partner Agreement? It comes before any introduction.

For wording and how to disclose your referral relationship, use the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner). The first valid introduction within the 90-day window is credited when the company submits a verified application. A [data audit](/proof/what-is-a-data-audit) is the step after the company agrees to talk.

## 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.

When every field in the brief is either filled from a checkable source or marked unknown, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before sending it to the head of academic operations.

## Sources

- https://refer.sourcex.si/terms
- https://docs.moodle.org/402/en/Rubric
- https://www.gov.uk/guidance/ofqual-handbook-technical-qualifications/interpretation-and-definitions-condition-tq23
- https://www.govinfo.gov/content/pkg/CFR-2023-title34-vol1/pdf/CFR-2023-title34-vol1-sec99-30.pdf
