To prepare for your first ESA contract, identify a suitable opportunity, establish the bidding entity’s registration and eligibility, and work out how the team would deliver the requested result. Treat the proposal as a commitment to engineering work: read the applicable documents, expose assumptions, assign responsibilities and plan the evidence. The useful starting question is which specific piece of work your company can deliver credibly.
This guide is for engineering suppliers entering an ESA activity directly or through an industrial team. It covers the shared route that national guides can build on. The checklists below are preparation aids: the issued invitation and any subsequent agreement determine the actual submission and delivery obligations.
Find an opportunity that matches a deliverable
ESA’s business guidance welcomes space and non-space companies and says that most opportunities are published through esa-star Publication. Start there to locate a procurement, then describe its requested outcome in plain language. A study, an equipment development and a test service may use similar technology while requiring very different evidence and delivery capacity.
Write a short opportunity note before assembling a large team. Record what is being purchased, what your company contributes, who would own the complete result, and what information is missing. Include the source and version of the notice so a later change is visible. A search result or an old announcement is a route to the documents, not sufficient evidence that a competition remains open.
Register the right legal entity in esa-star
ESA’s registration instructions distinguish Light and Full entity registration. Light registration gives access through proposal submission; contract award requires Full registration. The instructions also ask organisations to check whether they already exist as an entity or a business unit before creating a new entry.
Assign an owner for registration and confirm which legal entity would sign the agreement. Keep the company details used in the proposal consistent with that entity. Allow time to resolve validation questions and access problems before the submission window becomes critical. Registration is an administrative preparation task; it does not settle the opportunity’s technical fit or the bidder’s eligibility.
Check eligibility and national support for the actual route
A national-delegation step can be central to a particular programme. For example, the downstream ARTES direct-negotiation guide requires national authorisation covering the full proposal and connects funded participation to programme states identified in the invitation. Its instructions also address the countries of prime contractors and subcontractors. Keep that example within its programme scope.
Build an eligibility note from the actual invitation: participating countries, permitted entity types, the proposed role of each partner, any national-support requirement and where clarification should be sought. Mark unknowns explicitly. If a partner changes, revisit that note; an apparently small change in the team may alter the conditions that made the proposal viable.
Ask the relevant delegation about the named programme and activity, rather than asking whether your company is generally eligible for ESA funding. Share the proposed work, location, team and technical objective. Keep national support and the procurement decision as separate entries in the plan so that one is not accidentally reported as the other.
Choose a prime or subcontract role deliberately
ESA’s C1–C4 procurement measures distinguish actions reserved for certain non-prime or SME participants from competitions requesting their participation in industrial teams. The applicable measure is attached to the procurement. It is a useful reason to inspect the invitation closely, rather than assuming a first-time company must always work under a large prime.
Choose the role by delivery responsibility. If your team can credibly supply one specialised analysis or equipment element, define that boundary and the inputs it needs from others. If you propose to lead, identify who will integrate the complete technical response and reconcile partner assumptions. For a subcontract, ask the buying company for the applicable technical and management requirements and its acceptance route before treating the work package as settled.
Turn the tender package into a reviewable response map
Use this original worksheet to connect the issued material to decisions. Adapt the document labels to the actual package; this is not a prescribed ESA submission form.
| Material to inspect | Question to resolve | Record to prepare |
|---|---|---|
| Invitation and submission instructions | Who can respond, how, and in which form? | Eligibility and submission checklist with an owner |
| Technical scope and applicable documents | What result and evidence are required? | Obligations register and clarification log |
| Deliverables and review expectations | What must exist when the customer evaluates progress? | Deliverable plan linked to technical activities |
| Commercial and contractual material | Which assumptions affect the offered commitment? | Commercial review and documented exceptions |
| Team contributions | Who supplies inputs and accepts each interface? | Work-package boundaries and partner commitments |
Read across the map. If a technical response promises a test, its schedule, resources and deliverable should tell the same story. If a partner supplies a model, identify the model’s required maturity and delivery point. This cross-check is more useful than checking whether each proposal section merely contains text.
For each uncertainty, retain the source reference, proposed interpretation, consequence and question. Follow the invitation’s designated clarification process. Distinguish a question sent from an answer received, and update the affected response when an authoritative answer arrives. Do not silently turn a supplier assumption into a customer commitment.
Establish which ECSS obligations enter the work
ECSS-S-ST-00C Rev.2 explains that ECSS documents become applicable through business agreements and that the supplier demonstrates compliance with its customer’s project requirements. Review the invoked editions and agreed applicability for the work being offered. The agency name alone does not define the complete standards obligation.
Separate applicability from fulfilment. First identify the requirement that belongs in the project; then explain the activity, procedure, deliverable or product evidence that would satisfy it. Some obligations concern how the project is managed, so a product test cannot answer every compliance question. Use the first ECSS contract checklist for a deeper pre-bid review and the worked compliance matrix to structure the response.
Fictional example: the Lark attitude-control unit
Fictional supplier example. Lark is preparing a technical deliverable for an attitude-control unit. The team believes it can provide the control design and supporting analysis, but its proposed verification depends on a customer-supplied spacecraft model. No real ESA tender or mission is represented.
The initial draft says that pointing performance will be demonstrated. During the bid review, the engineering lead asks which model version will be supplied, which operating conditions the analysis must cover and who will accept the model’s suitability. The team records these as assumptions requiring resolution and connects them to the analysis deliverable.
The resulting response is more precise: it identifies the planned analysis, its required inputs, the evidence to be produced and the unresolved customer input. If the model will arrive later than assumed, the team can revisit the work sequence before committing. The lesson is to make a dependency inspectable, not to fill uncertainty with a confident verification claim.
Prepare the handover from proposal to delivery
Before submission, have someone who did not write the response trace one proposed deliverable back to the requested outcome, its resources and its acceptance evidence. Check that every material exception or assumption is visible in the appropriate submission location. Preserve the exact files submitted and the acknowledgement from the designated system.
If negotiations change the work, compare the resulting agreement with the reviewed bid. Transfer accepted commitments, unresolved inputs, partner boundaries and applicable documents into the delivery setup. Mark which earlier proposal assumptions have been replaced. That gives the project lead a useful starting record instead of a collection of persuasive paragraphs whose status is unclear.
Organise the engineering work in Arc
Arc’s ECSS workflows connect applicable obligations with requirements, engineering work and evidence. ECSS project templates help teams start that setup, and ECSS compliance agents can check relevant clauses and propose edits for review.
For the Lark example, begin with the agreed source set and the analysis dependency. Ask reviewers to assess whether the proposed relationships explain the commitment and expose missing inputs. Keep the customer’s applicability and acceptance decisions explicit. The Arc ECSS project guide explains the broader workflow for carrying a first contract into controlled engineering delivery.
Frequently asked questions
How do I start doing business with ESA?
Check the official Business with ESA guidance, identify a relevant opportunity and register the bidding entity in esa-star. Assess the specific invitation’s country, programme and bidder conditions before investing in a full proposal.
Can I submit an ESA proposal with light registration?
ESA states that light esa-star registration permits proposal submission, while award of an ESA contract requires full registration. Complete the required entity information early and follow the current registration guidance.
Does every ESA bid require national-delegation approval?
Do not assume one rule for every ESA opportunity. National authorisation is required in specified programme routes, including the downstream ARTES direct-negotiation route cited here. Check the actual invitation and relevant national guidance for your team.
Can a small company work as a subcontractor on an ESA project?
ESA’s SME procurement policy includes measures encouraging non-prime and SME participation in contractor teams for specified procurements. The relevant invitation determines the conditions; the supplier must also understand its agreement with the company buying its work.
Does using an ECSS template qualify a supplier for an ESA contract?
A template can help organise the project, but it does not establish bidder eligibility, an award or compliance. Confirm the opportunity conditions and applicable project requirements, then prepare the work and evidence needed to satisfy them.
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.