For a class's instructors and support staff, who review its submissions, and for Owners and Admins, who publish the projects, set tracks and release them to a class.
- Who can do what
- An Instructor or Support member of a class reviews that class's submissions; Owners and Admins review every class and are the only ones who can open Manage the Project Lab. Guests never review. Nobody reviews their own submission, and staff cannot submit — use a separate student account to try the student side.
- Set up a class
- Everything is in Manage the Project Lab, reached from Trainer tools on the lab page.
- 1Projects: open each brief and press Publish. Under Who can read it once published, choose Everyone (the public site too) or Members only. Until then a brief is a draft only staff can see.
- 2Tracks & trainers: pick the class, select students and use Set track for selected — Data Engineering or Data Science.
- 3In the same tab, make each trainer Instructor (reviews) or Support (reviews).
- 4Schedules: Release a track to a class with a Start date (Day 1), and choose whether late work and resubmissions are allowed. Day N opens on the start date plus N − 1.
- Review a submission
- The review workspace lists submissions from your classes, newest first, filtered by status, class, specialization and project; late ones are marked Late.
- 1Open a submission. It becomes Under review, and the student can no longer replace it.
- 2Open the repository (it opens in a new tab) and read the code, its README and the student's notes. The submission shows the default branch and the latest commit GitHub confirmed when it was submitted.
- 3Where the project asks for them, open the report, demonstration video and slides links listed under the repository.
- 4Mark each criterion of the project's rubric — always out of 100. Most projects use Correct functionality /35, Python fundamentals /30, Code organization /15, Error handling /10, Documentation /10; a project with its own rubric shows its own criteria. Where the project offers bonus marks, give them in the Bonus box: they are shown beside the score, never added into the 100. Under each mark, say why — the student is emailed every mark with your reason beside it.
- 5Press Approve, or write what needs to change and press Request changes — feedback is required to request changes.
- Re-check a repository
- Re-check link asks GitHub about the repository again and refreshes its latest commit. If GitHub says it has been deleted, made private or emptied, the submission shows Repository unavailable — in the list and on the submission. If GitHub could not be reached, it says so and keeps the last result; that says nothing about the repository. Re-checking never changes a status, a mark or a decision: those stay yours. A commit date is the committer's own clock, so it shows the repository has work in it, not who wrote it or when. Submissions made with uploaded files before submissions became GitHub-only are labelled Legacy and keep their files.
- Email students about their projects
- Owners and Admins: in Review submissions, set the filters to the students you mean — a class, a specialization, a project, a status — and press Email students. Choose Students on this list for the submissions shown, or Everyone enrolled for everybody on those projects whether or not they have submitted (status does not narrow it). It shows how many students and who before anything is sent. Write a subject and a message — **bold**, a line starting "## " for a heading and lines starting "- " for a list — and add a CC if you want a copy of each; each student gets their own copy addressed to them by first name, with a link to their projects, and replies come to you. Send test to me first, then Send, and confirm. If a submission arrives while you write, the count changes and you are asked to check the list again before it sends. Every email is recorded.
- Reopen, re-mark and export
- Reopen takes an approval back so the student may submit again; the approval and its marks stay in the history. If you see already reviewed or replaced, the student submitted again or another trainer marked it first: reload and mark the current attempt. Export results (CSV) downloads the current filter with every criterion, the total, the reviewer and the feedback.
- See who is enrolled and how it is going
- Overview shows active challenges, assigned students, submission and completion rates, the average score, pending reviews and performance by project. Enrolled lists everyone on a track — name, email, class, whether they Enrolled themselves or were Assigned by track, their days, submissions and approvals — with search and a CSV export. The enrolled count on a project includes both.
- Change dates safely
- Releasing a track to the same class again moves its dates and never touches a submission. A project's schedule cannot be removed from a class once anybody in it has submitted; change its dates instead. A file resource that is not public can only be downloaded by signed-in people, even on a public project.
- When a student is stuck
- Check three things: their track, their class's schedule, and their submission's status. Not part of your specialization yet: set their track. Not been released to your class yet: release the track, or the start time has not come. (A passed deadline never blocks anyone: late work is always accepted and tagged Late.) Resubmissions are not allowed: allow them on that schedule. A repository refused as missing or empty: it is private, misspelt or has no commits, and the student must fix it on GitHub. Told to try again shortly, many students at once: GitHub is rationing our checks — ask the platform team to set GITHUB_TOKEN. A submission a trainer cannot see was made under a class they do not review, or was replaced — check Enrolled, and filter the queue by All. If none of that explains it, send the platform team the person's email, class, the project's track and day, the exact message with a screenshot, and the time in Nairobi.