Proposals for livestock investment are rejected far more often than they are funded, and the reasons repeat. Very few of them concern the technical merit of the idea. Most concern whether the document demonstrates that the idea can be delivered, measured, and defended.
What the reader is actually assessing
An appraisal officer reading a concept note is answering four questions, usually in this order:
- Is the problem real, and is it the problem this intervention solves?
- Will this specific intervention change it, and what is the evidence?
- Can this organisation deliver it at this scale, on this budget?
- Will we be able to tell afterwards whether it worked?
A document that answers all four survives appraisal even when the idea is unexciting. A document that answers only the first two — which describes a large share of submissions — does not, however compelling the technical case.
The recurring failures
The problem is described, but not evidenced
"Low productivity" is a symptom with many causes. Whether the binding constraint is disease burden, dry-season feed, genetics, market access or animal health service coverage determines the entire design. A proposal that has not established which constraint actually binds is proposing an intervention on the basis of assumption, and appraisers recognise this quickly.
The logic jumps
The chain from activity to outcome is often missing a step. Training is delivered — but what makes participants apply it? A service is established — but who pays for it once the project closes? Each link needs to be stated, along with the assumption it depends on. The assumptions are usually where the risk actually sits, and burying them makes a proposal look either naive or evasive.
Beneficiary numbers are asserted
Large reach figures with no derivation are a familiar signal. A defensible number is built up: this many households in the target area, this proportion keeping the relevant species, this coverage rate, over this period. Showing the arithmetic is more persuasive than a bigger unexplained figure.
No credible delivery vehicle
Funders are assessing institutional capacity alongside technical design. Who implements, what have they delivered before at this scale, what is their financial management capacity, and what happens if the key individual leaves? Where capacity is genuinely thin, saying so and budgeting to strengthen it is more credible than implying it exists.
Monitoring designed after the fact
If the baseline is not defined before implementation begins, the effect cannot be demonstrated later. Retrofitted monitoring produces activity counts — animals vaccinated, farmers trained — rather than evidence of outcomes, and evaluators will report exactly that.
Sustainability is a paragraph, not a plan
"Activities will be sustained through government uptake" is not a plan unless the relevant budget line, institutional owner and timeline are identified. This section is read with particular care, because it is where over-optimism concentrates.
Practical drafting advice
Write the results framework before the narrative. If the outcome indicators cannot be specified, the intervention logic is not yet finished, and the narrative will paper over the gap.
Name the risks, including the uncomfortable ones. A proposal with a candid risk section and credible mitigation reads as competent. One with no serious risks reads as unexamined.
Cost realistically. Under-costing to look competitive produces implementation failure, and experienced appraisers price the omissions themselves.
Match ambition to the instrument. A design that suits a large sovereign loan does not suit a small grant window. Reading the funder's own criteria and answering them in their own terms is a surprisingly large share of the work.
None of this is about presentation. It is about whether the thinking behind the document is finished. A proposal is fundable when the reader can see that the author has already asked themselves the hard questions — and has answers.