Writing a Research Proposal: Components, Feasibility and Why Proposals Get Sent Back

Proposals are read in different situations: for doctoral admission, for confirmation or upgrade reviews during a PhD, for approval of a master's dissertation topic, or for a committee proposal defense in many US programs. The format varies, but reviewers ask the same underlying questions. Is the problem significant? Is the question clear and researchable? Does the author know the relevant literature? Is the method appropriate? Can this be done by this person, in this time, with these resources? And is it ethical?

Keep those questions visible as you write. Every section of the proposal should answer at least one of them. A proposal that is interesting but vague on method, or rigorous but unclear about why the question matters, will struggle.

Always follow your program's template if one exists; required headings and word limits differ widely, from two pages for some admissions to a full draft of the first three chapters for some US dissertation proposals. The table below describes the components most proposals share.

Start with a problem, not a topic. 'Remote work' is a topic. 'Managers in small firms lack evidence on how remote work affects the onboarding of new employees, and existing studies focus on large corporations' is a problem. A good problem statement names the gap and implies why filling it would matter.

Research questions then turn the problem into something answerable. Strong questions are specific about the population, the phenomenon and the relationship or experience you want to understand. They are open enough to need research, but narrow enough to answer within your project. For quantitative studies, hypotheses state expected relationships that can be tested. For qualitative studies, questions often begin with 'how' or 'what' and focus on meanings or processes.

Check alignment. Your aim, objectives, questions, method and analysis should form a chain in which each link follows from the previous one. A mismatch, such as a 'why' question answered with a descriptive survey, is an easy thing for reviewers to spot. If your questions feel unsettled, working on research questions and hypotheses before drafting the rest usually saves time.

• Too broad: 'What is the impact of social media on young people?'
• Better: 'How do first-year university students in one country describe the role of short-video platforms in their study routines?'
• Testable: 'Is daily short-video use associated with lower self-reported study time among first-year students, controlling for course load?'

The proposal's literature review is shorter and more strategic than a thesis chapter. Its job is to show that you know the key work, to show where it falls short, and to set up your questions. Organize it around themes or debates that lead to the gap, and finish with a paragraph that explicitly states what your study will add.

Include recent literature. A proposal citing mostly sources more than a decade old suggests that the author has not checked whether the gap is already filled. Reviewers who know the field may know of a recent study that addresses your question; searching thoroughly protects you from that.

Reviewers need to be able to judge whether your method will work. Vague statements such as 'data will be collected through interviews and analyzed thematically' are not enough. Say who the participants will be, how you will recruit them, how many you plan and why, what the interview guide or instrument will cover, and which specific analysis approach you will follow.

Justify each major decision by linking it to your questions. Name alternatives you considered where it helps. If you plan statistical analysis, state the main tests or models and how you will determine sample size. If you plan qualitative analysis, name the approach and the source you will follow.

Mention piloting where appropriate, how you will handle missing data or non-response, and how you will protect rigor. These details show that you have thought through the study in practice, not only in principle.

Feasibility is where many otherwise strong proposals fall down. Reviewers need to believe that the project can be completed on time. Address feasibility directly rather than leaving the reader to guess.

• Access: do you have permission or a realistic route to the organizations, participants or datasets you need? Letters of support help.
• Time: does your timeline allow for ethics approval, recruitment delays, analysis and writing, with some buffer?
• Skills: do you have, or will you gain, the methodological skills required? Mention planned training.
• Resources: software licenses, travel, transcription, participant incentives, and whether they are funded.
• Scope: is the number of research questions, sites or participants manageable for one person?
• Risks: what could go wrong, such as low response rates, and what is your contingency plan?

Ethics sections in proposals are often brief, but reviewers read them closely because problems here can stop a project entirely. Identify which approvals you will need, such as a university research ethics committee, a health service or school authority, or permission from an organization whose data you will use. Explain how you will obtain informed consent, how you will protect confidentiality through anonymization or pseudonymization, where data will be stored and for how long, and how you will respond if a participant becomes distressed or discloses something that raises safeguarding concerns. If you plan to use online data, secondary datasets or AI tools, say how their terms of use and your institution's policies apply.

The significance section answers the question 'so what?'. Be concrete about who could use the findings and how: other researchers testing a theory, practitioners designing a program, or policymakers weighing an option. Distinguish between the contribution the design can support and the broader impact you hope for. A small qualitative study can make a valuable conceptual contribution without claiming to change national policy. Proportionate claims read as credible; inflated ones invite skepticism and are a common reason reviewers ask for revisions.

Supervisors and committees return proposals for predictable reasons. Knowing them in advance lets you address them before submission. Many are about clarity and alignment rather than the idea itself.

• The research problem is unclear or the gap is asserted rather than demonstrated from literature.
• Research questions are too broad, too many, or not answerable with the proposed method.
• The methodology is vague: sample, instruments or analysis are not specified.
• There is a mismatch between paradigm, design and questions (for example, generalization claims from a small purposive sample).
• The literature review is descriptive and outdated, and misses recent key studies.
• Feasibility is not addressed: no plan for access, unrealistic timelines or missing resources.
• Ethical risks are underestimated, especially with vulnerable participants or sensitive data.
• The contribution is not stated, or is overstated relative to the design.
• Writing issues such as inconsistent terminology, missing citations or formatting errors distract from the content.

Write for a smart reader who is not a specialist in your subfield. Define key terms on first use and use them consistently. Use headings that match the template so reviewers can find what they need quickly.

Use the future tense for planned work ('I will interview…'), and be confident but measured. Avoid promising outcomes you cannot know, such as 'this study will prove'. Instead, describe what the study is designed to examine and what kinds of contribution it could make.

Before submitting, check word limits, reference formatting, and whether appendices such as draft instruments or consent forms are required. Ask a peer to read the proposal and summarize your question and method in two sentences. If they cannot, the proposal may not yet be clear enough.

Most proposals are approved with some revisions. Read feedback carefully, group comments by theme, and respond systematically. If you are asked to revise and resubmit, a short response document listing each comment and the change you made shows reviewers that you took their advice seriously.

If you disagree with a comment, discuss it with your supervisor and explain your reasoning politely, supported by literature. Committees respect well-reasoned disagreement more than silent non-compliance. Treat the proposal as a living plan: the approved version guides your study, and later chapters will build on it.