Make a Research Proposal Feasible: Scope, Methods and Available Resources

A research proposal can be ambitious without promising to solve an entire national or continental problem. For a prospective research master's or PhD student, a useful starting question is: what can I investigate convincingly with the time, access and skills available?

The checklist below is an editorial planning tool, not a university template. Use it to test your idea before writing the version required by your chosen department. It applies to applicants considering research in African institutions as well as overseas universities; it does not establish eligibility for any particular scholarship.

Check what the programme actually requests

Oxford's research-proposal guidance illustrates why this matters: some courses require a proposal, while some scientific routes ask instead for research interests or preferred groups. The course page controls the specifications. An unnecessary or over-length proposal can create problems, and a proposal does not replace a separately required writing sample.

Start a document headed “Instructions to follow” and record the permitted length, required sections, assessment criteria and submission format. Keep that document separate from your manuscript. It will become your final compliance checklist rather than another paragraph competing for space in the proposal.

Reduce the question until the evidence is manageable

Write your broad interest first, then narrow it through a population, place, period or mechanism. “Improving graduate employment in Africa” is a motivation. A question about how a defined group navigates a particular training-to-employment transition is closer to a researchable project.

This is an illustrative exercise, not a ready-made research question. Your final scope should emerge from your own reading and the field's methods. Ask yourself what evidence would change your understanding. If almost any finding could fit the question, it may still be too vague.

Try stating the boundary explicitly: what will this project not investigate? Leaving something out is often necessary to make the core question credible. You can mention future extensions without making them part of the funded degree.

Connect every method to a question

For each proposed method, write the following in plain language:

1. What information will it produce?
2. How will that information help answer the research question?
3. Where will the information come from?
4. What training or resources will be needed?
5. What would make the approach fail?

A list of sophisticated methods is not a substitute for explaining their purpose. If you propose interviews, consider whom you need to reach and why. If you propose a dataset, establish whether it exists and whether access is realistic. If you propose laboratory work, identify the relevant equipment and expertise without claiming access you have not secured.

Distinguish available resources from hoped-for resources

Create three short lists: confirmed, reasonably obtainable and unresolved. Include archives, participants, software, equipment, language skills and institutional permissions where relevant. Keep written evidence of any access agreement, but do not present an informal conversation as formal permission.

Now test a fallback. If a dataset becomes unavailable, could a narrower question still be answered responsibly? If an archive cannot be visited, would another source support the same argument? A fallback should preserve the research purpose, not quietly change the project into something unrelated.

Discuss ethics and permissions with the institution before collecting data. This guide is not ethics approval, and an application-stage plan does not authorise access to people, records or sites.

Make the timeline explain the work

Avoid filling a calendar with broad labels such as “research” for most of the degree. Break the project into decisions and outputs: literature review, methods training, access arrangements, pilot work, collection, analysis, drafting and revision. Add room for dependencies instead of assuming everything can happen simultaneously.

Use the exercise to find bottlenecks. If analysis depends on completing a training course, place that course before the analysis. If fieldwork depends on approval, show that dependency. A timetable is most useful when it exposes an unrealistic assumption early enough to change it.

Explain why the host is appropriate

Oxford's supervisor guidance advises applicants to follow course-specific instructions on contact and matching. Do not send the same proposal indiscriminately to academics whose interests only loosely overlap yours.

Read the target group's recent work and identify the concrete resources or expertise your project needs. Then explain the connection without flattery. The question is not whether the institution is famous, but whether the proposed work can be supported there. Where advance contact is appropriate, use it to resolve a specific uncertainty rather than request a generic endorsement.

Review for honesty and ownership

Oxford also stresses that the proposal must be the applicant's own work and points to its rules on plagiarism and AI use. Check your target institution's equivalent rules before using outside assistance. Keep citations accurate, distinguish your ideas from others' findings, and never invent preliminary results or supervisor approval. Oxford proposal requirements

Finish with a feasibility review by someone who can challenge your assumptions. Ask which claim is least supported, which step is most likely to slip and what you should remove. The strongest revision may be a smaller, clearer project that you can defend, rather than a longer proposal with more promises.