Preparing for a defence tender is not about assembling procedures. It is about demonstrating that the organisation can translate future contractual requirements into controlled processes, assigned responsibilities and reliable records. Before submitting a bid, the organisation must define the scope of its commitments, assess both internal and supplier capability, and verify the evidence trail from each requirement through to product or service release. If any of these elements cannot be confirmed with confidence, the issue should be resolved before the contract is signed rather than carried into delivery.
A tender tests capability, not documentation
The decision to participate in a defence procurement procedure should be based on an assessment of the proposed undertaking, not simply on a review of existing procedures. The analysis must cover the complete delivery cycle: identification of requirements, design or delivery planning, purchasing, manufacture or service provision, inspection, release and control of nonconformities. Only this end-to-end view will identify the requirements that create the greatest cost exposure, schedule risk or dependency on subcontractors.
An ISO 9001 certificate is not, by itself, evidence of readiness—particularly where its scope does not cover the processes or locations intended for the contract. Nor is a complete set of procedures sufficient. Contract delivery capability is demonstrated by alignment between requirements, responsibilities, resources, operational records and acceptance criteria for the product or service. Bid approval should therefore involve not only sales and senior management, but also those responsible for quality, operations, purchasing and technical resources.
A common gap emerges only after the bid has been selected. The company has confirmed that it can meet the quality requirements, but during mobilisation discovers that it has no effective mechanism for flowing the relevant requirements down to subcontractors or demonstrating batch traceability. The problem is not the absence of a declaration. It is the disconnect between the commitment made and the organisation’s delivery capability: undefined purchasing inputs, missing supplier records, and no reliable link between material, inspection and release for a specific product batch.
AQAP 2110 should therefore be read alongside the procurement documentation, draft contract, technical specifications and the customer’s quality requirements. The scope of the organisation’s commitments depends on the requirements applicable to the particular product, service and supply chain. It should not be derived solely from the standard or from the current certification scope. Before submitting a bid, the organisation needs a documented requirements review and a formal decision on the scope of conformity it intends to declare. The distinction between holding documents and being able to demonstrate an effective system is explored further in AQAP 2110 – which documents and processes do defence-sector auditors most commonly examine?
Requirements review before bid submission
The pre-bid review should result in a formal decision on the conditions and boundaries under which the bid may be submitted. It should not be limited to confirming technical parameters. The foundation is a requirements register covering the invitation to tender, technical annexes, draft contract and the organisation’s proposed bid. It should include quality, documentation and acceptance requirements, together with requirements relating to traceability, configuration management, subcontractor control, access for customer representatives and the handling of nonconformities.
The register is sufficiently detailed when every commitment can be assigned to a process, an accountable person, a method of fulfilment and the evidence expected to demonstrate completion. It should also show the associated risk and decision status, ensuring that unclear or unachievable requirements are not accepted by default.
| Source | Requirement | Process and owner | Method of fulfilment | Evidence | Risk | Decision status |
|---|---|---|---|---|---|---|
| Technical annex | Material batch traceability | Purchasing and production — designated owners | Transfer identifiers into production documentation | Material certificate, goods receipt record, batch record | Loss of linkage after material splitting | Action required |
| Draft contract | Acceptance at the subcontractor’s premises | Purchasing and quality — designated owners | Include access rights and the acceptance point in the purchase order | Purchase order, inspection plan, acceptance report | Subcontractor does not consent or is unavailable | Unclear |
The bid compliance matrix must expose inconsistencies between documents rather than reduce them to a single convenient interpretation. Each item should be assigned one of the following statuses: met, action required, unclear, or unacceptable without clarification or amendment. A commercial assumption is not a substitute for a documented interpretation of a requirement. Before the bid is submitted, the organisation must clarify any matter that could affect price, schedule, responsibility, acceptance criteria or its ability to demonstrate conformity. Execution details may remain open until before delivery only where they do not alter the commitment and have an assigned owner and resolution date.
A schedule may appear achievable for in-house production but become unworkable once material qualification, acceptance at a subcontractor’s premises and the time needed to agree the quality plan are taken into account. Machine availability alone does not demonstrate delivery capacity. The required schedule should be compared with confirmed process and supplier capabilities, including dependencies and appropriate time and cost contingencies. Useful measures include the number of requirements without an owner or identified evidence, and the number of open questions submitted to the customer together with their target closure dates.
Following the assessment of process capability, resources and uncertainty, management should approve one of the following decisions:
- submit the bid on the defined terms;
- request clarification of the requirements;
- include the cost of additional controls or safeguards;
- withdraw from the procurement procedure.
The approval should record the assumptions adopted, unresolved risks and people responsible for the required actions. AQAP 2110 does not replace this management decision. It provides a structured basis for demonstrating how contractual requirements have been translated into controlled processes and records. A similar evidence-completeness principle is discussed in NIS2 and KSC documentation before an inspection: which policies, registers and evidence are actually required, although the obligations and bases for conformity are different.
Contract-critical processes
The entire quality management system does not need to be rebuilt before the contract is signed. The organisation does, however, need to design and test the processes on which fulfilment of its contractual commitments will depend. The contract process map should identify every transfer of responsibility: from sales and bidding through design, purchasing, production or service provision, inspection and storage, to the person authorised to approve product release.
For each handover, define the required inputs, acceptance criteria, process owner, record confirming completion and the response to incomplete information. The absence of an owner or defined entry and exit criteria is a process gap, even where a general procedure exists.
A critical decision is whether the organisation’s responsibility includes design. If it does, the methods for controlling design inputs, reviews, verification, validation, changes and configuration must be established before contract signature. This also applies where the technical solution is created by modifying an existing product or further developing customer documentation. Design can be excluded only where the actual allocation of responsibility justifies that exclusion—not because doing so is administratively convenient.
In parallel, the contract quality plan should define the delivery stages, acceptance criteria, inspection and acceptance points, required records, responsibilities, treatment of nonconformities and conditions for release. It may reference existing documents, but its content must be specific to the contract.
Readiness should be tested through a product-flow scenario rather than through document review alone. A requirement should be traced from the tender documentation through material purchasing, execution, inspection and storage to the record supporting release. This exercise should confirm the status of the measuring equipment required for the intended scope, control of customer-supplied material, product identification and unambiguous inspection status.
A typical gap occurs when traceability is maintained at the production workstation but lost during repacking, batch splitting or transfer to an external processor. On return, the product may be technically conforming, yet the organisation may be unable to link it reliably to the material, work order, inspection results or approved configuration.
AQAP 2110 requirements should therefore be assessed in terms of whether processes can generate reliable evidence—not by counting approved documents. A trial trace should reveal processes without defined inputs, outputs, criteria or responsibilities, as well as measuring equipment that is unavailable or not ready for use. The mechanisms that determine whether the commitment is feasible must be operational before the bid is submitted. Detailed solutions may be activated after contract signature only where implementation has been planned, ownership assigned, and neither delivery timing nor conformity is put at risk.
Suppliers must operate under equivalent control
Outsourcing part of the work does not transfer responsibility for delivery conformity to the subcontractor. During bid preparation, the organisation must establish which technical, quality, documentation and acceptance requirements need to be flowed down into purchase orders. These should cover the applicable technical documentation, acceptance criteria, required certificates and records, rules for reporting changes and nonconformities, and any inspection or acceptance points. One useful readiness measure is the number of contractual requirements not yet incorporated into purchasing conditions.
Supplier classification should reflect the supplier’s impact on conformity, configuration and contract timing—not simply purchasing value. A small company performing a special process may be critical, as may a laboratory providing a result required for product release or a manufacturer supplying a single long-lead component. Before including such a source in the bid, confirm its resources, competence, process capability and actual lead times. Capacity constraints, required acceptance points and the availability of an alternative source should also be identified.
Pre-contract evaluation cannot end with a questionnaire and declaration of conformity. It should examine traceability, change control, treatment of nonconforming product and the supplier’s ability to provide evidence required by the organisation, the customer or the relevant oversight functions. A typical case involves a supplier that declares the product will be manufactured to drawing but cannot maintain the link between incoming material, process parameters, inspection results and the batch dispatched to the customer. The product may meet dimensional requirements, but the absence of a continuous record trail prevents credible demonstration of conformity.
Before bid submission, prepare a list of critical suppliers, record the basis for their qualification and identify those requiring on-site verification. An audit is particularly appropriate where a supplier performs a process that determines product characteristics, is the sole source, or provides evidence on which acceptance will depend. The method is discussed further in Supplier audit before contract signature – reducing quality and delivery risk.
If a supplier refuses to disclose process records, an appropriate secure method of reviewing them should be agreed or other objective evidence obtained. An inability to confirm capability is a bid risk, not a gap to be addressed after contract signature. This approach to supplier control is consistent with AQAP 2110 – quality assurance system for military suppliers.
Evidence, not declarations
Contract readiness is demonstrated through objective audit evidence, not by the number of approved procedures. Each item of evidence should identify the activity performed and its result, the responsible person, the date, and the link to a specific requirement, product, batch or change. A blank form merely shows that space has been provided for a future record. A procedure shows that a method has been defined. Neither document, on its own, demonstrates that the process operates effectively.
A core readiness evidence pack should include:
- requirements review results;
- a responsibility matrix;
- the contract risk assessment;
- the delivery process map;
- inspection and release criteria;
- supplier qualification results;
- competence control records;
- documentation from the trial run.
Record storage locations, access permissions, approval rules and retention periods should be established in line with the procurement requirements, the future contract and applicable legislation. An internal measure of completeness may be the percentage of requirements for which available evidence can be identified during a specific review.
The most meaningful test is a trial contract or simulation of a representative order. The team should take a selected product or batch from the customer requirement through planning, purchasing and execution to the inspection record, release decision and archiving. A simulation does not replace records from an actual contract where the customer requires evidence generated during real delivery. Before signature, however, it can test process capability and the continuity of traceability. Useful measures include the number of breaks in the evidence trail and the time required to reconstruct the complete set of records for a specified batch or order.
If the trial cannot connect the material certificate to the batch, the inspection result to the correct revision of the documentation, or the release decision to an authorised person, management has objective information about a genuine control gap. Corrective action should eliminate the cause of the break—for example, ambiguous identification, unassigned responsibility or inappropriate record-access permissions—instead of merely completing a missing form. The readiness audit should therefore follow the evidence trail rather than focus only on whether documents are present.
This approach reflects the logic of AQAP 2110 requirements – a management system for defence-sector suppliers: requirements must be translated into controlled activities and demonstrable results. Evidence integrity is a common principle across different areas of conformity. A useful supplementary reference is NIS2 and KSC documentation before an inspection: which policies, registers and evidence are actually required, where the ability to connect a requirement, responsibility, action and record is equally important.
The decision gate before contract signature
Contract signature should be preceded by a formal contract-readiness review involving commercial, quality, technical, purchasing, production and finance functions. No single function has visibility of the complete risk profile. Quality requirements may affect technology, purchasing, schedules, costs and the ability to demonstrate conformity. The review must produce an unambiguous decision: approved, conditionally approved or not approved, together with a register of accepted risks and identification of the person authorised to accept them.
Approval requires closure of critical requirements, confirmation that resources and competence will be available during the planned delivery period, qualification of supply sources and verification of traceability mechanisms. The organisation should also agree what evidence will be generated, who will approve it, where it will be stored and how long it will be retained. Each condition should be classified as closed, conditional or open.
Conditional approval is justified only where the action has an owner, deadline, allocated resources and defined escalation route, and where failure to close it would not undermine either the declaration made during the procurement procedure or the contractual commitment. For example, the final report template may remain open if the required data set, responsibility and approval deadline have already been agreed.
A missing critical process, unavailable required competence or unverified capability of a key supplier must be treated differently. Such gaps should prevent contract signature and lead to renegotiation of quality conditions, adjustment of the schedule or provision of additional resources.
The final checklist is not intended to create more documents. Its purpose is to determine whether the organisation can accept the commitment responsibly. The contract risk review should end with one of four decisions: sign, renegotiate, strengthen capability before signature, or withdraw. Only after approval should the contract delivery plan be activated. In relation to AQAP 2110 – quality assurance system for military suppliers, the decisive criterion remains demonstrated capability to fulfil the requirements—not the completeness of procedures alone.
Masz pytania? Porozmawiajmy.
Bezpłatna konsultacja – bez zobowiązań.
