Research and Dissertation Proposals: What to Include

A proposal is the document that turns an idea into a project. It convinces a supervisor, a committee or a funder that your question is worthwhile, that you know the field and that you have a realistic plan. It is also the best protection you have against the most common research problem: starting data collection before you have worked out what you are doing.

This guide covers the standard sections of a proposal, advice on each, a planning timeline and the reasons proposals are sent back for revision.

What a proposal is for

A proposal serves several purposes.

• Approval: a department or committee uses it to decide whether the project can go ahead.
• Feedback: it gives your supervisor something concrete to respond to.
• Planning: it forces you to think through methods, ethics and time.
• Funding or admission: for scholarships and doctoral programs, it is part of the application.
• A foundation: much of its text becomes the introduction and methods of your dissertation.

Treat it as a working document, not a hurdle.

Standard sections

Departments vary, so follow your own template. Most proposals include:

Some proposals combine sections or add others, such as limitations, risks or dissemination plans.

Title

Make it clear and specific. A good title tells readers the topic, the population or setting and sometimes the approach. "Peer Mentoring and First-Year Retention among New Graduate Nurses in Two Community Hospitals: A Mixed-Methods Study" is more useful than "Nursing Retention."

Introduction and background

Open with the context and move to the specific problem. Give enough background for a committee member outside your subfield to follow. Keep it focused, since later sections handle the details.

Problem statement and rationale

Explain the problem, show evidence that it matters and state what is missing from current knowledge. Our guide to writing a problem statement explains how. The rationale answers: why this study, and why now?

Research questions and objectives

State your main question and any sub-questions, and, if your department uses them, your aims and objectives. Make sure each can be answered with the methods you propose. See our guide to research questions and objectives.

Literature review

A proposal's review is shorter than a dissertation chapter. Its job is to show that you know the main work, can see the debates and have found a real gap. Organize by theme, synthesize rather than list and end with the gap that your question addresses. Aim for quality over quantity.

Methodology

This section often decides whether a proposal is approved. It should explain:

• Design: what kind of study and why it fits your question.
• Participants or data: who or what you will study, how many and how you will select them.
• Instruments: surveys, interview guides, tests or datasets.
• Procedure: the steps in order.
• Analysis: how you will turn data into answers.
• Validity and reliability or trustworthiness: how you will make sure your results are credible.
• Limitations: what your design cannot do.

Match methods to questions. A question about experiences suits interviews, while one about group differences may suit a survey or experiment. Our guide to the methodology chapter covers each element in more detail.

Ethics

Show that you have thought about the people involved. Cover informed consent, confidentiality, data storage, risks and benefits and any vulnerable groups. Note which approvals you need, such as a university ethics committee or an institutional review board, and allow time for them. Many committees will not approve a proposal without an ethics plan.

Timeline

A realistic timeline builds trust. Break the project into stages, such as literature review, ethics approval, data collection, analysis, drafting and revision, and give dates or durations. Build in buffer time, since approvals and recruitment often take longer than expected.

These are only illustrative. Fit the dates to your own program.

Resources and budget

List what you need: software, equipment, travel, transcription, incentives, access to participants or datasets. If the work is unfunded, say how you will manage within your own resources. Overlooking costs is a common sign of an unrealistic plan.

Expected outcomes and contribution

Explain what the study could add: new evidence, a practical recommendation, a test of a theory or a resource for practitioners. Be modest and accurate. Avoid promising results, since you do not yet have data.

Writing style

• Be clear and direct. Committees read many proposals.
• Use the future tense for what you will do.
• Be specific. Numbers, dates and named methods are more convincing than general promises.
• Cite credible sources.
• Stay within the word limit.
• Proofread. Errors suggest carelessness about the project.

How committees assess proposals

Committees often ask:

1. Is the question clear and significant?
2. Does the student understand the literature?
3. Are the methods appropriate and well described?
4. Is the project feasible in the time and resources available?
5. Are ethics and risks handled responsibly?
6. Is the writing clear?

If you can answer each yes from the text of your proposal, you are in good shape.

Common reasons proposals are sent back

• A question that is too broad or vague.
• No clear gap in the literature.
• Methods that do not match the question.
• A sample or data source that is not available.
• An unrealistic timeline.
• Missing or weak ethics plan.
• Too much literature and too little method.
• Unclear writing.

Most of these are fixable. A return for revision is usually specific advice, not rejection.

A sample one-paragraph summary

Many proposals begin with a short summary. A useful pattern is one sentence each for the problem, the gap, the question, the method and the contribution:

Newly graduated nurses often leave their first hospital job within a year, but little is known about whether unit-based mentoring helps in small community hospitals. This study asks how a mentoring program relates to first-year retention and how new nurses describe their mentoring. Using a mixed-methods design, it will compare retention before and after the program in two hospitals and interview 15 new graduates. The findings will inform onboarding decisions in similar settings.

(The study is illustrative.) Writing the summary first, then expanding each sentence into a section, is a good way to keep a proposal focused.

Common pitfalls in the first draft

Most first drafts share a few weaknesses. They spend too long on background and too little on methods, so the committee cannot see how the work will be done. They promise more than the time allows. They describe a topic and never state a question. They list methods without explaining why those methods suit the question. Reading your draft with a committee member's eyes, asking "how will they actually do this, and by when?", reveals most of these problems.

Getting feedback before you submit

Share a draft with your supervisor early, even if it is rough. Ask a peer to read it for clarity and a librarian to check your search strategy. For structured feedback on a proposal draft, academic coaching on a dissertation proposal is worth considering.

A quick checklist

• Is the title specific?
• Does the introduction show the problem and its importance?
• Is the gap clear and supported by the literature?
• Are the questions focused and answerable?
• Do the methods fit the questions?
• Is there an ethics plan?
• Is the timeline realistic?
• Is the proposal within the word limit and correctly referenced?

Final thoughts

A proposal is a promise and a plan. Make the question clear, ground it in the literature, choose methods that fit and be realistic about time and ethics. Write it as if you were explaining the project to a smart colleague from another field, and it will serve both your committee and your own work for months to come.