A grant application must tell a coherent project story.
A grant application presents what you wish to achieve, the necessary means, and the support requested. The funder must be able to understand the link between these elements without reconstructing your reasoning themselves.
The guiding thread is simple: one objective, actions, expenses, and appropriate evidence. Each piece must help to understand or verify a part of the project.
The list of expected documents depends on the scheme, your structure, and the stage of the application. An application file and a payment request are not prepared with exactly the same documents.
If you are still unsure about the solution to request, start with our guide to innovation funding according to your stage. The writing work becomes more useful when the track already corresponds to your project.
1. Check the rules before you start
Before writing, gather the scheme sheet, its regulations, and the instructions from the submission portal. Note their date and keep the versions used.
Your first reading should answer a few questions:
- Who can apply? Status, location, size, or age of the structure.
- What project is targeted? Objectives, activities, and stage of development.
- What expenses can be examined? Categories, period and method of calculation.
- When should you submit? Possible deadline and preliminary steps.
- What documents are required? Mandatory templates, signatures and appendices.
- How is the support paid? Conditions, payment requests and expected follow-up.
Check the schedule before incurring expenses
Depending on the scheme, incurring an expense too early may jeopardise its consideration. The French Tech Grant sheet states that expenses incurred before the submission of the application cannot be retained.
Do not automatically transpose this date to another aid. Clarify the applicable rule for your file, especially before signing a quote or starting work. An initial exchange with an advisor does not necessarily replace the required submission.
2. Present the project with concrete actions
Your reader should quickly understand what will change thanks to the project. Start with the current situation, then explain the desired outcome and the work needed to achieve it.
You can structure your presentation around five elements:
- The need: the difficulty or opportunity you are addressing.
- The audience: the users, clients or beneficiaries concerned.
- The objective: what you wish to have achieved by the end.
- The actions: the planned steps, their responsible parties and their schedule.
- The expected results : the elements that you will be able to observe or measure.
Replace broad intentions with a readable programme
Imagine you are at the head of a small to medium-sized enterprise and you wish to test a new solution with professional clients. "Accelerating our innovation" describes an intention, but still leaves many questions open.
You could specify that the project involves adapting a prototype, organising trials within a defined scope and analysing the results before a deployment decision. The funder would then understand what the requested resources should enable to achieve.
Present future results as objectives, with their assumptions. A planned test is not a test conducted; an interested client is not a signed contract.
Link your project to the selection criteria
Take the criteria announced in the regulations and identify, for each, the elements of your project that meet them. You can use a working grid "criterion, response, available proof".
If a criterion remains poorly supported, indicate the work to be done before submission. An ambitious formula does not replace missing information.
3. Build a budget that you can explain
The budget translates the action programme into expenses. For each line, you must be able to explain its usefulness, its calculation and its schedule.
Start with the total cost of the project. Then identify the items proposed in the application, subject to the rules of the scheme.The project budget and the amount of expenses retained for aid may be different.
| Proposed position | Question to be resolved | Possible preparation element |
|---|---|---|
| Team time | Who is involved, in what action and with what workload? | Forecast distribution of work and requested calculation method |
| External service | What result do you expect from the provider? | Detailed quote and scope of mission |
| Equipment | What is its purpose in the project and how should its cost be presented? | Quotes and accounting rules to be confirmed |
| Tests or trials | What needs to be checked and under what conditions? | Testing programme, schedule and estimate |
| Other expenses | What direct link exists with the planned actions? | Explanation of the need and document expected by the system |
This table helps to prepare your budget. It does not mean that all these items are eligible for the sought grant.
Make the calculations verifiable
Avoid a line "development: total amount" if you can distinguish the work and resources mobilised. Document the quantities, periods or services that explain your estimate.
Also check the presentation convention: excluding tax or all taxes included, treatment of VAT, actual expenses or planned flat-rate method. For certain programmes, costs are calculated according to specific rules; use the requested templates.
Distinguish expenses and resources
The funding plan shows how you intend to cover the cost of the project. Clearly separate:
- the resources already confirmed;
- the ongoing requests;
- the funding still being considered;
- the amount requested in this application.
Have the rules on accumulation checked and declare any other requested support according to the guidelines. Do not assume that the same expense can be covered multiple times without reviewing the applicable rules.
Finally, prepare a cash flow schedule. Even when support is granted, its payments may depend on milestones and justifications. Our guide on non-dilutive funding and its limits delves into these points of attention.
4. Organise the justifications from the preparation stage
The simplest way is to prepare a shared file with a tracking list. For each document, indicate the responsible person, the expected date, and the available version.
You can organise the documents into four sets:
- Structure: identity of the applicant organisation and required administrative documents.
- Project: presentation, schedule, partners, and technical elements.
- Budget: estimates, quotes, calculations, and planned resources.
- Monitoring: elements of achievement and payment to be gathered during the project.
Distinguish between estimation, achievement, and payment
These documents do not answer the same question:
| Document | What it helps to establish |
|---|---|
| Quote | The proposed scope and estimated cost of a service or purchase |
| Invoice | The billed expense, without demonstrating its payment on its own |
| Accepted proof of payment | The settlement of the expense according to the funder's requirements |
| Report, deliverable or minutes | The execution of an action or the expected output |
| Time tracking, when requested | The allocation of work to the project according to the required method |
The exact list remains that of the system. For European funds, simplified cost methods may change the documents to be provided: do not systematically request the same file from all projects.
The national portal offers guides for project holders and beneficiaries of European funds, organised according to the relevant authorities and territories. They provide an entry point to find the appropriate guidelines.
Keep a simple organisation
Assign a reference to budget items and reuse it in your filing. For example, a testing service may have the same reference in the quote, financial table, and tracking file.
Keep a reference version of the documents. The file "final-budget-really-final" also deserves a retirement: prefer a readable date and version number.
The R Employment case: linking multiple needs to a funding approach
R Emploi combines the reuse of building materials and professional integration. The organisation needed to finance skills, equipment, and reorganisation requirements related to a change of premises.
Vivinnov worked on the link between these needs and the overall project, then on the avenues to pursue: business foundations and public schemes. The support focused on targeting, preparing applications, and following up on the processes.
This case illustrates three useful points for preparing your file:
- Distinguish the needs, even when they contribute to the same development.
- Explain their usefulness, by linking them to the actions and the relevant audiences.
- Adapt the applications, according to the interlocutors and their expectations.
The R Emploi client case details the steps taken. It shows the preparation and submission work, without confusing these stages with a funding decision.
5. Review the file as someone discovering the project
Before submitting, have the file reviewed by someone who has not followed its drafting. Ask them to summarise the objective, the main actions, and the use of the requested amount.
If these elements remain difficult to rephrase, simplify the relevant passages. Add useful explanations rather than new technical vocabulary.
Your final check can be summarised in a few points:
- Do the objectives correspond to the described actions?
- Does each significant expense have a justification?
- Are the amounts and dates identical in the different documents?
- Are the confirmed resources distinguished from the ongoing requests?
- Are the expected annexes present, legible and up to date?
- Are the signatures and mandatory fields completed?
- Is there a person responsible for transmission and follow-up?
Also allow the necessary time to submit on the portal and resolve any file or access issues. The last evening is rarely the best time to discover a required format.
6. Also prepare for the continuation of the submission
Keep the submitted version, the annexes and the acknowledgment of receipt. Note the date, the contact responsible for follow-up and any requests for additional information.
A submitted file does not mean it is accepted. If a favourable decision occurs, review the conditions before building your follow-up: schedule, payments, indicators, communication obligations and supporting documents.
For European aid managed in Occitanie, the file follow-up guide specifically recalls the traceability of expenses, informing the instructing service in case of changes and the retention of documents. These obligations must be applied according to your awarding act and the programme rules.
If the project changes, contact the relevant service to find out what procedure to follow. Do not wait for the payment request to report a significant change in budget or schedule.
Frequently asked questions
No, the sections and documents depend on the organisation and the scheme. You can prepare a common base presenting your structure, the project and its budget. Then adapt this base to the required criteria and templates. A reused file without proofreading may retain amounts or objectives that no longer correspond to the request.
Not necessarily: an application can relate to a project yet to be completed. Estimates and quotes can then help explain the budget, according to the guidelines. Proofs of completion and payment are generally examined at other stages, with specific requirements for the scheme. Make sure to check the start-up rules before incurring expenses.
The amount retained depends on the decision and the conditions of the scheme. Some expenses of the project may not be taken into account, and a portion may remain to be financed. The payment terms may also create a discrepancy with your payments. Therefore, prepare a complete financing plan and cash flow monitoring, beyond just the requested amount.
Your next step
Take your budget and link each item to an action, an explanation and a document to prepare. You will quickly identify what is solid and what still deserves further discussion with the funder.
Do you want support to organise this work?
Our support for funding searches can cover the framing of the need, the preparation and monitoring of files, according to the agreed mission.
Let's talk about your project and your upcoming deadline to clarify the steps to prioritise.
Let's talk about your project