> For the complete documentation index, see [llms.txt](https://public.euroavia.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://public.euroavia.eu/miscellaneous/bylaws-subpages/4-definition-of-plans.md). # 4 Definition of Plans Official Version as of 27/09/2025 ### 4.1 5-year plan The 5-year Plan of EUROAVIA outlines the association’s long-term goals for the next five (5) years. The plan is a guideline of initiatives to stimulate growth of EUROAVIA. The International Board shall develop the aforementioned plan in collaboration with the Designated International Board officers, the Working Groups’ coordinators, one (1) representative of each Committee and EUROAVIA associates, and it must be presented and approved by two-thirds (2/3) majority at the Annual Meeting of the EUROAVIA Congress every five (5) years. The document must be made public to all (Prospective) Affiliated Societies/ (Prospective) Adjunct Members at least four (4) weeks before the start of the General Meeting. ### 4.2 The Business and Financial Plan The Business Plan is a document that translates the objectives outlined in the 5-year Plan into practical and operational initiatives. It focuses on the day-to-day activities, resource allocation, and timelines necessary to achieve the strategic goals. It shall contain all planned activities of the International Board and the existence of the foreseeable Working Groups and Committees with their tasks. The Financial Plan is a fundamental component of the Business Plan, which outlines the financial strategies and budget planning necessary to support the implementation of the initiatives outlined in the Business Plan. The Financial Plan shall also consist of a second financial concept without respecting prospective or estimated donations and sponsorships. The Business and Financial Plans are formulated every Business Year, in accordance with the previously outlined 5-year plan. The Designated International Board officers shall develop a Business and Financial Plan, and they must be presented and approved by the absolute majority at the Annual Meeting of the EUROAVIA Congress. Those documents must be made public to all (Prospective) Affiliated Societies/ (Prospective) Adjunct Members at least four (4) weeks before the start of the General Meeting. ### 4.3 Amendments to the 5-year Plan Any amendments to the 5-year Plan may be proposed by the International Board or at least five (5) Affiliated Societies in writing or the majority of the Working Groups’ Coordinators or the majority of the Committees’ representatives. Proposals for amendments must be made public to all (Prospective) Affiliated Societies/ (Prospective) Adjunct Members at least four (4) weeks before the start of the General Meeting where the amendment will be considered. The approval of amendments to the 5-year Plan shall require a two-thirds (2/3) majority vote during the General Meeting. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://public.euroavia.eu/miscellaneous/bylaws-subpages/4-definition-of-plans.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.