Blog

· By Thesisroom

Updated

Research Methodology for Research Proposal: What Reviewers Accept

How to write a proposal methodology before you have data: justify the design, give sample size its logic, plan the analysis and fallbacks, and answer reviewers in advance.

A hand typing on a laptop beside an open spiral notebook and a pencil on a wooden desk
Photo by Kelly Sikkema on Unsplash

The research methodology for research proposal writing is a plan with reasons. You name your research design, sampling, data collection, analysis plan and quality checks, and for each one you explain why it is the right choice for your question. Reviewers judge whether the plan can answer the question and whether you can carry it out.

That second test is what makes a proposal different from a thesis. You have not collected any data yet, so the reader has only your reasoning to go on.

What does the methodology section of a research proposal include?

Five parts, in this order: research design, sampling, data collection, data analysis, and how you will show the findings can be trusted. Add a short paragraph on ethics and one on limitations.

The USC Libraries guide to research proposals puts the aim plainly: “the objective here is to convince the reader that your overall research design and proposed methods of analysis will correctly address the problem.” It also says the methodology “is not just a list of tasks”.

Some universities set the space for it. The University of Suffolk’s PhD proposal guidance gives “Research design and methodology” up to 900 words and asks you to “include specific techniques, not just your general approach.”

How a proposal methodology differs from a thesis methodology

A proposal argues what you will do and why. A thesis reports what you did, including any changes to the plan.

That shows up in the tense. The University of Hull’s guide to proposals says “The majority of your proposal should be written in the future tense as you are explaining what you will be doing.” Its dissertation tenses guide says the methodology chapter is “almost exclusively written in the past tense.”

The reasoning carries over from one to the other. When you later write the chapter, our guide on how to write a methodology chapter picks up from here.

How do you justify your research design?

Show that your question needs this design. A question about cause and effect needs a design that can separate variables. A question about how people experience something needs a design that captures context.

Run your design through three checks:

  1. Fit. Does the question ask about relationships between variables, or about how something works in its setting? Match the design to that.
  2. Access. Can you get the data the design needs? A design you cannot carry out is not a plan.
  3. The obvious objection. If your question implies causation but your design is a one-off survey, say so yourself and explain why it is still the right choice.

Justification sentences you can adapt

Each one names the design, what the question demands, and the constraint that shaped the choice:

  • “A quasi-experimental design will be used because the intervention cannot be randomly assigned to individuals, but intact classes allow outcomes to be compared.”
  • “A multiple-case study design fits because the question asks how the practice differs across organisations, which a single case cannot show.”
  • “A mixed-methods design will test how common the problem is in a survey, then use interviews to explain why it happens.”

The USC guide calls the methodology “a deliberate argument as to why techniques for gathering information add up to the best way to investigate the research problem.” Sentences like these are that argument in miniature.

How much detail should sampling and data collection have?

Enough for a reviewer to see exactly who you will study, how you will find them, how many, and why that number. “Participants will be recruited from universities” invites the question you want to head off: can this be done?

Justifying sample size

A number on its own is not a justification. Name the logic behind it, and use the logic that belongs to your kind of study.

  • Quantitative studies: base the number on a power calculation. Cohen’s power primer explains that sample size, significance level, effect size and power are linked: each is a function of the other three. His worked example finds that a medium difference between two groups at α = .05 “requires N = 64 in each group”.
  • Qualitative interview studies: use information power or saturation. Malterud, Siersma and Guassora argue that “the more information the sample holds, relevant for the actual study, the lower amount of participants is needed.” They name five factors: the study’s aim, sample specificity, use of established theory, quality of dialogue and analysis strategy.
  • Saturation figures: Guest, Bunce and Johnson found saturation “within the first twelve interviews” in their study of 60 interviews with women in two West African countries. Treat that as one study’s finding, not a rule for yours.

Onwuegbuzie and Leech add a useful limit: a qualitative sample should not be so large that rich data is hard to extract, nor so small that saturation is hard to reach. If you will compare subgroups, they recommend “at least three cases per subgroup”. For how examiners later probe these numbers, see how to defend your sample size.

Data collection a reviewer can picture

For each method, give four details:

  1. The instrument, and where it comes from or how it was validated.
  2. How long each session or survey takes.
  3. How you will record and transcribe or store responses.
  4. When and where collection happens.

If you will use a chatbot to summarise literature or draft questions, say so and explain how you will check what it produces.

How do you write a data analysis plan before you have data?

Describe the analysis you would run if the data arrived as expected, in enough detail that a reviewer could sketch your results tables. “Appropriate statistical analysis will be conducted” tells them nothing.

For a quantitative study, pair each hypothesis with its test, the assumptions the test needs, and the figure you will report. Name the software and version.

For a qualitative study, name the analytic approach (for example thematic analysis), who will code the data, and how disagreements between coders will be settled.

Contingency plans without hedging

Reviewers will wonder what happens if the data does not behave. Answer with conditions, each with a threshold that triggers it:

  • “If the outcome data are not normally distributed, the groups will be compared with a Mann-Whitney U test.” The University of Maryland School of Nursing describes it as “the nonparametric alternative to the Independent t-test.”
  • “If fewer than the target number of interviews are completed by month six, a second site will be added.”

A stated fallback turns a weakness into evidence that you planned ahead.

How do you show your findings will be trustworthy?

Quantitative proposals argue validity and reliability. Qualitative proposals argue trustworthiness, using criteria from Lincoln and Guba.

Nowell and colleagues summarise those criteria as “credibility, transferability, dependability, and confirmability”. Korstjens and Moser list practical ways to meet them, including triangulation, member checks, thick description, an audit trail and a reflexive diary.

Name the specific techniques you will use. “Rigour will be ensured” is a description. “Two researchers will code the first five transcripts independently and compare codes” is a plan.

What about ethics and limitations?

Give each a short paragraph, even when formal approval comes later. For ethics, cover consent, anonymity, data storage and any risk to participants, and name the committee that will review the study.

For limitations, the USC guide asks you to “Anticipate and acknowledge any potential barriers and pitfalls in carrying out your research design”. Say “access to one archive may limit how far the findings generalise” before a reviewer says it for you. Our guide on how to write the limitations of a study shows how to phrase them without undermining the project.

A reviewer’s checklist for your draft

Read each paragraph of your methodology and mark it D (describes what you will do) or J (justifies why). Turn each D into a J by adding the option you rejected and why: “Interviews rather than a survey, because the topic is poorly documented.”

Then answer the question a reviewer will ask about each part:

  • Design: why this design and not the obvious alternative?
  • Sampling: how did you arrive at this number?
  • Data collection: why this instrument, and has it been validated?
  • Analysis: what happens to the data, step by step, including cases that fail quality checks?
  • Ethics: what could harm participants, and who approves the study?

If you cannot name the alternative you rejected, you have announced a choice, not justified it. The same answers will carry you through the oral exam, covered in how to defend your research proposal.

The most common gap is between the question you ask and what your plan can reach. Thesisroom’s Scope Check reads a research proposal and asks about the places where what it asks for and what it plans do not obviously meet. It does not say whether a project can be done, and what to do about a finding stays yours.

How long should the methodology section be?

We found no general rule for its share of the word count, so check your university’s guidance first. Suffolk, for example, allows up to 900 words for design and methodology in a proposal of 1,000 to 2,000 words.

If you need to cut, remove descriptive detail first: long software settings, textbook definitions, instrument manuals. Never cut the justification sentences. A shorter methodology that explains why beats a longer one that only lists what.

Frequently asked questions

How do I write a research methodology for a research proposal? Cover design, sampling, data collection, analysis and trustworthiness in that order, plus ethics and limitations. For each choice, explain why it suits your question better than the obvious alternative. Write it in the future tense.
What are the five parts of a methodology? In a proposal: research design, sampling, data collection, data analysis, and validity or trustworthiness. Add short paragraphs on ethics and limitations as well.
What tense should a proposal methodology use? Mostly the future tense. Hull’s library guide says most of a proposal should be in the future tense because you are explaining what you will do. The thesis methodology chapter later uses the past tense.
How do I justify a small qualitative sample? Name the logic: information power, saturation, or a complete group you can reach. Give an expected range and the point at which you will stop recruiting. A small number with stated reasoning beats a large one with none.
Do I need to cite methodological sources in a proposal? Yes. Cite the source of any instrument you borrow, the origin of your analytic approach, and the basis for your sample size. Uncited choices read as invented rather than chosen.
Can I use a chatbot to help write my methodology? Check your university’s rules first. If you use one, check every claim and reference against the real source, and say in the proposal how you used it and how you verified its output.

Sources

How this guide was made: Thesisroom drafted this guide with the help of AI writing tools. Every fact, figure and source in this post was checked against its original source before publishing.