What a Funder Has to Defend to Their Committee

A foundation's programme officer reads your proposal, asks good questions and says they will take it forward. That sentence starts the second half of the decision. The officer now writes a paper for a grant committee, a board of trustees, a family principal or a panel of assessors. Those people did not hear your call. They read the paper, question the officer and then approve, defer or decline. The recommendation carries the officer's name, and their judgement goes on the record with it.

One Technology, Three Funding Decisions sets out how venture, corporate and grant funders test different things. This guide follows the person who carries a grant case into a room you never enter.

The person you meet writes a recommendation

The Belief Gap, the 2026 guide by Aaron C. Leaman, checks six gates before any work on the case begins. One of them is authority, which asks whether this person can decide. In many funding processes, the person you meet recommends while another body approves. The guide's answer is to redesign the decision around the person in front of you. "Their decision is whether to take the case to that committee, so give them what they will need to defend it there."

That changes the job of the proposal. It has to make one person's recommendation easy to write and safe to defend. The officer carries three exposures. The work they back may fail to deliver. It may deliver and turn out to sit outside the funder's strategy. Or a committee member may ask a question the paper leaves them unable to answer. A recommendation puts their judgement on the record in a way a decline seldom does.

Check the mandate before the proposal

A proposal can fit the organisation and still miss the team, programme or funding instrument that owns the decision. Start by writing four lines. Which team owns this issue. Which objective the work serves. Which instrument that team can use. Which person can recommend it onward.

This matters when a funder is exploring a new structure as well as a new project. The officer may need to defend the mechanism internally before they can defend your application. Treat that as a separate decision. Give them the language, evidence and risk boundary for the structure first, then the case for your work inside it.

If the answer is outside this team's mandate, the useful next step is a referral or a different funder. Better writing cannot turn the wrong mandate into the right one.

What the committee will ask

Public programmes often score applications against published criteria. A family office may decide through one principal and an adviser, and a foundation board weighs each grant against its portfolio. The following questions form a useful working test for a funding case. Replace them with the published criteria and internal questions of the funder in front of you.

1. Fit. The link to the funder's strategy and why this organisation is suited to the work.
2. Change. What becomes different because of the money, by when and how the funder will know.
3. Contribution. What the grant adds and which part of the result the funder can reasonably claim.
4. Budget. The match between each cost and the work described.
5. Delivery. The team's ability to deliver and the plan for key-person risk.
6. Other money. Who else funds the work, and whether this grant unlocks or depends on that capital.
7. After the grant. What continues when this funding ends and which resource carries it.
8. Exposure. The reputational or delivery risks and the response to each.

Some of these belong to the gates. A grant outside the funder's mandate may be ineligible regardless of its communication. Test eligibility, funding instrument, authority and timing with the funder before working on a narrative. Find out before you rewrite anything. When Better Communication Is the Wrong Answer works through each check.

Structure the case around the recommendation

Build the proposal so the officer can lift the recommendation, amount and reason into the front of their own paper. Put the decision first and the background after it.

1. The decision. The amount, the period, what it pays for and when the funder decides.
2. The problem in the funder's terms. The funder's own stated objective, in its own words, and the gap your work fills inside it.
3. What the money does. Activities, the outputs they produce and the outcomes those lead to, with the budget lines beside them.
4. Evidence so far. Each result with its status and source.
5. What is still uncertain. What you do not yet know, and how this grant reduces it.
6. Risks. Each named risk, who carries it and what you will do if it happens.
7. Other funders and the plan after the grant. Who else pays, on what status, and which money takes over when this grant ends.
8. The next step. What the officer needs from you, and by when.

The third item is where funder cases most often come apart in the material we read. The narrative leads with outcomes, and the budget is mostly made of costs the narrative never mentions. Committees read the budget. A reader should be able to point at any budget line and find the activity it pays for in the text.

Budget lines that look administrative can carry the delivery model. Relationship-building, technical assistance, monitoring and local coordination need a stated purpose in the narrative if the budget pays for them. A reader should be able to point at any significant line and find the activity and outcome it supports.

State outcomes the officer can repeat

A committee member will quote one sentence of your outcomes back to the officer. Write that sentence so it survives being quoted. Use a measure, baseline, target, date and verification method when the programme is mature enough to support them. For exploratory grants, define the learning decision, milestones, evidence that will be produced and what a funder will know at the end. Do not invent a quantitative outcome to fill a template. The figures in this example are illustrative.

Before. "The programme will transform livelihoods and restore biodiversity across the region."

After. "By month 18, 120 households at three sites will earn income from agroforestry plots, against 40 today, recorded in quarterly sales logs that our field partner checks. Habitat recovery takes longer than this grant, so for this period we report seedling survival at 12 months on fixed plots."

The second version tells the committee what it can hold the officer to.

Strong figures need the most care because they are easy to repeat in committee. Give each one a stated measure, baseline, date and source. Where several organisations contribute to the result, say which part your work can reasonably claim and which remains shared.

Name the evidence limits before the committee does

Expect the funder to look you up. A funder may check the organisation's website, published accounts and prior claims before recommending it. Run the public-record check in advance, and separate it from the funder's own due diligence. A committee member who finds one figure overstated tends to discount the rest.

Run this check before the proposal goes.

• Outside figures. Trace every number you cite to its published source. Quote the source's own wording, date and page, and correct any figure the source does not support at the size you state.
• Your own claims. Mark each as measured, estimated or assumed, and say what would confirm it.
• Your public record. Read your website and your last annual report as the officer will. They should describe the same programme, the same numbers and the same team as the proposal.
• What you do not know. Write three to five lines under that heading in the proposal itself, each with how and when the grant will reduce it.

An officer who can name the limits before a committee member does sounds in command of the case. How to Build Credible Impact Stories From Evidence covers the labelling in more depth.

What to hand the programme officer

Give the officer a pack they can lift into their own template, with each item standing alone.

• The recommendation sentence, drafted. "We recommend a grant of [amount] over [period] to [organisation] to [activity], because [reason tied to the funder's strategy]. The main risk is [risk], and [response]." The officer will rewrite it in their own words. Writing it yourself shows whether your case produces that sentence at all.
• A one-page summary in the order of the eight steps above.
• The budget, reconciled to the activities, with its assumptions stated.
• An outcomes table with outcome, measure, baseline, target, date and method in each row.
• An evidence note listing each claim, its status and a link to its source.
• A risk register with each risk, its owner and the response.
• Other funders, with amounts and status marked as confirmed, applied for or in discussion.
• The plan after the grant, naming which money takes over. the nature restoration finance guide shows how grant money works best with a defined job and a point where it hands over.
• Answers to the three hardest questions you expect the committee to ask.

Then test the pack. Give it to someone who works in grant-making and has not seen your work. Ask them to write the recommendation sentence and to mark the first page where they could no longer defend it to their own committee. That mark is a working hypothesis for the First Break, the point where the case stops carrying evidence into a decision someone can defend. If their sentence differs from yours, rewrite the summary before you touch anything else.

The same logic applies to a buyer's champion inside a company, covered in What Your Buyer Has to Defend After You Leave the Room. The method for naming the decision and its owner is in Start With the Decision.

When a case has to reach a committee you will not meet, we build the funding narrative, the proposal and the pack the programme officer carries, through our pitches and decision materials work. If the officer likes the work and the decision still has not moved, The Belief Diagnosis finds where it stops and what to fix first, before anything is rewritten.

Sources and further reading

• The Belief Gap, Aaron C. Leaman, version 1.1, Brighter Future, 2026