Education · EU GPAI Code of Practice

EU GPAI Code of Practice for tutor and grader workflows

EU GPAI Code of Practice in tutor and grader workflows: what compliance requires, who asks for evidence, and the records to keep.

Legal forceVoluntary; adherence is a recognised way to show compliance with binding AI Act GPAI duties
Applies from2 Aug 2025
SectorEducation
Checked21 Oct 2026

01 / The rule

What EU GPAI Code of Practice requires

Providers of general-purpose AI models placed on the EU market that choose to sign; the Safety and Security chapter applies only to models with systemic risk.

  1. 01Transparency chapter: document each model (Model Documentation Form) and supply it to the AI Office and downstream providers on request.
  2. 02Copyright chapter: adopt a copyright policy, respect machine-readable rights reservations such as robots.txt when crawling, and offer a complaints point.
  3. 03Copyright chapter: take measures to reduce the risk of the model producing copyright-infringing output.
  4. 04Safety and Security chapter (systemic-risk models): adopt a safety and security framework and assess and mitigate systemic risks across the lifecycle.
  5. 05Safety and Security chapter: report serious incidents to the AI Office and maintain cybersecurity protection for the model.

02 / In this sector

In a tutor and grader workflow

Applies only to general-purpose AI models and their providers, not to downstream applications. Downstream builders rely on the documentation signatories must supply.

Usually asked by

District administrators, school leaders, and student equity teams.

Named alongside

Title VI · FERPA · §504 / IDEA.

Sector pagePlanisphere for education

03 / Records

Records to keep

  1. 01Completed Model Documentation Form per model version
  2. 02Published copyright policy and crawler rights-reservation handling
  3. 03Safety and security framework and model reports (systemic-risk models)
  4. 04Serious incident reports sent to the AI Office

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES

Go back to the source

PRIMARY

RELATED

Related: EU GPAI Code of Practice: the full guide · EU GPAI Code of Practice for defense · EU GPAI Code of Practice for medicine · EU GPAI Code of Practice for law