A grant proposal makes an argument for a project and for the person proposing it.
The proposal explains what is known, identifies a specific gap, and says how the project will address it. It also has to explain why the result would matter.
I often see proposals move from relevant background to detailed methods without clearly stating the contribution. The writer knows why the project matters and assumes the committee will infer it. A committee reading many applications may not.
The language matters too. Proposals full of “there is a need to study” and “it is important to investigate” hide behind passive constructions. The field’s needs do the persuasive work. The researcher disappears.
“I will analyze” names who will do the work. Grant committees assess the idea and whether the applicant can carry it out. As I say in the concision workshops, the reviewer may be reading at 9 PM after fifteen other proposals. They need to understand the project without reconstructing it.
Scope also affects credibility. A broad project leaves reviewers unsure where the work begins and ends.
In workshops, I ask which sounds more credible: “examine employment integration challenges facing recent immigrants in Canada,” or “examine how recent immigrants in Edmonton secure their first professional employment, using interviews and partnership with a local settlement organization”?
The second version gives the committee a population, a place, a method, and a plausible scale. It is also easier to connect to the project’s contribution.