Writing proposals that survive an appraisal committee

Appraisal committees have a reputation among proposal writers as black boxes — documents go in, and months later approval, rejection or an interminable query cycle comes out, with little visible logic. Having sat on both sides of that table, we can report that the process is far less mysterious than it appears. Committees reject proposals for a small number of recurring, predictable reasons, and almost none of them is "the cause was not worthy."

A committee — whether it is a donor's grant panel, a CSR board, a state-level sanctioning committee or a district-level vetting body — is not reading your proposal the way you wrote it. You wrote it as an advocate. They read it as risk assessors, asking one compound question: if we put money into this, what is the chance we get the promised results, on time, without embarrassment, and with accounts we can defend? Every section of the proposal either answers that question or wastes the committee's attention. Here is how the strong ones answer it.

Make the problem specific enough to be checkable

The weakest section of most proposals is, surprisingly, the problem statement. Writers treat it as throat-clearing — broad statistics about the state or the country, quotations from policy documents, a paragraph of urgency — before hurrying to the activities they already intend to do. Committees read this and register a red flag: this organisation starts from its solution, not from a problem it has examined.

A strong problem statement is narrow, local and checkable. It names the blocks or panchayats, describes the specific breakdown — not "poor health-seeking behaviour" but what people do instead and the observable reasons why — and cites evidence at the right scale, including the organisation's own field observation, honestly labelled as such. If credible local data does not exist, say so and build a rapid assessment into the first quarter; committees respect that far more than national figures stretched over a tehsil. One test serves the whole section: could a sceptical committee member visit the area and verify your description? If yes, you have a problem statement. If no, you have an introduction.

Show the causal chain, and show where it could break

Between "we will conduct trainings" and "maternal health outcomes will improve" lies a chain of assumptions, and appraisal committees are professionally suspicious of proposals that skip the links. Write the chain out explicitly: we do X; because of X, this group starts doing Y; because of Y, condition Z improves — provided these assumptions hold.

The counter-intuitive advice is to display the weak links yourself. A proposal that says "this design depends on ASHA workers having time for the additional protocol; where caseloads make that unrealistic, we will do the following instead" reads, to a committee, as the work of people who have actually run programmes. Proposals with no stated risks are not read as strong; they are read as naive, and naivety in a proposal predicts surprises in implementation, which predict awkward review meetings. Committees are staffed by people who have chaired those meetings.

Budget as an argument, not an annexure

Committee members read budgets the way editors read prose — for character. Three failures recur.

1. Round-number syndrome. Line after line at tidy lakh figures signals that nobody actually priced anything. Real budgets have unglamorous numbers derived from unit costs, and showing the unit-cost arithmetic is worth more than any narrative paragraph about efficiency.
2. The misaligned budget. The narrative says community mobilisation is the heart of the programme; the budget says vehicles and salaries are. Committees put the two side by side. Make sure they agree before the committee does it for you.
3. The vanishing Year 3. Costs that plainly continue — honoraria, maintenance, monitoring — quietly disappear from later years to fit the ceiling. Every experienced appraiser has seen this move and none is fooled. If the ceiling is genuinely too low for the design, shrink the geographic scope, not the arithmetic honesty.

While you are at it, answer the sustainability question with mechanics rather than adjectives. "The community will take ownership" convinces no one. "The gram panchayat has passed a resolution to include maintenance in its own plan; recurring costs converge with an existing scheme's norms; handover to the line department is scheduled and named in the district plan" — that convinces, precisely because each claim can be verified.

Respect the committee's actual reading conditions

Finally, some craft. Your proposal will most likely be read in a stack, late, by people who will spend twenty minutes on it before the meeting and rely on a two-page appraisal note prepared by someone junior. Write for those conditions. Put the entire argument — problem, response, cost, results, risks — into a genuinely self-contained summary, because for most of the committee the summary is the proposal. Answer the eligibility and compliance checklist items exactly where the format asks for them; a missing registration document or an unaddressed criterion gives a busy committee its easiest possible reason to defer you to the next cycle, and next cycles have a way of becoming next years. And keep a consistent set of numbers: if the summary says one figure for beneficiaries and the log-frame another, you have handed a sceptic the only weapon needed.

None of this is about gaming a system. Appraisal, at its best, is a due-diligence discipline, and proposals that survive it are usually programmes designed well enough to survive implementation too. Writing for the sceptical reader forces clarity about problem, mechanism and money that benefits the programme long after sanction. That is the standard our proposal development practice works to.

If you have a proposal heading toward an appraisal committee — or one that has just come back with queries — talk to us about strengthening it.