Typical FYP timeline (FYP1 and FYP2)
Many universities run the final year project over two semesters, often called FYP1 and FYP2, though the names and arrangements vary. FYP1 usually covers topic selection, proposal, literature review and methodology. FYP2 covers data collection or system development, analysis, writing and the final presentation or viva.
Your timeline depends on your university's calendar and assessment dates. Ask your coordinator for the official schedule, and then build your own plan with earlier internal deadlines.
Month-by-month milestones
A sample plan for a 12-month project (adjust it to your calendar):
| Period | Milestone |
|---|---|
| Months 1 to 2 | Choose topic, meet supervisor, define problem and objectives |
| Months 3 to 4 | Literature review and proposal; submit FYP1 deliverables |
| Months 5 to 6 | Methodology finalised, ethics approval if needed, instruments or design ready |
| Months 7 to 9 | Data collection or system development |
| Months 9 to 10 | Analysis or testing; draft results |
| Months 10 to 11 | Full draft, supervisor feedback, revisions |
| Month 12 | Final report, formatting, presentation |
Working with your supervisor
Your supervisor guides your work but does not do it for you. Agree on how often you will meet and how you will communicate. Before each meeting, send a short update with what you completed, what you are stuck on and what you plan next.
Take notes and send a summary after the meeting so you both have a record. Respond to feedback promptly and ask for clarification when it is unclear. Our supervisor guide covers this in more detail.
Time management
Break the project into weekly tasks and give each a clear output, such as "draft section 2.1" instead of "work on literature review". Set deadlines a week or two before the official ones, to leave room for delays.
Schedule fixed blocks for FYP work alongside your other subjects, and use a simple tracker or planner. Back up your files in more than one place. Start writing early, because writing often shows gaps in your understanding that you can still fix.
Common reasons projects fall behind
Common causes of delay are:
- A topic that is too broad or too ambitious.
- Delay in getting survey permissions, data or software access.
- Collecting data before the instrument has been checked.
- Leaving the writing to the end.
- Long gaps between supervisor meetings.
- Poor version control, so work is lost or overwritten.
If something is slipping, tell your supervisor early and discuss narrowing the scope.
Presentation preparation
Your presentation should cover the problem, objectives, method, key results and conclusion, with more time on results than on background. Keep slides simple, with one message each and readable charts.
Practise aloud with a timer. Prepare answers for likely questions: why you chose this method, what the limitations are and what you would do differently. Bring a backup copy of the slides and, for system projects, test the demo on the venue's equipment if you can.
Checklist
Use this to check your progress:
- Topic approved and objectives clear.
- Supervisor meetings scheduled and recorded.
- Proposal and literature review completed.
- Ethics or data permissions obtained, if needed.
- Data collection or development on schedule.
- Draft chapters sent for feedback.
- Formatting and references checked.
- Presentation rehearsed and files backed up.