Practical guide: designing, structuring and financing a territorial cooperation project with LEADER

1. Why consider LEADER cooperation?

Cooperation is useful when a rural area cannot solve a problem, develop an offer or reach a sufficient scale on its own. It involves organising joint work between several territories around a concrete objective, with partners who each bring skills, resources or access to different audiences. It cannot be reduced to a study visit or a series of meetings. A solid project produces reusable results: a tested service, a shared method, a tool, a structured tourism offer, a better-organised supply chain, or knowledge transferred to local stakeholders.

LEADER is a rural development scheme implemented under the common agricultural policy. Local Action Groups (LAGs) select operations against a local development strategy and the rules of their managing authority. Cooperation can bring together territories within the same country or from different countries. The exact conditions, eligible expenditure, procedures and deadlines are not identical everywhere, however. The first instinct should therefore not be to build a budget on an assumed rate, but to identify the LAGs concerned, their strategies and their applicable calls.

The right starting point is a field-level question: what result is impossible, too costly or less relevant to produce in isolation? If each partner can achieve the same result alone, without shared learning or shared benefit, the cooperation risks being artificial. Conversely, it becomes worthwhile when it makes it possible to pool rare expertise, compare experiments, connect complementary offers or create a service that goes beyond administrative boundaries.

2. Define a shared problem before looking for partners

Write a two-page concept note before approaching other territories. It should describe the problem, the audiences concerned, the available evidence, the intended result, the reason why several territories are needed, and the expected changes. Avoid vague phrases such as "strengthening attractiveness" without explaining what is currently missing. Instead, state precisely, for example, that several small rural destinations have scattered tourism products, a short season and no shared marketing method; or that several production areas face comparable difficulties in organising the logistics of local products.

Distinguish the shared need from local responses. Two territories can share an issue without having the same resources, audiences or constraints. The project must identify what will be built together and what must remain adapted to each territory. A shared platform might, for example, use a common booking method while leaving each partner in control of its own offer. A training programme might pool content while organising local sessions.

Base the diagnosis on concrete elements: visitor/footfall data, interviews with beneficiaries, current costs, time needed to access a service, available volumes, participation rates or lessons learned. There is no need to produce a disproportionate study, but the need must be demonstrated. Cooperation designed solely around the interests of the partner organisations risks funding activities that do not genuinely improve the situation of residents or businesses.

Then formulate a measurable objective. "Developing sustainable tourism" is too broad. "Designing and testing a touring-stay offer linking four rural territories, with a shared information system and booking monitoring over one season" is more workable. The objective must remain proportionate to the partners' resources, timeline and decision-making capacity.

3. Choosing between interterritorial and transnational cooperation

Interterritorial cooperation brings together territories located within the same country. It can simplify the working language, the administrative framework and the understanding of national policies, even though LAG or regional rules may differ. It is often suited to pooling services, structuring value chains, sharing equipment, creating tourist routes, or trialling a shared method.

Transnational cooperation involves territories from different countries. It is relevant when international comparison brings genuine added value: learning a method that works elsewhere, developing a cross-border offer, sharing skills, or addressing an issue that goes beyond borders. It requires heightened attention to language, timelines, funding regimes, procurement, taxation, travel, data and liability. Machine translation is no substitute for clear governance or for partners validating documents themselves.

Do not choose transnational cooperation simply because it seems more ambitious. If the objective can be achieved more effectively with territories from the same country, interterritorial cooperation may be preferable. Conversely, if the project genuinely depends on foreign experience, a foreign resource or a foreign market, limiting the partnership to a national territory may weaken the approach.

In both cases, check early on whether the LAGs concerned can take part in the type of operation envisaged, which authorities manage the funding, how decisions are made, and whether a lead partner is required. Terms and procedures can vary according to the programme and the programming period. Have the requirements confirmed in writing before finalising the arrangement.

4. Identifying the relevant LAGs and partners

Start with the LAG covering the project leader's territory. Review its local strategy, its action sheets, current calls and the contacts of its technical team. The European LAG directory and the EU CAP Network cooperation resources can help identify territories and understand cooperation practices. The French national network and regional networks can also point towards contacts and lessons learned.

Do not confuse a cooperation partner with a mere service provider. A partner takes part in the design, the decisions, the implementation or the transfer of results. A service provider delivers a defined service paid for under the applicable rules. This choice has consequences for governance, budget, procurement and eligibility. This classification must be determined with the LAGs and the managing authority, without seeking to bypass competitive tendering rules.

Assess partners on their concrete contribution. Can they reach the target audience? Do they bring a complementary skill? Do they have someone who will actually follow the project? Can they make decisions and provide the necessary documents? Can they pre-finance certain expenses if reimbursements are delayed? A generic letter of support does not prove an operational commitment.

For each prospective partner, prepare a summary sheet: territory covered, local need, relevant experience, proposed role, resources that can be mobilised, lead decision-maker, administrative capacity, constraints and expected benefit. Then organise a scoping discussion. The aim is to test alignment before requesting letters of commitment or incurring any expenditure.

5. Building a balanced partnership and a workable governance structure

An effective partnership does not require every organisation to carry out exactly the same amount of activity. It requires roles to be justified, transparent and balanced in relation to skills and resources. Define a lead partner or coordinator if the framework provides for one, but do not concentrate all decisions and knowledge within a single organisation. Partners must understand the commitments, deadlines, communication rules and the consequences of a delay.

Formalise simple governance. A steering committee can approve the overall direction, the budget, the deliverables and any major changes. An operational group follows the schedule and resolves day-to-day issues. Appoint a lead for each work package, a financial manager, and a contact for collecting indicators. For a small project, these functions can be held by the same people, but they must be explicitly assigned.

A partnership agreement must, at minimum, cover objectives, roles, contributions, decisions, timeline, financial flows, supporting documents, communication, data, intellectual property, risks, dispute resolution and withdrawal conditions. It must also specify what happens if a partner can no longer meet its commitments. The formal requirements for this agreement must be confirmed with the competent authorities.

Put in place a suitable decision-making mechanism. Not every decision needs a unanimous vote: day-to-day decisions can fall to the work-package lead, while changes in scope or budget require collective approval. Define response deadlines and who is authorised to sign. Unclear governance often causes more delays than the technical complexity of the project itself.

6. Turning the idea into work packages and deliverables

Structure the project into a few coherent work packages. A common pattern includes the shared diagnosis, design, piloting, evaluation and transfer. Each work package must have a lead, a period, activities, a budget, a deliverable and an acceptance criterion. Avoid lists of activities with no identifiable outcome.

A deliverable must be verifiable. It may be an approved specification, a tested digital tool, a service protocol, a marketed route, a shared catalogue, a comparative report, a training session delivered, or a documented business model. Specify the format, language, date, user audience and how partners will approve the result.

Set aside time for implementation and transfer. Cooperation projects sometimes devote too many resources to meetings, travel and studies, then run short of time to test solutions. For each study, state which decision it is meant to inform. For each meeting, state which decision or outcome it is meant to produce. A study visit is more useful when it leads to a concrete adaptation, a test, or a documented method.

Prepare a simple matrix: work package, activities, lead partner, contributing partners, deliverable, date, cost, indicator and risk. This matrix becomes the thread running through the application, the budget and the monitoring. It also helps identify duplication between partners and periods of overload.

7. Designing the budget without presuming eligibility

The budget must follow from the activities and the applicable rules, not the other way round. Build an estimate by work package and by partner. Identify personnel costs, travel, meetings, interpreting, studies, services, communication, any equipment, and operating costs, only where these categories are relevant and potentially eligible. An expense that is useful to the project is not automatically eligible for the funding requested.

For each budget line, show the calculation: quantity, unit cost, duration, valuation method and available supporting document. For personnel costs, check the authorised methods, proof-of-time requirements and the rules on indirect costs. For travel, confirm the caps, supporting documents, mission rules and admissible categories. For services, check the public procurement or competitive tendering rules, conflicts of interest, and documentation of the choices made. Do not artificially split purchases to avoid a procedure.

Distinguish between total budget, potentially eligible expenditure, amount requested, secured co-financing, co-financing still to be confirmed, and the funding gap remaining. Never present an intention to support as a secured resource. A financing plan must remain coherent if an expected contribution is delayed or refused. Ask partners to confirm their in-kind or financial contributions and how these can be recognised under the applicable framework.

Aid rates, caps, preparation costs, coordination costs and eligible expenditure vary according to the programme's rules, the territory, the LAG, the managing authority and the call. There is no universal rate to announce. Obtain a written answer on uncertain budget lines before making an irreversible commitment.

8. Planning for cash flow and reimbursement risk

A grant being awarded does not necessarily mean all expenses are paid upfront. Depending on the applicable mechanism, the project leader may have to advance costs, wait for supporting documents to be checked, or manage payment delays. A monthly cash-flow plan should therefore be drawn up covering expenses, income, partner contributions, any authorised advance payments, and foreseeable time lags.

Test at least three scenarios: a normal timeline, a delayed reimbursement, and co-financing paid later than planned. Calculate the maximum cash-flow requirement and identify who can bear it. A small association or local authority does not necessarily have the same capacity to advance funds as a larger organisation. Do not commit a partner to an activity without first checking its ability to fund its share when required.

Appoint a financial manager who keeps the budget up to date, checks supporting documents and flags discrepancies. Each partner must know the document-retention rules, how often expenses must be reported, and the approval process. A shared table can track the budget planned, committed, paid, declared, accepted and still to be paid. These concepts are not interchangeable.

Build in a realistic management margin, without treating it as automatically eligible expenditure. Any change to the budget, timeline or partner line-up may require prior approval. The precise rules must be checked before making any reallocation.

9. Examples of high-value-added cooperation

Rural tourism

Several territories can design a touring offer linking sites, accommodation, craftspeople and producers. The project must go beyond producing a brochure: it can test a bookable route, a shared quality method, coordinated signage, and a system for tracking outcomes. Partners must clarify who is responsible for bookings, who updates the information, the commercial terms, and who maintains the offer after the funding ends.

Food supply chains and logistics

Agricultural territories can compare available volumes, organise complementary outlets and test a pooled logistics solution. The outcome can be an operational study, a collection schedule, an ordering protocol or a shared pilot. The project must analyse actual costs, health and safety responsibilities, the regularity of volumes, and competition rules. Cooperation is not justified if volumes and users are not demonstrated.

Local services

Territories can pool a method for mobile outreach services, a booking tool, or the training of mediators. The project must specify the audiences, opening hours, locations, operational partners and continuity arrangements. Cooperation can transfer a model tested elsewhere, but it must adapt it to local constraints rather than mechanically replicating a solution.

Ecological transition

Several LAGs can exchange on climate adaptation, energy efficiency, water management, or making the most of local resources. The expected outcome can be a diagnostic protocol, a method for engaging stakeholders, or a comparative pilot. Projects must distinguish facilitation and learning activities from capital investment, which may be subject to different funding rules.

Rural digital technology

Cooperation can develop shared digital resources, a joint service, or a method for supporting small businesses. It must specify who owns the tool, who hosts the data, who handles maintenance, how users will be trained, and who will pay once the project ends. A prototype with no maintenance owner risks becoming unusable shortly after delivery.

10. Measuring results and demonstrating the value of cooperation

Define indicators from the design stage. Distinguish between resources mobilised, activities carried out, deliverables produced, and observed effects. The number of meetings is an activity indicator, not sufficient proof of impact. For a tourism project, one can track partners mobilised, offers actually marketed, bookings and visitor feedback. For a shared service, one can measure people reached, time to access, frequency of use, and cost per beneficiary.

For each indicator, set a definition, a baseline value where one exists, a realistic target, a data source, a collection frequency and an owner. Avoid targets that cannot be measured with the resources planned. If the result depends on external factors, describe that limitation and do not claim a causal link that the data cannot establish.

The added value of cooperation deserves specific indicators: practices transferred, decisions made thanks to shared learning, tools reused by several territories, savings or services made possible by pooling, and partnerships that continue after the project. It is also useful to document trials that did not work, provided one explains what was learned and how this changes what comes next.

Plan a mid-term review and a final review. They must lead to decisions: stopping an activity of little use, redirecting a test, strengthening a partner, or adjusting the timeline in compliance with the procedures. Data collected must be proportionate and protected in accordance with the applicable rules.

11. Communication, data and intellectual property

Define a targeted communication strategy. Identify the audiences who need to know about the project, the message that is useful to them, the channel, the person responsible, and the expected outcome. A social media post does not replace directly informing the businesses, residents or associations who might use the result. Plan accessible materials, any necessary language versions, and a method for keeping them up to date.

The visibility obligations linked to the funding must be checked in the applicable documents. Do not assume that a single logo or mention satisfies all requirements. Keep evidence of communication activities and designate the person who checks materials before they are published.

For digital tools, databases, photos, maps and shared content, establish usage rights, authorisations, re-use conditions, and maintenance responsibilities. Partners must know whether the result will be freely reusable, available under licence, or restricted to certain uses. Personal data requires a legal basis, appropriate information, limited access, and a defined retention period. The partnership should avoid collecting personal data simply because the technology makes it possible.

In a transnational cooperation, confirm the rules on data transfer and storage, the official languages of the documents, and the arrangements for resolving disagreements. These matters should be settled early, rather than after a tool has been created or content published.

12. Main risks and mistakes to avoid

The first risk is a partnership in name only: partners are listed, but their roles are not linked to the deliverables. To avoid this, give each one a verifiable contribution and a named person responsible. The second is a project that is too broad. Narrow the scope to a few achievable results rather than piling up unrelated themes. The third is a budget built before the activities, which can lead to poorly justified expenses or expenses incompatible with the applicable rules.

Another risk is incurring expenses before confirming the start conditions and the required authorisations. Do not assume that costs incurred before the application or the decision are eligible. Check the eligibility start date, procurement procedures, publicity rules and documentary requirements before signing a contract or ordering equipment.

Differences in timelines between partners can also jeopardise the project. Set internal deadlines ahead of the official ones, a format for submitting documents, and an alert mechanism. For a transnational cooperation, factor in public holidays, translation lead times, and each organisation's own approval processes.

Finally, do not confuse funding for the project with the long-term sustainability of its results. Before submitting the application, identify the owner of the tool or service, the annual costs, the person responsible for maintenance, and the income or budgets that will allow it to continue. If no one can take on these responsibilities, the model should be revised, or the result limited to a deliverable that will remain useful without significant recurring costs.

13. 90-day action plan

Days 1 to 15: scoping the need

Write the concept note, gather the first evidence of need, and define the expected shared result. Consult the LAG covering the project leader's territory, its strategy and the applicable calls. Note down the questions that need official confirmation: eligible partners, expenditure, timeline, co-financing, and the selection procedure.

Days 16 to 30: finding and qualifying partners

Identify territories and organisations whose experience matches the need. Hold scoping discussions and assess each one's operational capacity. Rule out partners who cannot define their contribution or assign a person to the project. Choose the form of cooperation based on added value, not prestige.

Days 31 to 45: designing the project

Define the work packages, deliverables, owners, indicators, timeline and risks. Draft a first partnership agreement and a roles matrix. Identify the decisions that require collective approval. Test the feasibility of the deliverables with potential users or beneficiaries.

Days 46 to 60: building the budget and confirming the rules

Request quotes or justifiable estimates. Build the budget by work package and by partner, then the financing plan and the cash-flow plan. Have uncertain budget lines reviewed by the LAG or competent authority. Check procurement procedures, the admissible start date, supporting documents, and visibility requirements.

Days 61 to 75: finalising commitments

Obtain internal decisions, letters of commitment, and required documents. Confirm financial or in-kind contributions and the person responsible for each task. Check the consistency between the application form, the budget, the timeline, the partnership agreement and the indicators.

Days 76 to 90: checking and preparing the submission

Carry out a cross-review of the application: one reader checks the project logic, another checks the figures and documents. Correct any contradictions, tasks with no owner, and insufficiently explained costs. Confirm the submission channel, signatures, deadlines, and the final list of documents. Do not consider the application submitted until an acknowledgement or proof of transmission has been kept.

14. Checklist before submission

• The shared need is demonstrated with concrete evidence.
• The added value of cooperation is clearly explained relative to acting alone.
• The type of cooperation and the participating territories are defined.
• Each partner has a role, an owner, and a verifiable contribution.
• The work packages produce identifiable, dated deliverables.
• The indicators are measurable and linked to a data source.
• The budget is detailed and uncertain expenses have been submitted for approval.
• The financing plan distinguishes secured resources from resources still to be confirmed.
• Cash-flow needs and payment time lags have been anticipated.
• The partnership agreement covers decisions, data, rights and risks.
• Procurement, visibility and document-retention rules have been checked.
• Maintenance and use of the results after funding ends have a named owner.
• The final versions of the application and proof of submission are archived.

15. Conclusion: funding useful cooperation, not just exchanges

A good LEADER cooperation project starts from a shared need, brings together partners capable of taking action, and produces reusable results. Its quality is not measured by the number of territories, trips or meetings, but by what the stakeholders will be able to do together that they could not do as effectively on their own. A shared method, a genuinely tested service, a better-organised value chain, or a tool maintained over time are far stronger results than a series of events with no follow-through.

The safest approach is to scope the problem, check local rules early, qualify the partners, build a realistic work plan, budget each activity and organise monitoring. Funding rules must be confirmed with the LAGs and competent authorities concerned: no rate, cap or timeline should be treated as universal. An application will be more credible if it makes its choices, risks and limitations visible, rather than promising effects that cannot be measured.

FAQ — 10 frequently asked questions

1. What is a LEADER cooperation project?

A project in which several territories or partners work together towards a shared rural development objective. It must demonstrate collective added value and comply with the strategies and rules applicable to the participating LAGs.

2. Is it compulsory to cooperate with a foreign territory?

No. Cooperation can be interterritorial, within the same country, or transnational, with partners from different countries. The choice should follow from the expected added value and the possibilities provided for under the applicable rules.

3. How many partners are needed?

There is no universal number to apply without consulting the relevant framework. A small, active partnership is better than a large number of partners with no concrete contribution. Check the requirements of the call and formalise the roles.

4. Can a service provider be considered a partner?

Not automatically. A partner contributes to the joint design or delivery; a service provider carries out a commissioned service. This distinction has consequences for governance and procurement rules. Have the arrangement confirmed by the competent authorities.

5. What costs can be funded?

This depends on the programme, the call, the LAG, the managing authority, and national or regional rules. Personnel, travel, studies, communication or equipment should never be considered eligible without specific verification.

6. Can spending start before the funding decision?

This should not be assumed. The dates from which costs may be eligible, and the start conditions, must be confirmed in writing. An expense incurred too early may remain entirely at the project leader's own expense.

7. How should the budget be split between partners?

Split costs according to actual tasks, resources mobilised and applicable rules. Document the calculation methods, the contributions and who is responsible for the supporting evidence. The split should not be made simply to artificially balance the amounts.

8. How can the added value of cooperation be proven?

Define indicators linked to shared outcomes: tools reused, methods transferred, services created, audiences reached, or savings made possible. Explain why these outcomes require collective action, and keep evidence of their use.

9. What happens if a partner withdraws?

The partnership agreement must provide for an alert, an assessment of the consequences, decisions on replacement or revision, and the necessary approvals. Any significant change may need to be approved by the funders. Do not freely reallocate activities or budget without checking the rules.

10. How can results be sustained after the funding ends?

Identify, from the design stage, the owner, the operational manager, annual costs, maintenance, and future resources. Test the economic or budgetary model before the project ends, and document responsibilities in a sustainability plan.

Institutional sources to consult

• EU CAP Network — LEADER cooperation: https://eu-cap-network.ec.europa.eu/networking/leader/tnc-cooperation_en
• EU CAP Network — LEADER cooperation offers: https://eu-cap-network.ec.europa.eu/networking/leader/tnc-cooperation/leader-cooperation-offers_en
• EU CAP Network — LAG directory: https://eu-cap-network.ec.europa.eu/networking/leader/lag-directory_en
• EU CAP Network — practical guide to LEADER transnational cooperation: https://eu-cap-network.ec.europa.eu/sites/default/files/publications/2025-03/eu-cap-network-leader-tnc-practical-guide.pdf
• Réseau national Agricultures et Ruralités — LEADER cooperation toolkit: https://reseau-pac.agriculture.gouv.fr/boite-outils-cooperation-leader
• European Commission — rural development: https://agriculture.ec.europa.eu/cap-my-country/rural-development_en

Links and their availability should be checked at the time of publication. For any real project, add links to the local LAG, the local strategy, the action sheet and the current call. These general sources do not replace the applicable territorial rules.

Practical pointers

Action plan

Define a shared issue; choose interterritorial or transnational cooperation; identify partners; formalise governance; build work packages and deliverables; validate expenditure and co-financing; submit to the LAGs; monitor and evaluate the results.

Eligibility conditions

Check separately the conditions of each LAG and managing authority, the local strategy, eligible partners, expenditure and national/regional rules. No uniform criteria should be assumed.

Funding and instruments

No universal rate. Budget, co-financing, preparation costs, coordination, travel, personnel and services depend on local rules and the call. Confirm in writing.

Access and procedures

Contact the local LAG; read its strategy and the action sheet; use the EU CAP Network directory and cooperation offers; obtain the call, the applicant guide and the national fact sheets; build a concept note and a budget per partner.

Points of caution

Avoid cooperation reduced to travel; confirm the rules before any commitment; anticipate cash flow, differences in rules, languages, governance, intellectual property, data, and maintenance of results.

Official sources

• EU CAP Network — LEADER transnational cooperation
• EU CAP Network — LAG directory and cooperation offers
• EU CAP Network — guide to the seven LEADER principles (French version)
• EU CAP Network — LEADER legislation in French