For a first space contract from Denmark, identify an ESA programme in which Denmark participates and establish the support conditions for the activity you want to pursue. Danish guidance and ESA tendering are connected parts of that route. Separate national support, your company’s eligibility and the eventual contract decision before building a technical proposal. Then define the work, partners and evidence your team would deliver.
The official Danish programme guide describes the participating programmes, while Danish technology guidance explains support for specific technology routes. This article focuses on that national preparation. Use the first ESA contract guide for the common registration and tender-review process.
Start with the Danish authority and the actual ESA programme
The Danish Agency for Higher Education and Science publishes information on space funding and counselling and identifies a contact for Denmark’s ESA membership. The supplier journey should be described using that authority’s real role and the relevant ESA process, rather than an assumed standalone Danish space-agency purchasing route.
Prepare a short enquiry about the proposed activity. State the technical result, where the work would happen, the expected customer and any partners. If you know an ESA programme or activity reference, include it. If you do not, explain the technology and development objective precisely enough for the enquiry to be directed to the relevant programme.
A useful outcome from that conversation is a named next step with a source: the current programme page, the appropriate support guidance or the actual invitation. Keep advice, application and award as different statuses in your opportunity record. A productive introductory discussion has value without being represented as an approval.
Match the development task to Danish programme participation
Denmark’s ESA programme overview distinguishes mandatory programmes from selected optional participation. It also explains esa-star opportunities and the Open Space Innovation Platform, OSIP, for ideas and campaigns. The listed GSTP route concerns upstream technology development. Start with the work you want to perform, then inspect the relevant programme rather than choosing a portal first.
Describe the development gap in engineering terms. What capability has been demonstrated, what remains uncertain and what evidence would resolve that uncertainty? Keep a proposed study separate from a promise to supply operational equipment. This helps the team compare the intended work with the actual activity description and identify whether a partner is needed.
Record the programme, activity and national guidance together. A broad programme description explains its purpose; a specific invitation establishes the requested work and conditions. Review both when deciding whether the company should pursue the opportunity. Do not infer that national membership gives unrestricted access to every ESA activity.
Understand activity-level support through a dated GSTP example
A particularly useful distinction appears in the 17 April 2026 GSTP Element 1 announcement. For the selected activities, Danish support is attached to the activity rather than exclusively to the actor that first expressed interest. The guidance says Danish actors registered on esa-star can compete when ESA issues the relevant invitation to tender.
This is a historical explanation of the published support mechanism, not a list of opportunities open today. The practical lesson is to identify what a support decision covers. An activity receiving national backing does not mean that a named company has already won its delivery contract.
Use the table below as an original review aid. The rows represent separate questions, each of which needs its own evidence for the chosen route.
| Question | Evidence to inspect | What remains to decide |
|---|---|---|
| Does Denmark participate? | Official programme participation information | Whether the particular activity is supported |
| Is this activity supported? | Current national guidance or activity decision | Which support conditions apply to the proposed team |
| Can this company bid? | Issued ITT and applicable eligibility conditions | Whether its proposal will be successful |
| Has work been awarded? | Formal procurement outcome and agreement | How the team will fulfil the agreed obligations |
Make the work location and partner roles explicit
The same dated GSTP announcement states that Danish funds for those activities must go to work in Denmark. It also says that the described route for a Danish subcontractor working with a partner in another ESA member state requires that other country to support the activity. Keep these conditions attached to the named programme example.
Before approaching a partner, write the work package you propose to own. Include the technical output, inputs needed from others, where the work is performed and who supplies each piece of evidence. Then compare that work share with the current support rules. A partner logo in a proposal does not establish a workable division of responsibility.
Pay particular attention to shared analyses and facilities. Identify who owns the input model, who runs the analysis and who can explain the result at review. If the delivery depends on access to another organisation’s information, resolve that access as a project dependency. The commercial arrangement and national support should describe a compatible technical plan.
Build a support record before the full technical response
The April 2026 Danish technology guidance describes national approval and ESA evaluation for the stated technology activities, while distinguishing other participating programme routes. Avoid applying one support-letter procedure to all ESA work. Confirm the sequence for the particular programme and keep the supporting instructions with the opportunity record.
A useful support record contains the legal entities, activity reference, proposed work share, location of each contribution, applicable national guidance and required next decision. Add the version of the technical brief reviewed and any conditions or unresolved questions. This is an internal preparation record, not an official application form.
Revisit it when the team changes. If a proposed partner replaces an analysis activity with a different deliverable, the technical plan and support request may no longer describe the same project. Ask the relevant authority about the revised scope rather than treating earlier correspondence as blanket approval.
Prepare a concise technical brief for useful advice
Bring a clear problem statement to the first substantive discussion. Describe the current engineering position, the intended development result, the evidence you will produce and the role of any customer or research partner. Include the main uncertainty that could change the scope. The brief should allow a reader to understand the proposed work without opening a complete company presentation.
For internal review, ask the technical lead to connect each proposed output to an activity and a necessary input. Ask the commercial lead to check that the work share and assumptions agree with the support record. When the actual ESA documents are available, reconcile the brief with them instead of copying the brief unchanged into the response.
Fictional example: Lark’s analysis work package
Fictional supplier example. A Danish Lark team is preparing an attitude-control-unit analysis deliverable with a potential partner elsewhere in Europe. It proposes to develop the unit model in Denmark while the partner provides spacecraft interface assumptions. This is an illustrative planning case, not a reported GSTP application or award.
The team first separates national-support questions from technical questions. It needs to establish the actual programme conditions for its proposed work share. Independently, it needs to define the interface-model version, operating cases and review evidence that make the analysis deliverable meaningful.
The engineering review finds that “partner supplies the model” hides a significant assumption: the delivered model must include the operating mode used in the analysis. Lark records that input requirement and assigns a partner contact to resolve it. If the information is unavailable, the proposal should show the limitation and the work needed to address it, rather than claiming the analysis is ready to close.
Connect the selected contract to its ECSS obligations
ECSS-S-ST-00C Rev.2 ties applicability to the business agreement and its project requirements. Once the work package is defined, inspect the invoked standards, editions and tailoring. National support for an activity does not by itself identify every engineering or process obligation entering the supplier’s agreement.
Use the ECSS applicability guide to identify what applies and the compliance-matrix example to organise responses and evidence. Keep responsibility for partner inputs visible alongside the obligations; a missing interface can matter more to delivery readiness than a long list of generic standards references.
Use Arc to organise the agreed engineering scope
Arc supports connected ECSS project work and provides ECSS project templates. Its ECSS compliance agents can check relevant clauses and propose edits for review. These capabilities provide a starting point for organising the obligations and evidence selected for the project.
For Lark, configure the relationship between the applicable requirement, analysis deliverable and partner-supplied model. Ask reviewers to assess the relevant source references and unresolved dependency. Keep national support decisions in their proper context: this engineering setup is a suggested use of Arc, not a Danish funding or procurement approval process.
Frequently asked questions
Who should a Danish company contact about ESA participation?
The Danish Agency for Higher Education and Science publishes guidance on ESA programmes, funding and counselling, and identifies a contact for Denmark’s ESA membership. Start with the programme relevant to your proposed work and the current official instructions.
Is Danish support the same as winning an ESA contract?
No. The April 2026 GSTP announcement describes Danish support for selected activities that ESA will tender. Eligible actors still compete through ESA’s process; a support decision does not itself award the supplier contract.
Must a Danish bidder have submitted the original GSTP expression of interest?
For the selected GSTP Element 1 activities described in the 17 April 2026 announcement, support attaches to the activity rather than a specific actor. The guidance says Danish esa-star-registered actors can compete when the relevant ESA ITT is issued. Check the actual invitation and current support conditions.
Does every ESA opportunity require the same Danish support letter?
No single process should be assumed. Danish guidance distinguishes approval for technology activities from other participating programme routes. Confirm the requirement for the particular programme, activity and team before preparing the submission.
How should a Danish supplier start preparing for ECSS requirements?
Read the proposed agreement and applicable project requirements, identify the invoked editions and tailoring, and map each obligation to work and evidence. ECSS templates and agents can assist preparation, while project applicability and engineering acceptance still need review.
Evaluate Arc
Turn your next space contract into a clear engineering plan.
Connect the technical commitments in your next space tender to a delivery plan. Arc brings flexible programme records, ECSS project templates and compliance agents that check relevant clauses and propose edits for engineer review.