Writing a research proposal that gets approved

Proposals are rarely rejected for being badly written. They are rejected for promising more than the time, the sample or the researcher’s access allows. Feasibility is the assessment criterion students most consistently underestimate.

What a panel is actually checking

• Is the question specific enough to be answered, rather than explored indefinitely?
• Can it be answered with the method proposed, in the time available?
• Does the researcher have realistic access to the data or participants required?
• Is there a genuine gap, or is this replicating something well established?
• Has the ethical dimension been thought about rather than mentioned?

Notice that only one of these is about the literature. Panels assume you can read; they are testing whether you can scope.

Narrowing until it is answerable

Almost every first draft is too broad. The useful move is to add constraints one at a time — population, context, timeframe, outcome — until the question could be answered with evidence you could plausibly gather.

“How does remote work affect employee wellbeing?” is a research programme. “How do hybrid working arrangements affect perceived work–life boundary control among knowledge workers in medium-sized firms in one European country?” is a study.

The narrower version looks less ambitious and is far more likely to be approved, because a panel can see how it would be done. Ambition in a proposal is demonstrated by the sharpness of the question, not its breadth.

The feasibility audit

Before writing, answer these honestly. If any answer is uncertain, the proposal needs to change rather than the answer being deferred.

1. How many participants can I realistically reach, and through what route?
2. Does my method need a sample size I cannot obtain?
3. Does this require ethical approval, and how long does that take at my institution?
4. Do I have access to the data, software or archives this depends on?
5. If the main route fails, what is the fallback design?

Components and what each is for

• Background — establishes that a problem exists, using evidence rather than assertion
• Problem statement — narrows from the background to the specific gap
• Aims and objectives — one aim, a small number of objectives that map onto method steps
• Preliminary literature — demonstrates the gap is real and not simply unread
• Methodology — design, sampling, instruments, analysis plan, with justification
• Timeline — realistic, including approval and write-up
• Ethical considerations — specific risks and specific mitigations

If your proposal was rejected

Read the feedback for which constraint was breached rather than as a general verdict. Panel comments are usually terse and almost always point at one of three things: the question is too broad, the method cannot answer it, or the contribution is unclear. Identify which, and rebuild around it. Rewriting the prose without addressing the constraint produces the same outcome a second time.