Submitting work
Assignments — projects, in most organisations' language — are the pieces of work you build and hand in for a human to mark.
Before you start
An assignment page shows the brief, the maximum score, the pass mark, and the rubric if there is one.
Read the rubric first. It is the list of things the person marking you will be looking for, written down in advance. Working from it is not gaming the system; it is the system working as intended.
Submitting
Submit project opens a short form.
| Field | Required | What goes in it |
|---|---|---|
| Repository link | Yes | The GitHub URL for your work |
| Live URL | No | A deployed or hosted version, if there is one |
| File URL | No | A link to any other file — a document, a design, a recording |
| Reviewer | No | Request a specific instructor |
| Difficulty | No | How hard you found it, 1 to 5 |
| Comments | No | Anything the reviewer should know |
Only the repository link is required. All of the URLs must be full, valid web
addresses starting http:// or https://.
Two things worth doing before you press submit:
Check the link works when signed out. A private repository that only you can open will be marked as though it were empty, because from the reviewer's side it is.
Use the comments box. "The tests for part 3 are failing and I know why but ran out of time" changes how your work is read. Silence does not.
The difficulty rating is not part of your grade. It is aggregated across the cohort and tells instructors which assignments are harder than they meant them to be.
After you submit
The submission appears under My Submissions, which has two tabs:
Unreviewed — handed in, waiting for a mark. You will see when you submitted and, once someone picks it up, who is reviewing it.
Reviewed — marked and returned, with the score and the written feedback.
You are emailed when a submission is graded, unless you have turned grade emails off in your preferences.
Submitting is worth 25 XP, once per assignment. Passing is worth 100, which is the largest single award short of finishing a course.
Statuses
| Status | Meaning |
|---|---|
| Unreviewed | Handed in, not yet marked |
| Reviewed | Marked, with a score and feedback |
| Review again | Your reviewer wants another version |
Review again is not a failure. It means the reviewer would rather see the work improved than mark it as it stands, and it is a better outcome than a low final mark on a first attempt.
Resubmitting
Where an assignment allows it, Resubmit on the submission opens the same form again.
Your previous submission and the feedback on it are kept rather than overwritten. The history of what you were told, and what you did about it, stays on the record — which is exactly what you want when a reviewer asks whether you addressed the last round of comments.
Each resubmission is a new attempt, and the attempt count is visible to your reviewer.
Reading feedback
The mark tells you where you landed. Only the comments tell you what to do differently, and those are the part worth your time.
Some organisations run an AI pre-review over submissions, which an instructor then approves, edits or rejects before anything reaches you. What you see is always what a human decided to send, whatever drafted it.
If feedback is unclear, ask. Your instructor's name is on the review.
When your work has not been marked
Marking is done by people, and queues have weather. Before chasing:
- Check the tab. Reviewed submissions move out of Unreviewed.
- Check the whole assignment has not been held back. Instructors can grade a whole batch and release it at once so nobody sees their mark before the rest of the cohort. Until that happens, your mark exists but is not yours to see yet.
- Then ask. After that, a note to your instructor is entirely reasonable.