The three claims every proposal must make
Strip away the section headings and every successful proposal argues exactly three things: this question is worth answering (significance), this design can actually answer it (feasibility of method), and this person/team can execute it with these resources in this timeframe (feasibility of plan). Committees reject proposals that nail two and skip one — most often the third.
Before writing, find out what your reader expects: a PhD application proposal (1,500–3,000 words, weight on the candidate and the question), a thesis/confirmation proposal (weight on method and timeline), or a funding proposal (weight on significance, impact, and budget — and a strict template). The structure below adapts to all three; the emphasis shifts.
1. Title, problem, and research question
Open with the problem, not the literature: one or two paragraphs establishing what is broken, unknown, or contested in the world, and why anyone outside your subfield should care. Then state the research question — specific enough to be answerable, framed so the reader can imagine what an answer looks like. Add two to four sub-questions or hypotheses if the design has natural components.
A working title earns its keep: concrete nouns, the population or setting if relevant, no puns. Committees skim; the title and the research question are often read ten times more than the rest.
2. A literature review that ends in a gap
The proposal’s review is short — usually a fifth of the document — and ruthlessly directional: what is established, where the disagreement or silence is, and how your question lands in that gap. Cite the field’s core and its last two years; both absences get noticed. End the section with an explicit gap statement: "No study has yet…" or "Existing work cannot distinguish X from Y because…".
3. Methodology: the section committees read twice
Describe design, participants/data sources, measures, procedure, and analysis plan in enough detail that a skeptical reader can check the logic: does this design actually discriminate between the answers to the research question? Justify the key choices against alternatives — why interviews rather than a survey, why this population, why this sample size — with citations for the methods themselves.
Two credibility signals reviewers look for: a real sample-size justification (power analysis for quantitative work, a saturation argument for qualitative) and honest treatment of limitations and risks with mitigation, including ethics approval where human participants are involved. A proposal with no limitations section reads as naive, not strong.
4. Timeline, outputs, and resources
Break the project into phases with dates — ethics, data collection, analysis, writing — and be honest about dependencies: ethics approval before recruitment, pilot before main study. A simple table or Gantt-style list is enough. For funded proposals, map the budget onto the phases and name the concrete outputs (papers, datasets, software, the thesis) with rough dates.
Timelines fail in review for two reasons: no slack (a plan where every step starts the day the previous one ends) and mismatch with the sample-size claims (recruiting 400 clinical participants in two months). Committees have seen both a hundred times.
Why proposals get rejected
The recurring rejection reasons, from committee members’ own accounts:
- A topic instead of a question — "exploring X" with no answerable core.
- Method–question mismatch: a design that cannot in principle produce the answer.
- No sample-size or saturation justification at all.
- A literature review that summarizes but never lands on a gap.
- Overpromising: three studies’ worth of aims in one project’s timeline.
- Template violations in funding calls — wrong length, missing sections. Desk-rejected unread.
Where Kahubi fits
Kahubi’s grant flow can find live funding calls (grants.gov, Vinnova, EU portals), extract their requirements, and draft proposal sections against them; the literature search and library chat build the gap argument from real papers; and power-analysis and survey planning land the methods numbers directly in the draft — which compiles to PDF or exports to .docx for whatever template the committee demands.
Last updated 2026-08-07.