Looking for a DASA open call? Start with UKDI’s current funding page

Companies searching for DASA funding should now begin with UK Defence Innovation’s live funding opportunities. The former DASA funding collection explicitly says the accelerator is part of UKDI and directs readers to the new service. That matters because historic DASA competition pages still appear in search results with useful-looking application instructions.

A familiar programme name is insufficient evidence that a call accepts applications. The DASA Open Call collection describes previous, closed cycles. A founder who builds a proposal around one of those documents may be using the wrong deadline, challenge or contract.

Even the current listing needs a date check. On 6 September, its open-call section still displayed a Security Open Call with a 27 August 2026 deadline. That date had passed. The same page said a new route for defence-focused innovations was being developed and that Defence Innovation Loans were paused. Neither statement supports assuming a continuously available defence open call or loan application.

The practical answer is to treat the live listing as the starting point and the selected competition document as the decision document. Record the competition’s exact name, application window, required maturity, eligible applicants, deliverables and contractual terms. Keep the document version alongside the internal decision to pursue it. This recommendation is a proposal-management method, not an assertion that every listed competition suits every company.

Consider a hypothetical civil software business that finds a DASA article through Google. Its first task is to trace the article forward to the current competition. Its second is to determine whether the buyer funds research to overcome an uncertainty or wants a mature product. Those are different commitments for the same engineering team. A good product can still be a poor research proposal when there is no meaningful development task matching the challenge.

The current submission guidance, updated on 3 September 2026, points applicants to UKDI’s online submission service. It also makes the company responsible for submitting on time. An internal deadline should therefore precede the published deadline and leave room for administrative and upload problems. Account creation and document preparation are part of proposal work, not chores to leave until the last hour. The UKDI fundable but not funded review explains why a positive assessment still differs from a funded project.

Build a small decision record before drafting: what uncertainty the project resolves; what evidence will demonstrate progress; who will deliver each task; what the company can complete within the proposed period; and which terms need review. The record should also identify the commercial next step after the research. That might be another development project or a separately competed supply contract. It should not be described internally as an order already won.

The September page contains several different clocks

The collection's update history helps explain why a familiar search result can be misleading. On 3 September it added Project PANOPTES to the themed competitions list and removed a Space to Innovate entry from the invited second-stage section. At the 6 September check, it listed 22 September for Innovation Support to Operations Cycle 8, 23 September for PANOPTES, and 17 September for the invited second stage of Novel Autonomy and Robotics. These dates belong to different competitions and access conditions. They do not announce the reopening of a general defence open call. UKDI live funding collection

For a company maintaining an opportunity database, the publication date of the collection is therefore a weak status field. The useful unit is the individual competition and stage. A change to one row can make the collection appear fresh while another row retains an expired deadline. An automated alert should prompt someone to inspect the changed competition, rather than move every opportunity under the UKDI heading into an active sales forecast.

The distinction is particularly important for a business with a broadly applicable software component. A data-processing product may appear relevant to several challenge titles. That resemblance does not tell the company whether a competition wants early research, a mature demonstration, a particular applicant location or a proposal from an already shortlisted team. Reading those conditions first can save several days of proposal work and reveal that the right preparation is a partner conversation for a future cycle.

Open call, market exploration and pipeline entry serve different purposes

The collection also separates market exploration from funding competitions and identifies DTEP in its future pipeline with timing to be confirmed. Market exploration gathers information about available and developing capabilities to inform possible future activity. It does not commit UKDI to launch a competition. Those two categories belong in a company's market intelligence record, while an eligible competition with a live deadline belongs in its bid schedule. UKDI opportunity categories

Consider a hypothetical supplier of maintenance data software. A market exploration response might explain the product's current integration requirements, commercial deployment model and evidence from existing customers. The purpose is to help the authority understand the market. A later research competition might instead request a costed investigation into a specific uncertainty. Copying the first document into the second would leave assessors without a defined experiment, delivery plan or explanation of what funding would change.

That distinction also shapes what the company discloses. A market description should make the capability understandable without assuming a confidential technical exchange has already been agreed. The company can identify the categories of evidence it holds and the questions it can investigate. Detailed material then follows the instructions and handling conditions of the actual route. A well-prepared response is useful because it is specific to the authority's question, not because it contains the largest possible amount of proprietary information.

Prepare an application that can move with the correct competition

The practical preparation during a route change is to maintain a reusable evidence base, then build a competition-specific submission from it. Keep the description of the existing product separate from the proposed research. Keep staff experience separate from the effort they can commit in the requested period. Keep a customer problem separate from a proposed deliverable. These distinctions make the material easier to adapt without carrying old deadlines, budget assumptions or eligibility statements into a new form.

UKDI's submission instructions add a concrete operational constraint: drafts do not automatically move into later competitions or open-call cycles, and a submitted proposal cannot subsequently be edited. That makes a locally retained, dated copy of the final application valuable. It allows the team to compare its proposal with feedback and prepare a deliberate resubmission, rather than rely on a draft associated with an obsolete cycle. Proposal submission and review

For a small team, the most useful handover is a short opportunity record linking the current competition document, submission workspace, responsible author and internal decision date. Commercial and technical staff should agree what must be true for the company to bid: a relevant challenge, available people, rights to necessary inputs and an affordable delivery plan. The record then turns a changing collection of government webpages into an actionable decision without mistaking page freshness for an invitation.

The transition to UKDI does not by itself establish a new funding entitlement, a new open-call schedule or universal eligibility. Those conclusions require the current opportunity documents. Old DASA pages remain useful for understanding previous activity, provided their dates remain visible. For business-development teams, the important change is where to verify an opportunity before spending scarce engineering and proposal time. The UKDI desirable, feasible and viable criteria guide separates user need, technical credibility and delivery planning in a proposal.