Course task submissions – teacher's guide

1 What this view is

Course task submissions is where you grade by hand the course tasks that do not use AI grading. When you create a course task and leave AI checking switched off, the students’ answers are not graded automatically but are routed to this view to wait for the teacher’s grading. Approved / rejected tasks always come here too, because they are always graded by the teacher.

Course task submissions→ Course → Task → Submission→ Points + feedback or Approved · Needs revision · Rejected→ Save grade or Return for revision

You can either grade the answer right away or return it to the student for revision with feedback. The student revises the answer and sends it again, and the revised version comes back to this view to be graded (sections 6–8).

The list combines the local course structure with the student and grade data in the cloud. Only tasks whose AI grading is switched off are included – tasks handled by the AI are graded automatically and are not shown here.

2 Structure of the view and filtering

Submissions are grouped in three levels: course → task → submission. At the top are the status filter and the Refresh button. The task’s header row shows the number of submissions and, for a points task, the maximum points (e.g. max 6 pts); an approved / rejected task shows Approved/rejected.

The All filter: course (📚) → task (📝) → submission rows. The rows show every status: Revised version, Ungraded (also an empty answer), Needs revision, Graded and Graded ⚠.

Status filter

To grade – the default, i.e. your work queue: new ungraded submissions and revised versions sent by students.
Needs revision – submissions you have returned to the student for revision and whose revision is still awaited.
Graded – submissions already graded (approved and rejected ones too).
All – all of the above.

In the All view the order is: first those to grade (newest first), then those that need revision, and last the graded ones. ↻ Refresh fetches the list again from the cloud – for example when you want to see whether the student has already sent a revised version.

If no submissions match the filter, the message “No manually-graded course task submissions.” is shown.

3 Submission row and statuses

Each submission row shows the student, a short preview of the answer, the submission time and a status badge. The arrow (▶) at the start of the row opens the submission.

Student – name and student number (any school code prefix is left out).
Preview – the beginning of the answer as text; an empty answer is shown in red as (Empty answer), so you see right away that the student wrote nothing.
Submission time – when the student submitted.

Status badges

Ungradedwaiting to be graded

Needs revisionreturned to the student for revision, waiting for their revision (section 6)

Revised versionthe student has sent a revised answer that is waiting for your grading (section 8)

Graded: 7/8 ptsgraded, points shown

✓ Approvedan approved / rejected task that has been approved (section 5)

✕ Rejectedan approved / rejected task that has been rejected (section 5)

Graded: 7 pts ⚠the student has edited the answer after grading (section 10)

4 Grading a submission

Click a submission row – it opens and shows the task prompt, the student’s answer and the grading form.

An opened submission: task prompt, model solution (opened), the student’s answer and the grading form with points and feedback filled in. Buttons: Save grade and Return for revision.

Parts of an opened submission

Task prompt – a yellow box with the task’s question.
📖 Model solution – an expandable block; click it to see any model solution for comparison (it takes no space by default).
Student answer – the student’s submission as it is (images and formulas are shown too).
Points – enter the points; if a maximum has been set for the task, it is shown (e.g. max 6) and works as the upper limit. In an approved / rejected task the result buttons replace the points field (section 5).
Feedback – free-text feedback the student sees.
💾 Save grade – saves the points and feedback. The row’s status changes to Graded, and the grading time appears next to it.
↩ Return for revision – sends the answer back to the student with your feedback, without points (section 6).

After saving, the submission moves under the “Graded” filter. The points and feedback are shown to the student in their own app.

The model solution opens for the student only after your grading. In manually graded tasks the student does not see the task’s model solution right after submitting, but only once you have saved the grade. Until then they see the text “The model solution is shown once the teacher has graded the task”. This way the model solution is not revealed before any revision round has taken place.

5 Grading an approved / rejected task

When a task’s grading method is Approved / rejected (set on the task card in the course editor, see Tasks and AI checking), it is not scored. In the opened submission, three result buttons replace the points field and the Save grade button:

✓ Approved – the work is approved. Feedback is optional. An approved task counts towards the student’s course progress and can be used as an unlock condition, but it adds no points.
↩ Needs revision – the same as Return for revision (section 6): the student revises the answer based on your feedback and sends it again. Feedback is required.
✕ Rejected – the work is rejected. Rejecting requires feedback – if the field is empty, the app asks: “Write in the feedback why the submission is rejected.” Before saving, the app asks for confirmation. The student sees your feedback and cannot send a new version; they are told to contact the teacher.

After saving, the form shows Current result: Approved or Rejected, and the row’s status badge becomes ✓ Approved or ✕ Rejected.

You can change the result later. The result buttons of a graded approved / rejected submission stay available: for example, you can approve work you rejected earlier once the matter has been sorted out with the student, or return it for revision. ↻ Remove grade makes the submission ungraded again (section 9).

6 Return for revision

If an answer is unfinished or needs correcting, you can give the student a chance to improve it before grading. ↩ Return for revision (in an approved / rejected task ↩ Needs revision) sends the task back to the student with your feedback. No points are saved – you grade the task only when the revised version comes back.

How to return a task

Open the submission by clicking the row.
In the Feedback field, write what the student needs to correct or add. Feedback is required – if the field is empty, the app asks: “Write in the feedback what the student needs to fix.”
Press ↩ Return for revision and confirm.
The message ✓ Returned for revision appears next to the button, and the row’s status changes to Needs revision.

Feedback written and the task returned for revision: the form shows ✓ Returned for revision, and the Return for revision button is no longer shown. Before sending, the app asks for confirmation in a separate window.

While the submission needs revision, the opened submission shows the note “Returned for revision [time] — waiting for the student.” The Return for revision button is hidden then, because the task is already with the student. You can still save a grade directly if you decide to grade the answer as it is.

You can also return a task that has already been graded: the earlier points are then hidden, and the student can revise the answer. A task can be returned for revision several times – every round is saved in the version history (section 8).

7 What the student sees

In the student app, the student gets the notification The teacher returned the task “[task name]” for revision. In the task list, the task has the badge Needs revision.

The student app’s task card in a revision round: status Needs revision, the answer editable, the Submit revised answer button and the teacher’s feedback below the answer (image from the student app’s guide video).

Feedback – the student sees your instructions on the task card below the answer field, in the box Needs revision — the teacher returned this task to you.
The answer opens for editing – the previous answer is ready in the editor, so the student can add to it and does not have to start from scratch.
Submit revised answer – when the student sends the revision, the task again waits for the teacher’s grading.
No points and no model solution – during a revision round the student sees neither points nor the model solution. The model solution opens only when you save the grade.
Approved / rejected task – the student sees the result Approved or Rejected instead of points. In a rejected task the answer field is locked, and the student is told to contact the teacher.

In the study calendar and the course progress, a task graded by the teacher is marked as done only once you have graded it (an approved / rejected task: once you have approved it). A task that needs revision or has been rejected is not done.

8 Revised version and earlier versions

When the student sends a revised answer, the submission returns under the To grade filter with the badge Revised version. The opened submission shows the note “The student has submitted a revised version (version 2).”

A revised version waiting to be graded: the version 2 notice, the opened “Earlier versions” block (the previous answer and the feedback you returned it with) and the previous feedback above the feedback field. The feedback field is empty.

Student answer — version n – the newest answer, to be graded. The version number increases with each revision round.
🕘 Earlier versions – an expandable block with every version previously returned for revision (newest at the top): the time of return, the answer at that time and the feedback you gave. So you can easily see what the student changed.
Previous feedback (returned for revision) – the feedback you returned the task with is shown above the feedback field. The field itself is empty, so the old feedback is not sent again by mistake.
Grade the revised version as usual (💾 Save grade, or the result buttons in an approved / rejected task) or return it for revision once more.

A task that needs revision has no points – points are given only when you save a grade for the revised version.

9 Remove grade

A graded submission has an extra button ↻ Remove grade. It removes the points (or the approved / rejected result) and feedback you gave, and the submission becomes ungraded again (under the To grade filter). The student’s answer does not change, and the task does not open for editing for them.

The form of a graded submission: Save grade, Return for revision, Remove grade and the grading time. Removing asks for confirmation in a separate window.

Note: this button used to have a different name (it reopened the task). If you want the student to be able to add to or correct their answer, use Return for revision (section 6) – Remove grade only removes the grade.

10 Answer edited after grading

If the student edits their answer after you have already graded it, the app warns you. The status is shown in red (Graded: 7 pts ⚠; in an approved / rejected task the badge ends with ⚠) and the opened submission has a warning bar.

The change warning. “Show originally graded answer” has been opened: the graded version is shown below the current answer, and the button now reads “Hide original”.

The warning bar tells you that the current answer differs from the graded one.
Show originally graded answer – shows the saved graded version below the current answer, so you can compare what the student changed.
You can update the points and feedback and save again – the warning then disappears and the new answer is saved as the graded version.