An NSIP Call 3 full technical proposal should show how funded work closes a specific technology gap and produces evidence of progress. As checked on 8 September 2026, the outline stage is closed. Full proposals are for invited applicants and are due 12 November 2026 at 23:59. The published timetable schedules invitations for 5 October. NSIP Call 3 announcement of opportunity
The National Space Innovation Programme (NSIP) Call 3 intends to award up to £20 million in co-funded grants. The official announcement defines the streams, eligibility, finance rules and submission process. Use its Flexi-Grant route and official application materials; this guide’s records are internal preparation aids. NSIP Call 3 announcement of opportunity
Which stream and maturity claim are you preparing?
| Stream | Grant request range | Published emphasis |
|---|---|---|
| Kick Starter | £150,000–£1 million | Roughly early-stage TRL 1–4; disruptive or novel proposals. |
| Major Projects | £150,000–£2 million | Projects should achieve higher TRLs 5–9, with commercialisation and investment emphasis. |
Both streams have a maximum duration of 30 months. The anticipated start is 1 April 2027 and projects must finish by 30 September 2029. Those dates need to be reflected in recruitment, procurement, facility access and partner commitments. NSIP Call 3 announcement of opportunity The TRL guide explains how to support a maturity claim with configuration-specific evidence rather than a number alone.
Worked example: make a robotic-tool proposal internally consistent
Fictional example: a team proposes a modular robotic tool for an in-orbit assembly application. The scenario assumes a bench mechanism exists, but mating repeatability under representative loads has not been demonstrated. Neither the scenario nor the proposed work establishes eligibility, a grant award or a real test result.
| Package / milestone | Work and inspectable output | Risk and owner |
|---|---|---|
| WP-1 / M-1: define the interface | Agree a host-interface draft, load assumptions and a measurable mating criterion; record open allocations | Systems lead: host load data may arrive late. |
| WP-2 / M-2: build the representative item | Document mechanism revision, materials and assembly state; review differences from the bench unit | Mechanical lead: part lead time could delay integration. |
| WP-3 / M-3: execute planned verification | Run the agreed mating sequence; retain procedure, raw measurements, configuration and anomalies | Verification lead: fixture stiffness may distort the measurement. |
| WP-4 / M-4: assess the result | Review criterion-by-criterion outcomes, residual gaps and the next development decision | Chief engineer: a completed campaign may still leave the intended application unsupported. |
Suppose the proposal’s narrative promises repeatable mating, but its budget pays only for a single demonstration. That is a consistency failure. The engineering team should define an appropriate repeatability campaign, cost the fixtures and measurement work, and align the narrative with what it can actually establish. The number of repetitions and permitted loads require a technical basis; this article does not prescribe them.
How do milestones differ from activities?
“Finish testing” identifies an activity boundary. A useful proposed milestone also names the item, success criterion, evidence set, reviewer and treatment of anomalies. For the robotic tool, M-3 might deliver the test record while M-4 decides what that record supports. Keeping those separate prevents a schedule tick from becoming an unsupported performance claim.
Use one identifier for each work package throughout narrative, cost breakdown, schedule and risk records. Ask each partner to confirm its inputs and handovers. Where a task depends on a customer specification, state the assumed version and the effect of a delay. This is Arc’s recommended reconciliation method, not a substitute for the official Part A, narrative and security materials described by the call.
What belongs in the risk and resource review?
Review people, facilities, equipment availability, host access and analysis effort together. A risk entry should name its cause, consequence, response and owner. Include the evidence that will tell you whether the response worked. For the fixture risk, that could be a planned correlation check before the full campaign, with a decision to modify the fixture if it is insufficiently representative.
Do not infer match-funding eligibility from this technical example. Use the official finance rules for your organisation and activity. Likewise, do not present expected commercial outcomes as already secured. A proposed customer evaluation and a signed order are different evidence states.
Before submission, have the bid owner reconcile the official form and annexes against the engineering records. Use review-readiness checks for unresolved technical decisions, ISAM planning for mission dependencies and the UK route hub for the broader funding context.
Try one work package in Arc
Arc connects requirements, interfaces, risks, verification activities and evidence in a programme model. Arc connected programme model Start with one bid commitment, its proposed evidence and the person responsible for the next decision. Engineers remain responsible for the technical judgement; using a tool does not establish eligibility, compliance or a funding award.
Frequently asked questions
Can a new applicant enter at the NSIP full-proposal stage?
The full-proposal stage is for applicants invited after the outline assessment. The outline stage closed on 21 August 2026. The later full-proposal deadline does not reopen initial entry.
When is the NSIP Call 3 full-proposal deadline?
The published deadline is 12 November 2026 at 23:59, checked on 8 September 2026. Use the current opportunity guidance and Flexi-Grant submission instructions; invitations are scheduled for 5 October.
Is the evidence workbook an NSIP submission form?
No. It helps reconcile your technical claims, work packages, milestones and evidence before completing the official forms. Follow the programme’s permitted document structure and submission route.
Evaluate Arc
Connect one bid commitment to its engineering evidence.
Try a work package in Arc: organise its requirements, interfaces, risks, verification work and evidence so your team can review the next decision.