Most guides on choosing a project topic start with "follow your passion." That's not wrong, exactly, but it skips the part that actually determines whether you finish on time: whether the topic is doable within the constraints you're actually working with. A brilliant topic you can't get data for, or can't finish before your defence date, isn't a good topic — it's a good idea for someone with more time and fewer constraints than you have right now.

Start from what you can actually access, not what sounds impressive

The single biggest reason Nigerian undergraduate and postgraduate projects stall isn't a weak idea — it's a topic that requires data, equipment, or institutional access the student doesn't actually have. Before you commit to a topic, ask yourself honestly: can I get the data this study needs, and can I get it within the time I have left? A topic that needs cooperation from three different banks' internal systems is a harder project than one built on a structured dataset you can access, a survey you can realistically administer, or a lab you actually have access to. This isn't about aiming low — it's about not building your timeline on an assumption you haven't tested.

Match the scope to your level, not the other way around

A BSc project and a PhD thesis both ask real questions, but they don't ask them at the same depth, and that's not a compromise — it's the point. A common mistake is scoping a BSc project like it needs to make an original contribution to the field, which buries a student in literature review requirements and methodological rigour that isn't actually expected at that level yet. Equally common at the postgraduate level: scoping a topic so narrowly that it doesn't leave enough room for the kind of original analysis a thesis committee will expect. If you're not sure where the line is for your level, look at three or four recently approved projects from your own department — not a generic online example — and calibrate against those.

Check for a genuine gap, not just an available topic

"Nobody has done this exact combination before" is a weak justification on its own — plenty of unstudied combinations exist because they're not actually interesting or useful, not because they're an undiscovered gem. A stronger test: does answering this question tell someone something they'd actually want to know? A gap that connects to a real operational problem (why do agent banking transactions fail more often in this specific context; what actually predicts which students drop out of this specific programme) tends to produce a more defensible project than a gap that exists purely because nobody happened to combine variables X and Y before.

Talk to your supervisor before you fall in love with the topic

It's tempting to fully develop a topic — background, objectives, the whole shape of it — before bringing it to your supervisor, so you can present something polished. In practice this often means more rework, not less: a supervisor who sees the topic early can flag a scoping problem, a data-access issue, or a methodology mismatch before you've built three chapters around it. Bring a rough version early, even if it feels premature.

A quick self-check before you commit

1. Can you name, specifically, where your data or evidence will come from — not "I will collect data," but the actual source?
2. Does the scope match what's normally expected at your degree level in your own department?
3. Could you explain, in one sentence, why this specific question matters to someone outside your own head?
4. Has your supervisor seen and responded to at least a rough version of it?

If you can answer all four honestly, you likely have a workable topic — not necessarily a perfect one, but one you can actually finish.