Defence tender support

Defence procurement position

Public evidence The Procurement Act 2023 contains a defined defence-and-security contract category and provisions specific to it. Official guidance explains that much of the Act still applies, including competitive procedures, conditions of participation and award criteria, while identified derogations and flexibilities address characteristics such as operational urgency, security of information, security of supply and technical refresh. Classification and any exemption must be determined from the actual requirement, not merely from the buyer being MOD. [ 001, 002, 003 ]

Evidence-linked insight · What this changes Suppliers must establish the governing route before shaping the bid. Ordinary goods or services purchased by a defence body, a covered defence-and-security contract, an exempt contract, a framework or dynamic-market competition, and a qualifying non-competitive arrangement do not share one rule set. This sector view identifies bid controls, but only the current notice, tender pack, contract conditions, security material and appropriate professional advice can determine applicability. [ 001, 003, 006, 010 ]

Strategic direction changes the questions buyers ask

Public evidence The Strategic Defence Review 2025 describes a shift towards warfighting readiness, a NATO-first posture, faster adoption of technology and a stronger relationship with industry. The Defence Industrial Strategy 2025 links national security with UK growth, innovation, industrial resilience and acquisition reform. These policy documents shape market context; they do not override a notice, confer supplier preference or prove that a bidder's offer contributes to a stated outcome. [ 004, 005 ]

Where we would start first Translate strategic language only where the requirement supports it. Identify the capability effect, time-to-field, sovereign or onshore dependency, interoperability, export opportunity, skills, production capacity or resilience mechanism that the proposed contract can genuinely influence. Provide a measurable chain from supplier activity to contract output and then to the authority's intended effect. Avoid repeating policy slogans without resources, milestones or evidence. [ 004, 005, 011, 012 ]

Buyer landscape and access routes

Public evidence The landscape includes MOD head-office functions, Defence Equipment and Support, delivery teams, Front Line Commands, the Defence Science and Technology Laboratory, Defence Infrastructure Organisation and other defence bodies. The Defence Sourcing Portal hosts advertised MOD opportunities, while procurement records may also appear on Find a Tender. Frameworks, the Space Technology Solutions dynamic market, research routes and preliminary market engagement are visible in the official examples used here. [ 009, 011, 012, 013, 014 ]

Where we would start first Maintain route-specific readiness across the central digital platform and any stated defence portal or commercial vehicle. Track acquisition pipelines and engagement, but confirm whether the opportunity is open to the market, restricted to admitted suppliers or dependent on a preliminary stage. The PRIMUS II record illustrates that dynamic-market membership can affect participation; it should not be generalised to unrelated MOD work. [ 003, 009, 013 ]

A sector spanning research, equipment and support

Public evidence Current notices demonstrate markedly different acquisitions. Peripheral cold-injury research sought market input for a laboratory-based service. PRIMUS II concerns maintenance and technical support for an authority-owned ground-station terminal. Remote Case Entry combines equipment procurement with training, spares, repairs, maintenance and obsolescence management. Aircraft Commodity Consumables uses consumption data, supply-chain modelling and documented traceability to support availability across platforms. [ 011, 012, 013, 014 ]

Evidence-linked insight · What this changes The winning evidence architecture must follow the acquisition. Research needs methodology, ethics or approvals where specified, data quality and translation into use. Equipment needs conformity, test, configuration and acceptance. Support needs availability, repair, technical data, competent people and obsolescence control. Commodity supply needs provenance, forecasting and stock assurance. Defence familiarity cannot substitute for subject-matter competence in the offered category. [ 011, 012, 013, 014 ]

Conditions, stages and trials must stay separate

Public evidence The official procurement examples show staged designs. PRIMUS II uses a competitive flexible procedure through a dynamic market, with participation assessment before invitation to negotiate. Remote Case Entry separates conditions of participation from a later tender process and planned confirmation trials. Its published record identifies scored technical areas for that competition. Aircraft Commodity Consumables records a completed competitive flexible procedure under the defence-and-security special regime. [ 011, 013, 014 ]

Where we would start first Build one compliance map for eligibility and another for award. Add gates for demonstrations, trials, negotiation, security information and final submission, retaining the buyer's stated sequence. Define what evidence is permissible at each stage and who approves it. A sophisticated technical answer submitted in the wrong response, an altered form or a late portal upload can fail independently of product merit. [ 001, 003, 013, 014 ]

Stakeholder assurance extends beyond procurement

Evidence-linked insight · What this changes Commercial staff need a lawful, affordable and manageable deal; capability sponsors need the required effect; users need operability in the intended environment; engineering and quality authorities need design, configuration and acceptance evidence; safety owners need controlled hazards; security teams need proportionate protection; support teams need maintainability and supply; finance needs credible whole-life cost; and senior responsible owners need schedule, dependencies and risk made visible. [ 003, 004, 007, 008, 011, 014 ]

Where we would start first Create an assurance map that links each stakeholder to a decision, artefact and acceptance point. Use technical authorities for matters that require their judgement and preserve separation between supplier assurance and authority acceptance. Where information is classified or commercially sensitive, keep the working group and evidence route within authorised boundaries. The public narrative should never disclose a vulnerability, protected location or controlled system detail. [ 007, 008, 011, 014 ]

Hard barriers and current capability

Evidence-linked insight · What this changes Potential barriers can include the correct legal entity, economic standing, admissible experience, dynamic-market or framework status, export-control position, specified quality capability, cyber requirements, secure facilities or people, and access to intellectual property, tooling or original-equipment support. None is universal. Some notices permit a commitment before award or reliance through another entity; others require current evidence at participation or tender stage. [ 003, 007, 008, 013, 014 ]

Where we would start first Form a qualification board early. For each condition, record its wording, assessment stage, bidding entity, evidence owner, validity, scope, permitted reliance and consequence of failure. Confirm whether a subcontractor's credential actually covers the work it will perform and whether the prime retains an unmet obligation. If clearance, certification, membership or rights cannot be obtained on the required timetable, surface a partner or no-bid decision rather than drafting around the gap. [ 001, 003, 007, 013, 014 ]

Security requirements are contract-specific

Public evidence The defence-and-security guidance defines relevant categories, including sensitive equipment, services or works involving classified information. MOD's Industry Security Notices cover topics such as Security Aspects Letters, contractual security conditions, classified subcontracting and supplier incident reporting. The collection changed during 2026. A supplier must use the notice and the contract's issued security instructions; a public summary is not enough to establish the required controls. [ 003, 008 ]

Where we would start first Map information and assets by classification, location, system, user, transfer, storage, disposal and incident route. Confirm facility and personnel requirements, foreign-national or ownership considerations, collaborating entities and security flow-down only where the procurement raises them. Protect tender materials with need-to-know access and approved tooling. Do not claim a clearance as a company-wide attribute when it belongs to a person, facility, contract or specific scope. [ 003, 006, 008 ]

Cyber assurance follows a risk profile

Public evidence MOD's Cyber Security Model version 4 is live. The published model describes authority risk assessment, four cyber risk profiles, controls in Defence Standard 05-138 Issue 4, supplier assurance questionnaires, subcontractor flow-down and a Cyber Improvement Plan route where requirements are not yet met. DEFCON 658 provides the contractual mechanism. The appropriate profile and evidence must come from the procurement, not from a generic defence-sector assumption. [ 007, 008 ]

Where we would start first Assign the Cyber Risk Assessment reference and profile to the correct contract and entity. Trace each control to implementation evidence, scope, system owner and continuing assurance. For subcontracted work, show the risk assessment and flow-down process rather than forwarding the prime's questionnaire. If a Cyber Improvement Plan is permitted, disclose the actual gap and delivery date; it is not evidence that the missing control already operates. [ 007, 008, 011 ]

Quality, safety and configuration cannot be reduced to certificates

Public evidence The Aircraft Commodity Consumables award record describes airworthiness-related provenance, labelling, documentation, recognised quality-management evidence and oversight in its own aviation context. The Remote Case Entry notice identifies quality assurance, safety, project management and integrated logistic support within its participation assessment and names AQAP 2110 as a contractual quality condition. These are procurement-specific examples, not a universal defence checklist. [ 011, 014 ]

Where we would start first Show how requirements move through design, production or service, inspection, test, acceptance, release, configuration control and corrective action. Identify the competent authority for safety and technical decisions. Keep certificate scope, approved sites, exclusions and expiry visible. If the solution changes after a trial or negotiation, reconcile specifications, hazard controls, support data, cost and configuration baseline before final commitment. [ 011, 014 ]

Evidence must preserve provenance and limitations

Evidence-linked insight · What this changes Relevant records may include acceptance results, reliability and maintainability data, configuration status, defect and corrective-action history, authorised designs, test facilities, supply performance, technical publications, competency records, software assurance, research outputs and service availability. A comparable contract can support credibility only if scale, environment, security, authority, platform and supplier role are made clear. Redaction must protect sensitive content without removing the point being evidenced. [ 007, 011, 012, 013, 014 ]

Where we would start first Operate a controlled evidence index with origin, owner, classification, contract permission, date, configuration, entity, scope and caveat. Link every scored claim to the smallest sufficient artefact and retain review history. Where export, customer or third-party restrictions prevent disclosure, seek the authorised evidence route or clarification rather than implying access. Separate a planned verification activity from an achieved result. [ 008, 011, 014 ]

Competitive and single-source economics require different controls

Public evidence Defence contracting includes competed and non-competitive routes. A May 2026 MOD announcement described reforms to parts of the single-source regime, including performance incentives and planned later changes; the announcement itself states that some measures were being laid, consulted on or intended for later instruments. Bidders must check enacted legislation and contract coverage rather than treating every announced feature as already in force. [ 010 ]

Evidence-linked insight · What this changes A viable price may need to fund design maturation, non-recurring engineering, equipment, spares, support, data, facilities, security, certification, testing, inflation, currency, obsolescence, surge and exit. Risk allocation, allowable-cost treatment and profit mechanisms vary. The commercial submission should reveal its cost drivers and dependencies while protecting negotiation authority; an artificially low acquisition price can create unaffordable availability or refresh later. [ 004, 010, 011, 013, 014 ]

Through-life support is part of the capability

Public evidence The sampled records make support explicit. Aircraft Commodity Consumables includes supply analysis, obsolescence management and technical support across long-lived platforms. PRIMUS II seeks maintenance and technical support for an authority asset. Remote Case Entry includes servicing, repairs, training, spares and obsolescence management over an extended period. These records illustrate why sustainment evidence can be as important as initial delivery. [ 011, 013, 014 ]

Where we would start first Define support concept, maintenance levels, repair loop, spares logic, technical data, tooling, training, obsolescence surveillance, configuration feedback and disposal. State assumptions about government-furnished assets, usage, environment and access. Model supplier failure and component discontinuance. Connect response and repair targets to inventory, skills and locations, then reconcile those resources to the commercial model and proposed performance measures. [ 011, 013, 014 ]

Mobilisation is a sequence of authority decisions

Evidence-linked insight · What this changes Defence mobilisation can include security onboarding, design reviews, facility or tooling preparation, subcontract placement, long-lead procurement, data delivery, trials, user training, initial spares, configuration baselines and service acceptance. Published Remote Case Entry milestones distinguish initial and fuller capability within its specific procurement. Such milestones should be used only when the authority defines them; their meaning is not identical across programmes. [ 011, 013, 014 ]

Where we would start first Build the integrated plan backwards from contractual acceptance and operational need. For every milestone, name the evidence, predecessor, decision authority, resource, security dependency and contingency. Expose long-lead and government-furnished dependencies. Do not schedule trials as decorative endpoints: allocate representative equipment, environment, instrumentation, anomaly resolution and regression. Define what happens if acceptance is delayed without compromising safety or controlled information. [ 011, 013, 014 ]

Industrial resilience and partner structure

Public evidence The Defence Industrial Strategy emphasises a resilient industrial base, UK growth, innovation and changed acquisition. MOD security and cyber material makes clear that obligations can extend into subcontracting. The current notices also show opportunities identified as suitable for smaller businesses. None of this removes the need for a lawful procurement, a deliverable prime model or transparent evaluation against the published criteria. [ 004, 007, 008, 012, 013, 014 ]

Where we would start first Map critical suppliers, sole sources, foreign dependencies, lead times, capacity, tooling, data rights, quality authority, security scope, cyber flow-down, export controls and substitution. Use a consortium or specialist partner where it closes a defined gap and the route permits it. Secure governance, workshare, price, liability, evidence access, change control and continuity before submission. An aspirational partner ecosystem is not a resilient supply chain. [ 003, 004, 007, 008, 011 ]

Innovation must reach an accepted operational state

Public evidence The Strategic Defence Review and Defence Industrial Strategy promote faster technology adoption and closer engagement with industry. The cold-injury research notice is an example of preliminary market engagement used to understand capability, capacity and possible solutions before a planned tender. It expressly does not commit the authority to proceed. Market interest or a promising prototype is therefore not equivalent to a contract or accepted capability. [ 004, 005, 012 ]

Where we would start first Describe innovation through its maturity, user problem, test evidence, integration path, safety and security work, manufacturing or scaling capacity, support model and decision gates. State what is already demonstrated and what remains experimental. Design to the authority's cost and time boundaries where supplied. If intellectual-property, export or third-party rights limit exploitation, make that visible before the solution becomes central to the bid. [ 004, 005, 012, 014 ]

Performance measures must reflect capability delivery

Evidence-linked insight · What this changes Measures may include milestone achievement, acceptance quality, equipment availability, supply fulfilment, repair turnaround, reliability, configuration accuracy, defect recurrence, obsolescence action, training completion, security compliance or research deliverables. Operational outcomes often depend on authority and other-system inputs, so the contract must separate supplier-controlled performance from broader capability effects. A single aggregate status can conceal a safety, schedule or supply failure. [ 010, 011, 012, 013, 014 ]

Where we would start first Specify metric definitions, data source, baseline, clock, exclusions, confidence, reporting, validation and remedy. Link incentive or service-credit proposals to behaviour the supplier can control and model their financial exposure. Preserve technical and security exceptions from inappropriate public reporting while maintaining authority visibility. Use trend, root-cause and corrective-action governance rather than reporting a number without a decision route. [ 010, 011, 014 ]

Repeated defence-bid failure patterns

Evidence-linked insight · What this changes Weak pursuits confuse buyer identity with procurement regime, claim broad security credentials, rely on a prime or parent whose evidence cannot be used, present a prototype as fielded capability, omit data rights, ignore a long-lead sole source, price acquisition without sustainment, or cite a quality certificate whose scope does not cover the offered work. These gaps usually surface again at participation, trial, negotiation or mobilisation. [ 003, 007, 008, 011, 014 ]

Evidence-linked insight · What this changes Another failure is over-disclosure: moving controlled tender information into an unapproved collaboration environment, naming protected characteristics in public copy or using an evidence artefact beyond its permission. The opposite error is empty secrecy, where the response says detail is sensitive but provides no authorised proof route. Security and evaluator traceability must be designed together. [ 003, 006, 008 ]

Sector-specific Bid Strengthening Plan

Where we would start first The defence plan should settle classification, route, bidding entity and hard barriers first. It then maps capability effects, evidence provenance, security and cyber scope, safety and quality assurance, supply resilience, rights, price, trials, acceptance and sustainment. Each gap needs an authorised owner, admissible remedy, decision date and stop condition. Controlled materials should have a parallel handling plan rather than being copied into the general workspace. [ 001, 003, 007, 008, 011 ]

Where we would start first Before submission it may be possible to improve entity records, portal readiness, partner agreements, evidence indexing, resource confirmation, cost assumptions, test design and cross-volume consistency. It may not be possible to obtain missing rights, create mature performance history, build secure facilities or finish a technical qualification in time. Where the live documents demand existing capability, the honest remedy is partner, qualify or stop. [ 009, 013, 014 ]

Support boundary and client decisions

Where we would start first Under an agreed scope, Bid Champions can build pursuit governance, requirement and evidence matrices, contributor controls, review packs, commercial assumption logs, trial-readiness questions, mobilisation traceability and a strengthening backlog. It can coordinate authorised specialists and expose contradictions between capability, security, supply, schedule and price. It does not certify defence products, approve safety, grant clearance, interpret classified requirements publicly or guarantee authority acceptance. [ 003, 007, 008, 014 ]

Evidence-linked insight · What this changes The client owns bid/no-bid, entity and partner selection, technical solution, security representations, risk acceptance, export and legal advice, intellectual-property position, commercial limits and all submitted commitments. Those decisions need named executive, engineering, security, delivery and commercial approval. No Bid Champions defence client, award, metric or endorsement is asserted here because approved publication evidence has not been linked. [ 001, 003, 006, 008 ]

Capability retained and the next pursuit action

Evidence-linked insight · What this changes A disciplined pursuit leaves useful operating assets: route decision record, controlled evidence index, security and cyber mappings, configuration-aware proof, industrial dependency map, cost and schedule assumptions, test logic, acceptance criteria and through-life support model. Their value depends on configuration and access control. Owners must update them after design changes, incidents, assurance activity, supplier changes and policy revisions rather than treating the bid library as permanent truth. [ 004, 007, 008, 011, 014 ]

Where we would start first For a specific opportunity, start with the notice, route, issued security material and required commercial vehicle. Establish what must exist now, what can be matured before each stage and which claims need controlled evidence. Recheck the dated sources because guidance and notices continue to change. The four procurement examples prove current market variety only; they do not establish Bid Champions performance or a reusable MOD specification. [ 006, 008, 011, 012, 013, 014 ]

• Classify the procurement route before applying defence-specific flexibilities.
• Keep controlled evidence within authorised people, systems and disclosure routes.
• Reconcile technical maturity, trials, acceptance, schedule and whole-life price.
• Trace cyber, quality and security obligations through every delivery entity.
• Record announced reforms as prospective until their legal and contractual status is checked.