Track 1
Student marks analyser
A command-line tool that reads a class marks file, calculates averages and highlights students who need support. Teaches file handling, dictionaries and clean function design.
Outcomes
Defined skills, a project a student can defend, and records the institution can actually file. Stated plainly, with the limits included.
Representative projects for each track. Exact briefs are adapted to the branch and to what the cohort is capable of finishing well.
Track 1
A command-line tool that reads a class marks file, calculates averages and highlights students who need support. Teaches file handling, dictionaries and clean function design.
Track 2
A script that takes lecture notes or a PDF and returns a structured summary and question set using an LLM API. Students learn prompt design and how to handle API responses safely.
Track 3
A deployed web application that answers questions from a college's own documents using retrieval. Students ship it, share a link and explain every part of the pipeline.
Track 4
A system where separate agents plan, search, draft and review, coordinating through tool calls and shared memory. Students handle failure cases, not just the happy path.
Track 5
An automation for something the student actually does weekly — attendance collation, report formatting or content drafting — built with no-code AI tools.
Track 6
Students complete the progression end to end, finishing with a GitHub profile that shows range: fundamentals, tooling, a deployed app and an agentic system.
Assessment is designed to show whether a student can do the thing, not whether they attended.
Each week's practice set is checked for completion. This is the earliest signal that a student is falling behind, and it is where we intervene.
Every weekThe final project is built in stages across the track, so progress is visible throughout rather than only at the end.
OngoingStudents walk through their own project and answer questions about the choices they made. Copied work becomes obvious immediately.
Final fortnightThe college receives attendance, practice completion and project status per student — reported accurately, including students who did not finish.
End of cohortMost colleges run stages one and two in the first semester and stages three and four in the second.
Python fundamentals, or no-code tools for non-CSE branches
Prompting, APIs, workflows and simple automation
A first AI application, deployed and explained
Optional agentic systems for students ready to go deeper
A programme is only useful to a college if the claims around it are accurate.
Students who attend under roughly two thirds of sessions rarely complete a project, whatever the track. We flag this early rather than at the end, so the department can act while it still helps.
Next step
Tell us your student numbers, branches and preferred months. We will send a written proposal with dates, pricing and deliverables — usually within two working days.