Writing Problem Statements That Get Read

The problem statement is where most proposals are won or lost. If the reviewer
does not believe the problem is real, urgent, and yours to solve, nothing that
follows will rescue the application. Yet most municipalities write this section
backwards — describing the solution they want instead of the problem they face.

LEAD WITH DATA, NOT ADJECTIVES
Open with a hard fact, not a sentiment. Not "our youth face many challenges,"
but "62% of residents aged 18–29 have no formal employment, and 1,400 leave the
district each year in search of work." Numbers create urgency; adjectives create
doubt.

ANSWER FOUR QUESTIONS
1. WHO is affected — the specific group, disaggregated by sex, age, and
vulnerability.
2. HOW MANY — the scale, with a credible source or clearly stated estimate.
3. WHAT IS THE COST OF INACTION — what worsens, and what it costs in jobs,
income, health, or out-migration if no one acts.
4. WHY HERE, WHY NOW, WHY YOU — what makes your municipality the right place to
intervene and this the right moment.

SHOW THE CAUSE, NOT JUST THE SYMPTOM
Reviewers fund projects that address root causes. "There is no market" is a
symptom; "vendors lose 30% of perishable stock for lack of cold storage and
cannot reach buyers beyond the village" is a cause your project can target.

DON'T SMUGGLE IN THE SOLUTION
The problem statement names the gap; the next section proposes the fix. Mixing
them weakens both. Keep this section a clean, evidenced picture of the pain —
then let the solution earn its place by answering it precisely.

A well-built problem statement makes the rest of the proposal feel inevitable.