Marko's job is to make life easier — not to surprise you. Actions that affect more than a single thing, or that are hard to undo, show you a preview before they run. You explicitly confirm before anything happens.
This article explains how the confirmation pattern works.
When confirmation kicks in
Marko asks for confirmation when an action:
- Affects more than one thing — e.g. marking a batch, marking all pending submissions in an assessment, retrying all failed submissions in an assessment, re-running a question across every submission, or flagging a whole submission for review
- Changes a question for everyone — e.g. editing a question's total marks or its answer key / criteria, which re-totals or re-marks existing submissions
- Is hard to reverse — e.g. deleting an assessment or a submission, or merging two students
- Spends a submission credit — e.g. marking a submission, or re-marking a whole submission from scratch. Even for a single submission, the card states the cost (1 submission credit) and what the re-mark will replace before anything runs
- Confirms an assessment and starts marking — see the next section
- Will use a noticeable chunk of your plan — e.g. marking dozens of submissions
For single, targeted, easily-checked actions, Marko just gets on with it. These run directly, with no confirmation card:
- Reading data, opening a page, or answering a question
- Overriding a single mark to a value you gave
- Re-running one question on one submission (this doesn't cost a credit — re-marking a whole submission does, and is confirmed first)
- Renaming an assessment, updating its metadata, or changing a submission's class
- Roster edits on a single student (archive, unarchive, assign classes, set year group)
- Saving, editing, or clearing a memory preference — memory writes never show a confirmation preview; Marko just confirms in the chat that it's done
Marko still tells you what it did, and you can always undo or change these afterwards.
When an assessment is waiting for you to confirm
By default, a new assessment pauses before marking so you can check its questions and marking context. Nothing is marked until you confirm — that's the Pause to review setting under Settings → Customisation → Marking.