Every year, funders receive hundreds of applications for a handful of awards. The ideas are often similar in quality — what separates funded proposals from rejected ones is almost always structure and clarity.
Start with the problem statement. Describe the need in specific, local terms, backed by credible data. 'Youth unemployment in Kenya' is a topic; 'youth unemployment among TVET graduates in Kajiado County, where 61% remain out of work two years after graduation' is a problem a funder can act on.
Next, show your intervention is logical. Each activity should trace directly to an outcome, and each outcome to the problem. Reviewers use the 'if-then' test: if this activity happens, then this result follows — and the chain must hold without leaps of faith.
Budgets win or lose trust. Every line item should connect to an activity, and totals must match the narrative. A proposal that claims a lean operation but budgets for two vehicles invites rejection at the scoring stage.
Finally, comply ruthlessly. Page limits, font sizes, attachment lists, and deadlines are the first screening filter. Brilliant non-compliant applications are not read. Build a checklist from the call document and verify every item before submission.