Finding the right Local Action Group and checking a LEADER grant

Why the LAG fiche must start from an identified territory

An operational LEADER fiche cannot be universal in the sense of announcing a grant rate, a cap and dates applicable to all project leaders. It must start from a specific Local Action Group (LAG), its catchment area, its strategy and a call for projects that has actually been published. This guide is therefore a method for identifying the right LAG and preparing a verifiable local fiche. It does not claim to describe an open call in a given commune, since that information depends on the chosen territory.

The LAG is the local point of contact that implements the local development strategy. In France, LEADER support is managed within the framework of the FEADER, and the Régions play a central role in implementation. LAGs are formally designated for defined territories; their strategy determines the priorities, the types of operations and the support arrangements. The official national network provides an overview of LEADER and a map for finding the LAGs for the 2023-2027 period. The map and contact details must be checked as of the date of consultation.

For Capital OS, the LAG fiche must distinguish three levels of information: the general European framework, the implementation rules of the Région or the managing authority, and the specific conditions of the LAG or the call concerned. Information coming from a LAG must not be presented as a national rule. A territorial fiche must not be published as "open" without a date, an official source and confirmation that the submission period is still active.

Identifying the competent LAG for a commune

Start from the actual location of the project, not the registered-office address if the investment will be carried out elsewhere. Note the commune, postal code, département, region and, if the project covers several communes, the location of each activity. Then use the official map or directory of the national network. Do not simply choose the nearest LAG: catchment areas are defined and can cross the usual administrative boundaries.

Check the LAG's official name, its lead organization, its catchment area, the coordinator's contact details, the official page, the local strategy and current calls for projects. If in doubt, contact the team and request written confirmation of the catchment area. For multi-site or cooperation projects, ask whether each site must be within the catchment area, whether the lead partner must be established there, and how external partners can take part.

Record the information in the fiche: LAG name, verification date, source, commune covered, contact, strategy version and call status. A fiche that does not contain these fields is not ready to be published as a local grant fiche. It can remain a methodological guide, provided this is clearly stated.

Reading the strategy and the action sheet

The local strategy describes the territorial diagnosis, the objectives, the priorities and the expected results. Action sheets generally specify the types of operations, beneficiaries, expenditure and selection criteria. These documents must be read before presenting the project to the LAG. Identify the objectives the project could contribute to, then quote the exact wording of the strategy in the application.

Build a correspondence matrix. Column 1: strategy objective. Column 2: project activity contributing to that objective. Column 3: evidence of territorial need. Column 4: expected result. Column 5: indicator. Column 6: supporting document. This matrix makes it possible to identify a genuine match or, conversely, a mismatch. If no priority matches, the project must be redirected or referred to another source of funding.

Do not select an action sheet merely because it mentions a word from the project. A tourism project is not necessarily covered by an "attractiveness" priority if the action sheet targets only public services or collective projects. Likewise, an agricultural processing activity may fall under other FEADER interventions or regional aid rather than LEADER, depending on local rules. The match must be assessed on the objective, the beneficiary, the activity and the expenditure.

Checking the eligibility of the project leader and the operation

The local fiche must specify the categories of beneficiaries admitted: local authorities, associations, businesses, farmers, public bodies, partnerships or other structures depending on the call. It must also specify any exclusions, sector restrictions, size conditions, ownership rules and location criteria. Do not reuse a general list of beneficiaries as if it applied to every LAG.

For the operation, document the location, the nature of the investment, the planned start date, authorizations, the timeline, the results and the expenditure. Check whether the project must be new, whether work can begin before the application is submitted, whether a preliminary study is required, and whether certain sectors are excluded. Rules relating to State aid, public procurement, conflicts of interest and the combining of grants can be decisive.

The eligibility of expenditure must be examined line by line. Distinguish between tangible investments, intangible investments, services, studies, communication, operating costs and staff costs. For each line, note the applicable rule, the evidence required and the confirmation obtained. If the information is not published, do not invent an answer: write "to be confirmed with the LAG" and withhold any definitive statement.

The fiche must also describe the obligations after the grant is awarded: maintaining the investment, keeping supporting documents, publicizing the European funding, indicators, control visits or specific obligations. These must be drawn from the official documents of the call and the grant decision.

Checking funding and cash flow

Never display a rate or an amount without a precise local source. A LAG's budget and the total regional envelope are not the amount available to each project leader. The support rate can vary depending on the type of beneficiary, the expenditure, the aid scheme, the co-financing and the call. A figure published as an example must not be generalized.

The fiche must separate the total project cost, the potentially eligible expenditure, the expenditure confirmed as eligible, the amount requested, other sources of funding and the remaining amount to be covered by the project leader. Indicate whether amounts are excluding or including VAT, and how VAT is treated. Document any public co-financing required and the evidence expected. A funding application is not equivalent to a secured resource; flag any funding that is still under review.

A cash-flow timeline is essential. The project leader may need to pay suppliers before the grant is paid out. Plan for deposits, progress statements, processing times, payment requests and any checks. For a small business or an association, this timing gap can be riskier than the final amount to be covered. The fiche should direct the reader to a financial adviser if the project depends on a delayed reimbursement, without promising an unpublished payment schedule.

The combining of grants must be checked against the applicable rules. The same costs cannot be funded twice. Keep a table of funding by expenditure line, period, scheme and funder. If other funding is sought, declare it to the LAG and ask how to coordinate the applications.

Procedure: from first contact to payment

The exact process depends on the territory, but it often includes a pre-eligibility discussion, a formal application, administrative and financial review, selection, the award decision, project implementation and the payment request. The fiche must specify the actual steps and the parties responsible, distinguishing the LAG's facilitation role from that of the authority responsible for review and payment.

Before submission, prepare a project summary, administrative documents, quotes, the budget, authorizations, the financing plan, strategy elements and indicators. Check the submission channel and the format of the documents. Completeness rules and response times must be taken from the official guide. Keep an acknowledgment of receipt and a copy of the submitted version.

During the review, respond precisely to any requests for additional information and keep a record of the exchanges. Do not substantially change the project without consulting the competent authority. A change of supplier, cost, timeline, location or scope may require prior approval.

For payment, keep invoices, proof of payment, contracts, quotes, deliverables, before/after photos if required, competitive-bidding documents and proof of publicity. The fiche must specify the format of supporting documents and the record-keeping obligations only when these are explicitly documented. If the local rule is not accessible, state that it must be confirmed in the beneficiary's guide.

Method for writing a Capital OS local fiche

A local fiche ready for publication must include: an action-oriented title, the grant identifier, the programme, the LAG name, the territory covered, the managing authority, the call status, the date of last verification, the official source, the objective, beneficiaries, operations, expenditure, amount or rate, co-financing, timeline, procedure, documents, contact, post-award obligations and FAQ. For each figure, keep the exact source and the date it was consulted.

Add a "verification level" field. For example: verified in the text of the call; verified on the official page but details to be confirmed; information provided by the LAG in writing; information not published. This field prevents an item that has merely been inferred from being shown as certain. The date of last verification must be visible, and a fiche whose call has closed must be marked "closed" or "historical", never "open".

The title must answer a user intent, for example "Check the LEADER grant from [name] LAG for a rural tourism project". Avoid a generic title that would suggest the funding is available throughout the whole country. The main content must start with the benefit, then give the conditions that have actually been verified. Do not open with a long disclaimer; provide a useful answer first and then distinguish the points still to be confirmed.

Internal linking must connect the local fiche to the overall LEADER guide, to the relevant cluster guides — tourism, local shops, short supply chains, heritage — and to other schemes that can fund a different part of the project. Links must be contextual, not merely a list of keywords. If no active call is confirmed, offer the guide for identifying the LAG and preparing a meeting, without presenting the fiche as an open grant.

FAQ — identifying and working with a LAG

Q1. How do I find the competent LAG? A. Look up the project's commune in the official map or directory of the national network, then confirm the catchment area with the LAG.

Q2. Does the LAG decide all the rules on its own? A. No. It implements a strategy within a European, regional and national framework. The managing authority and the official procedures remain decisive.

Q3. Where can I find the rate and the cap? A. In the applicable action sheet and local call. Do not transpose an amount found in another territory.

Q4. What should I do if no call is open? A. Contact the coordinator to find out the timeline, prepare the project and explore other suitable grants. Do not present a future call as open.

Q5. What documents should I ask the LAG for? A. The local strategy, the action sheet, the regulation or call, the applicant's guide, the list of expenditure, and the submission and payment rules.

Q6. Can expenditure start after an initial meeting? A. Not without checking the applicable rule and obtaining written confirmation. A meeting does not constitute authorization to start.

Q7. How do I know if information is reliable enough to publish? A. It must be linked to a dated official source, or to written confirmation from the LAG. If it is not verified, it must be marked as to be confirmed.

Q8. Can a local fiche be published without amounts? A. Yes, if it is honestly presented as an orientation fiche or a method for making contact, and not as an open call with unconfirmed financial parameters.

Mandatory fields for a published local fiche

• LAG name, catchment area and commune concerned.
• Link to the strategy, the action sheet and the official call.
• Call status and date of last verification.
• Confirmed eligible beneficiaries, operations and expenditure.
• Sourced rate, cap, co-financing and aid scheme.
• Timeline, procedure, contact and documents expected.
• LAG-specific FAQ and clear mention of information still to be confirmed.

Quality-control model before publishing a LAG fiche

Before publishing a local fiche, carry out a two-level check: first the reliability of the information, then its usefulness for the project leader. Reliability requires that each decisive criterion be linked to an official document, a date and a specific territory. Usefulness requires that the page let a business or an association know whether it should get in touch, which documents to prepare and which questions to ask. A page full of administrative vocabulary but without concrete steps does not meet the user's need.

Create a control table with one row per critical piece of information: catchment area, beneficiaries, activities, expenditure, rate, cap, co-financing, dates, start of expenditure, procedure, documents, contact and payment. For each row, note the source, the date consulted, the passage that supports the information, the level of certainty and the next verification date. If a piece of data is not published, explicitly mark it as not provided or to be confirmed. Never replace missing information with an average from another territory.

Check that the call status matches the date of consultation. An open call must include a link to the submission documents and a verified closing date or condition. A closed call must be presented as historical, with a clear indication that it no longer accepts applications. If the LAG indicates that a future call is being considered without an official date, the fiche must use cautious wording and must not invite the reader to apply immediately.

Check the links: they must point to the LAG, the Région or the relevant official authority, and not solely to a commercial aggregator. If the official site redirects or has changed, update the URL and record the change. Named contacts should be kept only if they are published and relevant; otherwise, prefer a functional email address or the official contact page.

Recommended structure for a local LEADER funding fiche

1. Action-oriented title mentioning the territory. 2. Summary explaining in a few sentences the purpose of the call and the projects targeted. 3. Status and date of last verification. 4. Territory covered and LAG name. 5. Objectives and action sheet. 6. Eligible beneficiaries and exclusions. 7. Eligible operations and expenditure. 8. Amounts, rate, cap, co-financing and VAT rules, only if verified. 9. Timeline and submission channel. 10. Supporting documents. 11. Selection process. 12. Post-award and payment obligations. 13. Official contact. 14. Local FAQ. 15. Sources and update date.

The page must primarily answer the questions the project leader asks before investing time: is my project in the right territory? Is my status admitted? What type of project is targeted? Is the call active? Which expenditure is covered? Who should I ask for confirmation? What are the next steps? Regulatory details must be explained when they change the decision or the preparation of the application.

The content must also distinguish mandatory criteria from selection criteria. A project can be eligible without scoring well; it may meet the administrative conditions but contribute weakly to local priorities. Describe the selection criteria only if they are published, and explain how the project leader can document its contribution without promising a score or funding.

Setting up an update schedule

LEADER fiches change when a call opens or closes, when the available budget changes, when documents are amended, or when a LAG updates its priorities. A local fiche must have an owner responsible for updates and a verification schedule. In the absence of automation, define a checking frequency and triggers: new LAG news, a new version of the regulation, a new submission date, a change to the envelope, or a change of contact.

Keep a version history: date, field changed, source, reason and the person who verified it. When a call closes, keep the page for its historical and SEO value if it still adds value, but visibly change its status. Add a link to the current strategy or the LAG's contact details so the reader can find out about upcoming opportunities, without suggesting that funding is still open.

The FAQ must also be updated. An answer about amounts, the closing date or expenditure must not remain unchanged after a call has closed. General questions — how to identify a LAG, why being rural is not enough, how to prepare a budget — can remain stable, whereas answers specific to a call must be dated.

Avoiding content and SEO mistakes

Avoid pages that repeat the same generic text while only swapping the territory's name. A fiche must include specific, genuinely verified information: catchment area, strategy, priorities, beneficiaries, dates, criteria and contacts. If no local data is available, publish a national method guide rather than a fake territorial fiche. Transparency builds trust and prevents search engines from indexing near-identical pages with no distinct value.

Titles should express a useful action, such as "Check the LEADER grant from [name] LAG for a rural tourism project" or "Prepare a LEADER application for a local services project". The page must contain descriptive subheadings, a relevant FAQ and links to the guides that explain the broader concepts. Do not artificially repeat the keywords "LEADER grant", "rural grant" or "FEADER"; explain the conditions, the process and the documents required.

FAQ structured data, if used on the site, must match exactly the visible questions and answers. Do not create artificially universal answers about local amounts or criteria. Internal links must point to complementary content, not to unrelated pages. The page must also offer a clear action: identify the LAG, consult the official call, prepare the documents, or contact the right point of contact.

FAQ — checking and publishing LEADER fiches

Q1. Can a fiche be published without an open call? A. Yes, as a method guide or orientation page, provided it is not presented as an open grant and the information is dated.

Q2. Can the amounts from another LAG be reused? A. No. Amounts and conditions are local and must be linked to the applicable source.

Q3. Which source should take precedence? A. The official documents of the competent authority and of the LAG for the territory and call concerned. A general page serves to explain the framework, not to prove local criteria.

Q4. What should I do if the regulation and the web page seem to contradict each other? A. Do not resolve it by guesswork: contact the competent authority, request written confirmation and log the discrepancy in the audit register.

Q5. How often should a fiche be checked? A. According to the calendar of calls and any published changes. At a minimum, check before publication and before any statement that a call is still open.

Q6. How should missing information be handled? A. Mark it as not published or to be confirmed, then contact the LAG. Never infer it from a neighboring territory.

Q7. Should old fiches be kept? A. Yes, if they have historical or editorial value, but their status must be clearly marked as closed or historical.

Q8. How can generic SEO pages be avoided? A. Every local page must contain verified local information; otherwise, publish a national method guide rather than an artificially territorialized page.

Practical pointers

Action plan

Locate the project; find the official LAG; read the strategy and action sheet; confirm beneficiary, expenditure, funding and dates; document the sources; prepare submission and payment; update the editorial status.

Eligibility conditions

Methodological guide, not a funding call. Eligibility must be established for each specific LAG, commune, project leader and call.

Funding and instruments

No amount or rate is announced in this method fiche. Extract these parameters only from an active, dated official call.

Access and procedures

Use the official map/directory of the national network, confirm the catchment area with the LAG in writing, and request the strategy, action sheet, call and applicant's guide.

Points of caution

Do not present this method as an open grant. Local rules vary; closed calls must be marked as closed or historical.

Official sources

• EU CAP Network — European LAG directory and search filters
• EU CAP Network — French LEADER/CLLD page
• EU CAP Network — LEADER legislation in French
• L'Europe s'engage en France — LEADER overview