Thank you for sharing these materials, Benard, and to Dr. Kagaigai for such a practical session. A few points landed with particular weight, given what we have been navigating at Purpose Rwanda in recent proposal cycles.
The PICO-Gap framework for background writing (Problem, Importance, Current gap, Our approach) put language to something we had been doing instinctively but not naming clearly. In our recent applications, we noticed our strongest sections were always the ones where we led with local, specific data rather than general statements about addiction as a global issue. This material confirms why: reviewers need to feel the urgency at the local level before they can evaluate the solution.
The point on SMART objectives, particularly the warning that "reviewers are experienced, overpromising destroys credibility," is one I now actively watch for in our own drafts. We learned this directly after an earlier rejection, where I suspect our objectives read as more ambitious than our budget and timeline could genuinely support. Rebuilding a smaller, more honestly scoped application afterward taught me that achievable is not a lesser standard than ambitious, it is what makes ambition believable.
The line "every budget line must trace to a specific activity in the methodology" is one I now treat as a hard rule. While preparing a recent budget for a research-preparation grant, we deliberately itemized every cost against a specific deliverable, rather than presenting broad category totals, precisely to avoid the mismatch this material warns against.
One personal takeaway I will apply going forward: writing the objectives section in active voice, "we will," not "it is proposed that," as the material emphasizes. It is a small shift in language, but it reflects a larger shift in posture, from asking permission to declaring intent.
Grateful for this resource and for a community that keeps returning to the fundamentals that actually determine funding outcomes.
