How do you mark a whole class set with JeddAI in one workflow?

What does a one-workflow class-set marking process look like in JeddAI?

It is a single, continuous flow with three stages: set up your criteria once, load the whole class set, then review and finalise the drafts JeddAI produces. Instead of opening thirty scripts one at a time, you prepare your marking standard, run the entire class in one batch, and spend your time editing feedback that already tracks your criteria rather than writing each comment from a blank page.

The point of keeping it in one workflow is that nothing falls between the cracks. The rubric, success criteria and comment banks you set up are applied to every student in the same run, so the class is marked against one fixed standard rather than a standard you rebuild script by script. You still decide every final mark and comment, but the repetitive drafting happens once.

How do you set up the criteria the whole batch will be marked against?

Before you load anything, prepare the three things JeddAI marks against: your rubric, your success criteria and your comment banks. In an NCEA context that usually means the achievement standard and its criteria for the internal assessment, plus the success criteria you already share with students. The closer this setup is to how you mark now, the less you edit once the drafts come back.

You do not have to build it from scratch. If your department has an agreed marking guide aligned to the relevant achievement standard, use it, and paste in the feedback phrases you reach for most so students hear a consistent voice. A few minutes organising this once is what makes the rest of the workflow fast, because it removes guesswork from every draft.

• The assessment task or question your class responded to, for context.
• Your marking guide or rubric, aligned to the achievement standard.
• Success criteria describing what a secure response looks like.
• A comment bank of the feedback phrases you reuse most.
• The class set of responses, named and matched to each student.

How do you load an entire class set into a single run?

You load the full class in one step by connecting or uploading every student’s work before you start marking, rather than adding scripts one by one. Loading the whole set is what turns marking into a single workflow: JeddAI drafts marks and feedback for every response in the same run, applying your criteria evenly instead of you re-establishing the standard for each student.

This is also where handwritten and typed work come together. Whether students submitted documents or scans, you bring them into the one batch so the class is marked as a set. Naming each file clearly and matching it to the right student up front keeps the workflow tidy, so when the drafts return you know exactly whose feedback you are reviewing.

The load step is the moment to sanity-check your coverage. A quick look that the number of files matches your roll, and that no student is doubled up or missing, heads off the small mismatches that would otherwise surface halfway through review. Getting the set complete before you run it keeps the batch clean from the start and saves you unpicking it later.

How do you review a full batch of drafts without breaking the workflow?

Review the batch in passes rather than perfecting one script before moving to the next. First skim the marks across the entire class to check the spread looks right, then read closely where a mark sits near a grade boundary or looks out of step with the student you know. Keeping the review in one place is what holds the workflow together.

Triaging this way keeps your judgement where it counts. Secure, clearly mid-range responses usually need only a light check, while borderline cases and unusual answers get your full attention. You accept the drafts that match how you would mark by hand, sharpen the comments that miss nuance, and adjust any mark you disagree with, because nothing is finalised until you approve it.

• First pass: skim marks across the class and check the spread.
• Second pass: read closely near grade boundaries and surprising results.
• Accept drafts that already match how you would mark by hand.
• Edit the comments and marks that miss context only you can see.

How does one workflow keep marking consistent across the class?

One workflow keeps marking consistent because every student is drafted against the same rubric and comment bank in a single run, rather than a standard that drifts as you tire. When you mark thirty scripts by hand across several sittings, the first and the last can pull apart; batching from one fixed set of criteria measures every response with the same yardstick.

That consistency matters in New Zealand, where internally assessed NCEA work is subject to moderation. Marking the class as one set, against the achievement standard, makes it easier to show that every student was judged on the same basis. Your editing then goes into the responses that genuinely need a second look, not into holding the standard steady in your head.

It also makes reporting cleaner. Because the whole cohort was marked in one pass against a shared standard, the marks you hand back sit on the same scale, so grade distributions and any later verification tell a coherent story rather than reflecting how tired you were on a given evening. One workflow gives you a record that is easier to stand behind.

How do you mark a whole class set with JeddAI while staying in control?

You stay in control by treating every draft as a starting point you approve, edit or override. JeddAI removes the repetitive drafting across a class, but you make the final call on each mark and comment, the way you would check a colleague’s marking before it goes back to students. Faster batch marking never means handing over your professional judgement.

A tool like JeddAI helps you apply the same criteria evenly across a whole class and cut the time spent drafting routine feedback, while you review and finalise every result. Built in Australia and used across Australian and New Zealand classrooms, it keeps the workflow anchored to your own standards. You can Get started with JeddAI on a single class set and see how it fits the way you already mark.

Frequently asked questions

Can you mark part of a class before everyone has submitted?

Yes. You can run the responses you have and add late submissions to a later batch. Each run drafts against the same criteria, so work marked separately stays consistent.

Does marking a whole class in one workflow work for NCEA internal assessments?

Yes. You set up the achievement standard and its criteria once, then mark the class against them. You still review and finalise every result, and normal moderation processes still apply.

How big a class set can you mark in one run?

The practical limit is your own class size. The workflow is built to draft feedback for every student against the same criteria in a single batch, whatever the number.

Do handwritten and typed responses go through the same workflow?

Yes. You bring scans and typed documents into the one batch so the whole class is marked as a set, rather than splitting the workflow by submission type.

Get started with Jeddle

Jeddle gives teachers and students instant, syllabus-aligned feedback powered by JeddAI.

Get started with JeddAI

Looking for study material? Browse Jeddle's Australian-English subject resources, or explore more articles on Using Jeddle.