A clear place to hand in your work
Find the brief, choose the right files or repository and keep the hand-in connected to your course.
Know what belongs in the submission
The assignment should make its deliverables clear. Verse brings the brief and hand-in fields together, so the next step is easier to follow.
Put the assignment in view
Read the brief
Check the task, expected deliverables, deadline and course rules before choosing your work.
Add your details
Identify the hand-in with the matriculation number and, where allowed, the members of your group.
Include what helps the review
Add setup notes and the files or repository the lecturer needs to understand the project.
Source files with the context they need
A working program is easier to review when its setup is clear. Use your README or submission note to explain how to run the work and what is included.
Sample course · CSC 201 · Programming fundamentals
Collections and search
Build a program that stores, searches and sorts a collection. Include the source and a README explaining how to run it.
- Hand in
- A code archive or repository link
- Include
- Matriculation number and setup notes
- Review
- Lecturer feedback alongside the submission
Keep track of what comes next
A submission history helps distinguish a replacement from an earlier version. The course’s policy should make clear whether and when replacements are allowed.
When the lecturer gives feedback, it belongs with the assignment and submission it refers to.
Questions about the preview