Quick marking¶
Quick marking is the simplest of the 3 marking modes in Janison Insights. There's no marking project, no marking team, and no quality controls. A marker opens one screen, works through the extended-text responses for an assessment event, and submits scores as they go.
Use it for low-stakes assessments with straightforward scoring: class quizzes, progress checks, formative tasks. If you need standardisation, double marking, blind quality monitoring, or sampling, none of those controls exist in quick marking. Use a standard marking project or an enrolment based marking project instead.
What quick marking covers¶
Only extended-text responses reach the Assessment Responses screen, where markers work. Multiple choice, numeric entry, and every other item type are scored by the platform and never reach a marker here.
So quick marking isn't a general-purpose marking screen — it's the extended-text part of a test that is otherwise marked automatically.
The test itself also has to be set up to expect manual marking. Quick marking only lists responses waiting to be marked, so the test's marking option has to leave something for a marker to do:
- Mixed or Manual — extended-text responses reach the marker.
- Automatic — the test is marked on submission, so nothing reaches a marker.
- Do not Mark, or a survey — there's nothing to mark.
How it differs from the other marking modes¶
Every assessment event uses exactly one marking mode, chosen on the event itself. This is what you're picking between.
| Quick marking | Enrolment based | Standard | |
|---|---|---|---|
| Marking project | None | Required | Required |
| Marking team and roles | None | Chief, senior, base markers | Chief, senior, base markers |
| Quality controls | None | Seed scripts | Seed scripts, standardisation, double marking, sampling |
| Where markers work | Assessment Responses screen | Marking project | Marking project |
| Work allocation | None — every marker sees every response | Scripts allocated to markers | Scripts allocated to markers |
| Items marked | Extended text only | All manually marked items | All manually marked items |
| Best for | Low-stakes, simple scoring | Staggered or open test windows | Whole-cohort summative assessment |
The trade-off is deliberate. Quick marking removes the governance layer to remove the setup cost. You get a marker onto responses in minutes, but you give up the mechanisms that keep marking consistent between markers.
Important
There is no work allocation in quick marking. Every marker who can reach the screen sees the same pool of responses, limited only by the classes they have access to. Nothing is locked while someone works on one.
If 2 markers open the same response, the first to save claims it. The second marker gets an error, because the response is no longer waiting to be marked.
Filtering by class is the only way to divide the work, and each marker applies that filter themselves. It isn't an assignment, so agree who takes what before you start.
What you need to do¶
Quick marking has 2 halves, usually done by different people.
An administrator sets the event's marking mode to Quick marked event while the event is still in draft. They can also add group types so markers can filter by class, and switch on AI co-marking. See Set up a quick marked event.
A marker then works through the responses from Marking > Quick Mark Assessments once the event is in delivery. See Mark responses.
Warning
Set the marking mode before you progress the event out of Draft. The Event Marking Settings panel becomes read-only as soon as the event leaves draft. There's no way to convert an event from one marking mode to another afterwards.
Settings¶
Administrators configure quick marking on each assessment event, in the Event Marking Settings panel of the event. The panel is editable only while the event is in Draft.
Event marking mode — sets the mode for this event. Choose Quick marked event to use quick marking. The other options are Standard marking project and Enrolment based marking project.
Allow Group Type filtering — adds one or more group types, which lets markers filter responses by class on the Assessment Responses screen. If you don't add any group types, every response in the event is included and the class filter isn't shown.
Enable AI Co-Marking — lets an AI marker suggest a score for each response, which a marker then reviews and finalises. This option only appears when an AI marking provider is active and has at least one model configured. See AI co-marking.
The same 3 settings exist as tenant-wide defaults at Settings > Assessment Event Settings, applied to newly created assessment events. There they're labelled Default event marking mode, Default Group Type filtering, and Enable AI Co-Marking by Default.
For the full detail on each, including what happens when you leave group types empty, see Set up a quick marked event.