Assessors read a great many applications that are clear, well structured, free of error and still unfundable. That combination confuses people, because the obvious explanation, that the writing let it down, is usually wrong. The problem sits underneath the writing.
Four failures that no amount of editing fixes
The need is asserted rather than evidenced. The model is described in the organisation's internal language rather than in terms the funder can assess. The outcomes are aspirations rather than measures, so there is nothing to hold the program to. And the budget quietly tells a different story from the narrative above it. Every one of these is a design fault, and prose cannot repair any of them.
What a program logic is actually for
A program logic is not a compliance artefact. It is a claim about causation, written down so it can be tested. Inputs, activities, outputs, outcomes, and crucially the reasoning connecting each step to the next. Its value is that it makes disagreement possible. If a step in that chain cannot be defended in a room, it cannot be defended by an assessor either, and better to find that out in week one than in year one.
The order matters
Design first, write second. Where the model is already strong, the writing is close to transcription. Where it is not, writing first produces a fluent description of something that will not survive scrutiny. Organisations resist this order because design feels slower, and it is, right up until the third unsuccessful application.
The part that keeps paying
The program logic and outcome framework do not expire with the funding round. They carry into every subsequent submission, into reporting, and into the conversation you have with your board about whether the program is working. That is usually worth more than the individual grant.
