Evidence · Corrections

Corrections and right of reply

Any finding can be challenged: missing policies, newer versions, broken links, misreadings or disagreements with the method.

Choose a route

Factual correction

We applied the rubric wrongly or missed a document. If accepted, the finding changes.

Examples
  • a policy or regulation exists that we did not review;
  • a newer version replaces the document we cited;
  • we misread or mistranslated a provision;
  • a link is broken or points to the wrong document.

Open the correction form on GitHub

Methodology disagreement

The rubric itself is wrong. Recorded publicly for the next version; current findings stay.

More about disagreements

Use this route if you accept that we applied the rubric correctly but think the rubric itself is wrong. For example, a safeguard should be defined differently, or a national system achieves the same protection another way. Disagreements are shown alongside the finding where relevant.

Open the methodology form on GitHub

New to GitHub? Here is what to expect

  1. Choose a factual correction or a methodology disagreement above.
  2. The button opens a structured GitHub form. Sign in, follow the prompts and submit it; a pseudonymous account works.
  3. The request, review and outcome remain public so changes can be audited.

Do not submit personal data, names, allegations or case details. StudentSafe Europe reviews published evidence, not individual cases.

StudentSafe Europe does not currently have a safe private submission route. GitHub is the only route; this is a known limitation.

Process

What happens next

  1. Logged Public ID, e.g. C-2026-001
  2. Marked disputed Shown next to the finding
  3. Independent review By someone who did not make the finding
  4. Reasoned outcome Written reasons, public commit
  5. Kept in history Nothing silently overwritten

We aim to acknowledge within 10 working days. Nothing is silently overwritten.

Each step in detail
  1. Acknowledgement. The request is logged with an ID such as C-2026-001. We aim to acknowledge requests within 10 working days.
  2. Disputed marking. If the request raises a substantive question, the affected finding is marked disputed and the dispute is shown publicly next to it. The finding is not removed.
  3. Review. A reviewer who did not make the original finding checks the new evidence against the rubric.
  4. Outcome. The request is accepted, partially accepted or not accepted, with written reasons. Any change to data is made in a public commit that references the correction ID.
  5. Record. The earlier finding remains in the public history. Nothing is silently overwritten.

Reply and privacy

Right of reply

Institutions may publish a reply of up to 300 words on their profile, whatever the outcome.

Please do not include

  • Names of staff or students
  • Allegations or complaint files
  • Health information or private correspondence

Requests are public. StudentSafe Europe cannot investigate individual cases.

Log

Public corrections log

No correction requests have been received yet.

Log file: data/corrections.yml · Full policy: correction-policy.md · right-of-reply.md