How many weeks do you actually have?
Not the number on the calendar. The number left after exams, breaks, and the buffer you will need when your guide asks for changes in February. Most students are surprised, and it is better to be surprised now.
Enter your submission date to see how many weeks you actually have.
Why the buffer is not negotiable
Every final year project loses time to the same four things: a guide asking for a change after review, a feature that breaks the week before submission, the report taking twice as long as planned, and something in your personal life that does not care about your deadline.
Four weeks covers those. Students who plan without a buffer are not planning to finish early — they are planning to submit something incomplete, they just do not know it yet.
Common questions
- How many weeks do I need for a final year project?
- Between nine and sixteen usable weeks for a moderate project, where usable means after exams, breaks and a four-week buffer are removed. Most students who believe they have twenty-four weeks have around eleven once those are subtracted honestly.
- Why should I keep a four-week buffer?
- Because guides ask for changes late, features break in the final fortnight, and the report always takes longer than planned. A buffer is not slack — it is the part of the schedule that absorbs everything nobody planned for. Projects without one submit incomplete.
- What if I have almost no time left?
- Cut scope hard rather than working faster. Pick one core feature, build it properly, document it honestly, and declare the rest out of scope in chapter one of your report. A small project you can defend beats a large one you cannot.
Not enough weeks?
That is the situation this site exists for. The project gets built for you — code, report, diagrams, deployment — and your remaining weeks go into understanding it in daily sessions rather than fighting it alone.