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, 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, because quick marking only lists responses waiting to be marked. A test that's marked automatically leaves nothing for a marker to do. For the marking options that work, see Before you start.
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 |
| Quality controls | None | Seed scripts | Seed scripts, standardisation, double marking, sampling |
| 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 |
Important
A response isn't reserved while you have it open. If 2 markers work on the same one, the first to save claims it, and the second marker's save is refused with "Cannot review: the answer is not in pending review state." — the response has already moved to Reviewed (Editable).
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
The marking mode is a permanent choice. There's no way to convert an event from one mode to another, so picking the wrong one means recreating the event.
Settings¶
Quick marking is configured on the assessment event itself, in the Event Marking Settings panel, which is editable only while the event is in Draft. Three settings shape it:
Event marking mode — sets the mode for this event. Choose Quick marked event to use quick marking.
Allow Group Type filtering — lets markers filter responses by class on the Assessment Responses screen.
Enable AI Co-Marking — lets an AI marker suggest a score for each response, for a marker to review and finalise. See AI co-marking.
All 3 also exist as tenant-wide defaults for newly created events, at Settings > Assessment Event Settings. For what each one does in full, and for the settings elsewhere in the platform that affect quick marking, see Set up a quick marked event.