IMPORTANT NOTICE
What is the Application Form?
The Application Form is the template for EU grants applications; it must be submitted via the EU Funding & Tenders Portal before the call deadline. 
The Form consists of 2 parts:.
•	Part A contains structured administrative information  
•	Part B is a narrative technical description of the project. 
Part A is generated by the IT system. It is based on the information which you enter into the Portal Submission System screens. 
Part B needs to be uploaded as PDF (+ annexes) in the Submission System. 
How to prepare and submit Part B?
The Application Form must be prepared by the consortium and submitted by a representative. Once submitted, you will receive a confirmation.
The templates to use are available inside the Submission System. Please note that not using the correct template may lead to the inadmissibility of your proposal 
To ensure a proper evaluation of your project, the appropriate sections of the template must be filled in depending on whether the call has one or two submission stages. For stage 1 (concept note), some sections are not applicable (noted as n/a); for stage 2 (full proposal), all sections must be completed.
You can submit your proposal in any official EU language (the project abstract/summary should however always be in English). For reasons of efficiency, we strongly advise you to use English for the entire application.
Character and page limits:
•	page limit: see Call document
•	supporting documents can be provided as an annex and do not count towards the page limit
•	minimum font size — Arial 10 points. 
•	page size: A4 
•	margins (top, bottom, left and right): at least 15 mm (not including headers & footers).
Please abide by the formatting rules. They are NOT a target! Keep your text as concise as possible. Do not use hyperlinks to show information that is an essential part of your application.
 If you attempt to upload an application that exceeds the specified page limit, you will receive an automatic warning asking you to shorten and re-upload your application. For applications that are not shortened, the excess pages will be made invisible and thus disregarded by the evaluators.
 Please do NOT delete any instructions in the document. The overall page limit has been raised to ensure equal treatment of all applicants. Removing the instructions may result in your proposal being considered inadmissible. 
 This document is tagged. Be careful not to delete the tags; they are needed for the processing.

 

TECHNICAL DESCRIPTION (PART B)
COVER PAGE
Part B of the Application Form must be downloaded from the Portal Submission System, completed and then assembled and re-uploaded as PDF in the system. Page 1 with the grey IMPORTANT NOTICE box should be deleted before uploading.
Note: Please read carefully the conditions set out in the Call document (for open calls: published on the Portal). Pay particular attention to the award criteria; they explain how the application will be evaluated.

PROJECT	
Project name:	[project title]	
Project acronym:	[acronym]	
Coordinator contact:	[name NAME], [organisation name]	

TABLE OF CONTENTS
ADMINISTRATIVE FORMS (PART A)
TECHNICAL DESCRIPTION (PART B)
COVER PAGE
PROJECT SUMMARY
1. RELEVANCE
1.1 Background and general project objectives
1.2 Specific project objectives
1.3 Compliance with LIFE programme objectives and call topic
1.4 Concept and methodology
1.5 Upscaling results of other EU funded projects (n/a for concept note)
1.6 Complementarity with other actions (n/a for concept note)
1.7 Synergies and co-benefits with other LIFE sub-programmes (n/a for concept note)
1.8 Synergies and co-benefits with other EU policy areas (n/a for concept note)
2. IMPACT
2.1 Ambition of the impacts
2.2 Credibility of the impacts
2.3 Sustainability of project results
2.4 Exploitation of project results (n/a for concept note)
2.5 Catalytic potential: Replication and upscaling
3. IMPLEMENTATION
3.1 Work plan
3.2 Work packages and activities (n/a for concept note)
Work Package 1
Work Package …
Timetable (n/a for concept note)
3.3 Stakeholder engagement
3.4 Impact monitoring and reporting (n/a for concept note)
3.5 Communication, dissemination and visibility (n/a for concept note)
4. RESOURCES
4.1 Consortium set-up
4.2 Project management (n/a for concept note)
4.3 Green management (n/a for concept note)
4.4 Budget (n/a for concept note)
4.5 Risk management (n/a for concept note)
5. OTHER
5.1 Ethics
5.2 Security
6. DECLARATIONS
ANNEXES

#@APP-FORM-LIFESAPOAG@#
#@PRJ-SUM-PS@#  [This document is tagged. Do not delete the tags; they are needed for the processing.]
PROJECT SUMMARY 
Project summary  	
See Abstract (Application Form Part A).	
#§PRJ-SUM-PS§# #@REL-EVA-RE@# #@PRJ-OBJ-PO@#
1. RELEVANCE 
Fill in only sections 1.1-1.4 at stage 1 (concept note). Fill in all sections at stage 2 (full proposal).
1.1 Background and general project objectives
Background and general project objectives
Explain the problem and the needs to be addressed in the project. Describe the background, starting point / quantified baseline of the project. 
Please explain in which location and/or sector the main activities of the project will take place and justify that choice.
For Nature and Biodiversity:
Provide a clear and quantified description of the conservation issue and threats targeted, as well as relevant background information and quantified figures defining the baseline to justify the proposed Interventions by 
At stage 1 (concept note) when relevant, describe the main species/habitats directly targeted by the project: scientific name; refer to the Annex(es) of the EU Birds or Habitats Directive where they are listed; population size within each project area; conservation status; habitat name and Natura 2000 code; % of the cover within each project area; conservation status.
At stage 2 (full proposals), when relevant, provide a brief description of the areas where conservation actions will be implemented and main species and / or main habitats directly targeted by the project, and submit the following annexes: 
•	maps 
•	description of sites 
•	description of species and habitats
Describe the previous conservation efforts in the project area or for the habitats/species targeted.
For Circular Economy and Quality of Life (n/a to Environmental governance topics):
Describe the previous technical preparatory work and results of previous research and development activities, showing the status of technical development achieved for the proposed solution, including the technical readiness level (TRL) where relevant and proving its technical feasibility.
Explain the scale at which such results have been obtained and if prototypes have been already developed and tested. Their scale/dimension and relevant results and conclusions have to be clearly presented. Illustrate available best practices in the relevant sector (state of the art) and clearly and concisely explain the environmental, technical and economical improved performances/ advantages introduced by the proposed solution in case this is claimed to be innovative/ demonstrative.	
Insert text

1.2 Specific project objectives
Specific project objectives 
Describe the specific objectives of your project (clear, measureable, realistic and achievable within the duration of the project).	
Insert text

1.3 Compliance with LIFE programme objectives and call topic
Compliance with LIFE Programme objectives
Explain how the project contributes to the specific objectives of the LIFE Programme and the sub-programme targeted by the call (Nature and Biodiversity, Circular Economy and Quality of Life, Climate Change Mitigation and Adaptation or Clean Energy Transition). 	
Insert text

Compliance with the call topic
Indicate the call topic to which your proposal relates, and explain how the proposed project addresses the scope of the topic description in the Call document.	
Insert text
	
#§PRJ-OBJ-PO§# #@CON-MET-CM@#
1.4 Concept and methodology
Concept and methodology
Describe the overall intervention logic of the project, including the main idea and assumptions (i.e. how are the proposed activities and steps of your project expected to lead to the intended changes in terms of outcomes and impacts).
Explain the methodology, i.e. the main tools, techniques, methods and procedures you will use to implement the technical part of your project. Justify why the proposed methodology is the most suitable for achieving the project’s objectives. 
For Clean Energy Transition: 
Describe the market barriers, the needs and constraints of market actors, and how your concept will address them concretely.
For Circular Economy and Quality of Life (n/a to Environmental governance topics):
Describe the technical details of the proposed solution (process, material, product etc.) using a flowchart and including, where possible, the general mass and energy balance. Explain how you plan to establish your supply chain.
Specify the scale (e.g. production capacity) and output of the project (e.g. quantity produced/sold during the project). The chosen technical scale should be one that allows the evaluation of the technical and economic viability of the proposed solution. In case of close-to-market conditions the target should be industrial/commercial scale already during the project.	
Insert text
	
#§CON-MET-CM§# #@COM-PLE-CP@#
1.5 Upscaling results of other EU funded projects (n/a for concept note)
Upscaling results of other EU funded projects (n/a for concept note)
Explain if and how the proposal builds on or up-scales results of other EU funded projects.	
Insert text

1.6 Complementarity with other actions (n/a for concept note)
Complementarity with other actions (n/a for concept note)
Explain how the project is complementary to other regional, national or international initiatives/activities/projects. How will it integrate the results from these other actions? 	
Insert text

1.7 Synergies and co-benefits with other LIFE sub-programmes (n/a for concept note)
Synergies and co-benefits with other LIFE sub-programmes (n/a for concept note)
Describe synergies with other LIFE sub-programmes (Nature and Biodiversity, Circular Economy and Quality of Life, Climate Change or Clean Energy Transition). Describe spillover effects (co-benefits) in addition to those targeted by the project. If possible, quantify the contribution.
Identify the activities/tasks that address these policy objectives of other LIFE sub-programmes.	
Insert text

1.8 Synergies and co-benefits with other EU policy areas (n/a for concept note)
Synergies and co-benefits with other EU policy areas (n/a for concept note)
Describe the synergies and positive spillover effects (co-benefits) with other EU policy areas (for example agriculture, health, civil protection, jobs and growth, etc.). If possible, quantify the contribution.
Identify the activities/tasks that address these other EU policy objectives.	
Insert text 

#§COM-PLE-CP§# #§REL-EVA-RE§# #@IMP-ACT-IA@#
2. IMPACT 
Fill in only sections 2.1-2.3 at stage 1 (concept note). Fill in all sections at stage 2 (full proposal).
2.1 Ambition of the impacts
Ambition of the impacts
Identify and quantify the effects of the project (during the implementation and up to 5 years after its end). 
Be specific and provide only information about impacts that are a result of your project. The impact of other projects should not be taken into account.
Wherever possible, use quantified indicators and targets.  
Note: In addition to the description above, for stage 2 (full proposals) include quantified indicators in Part C of the application forms (both horizontal KPIs for the LIFE programme as well as any specific KPIs relevant to the proposal). Ensure correspondence between Part B and Part C.	
Insert text

2.2 Credibility of the impacts
Credibility of the impacts
Show the steps of your calculations and base yourself on the activities mentioned in your work plan. 
Justify and substantiate the baselines, benchmarks and assumptions you used, making reference to relevant publications, studies or statistics. 
Try to use the same methodologies for calculating impacts (avoid using different methodologies for each partner, region or country). 	
Insert text
	
#@SUS-CON-SC@#
2.3 Sustainability of project results 
Sustainability of project results
Describe your strategy to sustain the project’s results after the EU funding ends. Consider the following aspects: 
•	How will the project impact be ensured and sustained? Which tasks will you carry out during the project to ensure that?
•	Which parts of the project should be continued or maintained? How will this be achieved and which resources will be necessary? 	
Insert text 	
#§SUS-CON-SC§# 
2.4 Exploitation of project results (n/a for concept note)
Exploitation of project results (n/a for concept note)
Do you foresee other ways of exploiting the project’s results (e.g. utilisation in further research, in developing / creating / marketing a product or process, in creating / providing a service, in standardisation activities etc.)? Who are the targeted users?
For close-to-market projects: Describe the reference market: actual and potential market size, features of prospective customers and of their demand, competitors, market and regulatory barriers, etc. Explain the economic feasibility of the proposed solution comparing cost, price or other economic investment variables (e.g. payback period, net present value, etc.).
Note: Don’t forget to include the activities in the mandatory Work Package for Sustainability, replication, and exploitation of project results. 	
Insert text 	

2.5 Catalytic potential: Replication and upscaling 
Catalytic potential: Replication and upscaling (n/a for concept note)
Describe the potential for the results to be replicated in the same or other sectors or places. Which factors might favour or limit the replication?
Describe the potential for the results to be up-scaled by public/private actors or through mobilising larger investments or financial resources. What is the coverage and size of the market? Who are the potential users of the results?
Describe the strategy and tasks to multiply the impact of the project (during implementation or afterwards). How will its main actions and results be replicated elsewhere?
Note: Don’t forget to include the activities in the mandatory Work Package for Sustainability, replication, and exploitation of project results. 	
Insert text 	
#§IMP-ACT-IA§# #@QUA-LIT-QL@# #@WRK-PLA-WP@#
3. IMPLEMENTATION
Fill in only section 3.1 and 3.3 at stage 1 (concept note). Fill in all sections at stage 2 (full proposal).
3.1 Work plan
Work plan
Provide a brief description of the overall structure of the work plan (list of work packages or graphical presentation (Pert chart or similar)).	
Insert text

3.2 Work packages and activities (n/a for concept note)
WORK PACKAGES (n/a for concept note)	
Work packages
This section concerns a detailed description of the project activities. 
Group your activities into work packages. A work package means a major sub-division of the project. For each work package, enter an objective (expected outcome) and list the activities, milestones and deliverables that belong to it. The grouping should be logical and guided by identifiable outputs. 
The number of work packages should be proportionate to the scale and complexity of the project. WP1 should cover the project management and coordination activities (meetings, coordination, project monitoring and evaluation, financial management, progress reports, etc.) and all the activities which are cross-cutting and therefore difficult to assign to just one specific work package (do not try splitting these activities across different work packages). WP2 (and further WPs) should be used for the other project activities. You can create as many work packages as needed by copying the structure of WP1.
Include a mandatory work package called ‘Sustainability, replication and exploitation of project results’. 
For Nature and Biodiversity, include also a mandatory work package on ‘Monitoring and evaluation’.
In addition, ensure your work packages cover also the following activities: 
•	dissemination and communication, including networking with other LIFE projects
•	impact monitoring and evaluation 
•	reporting of (estimated and actually achieved) key-performance indicators (KPIs) in the LIFE KPI web tool within the first 9 months from grant signature and at the end of the project
Work packages covering financial support to third parties ( only allowed if authorised in the Call document) must describe the conditions for implementing the support (for grants: max amounts per third party; criteria for calculating the exact amounts, types of activity that qualify (closed list), persons/categories of persons to be supported and criteria and procedures for giving support; for prizes: eligibility and award criteria, amount of the prize and payment arrangements). 
Mandatory deliverables:
•	dedicated project page on the beneficiaries’ websites
•	exploitation plan including replication component / business plan including replication component / ‘After-LIFE Conservation Plan’
•	extract of the project data from the LIFE KPI webtool (month 9 and end of the project) (n/a for Clean Energy Transition)
•	in case of land purchase, digital copies of the land register (with "conservation clause") 
 Enter each activity/milestone/output/outcome/deliverable only once (under one work package).
 Ensure consistency with the detailed budget table/calculator (if applicable). (n/a for prefixed Lump Sum Grants)	
Objectives and results
List the specific objectives to which the work package is linked and expected results.	
Activities and division of work (WP description)
Provide a concise overview of the work (planned tasks). Be specific and give a short name and number for each task. The tasks should be numbered continuously, linked to the WP they relate to (e.g. T.1.1, T.1.2, T.2.1, etc.).
Show who is participating in each task: Coordinator (COO), Beneficiaries (BEN), Affiliated Entities (AE), Associated Partners (AP), indicating in bold the task leader. 
Add information on other participants’ involvement in the project e.g. subcontractors, in-kind contributions. 
Note: 
The Coordinator remains fully responsible for the coordination tasks, even if they are delegated to someone else. Coordinator tasks cannot be subcontracted.	
Milestones and deliverables (outputs/outcomes)
Milestones are control points in the project that help to chart progress (e.g. completion of a key deliverable allowing the next phase of the work to begin). Use them for major outputs or achievements expected during the project time, and not only at the end.  Please limit the number of milestones by work package.
Means of verification are how you intend to prove that a milestone has been reached. If appropriate, you can also refer to indicators.
Milestones have a continuous numbering not linked to their WP (e.g. MS1, MS2, etc).
Deliverables are project outputs which are submitted to show project progress (any format). Refer only to major outputs. Do not include minor sub-items, internal working papers, meeting minutes, etc. 
For deliverables such as meetings, events, seminars, trainings, workshops, webinars, conferences, etc., enter each deliverable separately and provide the following in the 'Description' field: invitation, agenda, signed presence list, target group, number of estimated participants, duration of the event, report of the event, training material package, presentations, evaluation report, feedback questionnaire. 
For deliverables such as manuals, toolkits, guides, reports, leaflets, brochures, training materials etc., add in the ‘Description’ field: format (electronic or printed), language(s), approximate number of pages and estimated number of copies of publications (if any). 
Deliverables a continuous numbering linked to their WP, (e.g. D1.1 in WP1, D2.1 in WP2, etc).
For each deliverable you will have to indicate a due month by when you commit to upload it in the Portal. The due month of the deliverable cannot be outside the duration of the work package and must be in line with the timeline provided below. Month 1 marks the start of the project and all deadlines should be related to this starting date.
The labels used mean:
Public — fully open ( automatically posted online on the Project Results platforms)
Sensitive — limited under the conditions of the Grant Agreement
EU classified — RESTREINT-UE/EU-RESTRICTED, CONFIDENTIEL-UE/EU-CONFIDENTIAL, SECRET-UE/EU-SECRET under Decision 2015/444. For items classified under other rules (e.g. national or international organisation), please select the equivalent EU classification level.	

Work Package 1 
Work Package 1:  [Name, e.g. Project management and coordination] (n/a for concept note)	
Duration:	MX - MX 	Lead Beneficiary:	1-Short name	
Objectives and results	
•		
Activities and division of work (WP description)	
T.1.1 [Task Name] (Participant X, Participant Y, etc.):
Description…
T.1.2 [Task Name] (Participant X, Participant Y, etc.):
Description…
	
Milestones and deliverables (outputs/outcomes)	
Mile-stone No	Milestone Name	WP No	Lead Beneficiary	Description	Due Date
(month number)	Means of Verification 	
MS1		1					
MS2		1					
Deliverable No	Deliverable Name	WP No	Lead Beneficiary	Type	Dissemination Level	Due Date
(month number)	Description 
(including format and language)	
D1.1		1		[R — Document, report] [DEM — Demonstrator, pilot, prototype] [DEC —Websites, patent filings, videos, etc.] [DATA — data sets, microdata, etc.] [DMP — Data Management Plan] [ETHICS] [SECURITY] [OTHER]	[PU — Public] 
[SEN — Sensitive] 
[R-UE/EU-R — EU Classified] 
[C-UE/EU-C — EU Classified]
[S-UE/EU-S — EU Classified]
			
D1.2		1		[R — Document, report] [DEM — Demonstrator, pilot, prototype] [DEC —Websites, patent filings, videos, etc.] [DATA — data sets, microdata, etc.] [DMP — Data Management Plan] [ETHICS] [SECURITY] [OTHER]	[PU — Public] 
[SEN — Sensitive] 
[R-UE/EU-R — EU Classified] 
[C-UE/EU-C — EU Classified]
[S-UE/EU-S — EU Classified]

Work Package …
To insert work packages, copy WP1 as many times as necessary. 

Timetable (n/a for concept note)
Timetable (projects up to 2 years) (n/a for concept note)
Fill in cells in beige to show the duration of activities. Repeat lines/columns as necessary.
Note: Use the project month numbers instead of calendar months. Month 1 always marks the start of the project. In the timeline you should indicate the timing of each activity per WP.	
ACTIVITY	MONTHS	
	M 1	M 2	M 3	M 4	M 5	M 6	M 7	M 8	M 9	M 10	M 11	M 12	M 13	M 14	M 15	M 16	M 17	M 18	M 19	M 20	M 21	M 22	M 23	M 24	
WP1 - …																									
Task 1.1 - … 																									
Task 1.2 - …																									
Task … 																									

Timetable (projects of more than 2 years) (n/a for concept note)
Fill in cells in beige to show the duration of activities. Repeat lines/columns as necessary.
Note: Use the project months/years instead of calendar months/years. Month 1 always marks the start of the project. In the timeline you should indicate the timing of each activity per WP. You may add additional columns if your project is longer than 6 years. 	
ACTIVITY	YEAR 1	YEAR 2	YEAR 3	YEAR 4	YEAR 5	YEAR 6	
	M 1	M4	M 7	M 10	M 13	M 16	M 19	M 22	M25	M 28	M 31	M 34	M 37	M 40	M 43	M 46	M 49	M 52	M 55	M 58	M 61	M 64	M 67	M 70	
WP1 - …																									
Task 1.1 - … 																									
Task 1.2 - …																									
Task … 																									
#§WRK-PLA-WP§#

3.3 Stakeholder engagement
Stakeholders engagement
Identify any key stakeholders outside the consortium that are required to ensure the success of the project. How will you mobilise them to contribute to your project activities or participate in these? 
Annex Letters of support to demonstrate the type and level of commitment already secured (if any).(n/a for concept note)
For Nature and Biodiversity: If your project (or a part of it) depends on support of the competent authority or stakeholders, provide letters of support to show their commitment to the project (needed for full proposal, n/a for concept note)	
Insert text
	
#@PRJ-MGT-PM@#
3.4 Impact monitoring and reporting (n/a for concept note)
Impact monitoring, evaluation and reporting strategy (n/a for concept note)
Describe your overall approach to monitor and evaluate the impact indicators during your project. Ensure that you include specific tasks to monitor, evaluate and report impacts in the work plan (section 2 of this template). 	
Insert text 	
#§PRJ-MGT-PM§# #@COM-DIS-VIS-CDV@#
3.5 Communication, dissemination and visibility (n/a for concept note)
Communication, dissemination and visibility of funding (n/a for concept note)
Define your target audience(s). Describe the planned communication and dissemination activities to promote the action and its results and maximise the impact (to whom, which format, how many copies, etc.). Clarify how you intent to reach each target audience, and explain the choice of the dissemination channels. Describe the methods and indicators (quantitative and qualitative) to monitor and evaluate the outreach and coverage of the communication and dissemination activities and results.
Describe how the visibility of EU funding will be ensured.	
Insert text
	
#§COM-DIS-VIS-CDV§# #@CON-SOR-CS@#
4. RESOURCES
Fill in only section 4.1 at stage 1 (concept note). Fill in all sections at stage 2 (full proposal).
4.1 Consortium set-up 
Consortium cooperation and division of roles (if applicable) 
Describe the consortium composition. How will all the partners together bring the necessary expertise? 
In what way does each of the participants contribute to the project? Show that each has a valid role and adequate resources to fulfil that role. 
For stage 2 (full proposal), fill out the Participant information (annex) with more details on the participants and their project teams (key staff).	
Insert text
	
#§CON-SOR-CS§# #@PRJ-MGT-PM@#
4.2 Project management (n/a for concept note)
Project management, quality assurance and monitoring of progress (n/a for concept note)
Describe the management structures and decision-making mechanisms within the consortium. Explain how decisions will be taken and how regular and effective communication will be ensured. 
Describe the measures and methods planned to ensure good quality, monitoring, planning and control of project implementation.	
Insert text 	

4.3 Green management (n/a for concept note) 
Green management (n/a for concept note)
Describe the measures proposed to reduce the environmental impact of your project, for example through the use of green procurement, environmental management systems, etc.	
Insert text	
#§PRJ-MGT-PM§# #@FIN-MGT-FM@#
4.4 Budget (n/a for concept note)
Estimated budget — Resources (n/a for concept note) 	
See detailed budget table/calculator (annex 1 to Part B).	
#§FIN-MGT-FM§# #@RSK-MGT-RM@#
4.5 Risk management (n/a for concept note)
Critical risks and risk management strategy (n/a for concept note)
Describe critical risks, uncertainties or difficulties related to the implementation of your project, and your measures/strategy for addressing them. 
Indicate for each risk (in the description) the impact and the likelihood that the risk will materialise (high, medium, low), even after taking into account the mitigating measures.
Describe any barriers/obstacles and framework conditions (such as regulation and standards) that may be a risk for the achievement of the project’s objectives/impacts. 
Note: Uncertainties and unexpected events occur in all organisations, even if very well-run. The risk analysis will help you to predict issues that could delay or hinder project activities. A good risk management strategy is essential for good project management.	
Risk No	Description	Work package No	Proposed risk-mitigation measures	

#§RSK-MGT-RM§# #§QUA-LIT-QL§# #@ETH-ICS-EI@# 
5. OTHER
5.1 Ethics
Ethics 
	
Not applicable	
#§ETH-ICS-EI§# #@SEC-URI-SU@#                                                                                                                                      
5.2 Security
Security 
	
Not applicable	
#§SEC-URI-SU§# #@DEC-LAR-DL@#                                                                                                                                  
6. DECLARATIONS
Higher funding rate (for Nature and Biodiversity; n/a for concept note)	YES/NO	
Do you fulfil the conditions set out in the Call document for a higher funding rate (75% or 67%)?
If YES, explain and provide details.		
Insert text	

Double funding (n/a for concept note)	
Information concerning other EU grants for this project 
 Please note that there is a strict prohibition of double funding from the EU budget (except under EU Synergies actions). 	
YES/NO
	
We confirm that to our best knowledge neither the project as a whole nor any parts of it have benefitted from any other EU grant (including EU funding managed by authorities in EU Member States or other funding bodies, e.g. EU Regional Funds, EU Agricultural Funds, etc.). If NO, explain and provide details.		
We confirm that to our best knowledge neither the project as a whole nor any parts of it are (nor will be) submitted for any other EU grant (including EU funding managed by authorities in EU Member States or other funding bodies, e.g. EU Regional Funds, EU Agricultural Funds, etc.). If NO, explain and provide details.		

Financial support to third parties (if applicable) (n/a for concept note)
If in your project the maximum amount per third party will be more than the threshold amount set in the Call document, justify and explain why the higher amount is necessary in order to fulfil your project’s objectives.	
Insert text	

Seal of Excellence (if applicable) (n/a for concept note)
If provided in the Call document, proposals that pass the evaluation but are below the budget threshold (i.e. pass the minimum thresholds but are not ranked high enough to receive funding) will be awarded a Seal of Excellence.
In this context we may be asked to share information about your proposal with other EU or national funding bodies. 	
Do you agree that your proposal (including proposal data and documentation) is shared with other EU and national funding bodies to find funding under other schemes?	[YES] [NO]	
#§DEC-LAR-DL§#                                                                                                                                                                    

ANNEXES
LIST OF ANNEXES 
Standard
Detailed budget table/Calculator (annex 1 to Part B) — mandatory (n/a for concept note)
Annual activity reports (annex 3 to Part B) — mandatory, if required in the Call document (n/a for concept note)

Special
Other annexes (annex X to Part B) — mandatory, if required in the Call document (n/a for concept note)

HISTORY OF CHANGES	
VERSION	PUBLICATION  DATE	CHANGE	
1.0	15.04.2021	Initial version (new MFF).	
2.0	01.05.2022	Change of document short name.
Clarifications in the Important Notice (language, font size, concept notes, etc). Minor adaptation of structure (section 3.2 becomes section 3.3). Minor clarifications regarding other sections. Addition of declaration on SoE.
Consolidation, formatting and layout changes. Tags added.