Most “research proposal examples” online are either a bare template with headings and no content, or a real proposal from one discipline that is hard to translate to yours. This page does something different. It shows a full mini proposal on one topic, then stops after each section to explain the reasoning. The topic is invented, the cited authors are placeholders, and the numbers are plausible rather than real, so you can borrow the shape freely without borrowing anything you would need to verify.
The example is written for a master’s-level dissertation in education, but the structure transfers to psychology, business, health, sociology and most applied fields. If you want the blank skeleton without the worked content, see A Research Proposal Template That Actually Guides Your Thinking. If you have not settled on a question yet, start with How to Write a Research Proposal That Starts With the Right Question and come back here.
How to read this example
The proposal text sits in the shaded blocks; the paragraphs marked Commentary are the tutor’s notes. The proposal runs about 1,100 words, shorter than the 2,000 to 4,000 most departments ask for, because it is compressed so that every sentence has a visible job. When you expand your own, add evidence, not padding.
1. Working title
Scheduled Peer Review and Revision Depth: A Comparison of Weekly and End-of-Unit Feedback in First-Year College Writing Courses
Commentary. A working title names the variables and the population, nothing more. Here the reader learns the intervention (scheduled peer review), the outcome (revision depth), the comparison (weekly versus end-of-unit) and the setting (first-year college writing) before reading a paragraph. Avoid clever titles at proposal stage; the committee is scanning for scope, and a title like “Finding Their Voice” hides it.
2. Background and problem statement
Peer review is a standard feature of first-year composition courses. Instructors typically ask students to exchange drafts once, near the end of a writing unit, shortly before the final version is due. Informal reports from writing program coordinators suggest that revisions made after this single exchange are often superficial: students correct surface errors but rarely reorganize paragraphs or rethink claims.
One plausible reason is timing. When feedback arrives days before a deadline, students may lack the time or motivation to make structural changes. Distributing peer review across a unit, so that drafts are exchanged weekly while ideas are still forming, may encourage deeper revision. Whether it does, in a typical first-year course with ordinary students and no additional instructor time, has not been tested in a controlled way.
This matters for program design. Weekly peer review costs class time. If it does not change the depth of revision, that time is better spent elsewhere. If it does, the change is cheap to implement across sections.
Commentary. Three paragraphs, three moves. The first describes current practice and the observed problem. The second offers a mechanism (timing) and states plainly that it is untested. The third answers the reviewer’s silent “so what?” by connecting the result to a decision someone has to make. Notice what is absent: no sweeping opening about the importance of writing, no statistics the writer would have to source. When you write yours, ask who would change what they do depending on the result, and put that person in the third paragraph.
3. Research questions and hypothesis
RQ1. Do students who receive weekly scheduled peer review make deeper revisions between first and final drafts than students who receive a single end-of-unit peer review?
RQ2. Does the type of revision differ between groups, specifically the proportion of changes classified as structural (reorganizing, adding or removing claims) versus surface (word choice, grammar, formatting)?
H1. Students in the weekly condition will show a higher proportion of structural revisions than students in the end-of-unit condition.
Commentary. Two questions and one hypothesis is a comfortable size for a one-semester dissertation. RQ1 is the headline comparison. RQ2 makes the outcome measurable by defining what “deeper” means: it is the ratio of structural to surface changes, not a vague impression. The hypothesis is directional because the design is quantitative and the background gave a reason to expect one outcome. If this were an interview study asking how students experience peer review, there would be no hypothesis, only questions. A common error is writing four or five questions that each need their own study. If a question would not change the methodology, it is probably a sub-point of another question, not a separate one.
4. Aims and objectives
Aim. To determine whether the timing of peer review affects the depth of revision in first-year college writing.
Objectives.
- Recruit four sections of the same first-year writing course taught by two instructors, assigning two sections to each condition.
- Collect first and final drafts of one 1,200-word argumentative essay from all consenting students.
- Code every change between drafts as structural or surface using a published revision taxonomy adapted for this study.
- Compare the proportion of structural revisions between conditions.
- Report findings to the writing program with recommendations for scheduling.
Commentary. The aim restates the purpose in one sentence; the objectives are the concrete steps that will achieve it, in order. Objectives should be things you can tick off. “Explore the role of feedback” is not an objective; “code every change between drafts” is. Reviewers use this list to check feasibility at a glance, and they will compare it against your timeline later. If an objective has no matching slot in the timeline, one of them is wrong.
5. Literature review
Research on peer review in writing instruction falls into three strands. The first examines whether peer feedback improves final-draft quality at all. Studies in this strand (for example, Author A, 2016; Author B, 2019) generally report modest gains, with larger effects when students are trained to give feedback. The second strand looks at the content of peer comments and finds that untrained reviewers concentrate on surface features (Author C, 2018). The third, smaller strand considers timing, but mostly in the context of instructor feedback rather than peer feedback (Author D, 2021), and mostly with upper-level or graduate students.
Two gaps follow. No study located for this review compares the timing of peer review directly while holding the amount of feedback constant. And the strand on timing has not been extended to first-year students, whose revision habits are still forming and who may respond differently to early feedback than experienced writers do. This study addresses both gaps.
Commentary. This is the whole literature section, and for a proposal it is close to the right size. It organizes the field into strands rather than listing authors one after another, and each strand ends by pointing at a limit. The final paragraph names two specific gaps and states that the study fills them. That sentence, “This study addresses both gaps,” is the hinge of the proposal. Everything before it justifies the study; everything after it describes how the study will be done. The placeholder citations are deliberate here; in your version, every one must be a real source you have read. For a method of building this section from a stack of articles, see How to Write a Literature Review That Maps the Conversation.
6. Methodology
Design. A quasi-experimental comparison of two intact groups. Random assignment of individual students is not possible because peer review takes place within class sections, so sections are assigned to conditions, balanced across the two instructors so that each instructor teaches one section in each condition.
Participants. Approximately 90 students across four sections of a required first-year writing course at one public university. Students who decline consent remain in the course activity but their drafts are excluded from analysis.
Intervention. Both conditions receive the same peer review prompt sheet and the same total number of peer comments (three reviewers per draft). In the weekly condition, drafts are exchanged in weeks 2, 3 and 4 of a five-week unit. In the end-of-unit condition, drafts are exchanged once in week 4 with three reviewers. Instructors are given a written protocol to reduce variation.
Data. The first draft (week 2) and final draft (week 5) of one argumentative essay from each consenting student.
Analysis. Each difference between first and final drafts is segmented and coded as structural or surface. Two coders code 20 percent of the sample independently to establish agreement before one coder completes the rest. The dependent variable is the proportion of structural changes per student. Conditions are compared with an appropriate test for two independent groups, with instructor entered as a covariate. RQ2 is answered descriptively with the distribution of change types in each group.
Ethics. Approval will be sought from the institutional review board. Participation is voluntary, drafts are anonymized before coding, and instructors do not know which students consented until after grades are submitted.
Commentary. This section is longer than any other, and it should be. Every feasibility question is answered in advance: why not randomize (intact sections), how many participants (about 90), what differs between groups (timing only, since comment count is held constant), what the raw data are (two drafts), how they become numbers (coding with an agreement check), and what test is used. Holding the number of comments constant is the most important design decision here; without it a critic could say the weekly group simply got more feedback. When you draft your own methodology, list every objection you can imagine and answer each one in the text. For a fuller walkthrough of this section, see How to Write a Methodology Section: A Step-by-Step Guide.
7. Timeline
Weeks Activity 1–3 Ethics application; instructor briefing; adapt coding scheme 4–5 Recruit sections; obtain consent 6–10 Five-week writing unit runs in all four sections 11–12 Collect and anonymize drafts; train second coder; agreement check 13–16 Full coding 17–18 Analysis 19–24 Write-up, supervisor feedback, revisions 25–26 Final formatting and submission
Commentary. Twenty-six weeks is realistic for a two-semester master’s project, and the table leaves visible slack: six weeks for write-up, two for formatting. Reviewers distrust timelines with no slack because something always slips, usually ethics approval. The timeline mirrors the objectives one for one, and because the writing unit is fixed by the academic calendar, the plan is built backward from it. If your data collection depends on a term, a season or an annual event, anchor the timeline to that date first.
8. Limitations
Sections are not randomly assigned, so pre-existing differences between groups cannot be ruled out; balancing instructors across conditions reduces but does not remove this concern. The study measures revision on one essay in one course at one institution, so results describe this setting rather than first-year writing in general. Revision depth is coded from drafts alone; the study cannot say why students revised as they did. A short follow-up questionnaire could address this in future work.
Commentary. Stating limitations shows the writer understands the design. Each one here is paired with a mitigation (balanced instructors) or a boundary on the claims the study will make (one course, one institution), and the last sentence turns a weakness into a future direction.
9. References
A full reference list in the required style follows. (Omitted here because the citations above are placeholders.)
Commentary. Even a short proposal needs complete references in the required style. Reviewers check whether the literature is current and whether the methodology cites the coding scheme it borrows; inconsistent references are read as a preview of how the dissertation will be handled.
Adapting this example to your own topic
Copying the sections and swapping in your subject produces a document that looks right and reads hollow. Work in this order instead.
- Write your research question first, in one sentence, with a population, a variable and a comparison or relationship. Test it against the example’s RQ1.
- Decide what data would answer it. That decision writes most of your methodology before you have looked at any template.
- Read until you can name the gap in two sentences. Then write the literature section backward from the gap.
- Build the timeline from any fixed dates, then check that every objective appears in it.
- Write the background last. It is easier to explain why a question matters once you know exactly what the question is.
The finished proposal should read as one argument in which each section makes the next one necessary: the background creates the problem, the questions define it, the literature proves it is open, the methodology shows it can be closed, and the timeline shows you can close it in time. For the project that follows, see How to Plan and Write a Dissertation Without Losing Your Way; if the topic still feels too large, How to Choose a Research Paper Topic You Can Actually Finish covers narrowing it.
Pre-submission checklist
Use this before sending the draft to your supervisor.
- The title names the variables and the population.
- The problem statement says who would act differently depending on the result.
- Each research question could change the method if it were removed.
- A hypothesis appears only if the design can test one.
- The literature section ends with a sentence that names the gap explicitly.
- The methodology answers who, how many, what instrument, what analysis, and what ethics process.
- The one thing that differs between groups or conditions is stated in a single sentence.
- Every objective has a slot in the timeline, and the timeline has slack.
- Each limitation is paired with a mitigation or a boundary on claims.
- All citations are real, read, and formatted in the required style.
If two or more lines fail, fix those before polishing the prose; reviewers forgive clumsy sentences far more readily than a plan they cannot picture.
Frequently asked questions
How long should each section of a dissertation research proposal be?
For a proposal of 2,000 to 3,000 words, a workable split is roughly 10 percent background, 5 percent for the questions and aims, 25 percent literature, 35 percent methodology, and the rest for timeline, ethics, limitations and references. Methodology gets the most space because it is where most proposals fail. Always follow your department’s template if it gives its own limits.
Should a research proposal state a hypothesis or a research question?
It depends on the design. Quantitative studies that test a relationship usually state both: the question, then a directional hypothesis that names the expected result. Qualitative and exploratory studies state questions only, because the point is to find out what is there rather than to confirm a prediction. Stating a hypothesis for an interview study looks like a misunderstanding of the method.
Can I use the same literature review in the proposal and the dissertation?
Partly. The proposal version is short and has one job: show the gap your study fills. The dissertation chapter is longer, covers more sources and organizes them by theme. Most students expand the proposal’s literature section three to five times over, keep its gap statement almost word for word, and add the studies they found after the proposal was accepted.
What do reviewers most often send a proposal back for?
Vague methodology first, then scope. “Data will be collected and analyzed” tells a reviewer nothing; they want to know who, how many, what instrument, and which analysis. The second common problem is a question too large for the time available. A single site, one semester and a narrow variable will pass more easily than a multi-country comparison.