Selection panels read hundreds of applications in a compressed period. Most are competent, and competence does not distinguish. What distinguishes is evidence of fit and specificity — two things generic applications cannot fake.
Fit is assessed first, and it is checkable
Every scheme funds something particular: a discipline, a region, a career stage, a policy goal. Panels begin by asking whether you are what the scheme is for.
Read the scheme’s own description of its purpose, and read the profiles of recent recipients. Then make the alignment explicit rather than leaving the panel to infer it. If the scheme funds research with development impact, your application should say what impact, on whom, through what mechanism.
Applications that could have been sent to any funder are rejected quickly, and correctly.
Specificity is the strongest available signal
"I am passionate about improving education in rural communities" is a sentence anyone can write.
"I want to test whether the teacher-mentoring model piloted in three Punjab districts holds in schools without reliable electricity, because the original evaluation excluded them" is a sentence only someone who has done the reading can write.
The second demonstrates knowledge, specificity, and a real gap. It is also more interesting to read, which matters more than it should at application two hundred.
The research proposal must be legible to a non-specialist
Panels are usually mixed-discipline. Your assessor may be three fields away.
Lead with the problem in plain language, then the question, then the approach. Technical detail belongs after the reader is oriented, not before. If a colleague from another department cannot restate your project after one read, the panel will not either.
Recommenders need material, not a request
The strongest letters are specific, and specificity requires that your recommender has the details in front of them. Send, four weeks ahead:
- The scheme’s description and criteria
- Your draft proposal and personal statement
- A short note on what you would like emphasised, and why
- A reminder of concrete things you did in their course, lab, or supervision — with dates
This is not presumptuous; it is standard, and experienced referees expect it. A letter that says "she completed a difficult replication study in my methods course, identifying an error in the original coding scheme" carries weight. "A strong and diligent student" does not.
Budget and timeline are assessed as evidence of realism
Underestimating costs does not read as modesty. It reads as inexperience — and panels have seen projects fail from exactly that.
Cost the work honestly, justify each line briefly, and build in contingency. If the scheme caps funding below the true cost, say how the remainder is covered.
Write it early enough to leave it alone
The most common practical failure is submitting a first draft under deadline pressure. Applications improve substantially on rereading after a break, and the improvements are the specific kind — vague sentences becoming concrete, claims acquiring evidence.
Finish two weeks early. Reread cold. The version you send should not be the version you wrote.
We do this work every week — for MPhil and PhD candidates, faculty, and whole departments.
Start a conversation
