Writing a final year project in the order it's read -- Chapter 1 straight through to Chapter 5 -- is usually the hardest way to do it. Here's a more practical sequence.
Write in this order, not the reading order
- Chapter 3 (Methodology) first, once your approach is settled -- this is usually the most concrete chapter to start with, since it's describing decisions you've already made.
- Chapter 4 (Results) as data comes in. Write results incrementally as you gather them, rather than waiting until everything is finished to start.
- Chapter 2 (Literature Review) can be drafted early (you likely did this research before finalizing your approach) but finalize it once your actual findings are known, so it connects cleanly to what you discovered.
- Chapter 1 (Introduction) near the end. Counterintuitively, this is far easier to write once you know exactly what your project accomplished -- you're summarizing a finished piece of work, not predicting one.
- Chapter 5 (Conclusion) last, since it depends on everything before it.
Why this order beats writing straight through
Chapter 1 asks you to state your objectives, significance, and scope confidently -- much easier once you actually know what you did and found, rather than trying to predict it from a blank page months before you're done.
Getting past the blank-page problem
Don't start with the hardest chapter. Start with whichever chapter has the most concrete material already available to you -- often the methodology, since it's describing a decision you've already made rather than something you need to discover.
Pacing to your deadline
Work backward: take your remaining page count, divide by your remaining weeks, and build in buffer for at least one full correction round before the actual deadline. Steady, modest progress sustained consistently beats large bursts with long gaps between them.
Where UniDraft fits in
Once you have your real results and topic, UniDraft builds the structured document around them in the correct chapter order and formatting -- so the writing-process problem becomes an editing/confirming problem instead of a blank-page one.
