AI drafts the marking.
Teachers keep the judgement.
Every script comes back scored against your marking scheme, with inline comments and flagged uncertainties, ready for a teacher to review.
How GradeSail fits the marking workflow
Build the marking scheme
You add the questions, set each level's mark range, and write the descriptors in your own words, so the standard is explicit before any script is marked.
Every score GradeSail gives comes from this scheme.
Generate the first pass
GradeSail marks each submission against the scheme, drafts feedback, and flags what needs a teacher's attention.
Each score cites the criterion it came from and quotes the evidence from the script.
Review before release
Teachers check scores, edit comments, and approve before anything reaches a student. Approved results become a shareable, print-ready report that students and parents open from a link, without a login or an LMS.
Adjust a score or rewrite a comment, then move to the next script.
Built like a system, not a prompt
A purpose-built marking scheme editor
Choose a type for each question, a single criterion or a multi-band rubric, then enter its marks, levels, and descriptors in structured fields. Edit, reorder, and save as the department refines its standard.
A scheme library the department actually shares
Shared folders hold the department's official schemes by year, subject, and unit, and personal folders hold drafts. Every new assessment starts from the current shared version, so new staff inherit the department's scheme, not last year's PDF.
Know what still needs review
Each assessment shows how many scripts are reviewed, how many still need attention, and how many are still processing. The department dashboard shows review completion across all of them.
Versioned, auditable, remarkable
Pin a scheme version to past submissions. Remark a single script against a new version without uploading it again. Every change, whether edited or restored, stays traceable.
Four positions we won't move on.
The teacher is the marker.
AI produces a first pass. The teacher reads it, edits it, and signs it off. Judging a student's work is a professional act, and we leave it with the teacher.
Consistency lives in the marking scheme.
A shared marking scheme is the only honest basis for consistent marking. GradeSail marks against the scheme your department already uses. You can inspect it, and it stays the same across teachers, classes, and terms. The model is just the thing that applies it.
No black-box grades.
Every score traces to a criterion in the scheme and every comment to a specific point on the script, so a teacher can always explain the mark.
One setup, distributed to the team.
An admin or head of department sets up the assessment and its marking scheme once, then distributes it to teachers. Each teacher opens a ready-to-mark queue that uses the same scheme.
A draft to start from, and the final word on every mark.
Draft first
Review, don't restart
Teachers open each script to a drafted score and inline comments. Editing a draft is less work than starting from a blank page.
Every mark
Teacher reviewed
Nothing reaches a student until a teacher approves it.
Shared schemes
Consistent judgement
Explicit criteria reduce drift across scripts, teachers, and classes.
Run GradeSail on your next assessment.
Built for departments marking essays, comprehension, and extended written responses against a marking scheme.