How to Write a Research Proposal (Template and Example)

A research proposal is a short document that sets out what you plan to research, why it matters, and how you will do it, written before the research begins. It usually runs a title, an introduction with the background and significance, a focused problem statement, your research questions or objectives, a brief literature review, the proposed methodology, a timeline, and a list of references. Its job is simple: convince a supervisor, a committee, or a funding body that your question is worth answering and that you have a realistic plan to answer it. Below is a section-by-section template and a worked example so you can see what each part actually looks like.

Most students meet the research proposal as a gate. You cannot start the project, or get a supervisor assigned, until someone with authority has read your plan and agreed to it. That makes the proposal one of the highest-leverage documents you will write, because a few concrete pages now can save you from rewriting the whole study later. This guide covers what a proposal is and who reads it, the standard sections as a table you can fill in, a worked example of the key sections, how long it should be, how to keep your question and method feasible, why real cited literature matters, and the reasons proposals come back. One rule runs through all of it: your own programme's requirements beat any general advice here, so check your supervisor or programme guidelines and use any official template they provide.

What a research proposal is, and who reads it

A research proposal is a pitch backed by a plan. In a few pages it argues that your question is worth answering and that you have a realistic way to answer it. You are not reporting results, because you have not run the study yet. You are showing that the question is researchable, the method fits, and the work fits the time you have. The proposal is the thinking you do before the doing, written down so someone can check it.

Who reads it depends on where you are. For an undergraduate or master's project it is usually your supervisor, sometimes a small committee, deciding whether to approve the topic and assign supervision. For a PhD it is an admissions or progression committee judging whether the project is doctoral in scope and whether you can carry it out. For grant or scholarship funding it is reviewers comparing your plan against many others and asking whether the money would be well spent. The audiences differ in stakes, but they read for the same thing: a clear question, a method that can answer it, and evidence you have thought the project through. Write for a reader who is intelligent, busy, and slightly skeptical, and who will say yes only if the plan is concrete.

The standard sections of a research proposal

Proposals vary by level and field, but most share the same skeleton. The template below lists the sections you will usually be asked for and what each one is doing. Treat it as an orientation, not a rule: your programme's template decides the required sections, their order, and their depth, so confirm it before you build your document.

A few notes on the parts students misjudge. The title is provisional and should be; nobody expects the final wording here. The problem statement and the research question do related but different jobs: the problem statement names what is wrong or unknown, and the research question turns it into something you can actually investigate. The literature review in a proposal is not a full review, it is a focused sketch that shows you know the field and have spotted a gap. The timeline is the section experienced readers scan most carefully, because it reveals whether you understand the size of what you are proposing. Some programmes also ask for a hypothesis, an expected-outcomes section, an ethics note, or a budget, so check what yours wants.

A worked example of the key sections

It is easier to see a proposal than to describe one. Below is a short, illustrative sketch of the central sections for a fictional master's project, written to show the shape and the level of specificity, not to be copied. Your topic, field, and method will be different; what carries across is how each section narrows the one above it.

Notice what the example does. The title fixes a population and a period. The problem statement says what is unknown and why it matters. The research question is specific and answerable, and it adds one honest complication (onboarding) rather than sprawling. The method clearly can answer the question and is feasible in the weeks available. Every section narrows the one before it, which is exactly what a reader is checking for. The literature lines named here are illustrative placeholders; in a real proposal each would point to actual papers you have read, with real references in your list.

How long a research proposal should be

This is the first question every student asks, and the honest answer is the same one that applies to length everywhere in academic writing: check your programme guidelines or ask your supervisor, because it varies by level, institution, and field, and no number from a blog can override your programme's requirements.

A rough orientation still helps. An undergraduate or master's proposal often runs somewhere around 1,000 to 3,000 words, a few pages, while a PhD proposal or a funding application can run much longer, with a fuller literature section and a detailed methodology, sometimes ten pages or more. The proposal is short on purpose. It is a plan, not the study, and its value is in being concrete, not long. If you find yourself padding to hit a page count, you have probably misread the brief; confirm the expected length and the required sections before you write, and spend the space on specifics rather than filler.

Make the question and the method feasible

The research question is the heart of the proposal. Everything downstream, the method, the structure, the sources, flows from this one sentence, so it is worth more of your time than any other part. A strong research question is specific, answerable, and honest about scope. "How does remote work affect reported job satisfaction among first-year graduates?" is a question you can investigate. "Is remote work good?" is not a question, it is a conversation. The most common failure is going too broad; students reliably propose questions the size of a library. The fix is to narrow until the question names a specific effect, a specific population, and ideally a specific setting or period. We go deeper on shaping and sharpening it in how to write a research question, which is worth reading before you lock the proposal.

The method is where readers catch unrealistic plans, because the method is where ambition meets the calendar. The principle is simple and most students miss it: the method has to match the research question, and it has to fit the time and access you actually have. If your question is about how widespread something is, you need a quantitative approach, a survey, an experiment, a dataset. If it is about why or how people experience something, a qualitative approach fits, interviews, a case study, document analysis. Some questions want both. Choose the method that can answer the question you set, not the one that sounds impressive or that you already know the software for.

Then sanity-check feasibility before you commit it. Can you realistically gather the data in the weeks you have, with the access and skills you actually possess? A plan that needs interviews with fifty executives, a proprietary dataset, or ethics approval that takes a semester is a plan fighting your deadline. Name what you will collect, from whom, how, and how you will analyse it, and be honest about limitations. A reader trusts a modest method that clearly works far more than an ambitious one that clearly will not.

Why real, cited literature carries the proposal

The literature section is doing a specific job: it shows you have read enough of the field to know where your work sits and to name a gap that is actually open. You cannot sketch a gap in a field you have not read, and a reader can tell within a paragraph whether you have. This is the section that turns "I think this is interesting" into "here is what is known, here is what is missing, and here is how I add to it."

Start with academic databases rather than a general web search. Your university library catalogue, Google Scholar, and open indexes like OpenAlex surface peer-reviewed work instead of blog posts. Use the keywords from your research question, follow the reference lists of the strongest papers you find, and favour recent peer-reviewed work, reaching further back only for the foundational studies that newer work keeps building on. You do not need to read everything; for a proposal you need enough to map the field honestly, the main lines of work, where they agree and disagree, and the specific question nobody has answered, which is your gap. The full search method is in how to find sources for a research paper.

The non-negotiable rule is that every reference must be real and traceable. This matters more than ever because AI tools fabricate references that look completely real, with believable authors and a correctly formatted DOI that leads nowhere, and the literature section is exactly where a fake one slips in. A reference list with sources nobody can find is worse than a short one, because a single fake citation makes a reader doubt everything else. Before any reference enters your proposal, confirm the paper exists: search the title in Google Scholar, resolve the DOI at doi.org, and check the lead author publishes in the field. Keep your references in your programme's citation style from the start, and if you are unsure of a format, a general reference like the Purdue Online Writing Lab covers the major styles.

Why research proposals get rejected, and how to avoid it

Most rejections are not rejections of you; they are requests to narrow and make the plan concrete. The same handful of problems come up again and again, and every one of them is fixable before you submit.

• The topic is too broad to finish. A thesis-sized question hides a library of reading and a method you cannot complete in the time available. Narrow until the scope is something one person can do in the weeks you have.
• The research question is not actually a question. A theme ("social media and well-being") is not a question. Phrase it so it has a specific, answerable form, with a clear X, Y, and population.
• The method cannot answer the question. A qualitative case study cannot measure prevalence; a survey cannot explain lived experience. Match the method to what the question asks for.
• The method is unrealistic. The plan needs data, access, or approvals you cannot get in time. Choose a method that fits your real constraints and say so.
• The literature is thin or missing. If you cannot place your work in the existing research, a reader cannot tell whether the gap is real. Read enough to show the field and name the gap.
• The timeline ignores the deadline. A schedule that leaves no time for analysis or writing tells a reader you have not grasped the size of the work. Build the timeline backwards from your submission date.
• The references are unverifiable. A reference list with sources nobody can find signals the rest was not checked. Every source must be real and traceable.

If you address those seven before you submit, you have removed the reasons proposals usually come back. The deeper version of the same checklist applies to the thesis that follows the proposal, and we lay out that whole arc in how to write a bachelor thesis.

Where CiteOwl fits

You can write every part of a research proposal by hand, and many strong proposals are written exactly that way. Where a tool helps is the slow, error-prone middle: finding real literature for the review, keeping the references honest, and getting from a blank page to draft sections you can shape. CiteOwl is built for that, on a verify-first principle. It searches actual literature and reads what it finds, so the papers behind your citations are real, not generated from memory, and every claim it writes links to a source it actually read, with the supporting quote shown.

It can help you surface and cite the literature for your review, and it can draft and structure the sections of the proposal, the problem statement, the objectives, the method sketch, the outline. You review each one change by change as a plain diff and accept or reject it. The line it never crosses is doing the thinking for you. The research question, the method, and the argument stay yours; the tool just makes the work around them faster, with sources you can check. When the proposal is approved and the project begins, the same approach carries through.