Andalusia's Space Grants Divide Mission Responsibilities

Exploded conceptual view of one unfinished spacecraft with separate panel, antenna and sensor components. The text relates individual Andalusian grant projects to a shared mission.

Space Insights editorial illustration; AI-assisted.

Andalusia's grant rules connect individual projects to a shared satellite mission. Comparing the call with the award decision also separates coordination provisions from funding actually granted.

Andalusia approved EUR 15,789,625 in grants for satellite-industry projects in a definitive decision signed and published on 31 August 2026. The regional decision places the awards within a EUR 16 million authorised envelope and requires recipients to accept them expressly within 15 working days of publication. It establishes an award stage in a programme whose rules connect individual projects to a collective mission.

The decision gives a concrete setting for Regions Dual-use Open Strategic Autonomy (REGDUALOSA), the European Commission Joint Research Centre's study of dual-use industrial ecosystems. Announced by the Commission's defence and space directorate on 8 September, its policy brief draws on Andalusia, Poland's Podkarpackie region and Estonia. The satellite grants offer a way to examine how collaboration is organised below the level of regional strategy.

A shared mission as the entry condition

The original call, dated 5 June 2025, set out to develop Andalusia's ability to undertake a complete commercial satellite mission. Applicants had to belong to a business collaboration agreement covering the mission's work packages. Each participant would then apply for support for its own eligible project or activities within that arrangement.

The territorial rule concerned where investment, activities and services took place, independently of the recipient's registered office. Participation also had a size boundary: microenterprises were excluded. Large companies seeking industrial research or experimental development support had to demonstrate cooperation with more than one small or medium-sized enterprise (SME), extending beyond membership of the mission agreement itself.

These provisions make the collaboration agreement part of the funding structure. For a supplier evaluating such a consortium, membership and its own funded task answer different questions. The agreement connects the participant to the wider mission; the project application defines the activity for which that participant seeks support. An eligible technical contribution consequently has to fit both the regional activity requirements and the mission arrangement.

Coordination has its own place in the design

The call also provides for coordination support. Its Type D incentives cover coordination, information, assistance, collaboration and networking, linked to Work Package A for integrated mission management and coordination. The preamble identifies technical coordination, technical and functional requirements, and payload definition and selection among the intended activities. Coordination is therefore an explicit part of the programme design, alongside support for research and experimental development.

The August decision records a different funding outcome for this provision. It maps Type D to the innovative business groupings (AEI) measure and records EUR 0 awarded against EUR 200,000 authorised for that measure. The call establishes provision for support; the award table establishes what was granted under it. Actual mission coordination would need to be examined through the collaboration arrangements and their implementation.

That provision matters when reading the REGDUALOSA brief. Its Andalusia case identifies the absence of a large system integrator anchoring the regional value chain. That diagnosis concerns industrial structure: an organisation's place in a regional production network. Mission coordination concerns responsibilities within a particular collaboration. The two roles operate at different scales, and the brief's regional diagnosis cannot identify who fulfils a specific mission's duties.

The documents also have different purposes. The brief offers the author's policy analysis and recommendations; the earlier call specifies an actual support mechanism. Reading them together makes the regional ambition more concrete without treating a policy recommendation as a grant condition. The relevant evidence for a consortium's coordination remains its arrangements and implementation of the work described in the call.

What each grant recipient must deliver

The August decision sets a precise boundary around individual fulfilment. Page 11 describes the incentive's purpose as the beneficiary's own project or activity, insofar as it contributes to the satellite mission. Development of the wider mission does not condition or limit that individual fulfilment. The contribution to the mission remains part of the purpose against which the recipient's work is assessed.

This is accompanied by evidence obligations. For the applicable industrial research and experimental development categories, the decision requires a project certification report from an accredited certification body. Recipients must carry out and justify the activity supporting their grant. The programme thus combines a collective objective, provision for coordination support and evidence of individual project completion.

Our reading is that this separation can be a reasonable feature of collaborative research and development. Assessing a participant's own contribution separately may protect compliant work from becoming wholly dependent on another participant's performance. At the same time, the collaboration still needs its collective arrangements to connect those contributions. The decision explains the grant assessment boundary; the collaboration agreement and actual execution determine how the mission works across it.

Evidence at each level

For regional agencies and consortium managers, the useful comparison is between these levels of responsibility. A programme's collective objective describes the capability it seeks to encourage. Its coordination provisions describe eligible work supporting cooperation. Individual project obligations establish what a beneficiary must substantiate. Keeping those levels visible makes it possible to assess progress without asking a single grant figure to represent all three.

The next useful records would be acceptance or amendment decisions, published coordination arrangements and evidence of joint qualification or mission milestones. Acceptance would clarify the award's next administrative stage; technical evidence would show how the supported contributions work together. That progression is where the programme's published design can be compared with an operational result.

Sources