For each required field the DIANA form has its own prompts and questions. Don't treat them as a formality, your answer should address each of them in some way; evaluators use them to check you've covered everything that matters. The form is in English; below each field you'll find what DIANA is asking for, the character limit and our tip.
Creating your Company Profile
You create the Company Profile once per company, it describes who you are. Most fields are "not assessed during evaluation" (DIANA uses them only for statistics and eligibility checks), so fill them in truthfully but don’t stress over them. The decisive parts are the eligibility confirmations at the end.
Core Organisational Data
Your registered company name. It must be exactly the name under which you would sign a contract with DIANA if selected during the process.
The country where the company is headquartered, the main office where most key functions and strategic decisions take place. Must match your DUNS record.
The status of your DUNS number (Data Universal Numbering System). You select whether you have one or have applied for it.
You don’t need a finished DUNS at the time of applying, applying for it is enough. DIANA confirmed this on the webinar: if you advance in the process, they’ll request the DUNS from you afterwards. So you can safely choose "Have applied for DUNS but have not received" and continue.
The country where the company is legally registered, the jurisdiction in which your entity is incorporated with the relevant authorities.
The company’s registered address. It must match your DUNS record or application.
The year the company was founded. Must be consistent with your DUNS record.
The total number of full-time-equivalent staff (FTEs) across the company.
A small team is not a handicap. DIANA recommends at least 3 people, but it’s not a mandatory criterion, enter your real headcount. Don’t worry that only twenty-person companies stand a chance; that’s not the case.
If the company has a website, enter the URL. Optional.
Did your company emerge from another organisation or does it have ties to one (shared technology, IP, assets or founders)? Select your answer.
Funding
Have you raised dilutive funding so far, i.e. investment in exchange for equity in the company?
Have you received non-dilutive funding (grants, subsidies, etc.)? Select all that apply.
Technology and sector
Select the NATO emerging and disruptive technologies (EDTs) that fit your technical solution. More information at nato.int.
Pick only the areas that genuinely describe your solution. Ticking extra categories for "broader appeal" backfires, it looks unconvincing, as if you were building castles in the air. Fewer but accurate is better.
State whether your primary industry is Defence; Civilian; or Dual-use (both defence and civilian).
A purely defence company still makes sense in DIANA. Don’t be put off by the idea that "a defence company doesn’t need DIANA’s support", if you’re bringing a new civilian (dual-use) application of your technology, that’s perfectly fine and relevant.
Do you currently have customer contracts that generate revenue?
The estimated number of months the company can sustain itself at its current burn rate without new capital.
Team and founders
Which roles in the company are held by someone other than the CEO/founder? Select all roles covered by other people. If the CEO/founder covers everything, choose "None".
The number of company founders.
Does the company have a female founder (a woman among the founders)?
Do the founders or leadership have significant professional experience in the defence or national-security sector? (Prior employment, research or sustained collaboration with defence organisations, the defence industry, armed forces or security services.)
Does the company have a founder with a relevant technical background? This means formal education or significant academic/professional practice in engineering, computer science, applied sciences or a similar technical field related to your solution.
History and preferences
Have you ever applied to a NATO DIANA challenge before?
Have you been through another acceleration programme before?
Do you have experience with the defence industry?
Your main and secondary reasons for interest in DIANA (e.g. funding, mentoring, market access, test centres).
Your preferred accelerator location. Note: the actual accelerator assignment depends on several criteria, it is not a guarantee.
Confirmations, eligibility
These confirmations are decisive for eligibility. Unlike most of the earlier fields, they have a real impact, answer them truthfully.
Confirmation that your company’s headquarters are registered in a NATO member state.
Confirmation that your company does not have a parent company headquartered in a non-NATO member state.
Confirmation that your company has no ultimate beneficial owners (UBOs) from non-NATO member states exceeding 50%.
Confirmation that your company has no investors or stakeholders from strategically competitive states, including China, Russia, Iran or North Korea.
If you don’t meet one of these conditions (e.g. an ownership tie to a non-NATO state), it may lead to disqualification, but not always automatically. It depends on that state’s relationship with NATO and on the DIANA evaluators’ assessment. If you’re unsure, reach out to us beforehand.
Challenge application
The actual application of your solution to a specific challenge. It consists of the basic details, the Short Form and the Long Form. Watch the character limits on text fields, they are hard limits.
A common mistake: thinking you first submit only the Short Form and the Long Form later. That’s not the case. The Short Form AND the Long Form are submitted TOGETHER, with the deadline on 3 Jul 2026 (the 2026 call is now closed). Evaluators only read the Long Form in the second round of assessment, and only if they find your Short Form relevant. But you must submit both parts together by the deadline.
New Draft Proposal, basic details
The name of the technical solution you are proposing to the challenge.
Select the Technology Readiness Level (TRL) of the solution you are proposing to the challenge.
TRL 4-7 is the sweet spot, but don’t treat it as dogma, what matters most is the innovativeness and added value of the technology. DIANA has accepted solutions with both lower and higher TRL. TRL is a self-assessment: go through the scale and rate yourself realistically. Evaluators can spot significant over- and under-rating.
State whether your solution is software, hardware, or a combination of both.
State whether the solution is a standalone platform/system, or a subsystem/component that integrates into another system or platform.
Short Form proposal
4 parts · 1,500 chars eachThe short version of the application. Each of the four parts has a 1,500-character limit, write concisely and to the point.
Respond to these questions:
- Which elements of the challenge are you addressing?
- How does your technical solution solve the challenge?
- What is new or unique about your solution?
- Which defence and security needs does your solution meet?
Describe your technical solution. You may attach graphics or images that help convey your concept.
Respond to these questions:
- How will the challenge funding help mature your solution into a demonstrable and/or deployable technology?
- Key milestones: what will you achieve in 6 months and after one year?
- What are the most significant risks to reaching these milestones?
- How do you propose to mitigate those risks?
Respond to these questions:
- What are the defence and security applications of your solution? What adoption pathways have you identified?
- What is the market for your solution?
- What is your current level of public and/or private investment?
- Do you have relationships with industry primes? Do you plan to partner with a system integrator, or deliver an integrated solution?
You may upload a maximum of 2 images with graphics. They may contain words labelling elements within the image, but not narrative text with explanations or commentary. Images that thereby supplement the application text may cause ineligibility; images containing blocks of text will be discarded.
Long Form proposal
read only in round 2The detailed version. Evaluators read it only in the second round, if the Short Form was relevant, but it is submitted right away alongside the Short Form. Character limits differ between parts.
Summarise the solution in one sentence following the format: "the goal is to [provide this capability] using [this technology], to achieve [this impact]."
A short one-paragraph summary of the solution. Think of it as a written "elevator pitch".
Describe which elements of the challenge your solution addresses. Explain what is new or unique about it.
Describe the technical solution to the challenge in detail. Describe the current state of development and key performance metrics. Mention completed and planned test campaigns.
The longest field (12,000 characters), this is where the core of your technology belongs. It pays to add an architecture schematic or diagram as an image (not text as an image). Be specific and thorough: numbers, metrics, test results.
Give examples of how the solution could be used in defence and security, including direct military use cases. Describe the types of entities (military, civil protection, a national security agency, etc.) that could adopt the solution. You don’t need deep knowledge of defence operations, outlining potential applications is enough; examples are in the challenge brief.
Describe the solution’s end-user adoption potential and how it relates to addressable market segments and their use. Mention adoption pathways (government contracts, defence primes). How will you scale? Any IP rights or dependencies affecting commercial value? Expected revenue (incl. funding options), current runway and any open standards implemented.
Estimate the current TRL of the solution for defence applications and, if different, for civilian ones. Describe how the DIANA programme will help advance the TRL and how the solution can move toward a deployable capability. What is the overall roadmap to an operational solution? Key milestones at 6 months and after a year and beyond? Identify risks (technical and otherwise) and their mitigation.
Describe your team’s background and experience and how it is set up to deliver the roadmap and make use of the DIANA programme. How will you keep developing the solution while running day-to-day operations? Describe how you will use the €100,000 challenge funding, all funds must go toward the DIANA programme goals and relate directly to the proposed solution.
You may upload a maximum of 3 images with graphics. Same rule as the Short Form: they may contain element labels but no narrative text. Blocks of text as an image will be discarded.
Closing sections, tags and agreements
Tick the NATO EDTs that apply to your solution: Artificial intelligence (AI); Quantum technologies; Biotechnology and human enhancement; Space; Hypersonic systems; Novel materials and manufacturing; Energy and propulsion; Next-generation communication networks; Autonomous systems.
Select the tags that characterise your technical solution. You may choose as many as you like.
If you want to describe the technology with further tags, enter individual tags up to 50 characters, separated by commas. Optional.
Confirmation (in line with section 7.2(a) of the terms) that you have read the Terms and Conditions of Bidding in full and agree to them.
Confirmation that the application is submitted by a person working for the company under which it is registered, and that this is the company that would enter into any contract.
Confirmation that the applying entity is not a university, a non-profit or a not-for-profit organisation.
Agreement that the key people involved in Step 3, Virtual Panel Session will (if it comes to that point) participate directly in the accelerator programme and the related travel.
Agreement and understanding that the accelerator involves roughly 6 mandatory in-person thematic clusters at the assigned location and at events requiring transatlantic travel, and that mandatory completion of assignments is part of it.
In line with sections 7.2(a) and 7.2(b), DIANA may share your identity and documentation with NATO and allied stakeholders for the purpose of further opportunities, unless you opt out of such sharing.