Define numeric bands
Set school grade codes, labels and minimum percentages, with each threshold beginning the next band.
Grading scales &
reporting definitions
A shared language for achievement. A clear basis for reporting.
Give achievement a consistent language across your school. Define the scales and reporting rules your teachers use, then keep each reporting cycle connected to the reviewed version.
Start with how your school describes progress
Numeric bands.
Teacher judgement.
A consistent framework.
Use meaningful descriptors
Build ordered teacher-judgement labels for subjects that use descriptive attainment instead of percentages.
Choose the appropriate scope
Maintain academy-wide definitions or campus-specific versions for the reporting context they serve.
Explore reporting cyclesThe rules behind a reported result
Connect the scale
to the reporting approach.
Use reporting policies to select the result type and scale, define evidence buckets where needed and set the school’s effort and forecast labels. Keep the approval approach clear for the people preparing and reviewing results.
- Choose numeric results or teacher-judgement outcomes.
- For numeric results, define evidence buckets whose weights total 100%.
- Use pooled points or explicit task weighting within each evidence bucket.
A stable basis for every reporting cycle
Review the definition.
Keep the version.
Give staff a consistent reference for the reporting period. Activating a definition fixes that version’s content, while a later change begins as a new revision for review.
See report review & readinessPrepare a draft
Define the scale or policy and review its meaning, calculation rules and scope.
Activate the reviewed version
Make that version available for selection in the appropriate reporting context.
Revise without rewriting history
Create a new revision for future use. Creating a revision does not automatically replace the version selected for an existing reporting cycle.
For your team
A common reference
from subject result to school report.
Academic leaders
Agree the reporting framework.
Define the scales, result approach and reporting rules that reflect the school’s assessment policy.
Reporting administrators
Keep the setup deliberate.
Prepare and activate definitions in the right scope, then select the reviewed versions for reporting.
Teachers & reviewers
Work from the same definitions.
Use the assigned scale and policy while preparing, checking and explaining each reported result.
Defining achievement consistently
How do scales, calculations and revisions work?
See how a school-owned grading framework becomes a stable reference for reporting.
Can we use both numeric and descriptive grading?
Yes. Numeric scales define percentage bands beginning at 0%, using school grade codes and labels. Teacher-judgement scales use ordered descriptors without percentage thresholds. Choose the appropriate scale for the subject’s reporting policy.
How is a numeric subject result calculated?
Numeric policies use evidence buckets whose weights total 100%. Each bucket can pool earned and available points or weight each selected task. The final percentage is rounded half up to two decimal places before the grade band is selected.
What happens if required assessment evidence is missing?
Missing, unreleased, absent or excused evidence blocks the numeric calculation for review. It is not silently replaced by zero or redistributed across the other evidence. An explicit Not assessed outcome can be enabled in the reporting policy.
Can we change an active scale during a reporting cycle?
An active definition version stays fixed. Create and review a new revision for future selection. Creating a revision does not automatically replace the version selected for an existing cycle. Archiving removes a version from new selections while keeping its existing uses readable.
Keep exploring
One school. More connected possibilities.
Grading scales & reporting definitions
Give every reported result a consistent foundation.
Connect your school’s language for achievement with reviewed rules and stable reporting versions.