Plan a final year project backwards from your submission date: fix the dates your module sets, then decide when each chapter needs a full draft, leaving room for ethics approval, supervisor feedback and one complete revision. Here is a way to build that plan, and the places where projects usually slip.
Check my final year projectYour module or programme handbook sets the fixed points: when a proposal is due, whether and when an ethics application goes in, any interim submissions, the final submission and, in some programmes, a presentation. We do not list dates here, because they differ per institution, programme and year. Put them in a calendar first.
Then add everything else that competes for the same weeks: exams before and after Christmas, other module deadlines, placement, part-time work, the gap when your supervisor is away. A plan that ignores these looks generous in October and falls apart in February.
Students rarely run out of time on writing alone. The weeks disappear in places that are hard to control. Ethics committees meet on their own schedule, and a request for changes can add a round. Recruiting participants is slower than expected, especially in organisations where someone else has to say yes. Transcribing an hour of interview takes several hours. A literature review expands to fill whatever space you give it.
The chapter that suffers is usually the discussion, written last and fastest, although it is where much of your own thinking shows. If your plan leaves the discussion for the final week, move it forward.
Put one buffer after data collection, because that is where delays outside your control land. Put the second before submission, so a late comment from your supervisor or a printing problem does not become a crisis.
Ask your supervisor at your first meeting how much notice they need to read a chapter, and plan backwards from that. A draft sent two days before a deadline cannot get useful comments, however willing your supervisor is.
Keep the plan to one page: the milestones, what you need from your supervisor and when, and the two or three risks most likely to delay you, such as access to a site or a slow ethics decision. If your proposal asks for a Gantt chart, make one; otherwise a simple table does the job. Look at it once a month and change it when reality changes. A plan you have adjusted is more useful than one you abandoned.
Put an outside reading in your plan as a milestone, not as a last-minute check: after your first complete draft, with enough days left to act on it. Esmond evaluates the draft you wrote and marks where the argument, method or use of sources is weaker. It does not plan your project or write any part of it.
Be straight with yourself: Esmond works with language models, so using it is a form of AI use. Rules on AI differ per university, programme, module and assignment. Check your module or programme handbook before you upload, and if it is unclear, ask your supervisor or module coordinator and declare the use if your institution asks you to.
A review costs from €3.99, with a free preview first. The price follows the length of your document and you see it before you pay. No subscription, no account.
Earlier than feels natural. Writing up your method while you collect data, and drafting your literature review while you read, saves weeks at the end. Your module handbook sets the formal milestones.
It depends on your institution, the committee's schedule and the risk level of your project. Ask your supervisor at the start, and plan data collection so it does not depend on a best-case date.