| Mon 16 Nov 2026 |
Briefing lecture — your brief is presented. Students see the design briefs for the first time. Your brief needs to be with the organisers in good time before this; ask them for the current cut-off. |
| Thu 21 Jan 2027 |
Teams announced — expect to be contacted. Groups, clients and briefs are announced. Your team elects a contact person who will introduce themselves and ask to book Meeting 1. |
| Week 1 · 21–27 Jan 2027 |
Client meeting 1 — requirements. Clarify what you actually need and what success looks like. The team is advised to meet as early in the week as possible. |
| Week 2 · 28 Jan – 3 Feb 2027 |
Client meeting 2 — specification & plan. You receive the draft Functional Specification and Project Plan at least 24 hours beforehand. This is the meeting to correct the scope. |
| Week 4 · 11–16 Feb 2027 |
Client meeting 3 — progress. Progress Report 1 reaches you at least 24 hours beforehand. |
| Week 6 · 25 Feb – 3 Mar 2027 |
Client meeting 4 — progress. Progress Report 2 reaches you at least 24 hours beforehand. This is the last formal meeting before the team freezes the code. |
| Thu 11 Mar 2027, 12 noon |
Code freeze — team stops building. The team submits its video and a full copy of the repository to the examiners. No credit is given for anything added after this, so expect development to stop here. |
| Mon 15 Mar 2027 |
Videos online — you can watch and vote. Videos are available to staff, clients and students from Monday to Wednesday, and you can vote for your favourites. |
| Wed 17 Mar 2027, afternoon |
Exhibition and awards — you are invited. Public screening of the videos, an interactive exhibition with demonstrations of every project, and the awards. |
| Wed 17 Mar 2027, by 5pm |
Final Group Report reaches you. The last possible time for the team to email you the final report as a PDF. |