Prepare contract evidence, reporting owners and cost records before accepting a qualifying UK single-source defence contract or subcontract.
A supplier considering a UK single-source defence contract needs to understand the information obligations before choosing how to record costs and manage the work. Contract reporting is easier to support when the original commercial assumptions, approved changes and actual expenditure can be connected from the start. Reconstructing that history after the first reporting deadline can be expensive and unreliable.
SSRO's 3 September 2026 tutorial distinguishes statutory contract reports, supplier reports and DefCARS for qualifying subcontractors. Those separate tasks help organise the commercial team's preparation.
The first decision is the contract's status. The SSRO's assessment and notification FAQ, updated in July 2026, describes assessment of a proposed subcontract under the Defence Reform Act 2014 and Single Source Contract Regulations 2014. It identifies a £25 million assessed minimum among the qualifying-subcontract requirements, with value determined under the regulations.
That figure is one part of the assessment, rather than a complete rule that every subcontract above it automatically qualifies. The commercial team should obtain the relevant assessment and establish which legal entity, contract and work scope it concerns. A description such as strategic defence supplier does not determine the regulatory treatment of a specific proposed transaction.
If the proposed work changes before signature, ensure that the assessment still describes the transaction being agreed. A large preliminary package can become several different commercial arrangements, or a revised scope can introduce additional work. The person managing qualification should see the actual proposed agreement and its current value basis.
SSRO's report-submission overview distinguishes reports about qualifying contracts from supplier-level reports that apply when the relevant conditions are met. It identifies DefCARS as the system used to submit statutory reporting to MOD and the SSRO. The reporting obligation and the ability to use the system are therefore separate preparations.
For a hypothetical company providing a large support service, the project manager may know the contract's milestones and approved variations while group finance holds overhead and company-level information. One employee should not be expected to supply both sets of evidence merely because that employee has a DefCARS account.
Assign the information owners before assigning the form-filling task. The contract team can own the scope and delivery record; finance can own the relevant cost records and reconciliation; an authorised reviewer can check that the submission represents the company's approved position. The required reports and responsible reporting entity should be determined from the actual applicable guidance and contract circumstances.
The tutorial identifies pricing, planning and notification reports due within one month of entering a qualifying subcontract, plus applicable interim and final reports.
A month can pass quickly during mobilisation. The supplier may be recruiting people, opening project codes and agreeing practical customer arrangements at the same time. Preparing the required source information before signature avoids placing all of that work behind the delivery team's busiest period.
For the hypothetical support contract, the commercial manager can preserve the agreed scope, pricing assumptions, work-package allocation and approval record as one controlled starting package. Finance can check that the cost-record structure can distinguish the contract from other customer work. The reporting owner can identify any required information that remains unresolved before the start date becomes firm.
A price model and an accounting ledger answer different questions. The first explains the assumptions on which the offer was agreed; the second records what occurred. A useful reporting process preserves the connection without pretending that the two will always match.
Suppose the hypothetical service was priced using an expected staffing pattern and a subcontracted training element. During delivery, the customer approves a different timetable and the training provider changes its attendance dates. The team should be able to distinguish the original assumption, the approved contractual change and the actual invoice. Combining those events into an unexplained revised spreadsheet would make later analysis harder.
The practical design can remain simple. Use stable contract and work-package identifiers, retain the approved version of each commercial change and document material reconciliation differences. The aim is to let another authorised colleague understand why a reported figure differs from the original plan without relying on the estimator's memory.
The tutorial distinguishes contract and supplier record-retention periods and describes MOD's specified examination rights. The company should determine its exact retention obligations from the applicable provisions rather than apply a single informal rule to every file.
Operationally, an ownership map can identify where agreements, invoices, timesheets, approvals and relevant correspondence are held. The map should follow the company's actual systems. A finance ledger may hold the expenditure while a contract-management workspace holds the authorisation explaining it.
Plan for employee changes. If the bid estimator leaves, another colleague should still be able to identify the accepted assumptions and the evidence supporting them. This is particularly useful on a long service contract where reporting responsibility may transfer several times. An accessible, authorised record is more dependable than a large collection of attachments whose purpose only one person understands. The handover can identify which records are final, which contain assumptions and which require an approval before use. That distinction helps a successor prepare the next report without treating a working estimate as the company's confirmed position.
The tutorial requires notification on awareness of events or information materially affecting relevant costs, price or performance, rather than waiting for a regular report.
The commercial team therefore needs a way for delivery and finance to recognise a potentially material issue and raise it with the responsible decision-maker. The internal record should identify what changed, when it became known, which contractual obligation it affects and who is reviewing the required communication. That is different from sending every routine operational fluctuation to the customer.
For the support-service example, a proposed major change in the delivery arrangement could affect several records at once: the project forecast, subcontract commitment and customer timetable. Connect those records while the facts are current. The person deciding how to notify should have a coherent account of the change, rather than three departments' conflicting explanations.
Reporting requires people, access and review time. Estimate those resources using the actual obligations instead of treating compliance as an unlimited overhead absorbed by finance. For an initial planning exercise, the reporting owner can identify the expected contributors, the time required to reconcile the records and the person reviewing the final submission. The resulting estimate can be refined once the exact report package is confirmed, while still making the mobilisation dependency visible to management. The guide to reviewing MOD subcontract flow-downs explains how to connect a contractual requirement to an owner and a cost.
Also separate reporting from cash collection. A statutory submission and a customer invoice serve different purposes, even when they use some of the same underlying data. The public-contract supply-chain payment guide follows the invoice and remittance events that belong in the cash forecast.
A supplier ready for this work can explain the proposed contract's status, locate the information behind its price, identify the applicable reporting calendar and sustain the records during delivery. That capability gives management a concrete basis for deciding whether the contract fits the business and what preparation its commercial team still needs before accepting it.
SSRO September 2026tutorial, July 2026qualificationFAQ and reporting overview reviewed on 6 September 2026. The 2015 Act reference in the tutorial transcript is a source typo; the article uses the verified Defence Reform Act 2014. Examples are hypothetical.
Suggest a correction