A clearer way to hand in code
A department-shaped space for software assignments, from the brief and source files to the lecturer’s feedback.
Built for practical coursework
Programming exercises and software projects need context: what to build, how to run it and what belongs in the hand-in. Verse keeps those details together.
Give every assignment a clear starting point
The brief
Describe the task, the expected deliverables and the setup instructions the student should include.
The course rules
Set the submission format, deadline and late-work policy for the assignment.
The review context
Connect the work to its course, student or group, marking scale and feedback.
Designed around the work students build
A short programming exercise may need a source file. A larger project may need an archive or repository link, plus a README and a note on the group’s contribution.
Configure the hand-in around the assignment instead of squeezing every course into the same format.
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 feedback beside the work
Students need to understand what was reviewed and where to improve. Lecturers need the assignment context when giving that feedback.
An identifiable submission
Use the course and matriculation details to put a hand-in in the right context.
A visible submission history
Keep replacement submissions traceable, with the course’s resubmission rules guiding what is accepted.
A clear response
Put the lecturer’s feedback and mark alongside the work it refers to.