A submission is a piece of work a learner has handed in: an assignment they uploaded, or an attempt at a quiz or an exam built inside the course. Submissions gathers all of them on one board, so that a teacher can work through a week of marking in a single place instead of opening a separate screen for every exercise.

Two people normally live here. The subject teacher opens the board each morning and clears the oldest unmarked work first, because a correction that arrives three weeks late teaches nothing. The head of department opens it to see how much is still outstanding before the end of term. Teachers see only the courses allocated to them; the secretary and the head of school see every course in the school.

One rule shapes the whole screen: corrected work stays invisible to the learner until it is published. You can score, comment and revise as often as you like, and nothing leaks.

One row is one learner’s answer

The Type column tells you whether the row is an Assignment, a Quiz or an Exam. Next comes the item — the assignment title, or the module and lesson for a quiz or exam — then the Course, the Student with their matricule, and the moment they submitted. A learner who retakes a quiz produces a new row, and the earlier attempt stays on the board, which is usually what you want when a result is disputed.

The three statuses tell you where each row stands

Submitted means nobody has corrected it yet. Corrected means scores and comments are saved but the learner still cannot see them. Published means the correction is out. Filtering on this column is how you work the queue properly: filter on Submitted and you have your marking list, filter on Corrected and you have your release list.

The Published column is the one the learner sees

A tick means the learner has been told. That matters for timing: a class where everything is marked but nothing is published looks identical to a class where nothing has been touched — except that the first is one click from being released, and the second is a week of work away.

Open the row and read the work

Click the magnifier on a row to open the review. It shows the learner, the item and its maximum score, the learner’s answer to every question, the correct answer where there is one, and any attachments. The review panel is where you work.

Every question needs a score before the review saves

Give each question a score in the Score for this question box. For a quiz or an exam the ceiling is that question’s own points, and a higher figure is refused. The final score is then the sum of the question scores, so there is no separate total to enter. Saving is only accepted when every question carries a score: a half-corrected review is not written at all, and that is deliberate — a half-saved correction leaves the learner holding a result nobody chose.

Remarks and the redo request

Use Add remark on any question to leave written feedback the learner will read. Require a redo asks the learner to submit the work again, and it can only be used with a remark explaining why — so nobody is ever told to redo something without being told the reason. Work with no questions at all, such as a handwritten essay uploaded as a file, is marked in the Overall correction panel instead, with one score against the item’s maximum.

A published correction is locked

Once you publish, the learner can see the score and the remarks, and the row refuses further edits with a message telling them to resubmit. That is on purpose: a mark that can change quietly after a learner has read it is not a mark. When a genuine mistake is found, the honest route is to ask for a resubmission and mark the new attempt, which leaves the history intact and shows the correction happening.

AI correction produces suggestions, never decisions

Inside the review, Correct with AI grades the learner’s answers and returns a proposed score for each question, with remarks you can keep, edit or delete. It runs on prepaid AI credits, and you can stop it mid-way with Stop — in which case nothing is written at all. Whatever it proposes lands as a draft: read it, check the arithmetic, then save. If it suspects the work was produced by AI rather than by the learner, it says so and shows the evidence; that verdict is yours to keep or to discard.

Publishing is a scope decision, not a per-row one

Use Publish results in the toolbar to release everything in one go. Choose a Type and a Course, and every unpublished correction inside that scope is published together — so the whole class sees its results at once instead of discovering them one by one across a week. The right moment for it is after a class-wide marking session, before the module closes.

Why a released result is hard to change

Once results are out, the record stops being yours and becomes the learner’s. That is why this screen makes publication an explicit act with a named scope, keeps every score and remark in the activity history, and locks published rows against edits. When an error really does reach a learner, the honest repair is a new correction on a new attempt — visible to everyone, rather than a quiet change to a number they have already read.