Writing a Research Proposal: Questions, Methods, Feasibility and Contribution

Treat the proposal as a case for a study

A proposal should help a reader decide whether the work is important, answerable and feasible. It is more than a background essay followed by a method label. Every section should strengthen the connection between the problem, the evidence needed and the contribution the study could make.

Begin with a concise problem statement. Explain whose decision or understanding is affected, what remains uncertain and why the proposed work is timely. Avoid opening with broad declarations about the importance of education or technology. Specificity gives reviewers a clear basis for assessing relevance and prevents the scope from expanding without control.

Establish the argument from existing evidence

Summarise the literature around the question rather than describing one paper after another. Identify areas of agreement, disagreement and limitation. Distinguish a lack of evidence from evidence suggesting that an intervention does not work. Show how the proposed study addresses a defined uncertainty without dismissing previous scholarship.

Use sources that match the claims you make. A policy document may establish an institutional priority, but it does not necessarily demonstrate effectiveness. A small exploratory study may suggest a mechanism without establishing its prevalence. Accurate use of evidence signals that the project is built on a defensible understanding of the field.

Specify questions and objectives

Write a primary research question with a manageable scope. Add secondary questions only when they serve the main purpose and can be answered with the proposed data. Objectives should describe what the study will investigate, compare, estimate or interpret. They should not promise that a programme will succeed or that a preferred explanation will be confirmed.

If hypotheses are appropriate, explain the theoretical or empirical reasoning behind them. Where the work is exploratory, say so. Preregistration resources from the Center for Open Science can help teams distinguish planned tests from later exploration. ^[1] A proposal may also include decision points for refining instruments or recruitment after a pilot.

Describe methods at an executable level

Identify the setting, inclusion criteria, recruitment process, data sources, instruments and analysis plan. Explain why each method fits the question. Describe how missing data, non-participation or inconsistent records will be handled. For qualitative work, discuss the sampling rationale, researcher role and analytic approach rather than presenting software as the method.

If combining qualitative and quantitative evidence, explain where integration occurs and what it adds. NIH's mixed-methods guidance treats the combination of approaches as a design issue rather than merely collecting two kinds of data. ^[2] For any design, include enough detail for a reviewer to identify practical weaknesses before collection begins.

Demonstrate ethical and operational feasibility

Set out consent arrangements, participant risks, confidentiality, permissions and data storage. Name the roles responsible for recruitment, supervision and analysis. Build a timeline with dependencies: ethics review and access permissions must precede relevant activities, while transcription or data cleaning needs time before interpretation.

A budget should follow the actual work plan. Include necessary translation, accessibility, travel, software, data management and dissemination costs where applicable. Explain assumptions rather than filling categories mechanically. If access to a partner or dataset is uncertain, state the status and a realistic contingency. Do not present an informal conversation as a confirmed agreement.

Illustrative example: studying academic advising

Suppose a department wants to investigate why students rarely use its advising service. A weak proposal might promise to prove that awareness campaigns improve attendance. A stronger proposal first examines awareness, perceived usefulness, scheduling and trust, using service records and interviews with both users and non-users.

The proposal defines who can be recruited without pressure, how advisers will be separated from confidential interviews and what evidence would support a later intervention. It budgets for transcription and schedules analysis before recommendations are drafted. Its contribution is an informed explanation of barriers and a basis for redesign, not a guaranteed increase in attendance.

Conduct a final coherence review

• Does the background lead directly to the research question?
• Can the proposed evidence answer each objective?
• Are methods and analysis described consistently throughout?
• Are access, ethical review and permissions credible?
• Does the timeline include review, cleaning, analysis and writing?
• Are limitations and alternative explanations acknowledged?
• Are expected outputs distinct from hoped-for outcomes?

Ask a colleague unfamiliar with the project to explain the proposal back to you. If they cannot identify the question, method and contribution, revise those connections before polishing the language. Follow the specific institution or funder's format, because requirements vary. A clear proposal makes the study reviewable and provides a working plan that can be updated transparently.