Small associations apply for grants the way most people do their tax return: at the last minute, from scratch, in a panic. Then they wonder why the applications that took a weekend get rejected while a similar organisation down the road gets funded every year.
The difference is rarely the project. It is usually the file.
What funders are actually assessing
Behind whatever form you are filling in, funders are answering four questions.
Does this fit what we fund? The most common reason for rejection, and entirely avoidable. Read the funder's priorities and the eligibility criteria before writing anything. If your project needs reframing to fit, it probably does not fit.
Is the need real and evidenced? "There is a need in our community" is an assertion. Numbers, a survey, a waiting list, a statement from a partner organisation, these are evidence. Funders read hundreds of applications asserting need.
Can these people deliver it? Governance, accounts, track record, and whether the budget is coherent. This is where small associations lose ground unnecessarily, because they have the capability and have not documented it.
Will anything be different afterwards, and how will we know? Outputs are what you will do. Outcomes are what changes. Most applications describe outputs and call them outcomes.
Build the file once
Here is the single change that transforms grant applications from a weekend of work to an afternoon.
Almost every funder wants the same underlying facts in slightly different wrappers. Write them once, properly, and keep them in one document:
Legal name, RNA and SIRET numbers, founding date, registered address
Mission statement, in one sentence, one paragraph and one page
Governance structure, current board with roles and relevant backgrounds
Staff and volunteer numbers
Last two years of accounts, plus the current budget
Beneficiary numbers, with how they are counted
Three concrete examples of work delivered in the last eighteen months, with specifics
Existing partnerships and funders
Standard insurance and compliance documents
Most of the time small associations lose to grant paperwork is spent hunting for facts that already exist, in someone's email, in last year's application, in a folder nobody can find.
Once that file exists, each application becomes selection and adaptation rather than reconstruction.
Writing the application itself
Answer the question asked. Obvious, routinely ignored. If the form asks how you will measure impact, do not describe your activities again. Assessors work through a scoring grid, and unanswered questions score zero regardless of how good the rest is.
Lead with the need, not the organisation. Applications that open with the association's history lose the reader. Open with the problem, in specific terms, for specific people.
Be concrete about numbers. "We will support many young people" is worth less than "we will run 24 sessions for approximately 15 participants each, reaching around 80 individuals over the year." The second is checkable, which is precisely why it is more credible.
Make the budget match the narrative. If the project description emphasises outreach and the budget is 80 percent equipment, the assessor notices. Every significant budget line should be traceable to something described in the text.
Include your own contribution. Volunteer time, existing resources, other funding. Funders are wary of projects entirely dependent on them, and co-funding signals that someone else has already judged you credible.
Say what happens when the grant ends. Even if the honest answer is that the project ends, say so with a reason. Vagueness here reads as not having thought about it.
Respect the word limits. They are part of the assessment. Going over signals that you cannot prioritise.
Before you send it
Have someone outside the project read it. Someone who does not know your work will find the assumptions you cannot see.
Check every attachment listed is attached. Applications get rejected administratively for missing documents more often than anyone admits.
Check the numbers add up. Literally. Budget totals that do not sum undermine everything else on the page.
Keep a copy of what you sent. You will need it for the report, and for next year's application.
After the decision
If funded: diary the reporting deadlines immediately, and start collecting evidence from day one rather than reconstructing it at the end. Funders who get good reports fund again.
If rejected: ask for feedback. Many funders give it and almost nobody asks. It is the cheapest possible improvement to next year's application.
Where AI genuinely helps here
Grant writing is close to an ideal use case, because the underlying facts are stable and the work is reformatting them to different requirements.
Once the core file exists, generating a tailored first draft against a specific funder's questions is fast. Mirage Cloud includes an agent scoped to French association governance and grant files, which handles the loi 1901 context without needing it explained.
Two cautions. Check every number the draft produces against your actual accounts, because a plausible-looking figure that is wrong is worse than no figure. And rewrite the sections that make your case distinctive in your own words. Assessors read a great many applications and generated prose is recognisable. Use the tool to get past the blank page, then make the parts that matter sound like you.
Comments
Log in or sign up to join the conversation.