Be specific
Connect the comment to the work submitted and the expectations in the brief.
Review the work with its context
Keep the brief, submission details and feedback together when reviewing practical coursework.
A submission is more than a filename
The course, student details, setup notes and version all help explain what you are reviewing. Put those details beside the work.
Start with the right information
The assignment
Keep the task and expected deliverables in the review context.
The hand-in
See the course, matriculation number, source-file or repository details and the student’s note.
The course policy
Use the deadline, late-work approach and marking scale defined for that assignment.
Make feedback useful to the student
“Your search works correctly. Explain the input assumptions in the README, and separate the sorting logic from the interface.”
Illustrative feedback for a programming assignment
Show the next step
Explain what the student could improve or investigate next.
Keep the context
Attach the response to the submission it relates to, alongside the mark where appropriate.
A review flow your course can shape
Some courses use a single mark. Others need a more detailed rubric or a second review. Those requirements should be agreed during department setup.
The workspace preview demonstrates a mark and feedback note using a configurable total. It does not execute student code or automatically grade the work.