What funders and supervisors are actually scoring a proposal against, and the structural mistakes that sink otherwise strong research ideas.
A research proposal is not a research plan written down. It's a persuasive document written for a specific, time-pressed reader who is scoring dozens of similar documents. The strongest ideas regularly lose to weaker ones that are simply easier to say yes to.
"This project investigates the role of X in Y" tells a reviewer what you'll do, not why it matters. Leading instead with the specific gap in current understanding, what's known, what isn't, and why that gap matters now, gives the reviewer a reason to keep reading with the right expectations already set.
Vague questions ("exploring the relationship between...") are hard to evaluate and harder to fund, because a reviewer can't picture what a completed, successful project looks like. A falsifiable question, one with a clear answer that the methodology could actually produce, signals that you know exactly what "done" looks like.
Listing methods (e.g. "qualitative interviews will be conducted") without justifying why that method suits this specific question is one of the most common weaknesses in early-career proposals. Reviewers are implicitly asking: could a different, cheaper, or faster method have answered this equally well? Address that directly, briefly, before it's asked.
An unrealistic timeline is read as a competence signal, not just a scheduling detail. Reviewers reasonably infer that if you've underestimated how long recruitment or data collection takes, you may have underestimated other things too. Build in contingency explicitly, and say so, rather than leaving it implicit.
"This research will contribute to the field" is true of almost any competent study and therefore persuades no one. Naming the specific audience who will use the finding, and what decision or understanding it changes for them, is what separates a generic significance paragraph from a compelling one.