From assignment brief to useful feedback
A straightforward hand-in process, shaped around the course and the people using it.
Start with the course
A practical assignment works better when everyone knows what to submit, where it belongs and how it will be reviewed.
Set up the assignment
Give the task a home in its course. Define the brief, deliverables, due date and marking approach before students begin the hand-in.
Choose the hand-in format
Specify a code file, an archive or a repository link, depending on what the assignment involves.
Make the course rules visible
Set the deadline, late-work approach and whether the assignment supports a group submission.
Explain the review
Tell students what the lecturer will look for and what context to include with their work.
Let students hand in with context
Put the brief and submission fields next to each other. Students add their matriculation number, choose their work and include the notes needed to understand it.
What should go with the source?
Use a README or submission note for setup commands, dependencies and anything the lecturer needs to run the project. The exact requirements belong in the assignment brief.
What about repository links?
The course can accept a repository URL. Access requirements and the revision to review should be agreed as part of the assignment setup.
What happens after a hand-in?
A production workflow should acknowledge the hand-in and preserve its history. The interactive preview shows a local example; it does not upload files or issue an official receipt.
Review, respond and close the loop
Bring the submission details into the lecturer’s view. Review the work against the assignment, add a mark on the course’s scale and write feedback that helps the student understand the result.
The student sees that feedback with the submission it relates to.