Chapter 2 of 8 · 4 checks · 3 min
Choose and work with a supervisor
A supervisor who knows the area and meets you regularly is one of the strongest predictors of a smooth year. Choose deliberately and agree how you will work.
Approach supervisors whose expertise matches your projectShould
Why it matters and how to check
A supervisor who works in your project's area can spot problems early, point you to the right literature and support your project in front of the committee. Look at faculty profiles, recent publications, courses they teach and past FYPs they supervised.
Departments often require the supervisor to be a faculty member of the department; the University of Lahore's Islamabad campus guidelines, for example, require a CS and IT department faculty member. Check it is done: you can say in one sentence why each supervisor you approach suits the project.
Do
- Check faculty profiles and past FYPs they supervised
- Approach supervisors early, before slots fill
Avoid
- Choosing a supervisor only because they are known to be lenient
Approach a supervisor with a one-page idea, not a blank requestShould
Why it matters and how to check
Supervisors receive many requests. A team that arrives with a one-page summary of the problem, the users, the rough approach, the team's skills and a few questions stands out from "Sir or Madam, will you supervise us?".
Be open to their suggestions; many supervisors will reshape an idea or offer one from their own research. Check it is done: you have a one-page idea document ready to send or print before the first meeting.
Do
- Bring a one-page summary to the first meeting
- Ask what the supervisor would change about the idea
Avoid
- Asking for supervision with no idea or preparation
Agree meeting frequency, communication channel and review turnaroundMust
Why it matters and how to check
At the first meeting, agree how you will work: how often you meet, for example weekly or every two weeks, the main communication channel such as email, a team chat or office hours, how much notice they need to review a document, and what they expect to see at each meeting.
Write it in your first meeting notes and send them to the supervisor. This avoids the common problem of a team that does not meet its supervisor for months and then needs urgent sign-off. Check it is done: meeting frequency and channel are recorded in notes the supervisor has received.
Do
- Agree frequency, channel and review notice in the first meeting
- Send the agreed arrangement to the supervisor in writing
Avoid
- Waiting for the supervisor to call meetings
Clarify roles if you have an external supervisor or industry clientNice to have
Why it matters and how to check
Some projects have an external supervisor or client from a company or organisation. FAST's proposal form, for instance, has a field for an external supervisor alongside the faculty supervisor.
Agree who decides what: usually the faculty supervisor decides on academic matters such as scope, report and evaluation, while the external partner advises on requirements and data. Check whether the partner expects ownership of code or data, and raise it with your faculty supervisor before signing anything. Check it is done: roles and any ownership or confidentiality terms are written down and approved by your faculty supervisor.
Do
- Write down who decides scope and who advises on requirements
- Clear any ownership or confidentiality terms with your faculty supervisor
Avoid
- Letting an external client expand the scope without your supervisor's agreement