Final Year Project Acknowledgement: What to Write (With Examples)

Write your acknowledgement by naming the people who actually helped and saying briefly what each contributed. Check the required order and length, then proofread names and titles. Do not invent assistance or wait until printing to check the page.

Your thanks should be personal, while the surrounding preliminary pages stay consistent. UniDraft helps organise the names, contributions and project instructions you confirm into an editable document. Start your project document, then review every name and statement of assistance. See the final-year project workflow; only the relevant people can give actual approval.

The short answer

• Position: it sits in the preliminary pages, usually after the certification page and the dedication and before the abstract. Check your department's order, because some place it differently.
• Order: follow the stated local sequence; academic, practical and personal thanks is one possible drafting arrangement, not a national rule.
• Length: follow your instructions and keep it concise. An abstract's length does not establish an acknowledgement limit.
• Tone: sincere and specific; first person can fit a personal acknowledgement where your guideline allows it.
• Never: leave a placeholder, copy a senior's page, or thank people who did nothing for you.

Use the fictional samples as planning examples. Check every contribution before adapting a sentence.

Who to include, and in what order

A practical drafting order is academic help, other assistance, then personal thanks. This is an editorial suggestion, not a national Nigerian rule. Follow any stated order, describe what your supervisor actually did and make personal or religious wording your own choice. Acknowledgement does not establish that someone signed or approved the work. Cornell's thesis guidance gives one example of first-person acknowledgements; it does not govern your department.

Here is who belongs on the page, and why.

1. Your supervisor

Name them with their correct title (Dr., Prof., Engr., Mrs., Mr.) as it appears on your title and certification pages. Say what they actually did: read drafts, challenged your research design, sent you back to fix the analysis, gave you access to a laboratory. If you had a co-supervisor, thank them in the same paragraph.

2. The Head of Department and other lecturers

Thank the HOD only if they did something for you, such as approving your topic quickly or making equipment available. Lecturers who taught a course you relied on, or who reviewed your questionnaire or your code, deserve a line. A blanket "all the lecturers in the department" is fine as a closing phrase, but do not make it the whole paragraph.

3. People and organisations that made the data possible

Include this group when it actually contributed. If a company, hospital, school, ministry or laboratory gave you access, say so. Thank your respondents collectively. If you ran a survey, the people who filled it in (and anyone who helped you distribute it) are the reason your results chapter exists. If you did a pilot, thank the pilot participants too. Where you promised confidentiality, name the organisation only if you have permission.

4. Family

Parents, guardians, spouses and siblings who paid fees, gave you space or kept you going. Keep it short and specific: "for funding my data bundles and my printing" is better than "for their unending love" repeated four times.

5. Friends and classmates

Name people only for something real: proofreading, helping you debug, lending a laptop during a blackout, keeping you company in the library. If you want to thank a large group, use a collective phrase such as "my course mates in the [year] set".

6. A closing line

Keep any closing line concise. If faith matters to you and your instructions permit it, religious wording may go here or elsewhere. If it does not, end on gratitude to everyone who helped.

What makes an acknowledgement sound genuine, not generic

Specificity makes assistance clearer, but polished or specific wording is not proof that an event happened.

Generic: "I would like to thank my supervisor for his support throughout this project."

Specific: "I am grateful to my supervisor, [Supervisor's name], for his patient guidance through three rounds of corrections and for pushing me to strengthen my methodology chapter."

The second version is more specific; use it only if those correction rounds and that assistance really occurred.

A useful formula for each person is: who + what they did + what it changed for you. For example, "[Lecturer's name], who reviewed my questionnaire and helped me cut it from forty questions to twenty-five." Three parts, one sentence, and it cannot be mistaken for a template.

You already have the material. Look at your supervisor's marked-up drafts and the messages you exchanged. If you went through several rounds of supervisor corrections, the corrections themselves tell you what to thank them for.

A simple structure to follow

The following is an optional order, subject to your instructions:

1. Recognise your supervisor where they contributed and name one real contribution.
2. Thank the HOD and other lecturers who helped, in a sentence or two.
3. Thank the people or organisations that gave you data, access or equipment.
4. Thank your family briefly and specifically.
5. Thank friends and course mates who helped.
6. Close with one short, genuine line.

Use concise paragraphs within your required length. Follow your department’s presentation rules rather than treating a paragraph count as compulsory.

Three full sample acknowledgements

These are original fictional teaching templates, not records of real student assistance. Replace every bracket with your own true details, and delete any sentence that does not apply to you. Do not keep a line just because it sounds good.

Sample 1: formal wording to adapt

I express my sincere gratitude to my supervisor, [Supervisor's name], whose careful reading of every draft and insistence on clear research questions shaped this work from the proposal to the final chapter. His corrections were firm and always fair.

I am also grateful to the Head of Department, [HOD's name], and to the lecturers of the Department of [Department], particularly [Lecturer's name], who reviewed my instrument and advised on the analysis.

I acknowledge the management and staff of [Organisation], who granted me access to the data used in this study, and the respondents who gave their time to complete the questionnaire.

My deepest appreciation goes to my parents, [Parent's name] and [Parent's name], for their financial and moral support throughout my programme, and to my friends and course mates, whose encouragement sustained me. Above all, I thank God for the strength to complete this work.

Sample 2: warm and personal

The first person I must thank is my supervisor, [Supervisor's name]. There were weeks when I thought my methodology would never make sense, and it was his patience, and his habit of asking "why this and not that?", that finally made it work. Thank you, sir.

To [Lecturer's name], thank you for arranging weekend access to the laboratory, and to the technicians in the [Laboratory name] for never rushing me out.

To my mother, [Parent's name], who carried the burden of my school fees and never once complained, this work is as much yours as mine. To my brother [Sibling's name], thank you for the laptop that carried me through the final semester.

To [Friend's name] and [Friend's name], for proofreading late into the night, thank you. And to God, who kept me through it all: I am grateful.

Sample 3: short (about 80 words)

I thank my supervisor, [Supervisor's name], for his guidance and for reviewing my drafts until they were ready. I am grateful to the staff of the Department of [Department] for their support, and to [Organisation] for access to the data used in this study.

I thank my family for their patience and support, and my friends for their encouragement. Finally, I thank God for the grace to finish.

All three fictional examples happen to start with the supervisor; that shared structure does not establish a required order. Delete any invented story, religious line or contribution that does not reflect your actual experience.

Which style should you use?

Situation	Best style
Strict department, formal supervisor	Formal
You worked closely with a supportive team	Warm
Limited page space or many people to thank	Short
Project involved an organisation or hospital	Formal, with the organisation named (if permitted)

If you cannot decide, ask your supervisor which tone is acceptable, or look at two or three approved past projects in your department. Confirm tone rather than assuming a sample is acceptable locally.

What to avoid

Check for these avoidable problems.

• Placeholders left in. "[Supervisor's name]" or "Dr. ______" still in the printed copy is the classic embarrassment. Search the whole document for square brackets and underscores before you print.
• Someone else's page. Copying a senior's page can carry over their supervisor's name, their family members or their department. Use it for ideas only.
• Jokes and slang. Check the tone required for the document. Avoid wording that would be inappropriate for its audience.
• Thanking people who did nothing. A page that lists twenty names reads as padding, and the people who really helped get lost.
• Long religious or emotional passages. Follow the required length and keep any personal wording relevant; no universal sentence limit is supplied here.
• Wrong titles or spellings. Get your supervisor's name and rank exactly right. Check the title page and certification page, and match them.
• Claiming help you did not get. Do not thank an organisation for "access to data" if you did not use its data, and do not imply approval by an institution that did not approve your work. Your acknowledgement must be as truthful as your results.
• Sneaking in criticism. Even gently phrased complaints about a supervisor, a department or a delay do not belong here.
• Ignoring the format rules. Some departments require a particular heading style, spacing or position. Check your department's format guide.

Formatting and placement

The acknowledgement is part of the preliminary pages, which usually use lower-case Roman numerals (i, ii, iii). The heading, ACKNOWLEDGEMENT (some departments write ACKNOWLEDGEMENTS; use the form yours uses), is typically centred and in capitals, in the same style as your other preliminary page headings. The body text follows your report's font and line spacing.

Check whether your instructions require the heading in the contents page and how this preliminary page is numbered. Follow the established sequence rather than restarting numbering without a reason. If Word's numbering has confused you, our guide to Roman and Arabic page numbering in Word explains section breaks. For the wider layout, see the project formatting guide.

Once your document is finished, run the .docx through the free formatting checker to catch font, spacing and margin problems. Universities differ, so also look up your institution in the university format guides.

Draft it after checking the actual contributions

You can keep a list while working and finalise the wording after checking who actually helped. Things change late: your supervisor's title can be corrected on the title page, and you often remember someone you forgot near the end.

A quick process:

1. List names. Write everyone who helped in some concrete way: supervisor, lecturers, data providers, family, friends.
2. Add one fact per name. What did they do? If you cannot think of anything, they probably do not belong on the page.
3. Order them according to your instructions or an appropriate optional arrangement.
4. Write it out in concise prose using the permitted tone and length.
5. Trim anything that sounds like a template line.
6. Check spellings and titles against your title page.
7. Read it aloud once. Anything that makes you wince is a candidate to cut.

If you are working through a step-by-step final year project timeline, allow enough time to confirm contributions, names and any required review rather than postponing it to printing day. The abstract is the other page that tends to be rushed at the end, and our guide on writing the abstract covers it.

How the acknowledgement relates to the other preliminary pages

Students often mix these up. Briefly:

• Dedication: one or two lines, to a person or people. It is not the place for thanks.
• Certification: uses the signatories and wording your institution actually requires. Only authorised people can provide those endorsements.
• Acknowledgement: thanks, in prose, for help received.
• Abstract: a summary of the study.

Check names and titles against verified current details wherever they appear. The certification-page checklist explains how to confirm required wording, roles and signing arrangements. Do not put signature lines or "approved by" wording in your acknowledgement; personal thanks do not establish institutional approval.

Check the front section before your project defence: correct placeholders, names and page references. This guide cannot predict how a panel will grade a formatting mistake.

Pre-submission checklist

• The order follows my instructions, and every name and title is correct.
• Every person named actually helped, and I say how.
• Organisations named gave permission (or I have not named them).
• No brackets, underscores or "Dr. ______" left in.
• No text copied from a senior's acknowledgement.
• Length follows my instructions, with repeated or exaggerated thanks removed.
• Heading style and Roman page number match the other preliminary pages.
• Spelling of every name checked twice.
• Read aloud once, and I mean everything I wrote.

Where UniDraft fits in

If you also need a personal tribute page, the dedication guide distinguishes that choice from recognising actual assistance. Do not copy the same paragraph into both pages.

Check the current price and included correction allowance in the document workflow before payment.

Start your document →