← Back to Blog
final year project

How to Write the Introduction of a Final Year Project

A Chapter 1 outline: background, problem statement, objectives, scope, and significance

Chapter 1 sets expectations for everything that follows -- and is also, counterintuitively, one of the easier chapters to get right if you write it after most of the actual work is done rather than before.

What it needs to cover

  1. Background of the study -- context on the broader area your project sits within.
  2. Problem statement -- the specific gap or issue your project addresses, stated clearly.
  3. Aim and objectives -- what you set out to achieve, usually one aim with several specific objectives underneath it.
  4. Significance of the study -- why the answer matters, to whom.
  5. Scope and limitations -- what's included, and what's explicitly out of scope.

Why writing it last works better

The introduction asks you to state your objectives and scope with confidence -- far easier once you know exactly what your project accomplished than when trying to predict it from a blank page months earlier. Many students who write Chapter 1 first end up substantially rewriting it once the actual work reveals a different shape than originally planned.

The objectives mistake to avoid

Objectives stated too broadly are hard to evaluate as "achieved" or not. Compare:

Too broad: "To study the impact of technology on education."

Specific and testable: "To evaluate the effect of a specific mobile learning tool on quiz scores among 100 secondary school students over one academic term."

A reader should be able to tell, after finishing your project, exactly whether each objective was met.

Keeping scope and limitations honest

State plainly what your project does not cover, rather than implying broader applicability than your actual work supports. This isn't a weakness -- a clearly scoped project reads as more credible than one making implicit claims its methodology can't actually support.

Where UniDraft fits in

UniDraft helps structure your introduction around your project's actual, confirmed scope and objectives -- built once your real work is defined, so it accurately reflects what your project delivers rather than an early, unverified prediction.

Start your document →

Frequently asked questions

What does a final year project introduction need to include?

The standard components: background of the study, problem statement, aim and objectives, significance of the study, scope, and limitations. Your department's guideline may specify a particular order or additional subsections -- check before writing.

Why is the introduction easier to write last?

Because it asks you to state your objectives, scope, and significance confidently -- much easier once you actually know what your project accomplished than when trying to predict it from a blank page. Many students who write Chapter 1 first end up rewriting it substantially once the project is finished.

What's a common mistake in writing project objectives?

Stating them too broadly -- 'to study the impact of technology on education' isn't a testable objective. 'To evaluate the effect of a specific mobile learning tool on quiz scores among 100 secondary school students over one term' is specific enough that a reader can tell exactly what would count as achieving it.