Every deadline,before the crunch.
Point it at your schedule and it reads every due date, heat-maps the whole semester, and turns any brief into a three-day plan — so nothing sneaks up on you.
A tool I built from scratch to survive a full course load.
A semester is aminefield of dates.
Every module has its own briefs, tests and exams — buried in email, PDFs, a learning portal and a group chat. Miss one and the marks are simply gone. A calendar app won’t read a 12-page brief for you.
Threat-modelling case study
Weight 20% · one submission
2d 4h
A single assignment’s countdown races from two days down to overdue while it hides among email, PDFs and chats — the marks are lost.
Point it at yourschedule once.
Drop in the year’s assessment schedule — a PDF, a screenshot, a pasted timetable. Claude reads it and pulls out every deadline as a structured row: module, type, weight and due date, ready to review.
Portfolio of Evidence — Part 2
WEBD201 · Project
Normalisation & SQL worksheet
DBMS202 · Assignment
Threat-modelling case study
SECP210 · Assignment
Subnetting class test
NETW220 · Test
Final written exam
SECP210 · Exam
A schedule PDF is dropped into the app; Claude reads it and extracts five structured deadline rows with module, type, weight and due date.
See the crunchbefore it forms.
Every day is scored by what’s due on it — count, weight, and whether an exam or test lands — then painted on a heat map. The hot zones surface weeks out, so you start the heavy stretches early instead of the night before.
A month grid where each day is coloured by its workload — cool blue for light days, amber as work builds, red for the two crunch days carrying an exam and multiple submissions.
Drop a brief.Get the attack plan.
Upload the assignment brief to any deadline. Claude reads the whole thing and hands back the difficulty, the hours it’ll really take, the requirements, the penalty traps, and a checklist — everything you’d miss skimming it at 1am.
Portfolio of Evidence — Part 2
Build and document the second increment of your web portfolio: a responsive multi-page site with a working contact form, deployed live, plus a short reflection on your design decisions.
Requirements
Watch out
• Late penalty: 10% per day, capped at 3 days
• Unreferenced code from templates = plagiarism
Checklist
A brief is dropped into a deadline; Claude analyses it and fills the panel with difficulty, estimated hours, requirements, penalty warnings and a checklist.
The crunch, asthree calm days.
From that analysis, Claude sequences the work into a three-day plan — each day a single focus and a short list of timed tasks. The red-hot brief becomes a to-do list you can actually start.
Understand & scaffold
Build the hard parts
Polish, reflect, submit
Claude’s three-day plan for the brief — day one scaffolds, day two builds the hard parts, day three polishes and submits, each task carrying a time estimate.
Then watch itcool to done.
Move each deadline along as you go — pending, in progress, submitted, done. Module progress fills in, the heat drains off the calendar, and the finish line stops being a surprise.
0
tracked
0
due in 7 days
0
done
Portfolio of Evidence — Part 2
WEBD201 · Project · 30%
A dashboard: six deadlines tracked, three due within a week, two done. One deadline cycles from pending to done while three module progress bars fill in.