How to Write a Grant Proposal
Funders Actually Read

Most grant writing advice is useless.

Not because the people giving it don't mean well — they do. But the standard guidance ("be clear," "tell a compelling story," "show impact") describes the destination without telling you how to get there. It assumes the barrier is effort or awareness. It usually isn't.

The barrier is translation. Your organization knows what it does. You know why it matters. You've watched it change lives. What's hard is converting that knowledge into the specific language government and foundation funders are trained to look for — and doing it in a way that makes your proposal easier to approve than to reject.

I've written funded proposals and losing ones. The application that secured $200,000 from the Ontario Trillium Foundation — for an addictions pilot program serving individuals experiencing homelessness with high acuity needs — was the same organization's third Trillium submission. The program hadn't changed materially. The proposal had. That's the gap this post is about.

Funders are reading defensively

This is the thing most grant writers don't internalize: a program officer reviewing your proposal is not hoping you'll convince them. They're looking for reasons not to fund you.

Not out of bad faith. Because they have limited dollars, more applicants than they can fund, and an accountability obligation to justify every decision. Every vague claim, every unsupported assumption, every section that doesn't directly answer the stated criteria gives them an easy reason to score you down.

A funded proposal makes that job difficult. It removes the easy objections. It answers the questions the funder will ask before they ask them — about need, about evidence, about capacity, about outcomes measurement. It leaves a reviewer with nothing to flag.

That reframe changes how you write everything.

Your needs statement is not a statistics dump

This is where most proposals lose before they've really started.

The needs statement is not an invitation to cite every housing statistic you have access to. Point-in-time counts, provincial shelter data, national homelessness numbers — funders have seen all of it. What they haven't seen is a clear, specific argument about the unmet need your program addresses, in your community, for your population, right now.

The question your needs statement has to answer is not "is homelessness a problem?" Everyone agrees it is. The question is: why does your program need to exist? What is happening — or not happening — in your service area that your organization is specifically positioned to address? What does the gap look like on the ground? Who falls through it?

The strongest needs statements are hyper-local and primary-evidence-heavy. They cite your By-Name List data, your intake numbers, your waitlist, your community's coordinated access gap analysis. They name the population that isn't being reached and explain why. They make an argument — not a report.

Statistics don't make that argument for you. You make it, and then you use statistics to support it.

Funder fit matters more than proposal quality

You can write the best proposal of your career and lose because you applied to the wrong funder.

Before you write a single word, you need to know: Is this funder actually funding organizations like yours right now? What have they funded in the last two cycles? What outcomes are they prioritizing? Are their guidelines signalling a shift you haven't accounted for?

For Reaching Home applicants, this means understanding your Community Advisory Board's current priorities — what gaps they've identified in your community's system plan, where the funding envelope is being directed, whether your program model aligns with coordinated access goals. A proposal that doesn't speak to your community's designated priorities is a proposal that can't win, regardless of how well it's written.

For foundation funders, it means reading their most recent annual report, reviewing their current grantee list, and understanding whether their strategy has moved since the last time you applied. Funders evolve. Your research should too.

One thing organizations consistently underuse: information sessions and pre-submission consultations. Most government and foundation funders offer them before the deadline. These are not formalities. They're where you hear directly from the people who will score your proposal what they're prioritizing in this cycle. I've walked out of pre-submission consultations knowing exactly what needed to shift before we'd written a word of the full application. That intelligence changes a proposal more than any revision does.

Funder fit is not something you do once and file. It's active intelligence that shapes what you write and whether you write at all.

Know what the grant is actually for

Funder fit is about more than topic alignment. It's about understanding the type of funding you're applying for — and making sure what you're asking for matches it.

This is one of the most common and costly mistakes organizations without dedicated development staff make. They identify a funding need — often a salary, a coordination role, ongoing program costs — and go looking for a grant to cover it. The problem is that most grants aren't designed to fund those things. Government and foundation funders typically prioritize discrete, project-based initiatives: one-time efforts with a defined scope, clear deliverables, and either a built-in sustainability plan or an explicit intent to build lasting capacity. They are not, as a rule, in the business of funding your operating budget.

So when an organization submits a proposal framed around sustaining an existing staff position, or covering program costs that have been running for years, a reviewer sees the mismatch immediately. It's not that the need isn't real. It's that the request doesn't fit the instrument.

The fix is not to disguise operational costs as project costs. Funders have reviewed enough proposals to recognize that framing, and it undermines your credibility for everything else in the application. The fix is to find the right instrument for what you actually need — operating grants, multi-year program support, municipal service agreements — or to restructure what you're proposing into something that genuinely fits the grant's purpose.

Matching the request to the instrument isn't a technicality. It's the foundation everything else is built on.

The narrative has to do something

A grant narrative is not a program description. It is a persuasion document.

A program description tells a funder what you do. A narrative tells them why it will work, how they know you can deliver it, what changes as a result, and why your organization — specifically — is the right one to do it.

That last piece gets underwritten constantly. Organizational credibility is not a given. A funder reading your proposal doesn't already know your track record, your team's expertise, your sector relationships, or your data infrastructure. You have to demonstrate it. Not in a separate section that lists your achievements — throughout the narrative, woven into how you describe your approach.

Those sentences are not equivalent.

Outcomes are not outputs — and evaluation is not an afterthought

This is the mistake that most consistently separates unfunded proposals from funded ones, and it's worth being direct about.

An output is what you do. A meal served. A bed filled. A client contact logged in HIFIS. Outputs matter for operations. They are not outcomes.

An outcome is what changes for the person you serve. Increased housing stability. Reduced emergency shelter use. Improved self-reported quality of life. Sustained tenancy at six and twelve months. Government funders — particularly ESDC and provincial housing ministries — are increasingly outcomes-oriented, and they are sophisticated enough to notice when you've relabeled your outputs and called them outcomes.

The other failure mode is the proposal that names outcomes correctly but never connects them to anything. Strong proposals draw a clear line of sight from project goals to the specific activities that will be carried out, to the deliverables those activities will produce, to the measurable results the funder can expect, to the methods by which those results will be tracked and evaluated. Funders need to know not just that you intend to achieve something, but how you'll measure it and report it back. That chain — goals, activities, deliverables, results, evaluation — has to be explicit. Reviewers should not have to infer it.

Budget narratives are not footnotes

Most organizations treat the budget narrative as an administrative formality. It isn't.

The budget narrative is where a funder decides whether you know how to manage money. An underdeveloped budget narrative — one that lists line items without explaining them, or that doesn't connect expenditures to program activities — signals exactly the kind of organizational capacity gap funders worry about.

A strong budget narrative explains every major line item in the context of program delivery. It justifies staffing levels, explains indirect cost calculations, accounts for any cost-sharing or matching contributions, and demonstrates that the requested amount is proportionate to the scope of work. If there are items that might look unusual, name them and explain them. Don't leave a reviewer to wonder.

Write to the criteria, not around them

This sounds obvious. Organizations routinely don't do it.

Funder guidelines are a marking rubric. Every criterion they list is something they will score. If you address it fully, you score well on it. If you address it partially, you score partially. If you ignore it because your organization has a different and arguably better way of thinking about it, you score zero — regardless of how good your thinking is.

This is not an invitation to write hollow compliance copy. It's a reminder that your proposal exists inside a funder's evaluation framework, not outside it. Your job is to answer their question thoroughly and persuasively, not to write the proposal you think should be funded.

When you don't get funded, reach out

A rejection is information, not a verdict. Most organizations don't ask funders why they weren't funded. They should.

I once had a proposal declined by a municipal funder because the project didn't align with their funding priority for that term — not a judgment on the work, just a mismatch with where the envelope was directed that cycle. We called. They explained exactly that. They also flagged that the project might be a better fit for a different department. It was. That department funded the training program — and didn't stop there. They built sector-wide sessions out of it and opened them to organizations across the community.

That conversation happened because we made the call.

Most funding bodies are not adversaries. Many of them want to direct resources to organizations doing meaningful work. A follow-up after a rejection isn't a challenge to their decision — it's intelligence gathering. You learn what didn't fit, you learn where the fit might actually be, and occasionally you find a door that wasn't visible from where you started.

The organizations that treat rejection as the end of a relationship with a funder are leaving resources on the table.

Getting it right takes more than time

Most nonprofit staff are writing proposals on top of full program delivery responsibilities. They have expertise in the work — not in the translation. That gap is real, and it costs organizations funding they should be getting.

If your organization is preparing a Reaching Home application, an Ontario Trillium Foundation submission, a CMHC proposal, or any other government or foundation funding in the housing and homelessness space, Sibyl Consulting offers fund development support rooted in the sector.