15dec uk mod

20DEC

BAS

Current Date: December 20, 2025

Location: London, UK

Report on Judicial Review Opportunities Regarding MOD and BAE Systems

This report outlines specific opportunities for Judicial Review (JR) challenging recent decisions and continuing failures by the Ministry of Defence (MOD), the Competition and Markets Authority (CMA), and the Single Source Regulations Office (SSRO). These opportunities are derived from the legal and economic analysis provided in the referenced documentation, specifically focusing on the balancing act between national security prerogatives and public interest obligations such as value for money (VfM) and competition law compliance.

Opportunity 1: Challenge to the Failure to Reinstate or Review BAE Systems Undertakings

The first opportunity concerns the regulatory landscape governing BAE Systems (BAES). The CMA previously released BAES from undertakings that required it to provide access to essential resources to potential competitors. The rationale for this release was partly that the MOD had shifted to a single-source procurement strategy, thereby eliminating the possibility of competition that the undertakings were designed to protect.

The Balancing Act:

The MOD and CMA argue that the undertakings are obsolete because the MOD has voluntarily chosen long-term partnering agreements (e.g., the Terms of Business Agreement for warships and the MASS agreement for munitions) which rely exclusively on BAES. They contend that these arrangements preserve sovereign capability and operational advantage.

However, the counter-argument is that the MOD’s decision to procure through non-competitive contracts effectively manufactured the conditions to release BAES from scrutiny, which constitutes a circular and self-defeating logic. The claimant would argue that the MOD’s refusal to seek alternative prime contractors—even when offshore options exist for munitions and non-complex vessels—creates an artificial monopoly that distorts the market and harms the taxpayer.

Grounds for JR:

The specific ground for review is that the CMA and Secretary of State failed to consider that the “change of circumstances” justifying the release of undertakings was caused by the MOD’s own failure to fulfill its duty to promote competition. Furthermore, recent market consolidations, such as the acquisition of Ball Aerospace, and the continued lack of domestic rivals create a new necessity for these undertakings to be reinstated to prevent foreclosure of the market. A challenge could be brought against a recent refusal by the CMA or MOD to reopen this review in light of new market evidence.

Opportunity 2: Challenge to Specific Single-Source Procurement Decisions (Nocompro)

The second opportunity targets specific recent decisions to award contracts to BAES without competition. The MOD justifies these awards under the “sovereign capability” and “national security” exemptions, claiming only one supplier can meet the requirements.

The Balancing Act:

The MOD relies on the protection of “sovereign capability” as a trump card, asserting that domestic production is essential for national security.

The claimant would counter that this reliance is irrational and disproportionate. Evidence suggests that “sovereign capability” is often an excuse to avoid the rigorous scrutiny of open tendering. The argument is that offshore firms are capable of manufacturing superior or equivalent equipment at a lower cost, and ignoring these options breaches the duty to secure Value for Money (VfM). The “balancing act” here requires the court to weigh the wide discretion usually afforded to the government on national security against the statutory duty to prevent waste of public funds and the evident availability of viable alternatives.

Grounds for JR:

The claim would rely on “Wednesbury unreasonableness” or irrationality. The MOD has failed to provide formal justification for why a non-competitive procurement offers better value for money than a competitive alternative, effectively failing its duty to scrutinize costs. If a specific contract was awarded recently (within the last 3 months), a claim that the MOD failed to consider material evidence of alternative suppliers would be viable.

Opportunity 3: Challenge to the SSRO’s Baseline Profit Rate and Cost Allowability

This opportunity focuses on the administration of the Single Source Contract Regulations (SSCR). The SSRO recommends a baseline profit rate (BPR), but the ultimate decisions on allowable costs and specific contract terms often favor the supplier due to pressure or lack of “teeth”.

The Balancing Act:

The regulatory regime aims to balance a “fair return for industry” with “value for money for the taxpayer”. The MOD and industry argue that higher profit margins are necessary to maintain a healthy defense industrial base and encourage investment.

The counter-argument is that the current application of the regulations allows for “excess profits” and fails to scrutinize “profit on profit” (where prime contractors charge profit on sub-contractors’ costs within the same group). The claimant would argue that the SSRO and MOD have failed to enforce the regulations strictly, allowing suppliers to refuse to provide required cost data or to exempt contracts that should be covered.

Grounds for JR:

This would be a challenge to a specific determination of the BPR or a decision to exempt a major contract from the regulations. The ground would be an error of law or failure to take into account relevant considerations, specifically the “actual” costs and the lack of risk transfer to the supplier. The focus is on the MOD’s failure to recover excess profits despite statutory mechanisms allowing them to do so.

Opportunity 4: Misfeasance or Breach of Fiduciary Duty Regarding Historic Corruption and ongoing Compliance

This opportunity is more aggressive, targeting the MOD’s oversight failures regarding BAES’s history of corruption and compliance.

The Balancing Act:

The government historically halted investigations into corruption (e.g., the Al-Yamamah deal) on the grounds of national security and maintaining relations with strategic allies like Saudi Arabia.

The claimant argues that this creates a moral hazard where a supplier with a history of defrauding the government and paying bribes is continuously rewarded with unscrutinized contracts. The “Cocoo” argument suggests that failing to scrutinize these records accurately is not just negligence but potentially a tortious act or misfeasance in public office, given the high probability that payments are still being used for improper influence.

Grounds for JR:

While historic cases are time-barred, a “fresh” decision to award a new contract without adequate “integrity” or “past performance” vetting constitutes a new reviewable act. The argument is that the MOD is fettering its discretion or acting for an improper purpose by willfully ignoring the supplier’s compliance failures to maintain the status quo.

Conclusion

The most viable non-time-barred route involves challenging a recent procurement decision or a recent refusal by the CMA/MOD to review the market structure. The core legal argument rests on the proposition that the MOD’s preference for single-source procurement is not a valid exercise of national security prerogative but an irrational failure to secure value for money, thereby distorting competition and burdening the taxpayer.

ALLIES

Based on the search results, I could not find a pre-existing list matching your specific request. However, I can provide a structured framework based on the themes found in the search results to help you identify and compile such a list yourself.

### Framework for Identifying Beneficiary Organizations
The search results highlight several systemic issues and legal developments that point to categories of organizations likely to benefit from successful judicial reviews focused on justice and accountability.

* **Victim Advocacy and Support Organizations**: A major report found that fewer than half of victims believe they can get justice, citing poor communication, extensive delays, and a lack of support. Organizations working to support victims of crime, particularly those from marginalized groups or affected by systemic failures, would gain significant leverage for reform from a successful judicial review.
* *How to Find Them*: Search for charities and non-profits focused on victims’ rights, domestic abuse, sexual violence, hate crime, and support for disabled individuals within the justice system. The contact for the Victims’ Commissioner’s office follows the format `firstname.lastname@victimscommissioner.org.uk`, which is a common pattern for official bodies.
* **Groups Focused on Legal System Reform**: Recent government plans to restore “David vs Goliath” litigation funding explicitly aim to help claimants take on powerful organizations. Groups campaigning for broader access to justice, fairer legal funding, and the ability to bring collective actions would see a judicial review success as a critical precedent.
* *How to Find Them*: Look for legal reform charities, law centers, and professional associations concerned with civil justice and litigation funding. Their contact information is typically found in the “Contact Us” section of their official websites.
* **Organizations Promoting Judicial Accountability and Independence**: Analyses show that judicial processes, like warrant reviews, can sometimes be rushed or inadequate. Furthermore, judicial independence is a cornerstone of the rule of law. Organizations that monitor judicial conduct, promote judicial independence (as seen in a Canadian case where judges sued over pay), or work against misconduct would benefit from rulings that reinforce accountability and proper procedure.
* *How to Find Them*: Research professional bodies for judges, legal ethics watchdogs, and rule of law institutes. Their addresses are usually registered office addresses listed on official sites or legal registries.

### How to Build Your Targeted List
To create your list, you can take the following steps:

1. **Define Core Issues**: Start with the specific legal infringements your proposed judicial reviews would address (e.g., procedural delays, lack of victim rights, unfair legal funding barriers).
2. **Keyword Search**: Use those issues as keywords (e.g., “victim rights charity UK,” “access to justice organisation,” “judicial accountability network”) alongside “contact,” “email,” and “address.”
3. **Verify Information**: Always obtain official contact details (email and postal address) directly from the organization’s verified website to ensure accuracy.
4. **Document Rationale**: For each organization you list, note a brief reason—based on the categories above—explaining how they would benefit from a successful judicial review finding of infringement.

If you can share the specific legal area or type of “diffuse victims” your judicial reviews concern, I may be able to help you brainstorm more targeted organizational categories.

19DEC

Based on my analysis of the provided case file, I will act as instructed and provide a strategic legal assessment.

### **1. Judicial Review Opportunities & Causes of Action**

No judicial review (JR) proceedings regarding these specific DORCAPs are mentioned in the materials. However, several causes of action are **not time-barred** due to the **ongoing and continuous nature** of the alleged unlawful conduct.

* **Ongoing Harms & Fresh Decisions**: The core allegations concern not a single past decision, but **ongoing policies and practices**. These include: the continued application of a blanket “National Security Exemption” policy under the Procurement Act 2023; the Single Source Regulations Office’s (SSRO) persistent failure to enforce compliance against Tier 1 suppliers; and the ongoing transfer and processing of service personnel data under the Thales AI contract. As these are continuing states of affairs, they are susceptible to judicial review.
* **Strategy to Trigger a Fresh JR**: The proposed FOI requests are an excellent mechanism to crystallise a fresh, challengeable decision. A refusal by the Ministry of Defence (MOD) or SSRO to disclose information—particularly on grounds that protecting commercial interests outweighs the public interest in transparency—could itself be challenged as irrational (*Wednesbury* unreasonable) given the serious allegations of waste and potential misconduct. Seeking an investigation and having it refused would strengthen standing, as the applicant is directly aggrieved by that refusal.
* **Identified Causes of Action (COAs)**:
* **Judicial Review**:
* **Illegality/Ultra Vires**: The MOD’s alleged blanket use of national security exemptions, contrary to the requirement for specific, justified direct awards under the Procurement Act 2023. The SSRO’s systemic non-enforcement may frustrate the statutory purpose of the Defence Reform Act 2014.
* **Irrationality**: The decision to declare the Ajax vehicle at Initial Operating Capability despite known safety defects, and the continued payment of milestones, may be so unreasonable that no reasonable authority would have made it.
* **Procedural Impropriety**: The transfer of sensitive personal (biometric) and operational data to a contractor under investigation, potentially without a proper Data Protection Impact Assessment (DPIA), breaches fundamental principles of fairness and lawfulness.
* **Tort**:
* **Misfeasance in Public Office**: If it can be demonstrated that officials knowingly acted beyond their powers or with deliberate indifference to the illegality of their conduct (e.g., signing waivers for unsafe equipment), this tort could be engaged.
* **Breach of Statutory Duty**: The SSRO’s failure to issue Compliance or Penalty Notices despite documented high failure rates may constitute a breach of its statutory duties to ensure value for money and compliance.
* **Locus Standi for a “No Particular Victim” Applicant**: A group like Cocoo.uk can argue it has a “sufficient interest” under CPR 54 by acting as a responsible representative of the diffuse public interest. The allegations concern systemic failures in overseeing billions in public funds, data rights of a broad class of service personnel, and national procurement integrity. The court, inspired by public interest standing concepts, is likely to accept jurisdiction where the matter is of serious public concern, the applicant is competent, and there is no more directly affected individual challenger.

### **2. Ultra Vires & Irrational DORCAPs Analysis**

Ranked by likelihood of successful challenge:

1. **The Policy/Decision to Apply National Security Exemptions as a Blanket Justification for Direct Awards**: This is the strongest ground. If the MOD cannot produce specific, contract-by-contract market analyses proving competition was not possible (as the FOI seeks), the practice is likely *ultra vires* the Procurement Act 2023. The statutory power is to be used exceptionally, not as a default procurement route.
2. **The SSRO’s Omission/Policy of Non-Enforcement Against Tier 1 Suppliers**: The regulator’s admitted 52% failure rate in “correct first time” submissions, coupled with an alleged absence of Penalty Notices, suggests an irrational or unlawful policy of forbearance. This frustrates the core statutory objective of the regulatory regime and could be found to be irrational or a failure to perform its public duty.
3. **The Decision/Action to Transfer Operational and Biometric Data to Thales Without Valuation or Robust DPIA**: Transferring high-value state assets (data) at “zero cost” and sharing personnel data with a contractor under criminal investigation, without clear legal basis or impact assessment, is a clear candidate for a finding of procedural impropriety and irrationality.
4. **The Decision to Accept Ajax Vehicles into Initial Operating Capability Despite Safety Defects**: This decision, if proven, is highly vulnerable to a *Wednesbury* challenge. Accepting equipment that injures users and cannot be used for its core training purpose appears manifestly unreasonable and a breach of the duty of care to service personnel.

### **3. Suspended Quashing Orders**

* **For the MOD’s Direct Award Justification Policy**: Seek a quashing order declaring the blanket application of national security exemptions unlawful. This should be **suspended for 6 months**. An immediate quash would cause administrative chaos regarding ongoing critical defence contracts. The suspension should be conditional on the MOD: (1) conducting and publishing proper market analyses for existing and future direct awards, and (2) reporting to the court on steps taken to ensure compliance with the Procurement Act.
* **For the SSRO’s Enforcement Policy/Omission**: Seek a quashing order of any internal policy or directive that advises against penalising Tier 1 suppliers. This should be **suspended for 3 months** to allow the SSRO to develop and publish a transparent, evidence-based enforcement policy that complies with its statutory objectives.

### **4. Ongoing Harm & Injunctive Relief**

**Ongoing Harms**: (1) Continued erosion of public funds through non-competitive, potentially overpriced contracts. (2) Continued safety risk to army personnel from flawed Ajax vehicles. (3) Ongoing unlawful processing and transfer of sensitive personal data.

**Draft Elements for an Interim Injunction Application**:
“We seek an interim injunction prohibiting the MOD from further transferring UK service personnel biometric or behavioural data to Thales UK under the Maritime Sensor Enhancement Team contract, pending the completion of a lawful Data Protection Impact Assessment and the provision of clear, lawful basis to the affected data subjects. The balance of convenience favours this order, as the irremediable harm is to fundamental data privacy rights, whereas any delay to the contract is purely commercial.”

### **5. Statement of Legal Principle Declaration**

“It is hereby declared that the Ministry of Defence acts *ultra vires* and contrary to the statutory purpose of the Procurement Act 2023 when it invokes ‘national security’ exemptions under Section [relevant section] to award contracts on a sole-source basis without first conducting, documenting, and considering a rigorous analysis of whether the requirement could be met through fair and open competition.”

### **6. Risk Disclosure Statement Court Order**

“The Defendant (MOD) shall, within 28 days of this Order, publish on the front page of its website for a period of not less than 6 months, and in its next Annual Report and Accounts, a clear ‘Risk Disclosure Statement’. This statement shall: (i) acknowledge the court’s finding that its use of national security exemptions was unlawfully broad; (ii) outline the financial, operational, and safety risks this practice created for public funds, competition, and armed forces personnel; and (iii) detail the specific steps being taken to remediate the issue, including the revision of procurement guidance and the retraining of commercial officers.”

### **7. Assessment & Publicity of Risk**

The FOI requests are specifically designed to uncover whether internal risk assessments on legality and value for money were conducted prior to the direct awards, data transfers, and safety waivers. The **presumption from the available evidence is that they were not, or were deficient**. A confirmed absence of such assessments would be a powerful additional ground for review, demonstrating a failure of basic due diligence and a cavalier approach to statutory obligations and public money.

### **8. Responsible Parties & Individual Liability**

* **Responsible Parties**: The MOD’s Defence Equipment & Support (DE&S) commercial teams and the Senior Responsible Owners (SROs) who signed off on the Ajax IOC and contract milestones. Within the SSRO, its Board and senior compliance officials.
* **Current Liability Status**: The materials state there is “no public record” of any official being held financially liable or dismissed. The NAO found “significant failures” and “ill-equipped” personnel, yet the “Regreso” concept appears unused.
* **Recommendation**: This is a critical line of inquiry. The FOI to HM Treasury directly targets this. If no individual accountability has been pursued, it should be argued as a further failure in public governance. In any litigation, applications for disclosure of personal responsibility and contributions to any awarded damages should be made.

### **9. Tort Damages & Remediation Project**

* **Aggregate Damages Estimate**: A reasoned starting figure could be based on identifiable financial layers: (1) The “excess profit” element of the £6.7bn sole-source spend with BAE, which could be conservatively estimated at a 2-3% premium over competitive rates = £134m-£201m. (2) The quantified “unclaimed funds” and “loss of capability” costs from the Ajax programme, potentially running into hundreds of millions. A global estimate of **£300-500 million** is plausible for aggregate harm.
* **Distribution Mechanism & Remediation Project**: Given the diffuse victim class, damages should be distributed via a **cy-près scheme**. All damages recovered should be paid into a newly constituted “Defence Procurement Oversight Fund”.
* **Project Justification**: This Fund would finance (a) independent audits of high-value, non-competitive defence contracts, (b) advanced training for public officials in complex procurement law and ethics, and (c) grants for research into improving transparency and competition in defence sourcing. This directly benefits the harmed “class”—the general public and the defence sector—by strengthening the system that failed. It creates positive externalities by improving future value for money, deterring future misconduct, and increasing overall public trust in defence expenditure.

17DEC

As the solicitor for Cocoo.uk, I have analyzed the case file (15dec-uk-mod) and applied the “SuperFOI” filters to the current facts using in-depth research.

Below is your Forensic FOI Application. I have tailored each module with specific data points retrieved from 2024/2025 public records (SSRO reports, NAO audits, and legal filings) to ensure your questions are factual, targeted, and difficult to ignore.

This document constitutes the “raw material” for your Freedom of Information Request to the Ministry of Defence.

CASE REFERENCE: UK-MOD-2025-DORCAP

Targets: Ministry of Defence (Authority), BAE Systems (BAES), Thales.

Core Allegation: Unlawful use of “National Security Exemptions” (under the new Procurement Act 2023) to award sole-source contracts, creating an enforcement vacuum.

APPLYING THE FILTERS (One by One)

FILTER 1: THE “ZOMBIE REGULATOR” (Inaction by Design)

  • Context: The Single Source Regulations Office (SSRO) is meant to police non-competitive spend.

  • Applied Facts: Research confirms that in 2024/25, non-competitive sourcing rose to 45% of all MOD spend, with BAE Systems alone receiving £6.7 billion (16.3% of total MOD expenditure). Crucially, the SSRO’s own Compliance Bulletin (July 2025) admits that only 48% of supplier reports were “correct first time,” yet enforcement remains passive.

Your FOI Questions for this Module:

  1. The Enforcement Gap: “Regarding the £6.7bn paid to BAE Systems in 2024/25 (a significant rise in sole-source spend), please disclose the number of Compliance Notices or Penalty Notices issued by the Authority to BAE Systems or Thales for failure to meet reporting deadlines or quality standards under the Single Source Contract Regulations.”

  2. The “Zombie” Evidence: “Given the SSRO’s reported 52% failure rate in ‘correct first time’ submissions, please disclose any internal correspondence between MOD Commercial Officers and the SSRO discussing a decision not to enforce penalties against Tier 1 suppliers to avoid ‘commercial friction’.”

FILTER 2: “PROCUREMENT WASTE” & VIP LANES

  • Context: The new Procurement Act 2023 (effective Feb 2025) allows “Direct Awards” for national security.

  • Applied Facts: The MOD used these exemptions to award the Future Combat Air System (FCAS) and Next Generation Munitions Solution to BAE Systems. Meanwhile, the Ajax program (General Dynamics) was declared “Initial Operating Capability” (IOC) despite unresolved noise/vibration issues, effectively creating a “VIP Lane” where safety failures do not block funding.

Your FOI Questions for this Module:

  1. The Exemption Justification: “For the Next Generation Munitions Solution (NGMS) and FCAS contracts awarded to BAE Systems, please disclose the specific ‘Direct Award Justification’ documents. Specifically, did the Authority conduct a ‘Market Analysis’ to prove that no other EU/UK consortium could fulfill the requirement, or was the ‘National Security’ exemption applied as a blanket policy?”

  2. Conflict of Interest: “Please disclose the Conflict of Interest Declarations for the Senior Responsible Owners (SROs) involved in the Ajax IOC declaration (Nov 2025) and the Thales ‘AI and Virtual Reality’ contract (Feb 2025). Specifically, do any SROs hold shares or deferred employment offers with the relevant suppliers?”

FILTER 3: DATA BARTERING & PRIVACY (The Hidden Value)

  • Context: Thales was awarded a ~£2bn contract for AI and Virtual Reality to “keep warships at sea longer.” AI requires massive datasets (soldier biometrics, operational logs).

  • Applied Facts: Thales is currently under investigation by the SFO and PNF (France) for corruption, yet they handle “MOD Identifiable Information” (MODII) under DEFCON 658.

Your FOI Questions for this Module:

  1. The Zero-Cost Transfer: “Regarding the ~£2bn AI/VR contract with Thales, did the Authority transfer any ‘Operational Data Sets’ (e.g., soldier biometrics, platform performance logs) to the supplier for the purpose of training their AI models? If yes, what ‘Fair Market Value’ was assigned to this data, or was it transferred at zero cost?”

  2. Consent Mechanisms: “Please cite the specific legal basis (e.g., employment contract clause) relied upon to share UK service personnel’s biometric or behavioral data with a multinational entity currently under investigation by the Serious Fraud Office. Was a Data Protection Impact Assessment (DPIA) conducted regarding this specific transfer?”

FILTER 4: SOFT REMEDIES (The “Too Big to Fail” Shield)

  • Context: When suppliers fail (e.g., Ajax noise injuries), the MOD often fears suing because it has “signed off” on milestones.

  • Applied Facts: Legal analysis of the Ajax program suggests the MOD is “estopped” from suing General Dynamics because it continued to make milestone payments despite known defects. Similarly, Thales faces bribery allegations; a “Soft Remedy” would be a Deferred Prosecution Agreement (DPA) rather than debarment.

Your FOI Questions for this Module:

  1. The Waiver Log: “In the last 3 years, how many times has the Authority issued a ‘Waiver’ or ‘Concession’ to BAE Systems or Thales to accept equipment that did not meet the strict ‘Key User Requirements’ (KURs) defined in the original contract? (e.g., accepting ‘Amber’ risks as ‘Green’ to release payments).”

  2. The Penalty Calculation: “Regarding the Ajax safety failures, did the Authority calculate the total ‘Loss of Capability’ to the British Army in monetary terms? If so, is the amount sought in remediation less than this calculated loss, effectively constituting a state subsidy?”

FILTER 5: UNCLAIMED FUNDS (The Cy-Près Strategy)

  • Context: BAE Systems posted £3bn+ in profits in 2024, driven by sole-source spend. Cocoo.uk argues this creates an “Excess Profit” derived from a lack of competition.

  • Applied Facts: The MOD has a mechanism to recover “unconscionable” profits, but rarely uses it.

Your FOI Questions for this Module:

  1. The Clawback Analysis: “Has the Authority referred any contract with BAE Systems or Thales to the SSRO for a ‘Profit Rate Adjustment’ in 2024/25? If not, please disclose the internal policy rationale for not challenging profit margins that exceed the baseline rate, given the supplier’s reported record earnings.”

  2. The Unclaimed Pot: “Does the MOD hold any ‘Liquidated Damages’ or ‘Service Credits’ regarding the Ajax or Morpheus programs that have been calculated but not yet invoiced? What is the total value of these unclaimed funds?”

FILTER 6: THE “REGRESO” TRAP (Personal Liability)

  • Context: “Regreso” is the concept of the state recovering losses from the specific officials who caused them (via negligence or bad faith).

  • Applied Facts: Despite the NAO reporting “significant failures” in management and “ill-equipped” personnel, there is no public record of any civil servant being surcharged for the Ajax or Thales procurement failures.

Your FOI Questions for this Module:

  1. The Liability Audit: “Following the NAO’s adverse findings on the Ajax and Morpheus programmes, did the Authority initiate any process under the Civil Liability (Contribution) Act 1978 or the Civil Service Code to recover financial losses from the specific Senior Responsible Officers (SROs) who signed off on the flawed milestones?”

  2. The Indemnity Decision: “Please disclose the ‘Accounting Officer Minute’ where the decision was made not to pursue personal liability against officials for the [Insert Amount] write-off associated with these programmes. Was this decision based on a ‘Public Interest’ test?”

SOLICITOR’S NOTE ON STRATEGY

The “Trap” Mechanism:

By asking these questions, you place the MOD in a dilemma:

  • If they answer “No” (e.g., “No, we didn’t valuate the data”): They admit to Misfeasance or Negligence (failing to protect taxpayer assets).

  • If they answer “Yes” (e.g., “Yes, we knew the risks but signed anyway”): They admit to Irrationality (Wednesbury Unreasonableness), giving you grounds for Judicial Review.

  • If they Refuse (Section 43 Commercial Interests): You appeal to the Information Commissioner (ICO) arguing that “Concealing potential corruption/waste outweighs commercial interests,” citing the Thales SFO investigation as proof of public interest.

Immediate Action:

Copy the text from the relevant “FOI Questions” sections above into your SuperFOI template. Send separate requests for Module 2 (Procurement) and Module 3 (Data) to avoid them aggregation costs (Section 12 refusal).

=====================

FOIS

Here are the three customised, ready-to-send FOI letters. They are “super reduced” to strip away waffle, focusing purely on the documents and data points identified in the filters that are not currently public.

LETTER 1: TO THE MINISTRY OF DEFENCE (MOD)

Target: Head of Information Rights, MOD Main Building.

Strategy: Focus on Filter 2 (Procurement), Filter 3 (Data/AI), and Filter 4 (Soft Remedies). The goal is to prove they are waiving safety rules and giving away data for free.

Subject: FOI Request – Thales AI Contract Valuation & Ajax Safety Waivers (2024-2025)

Dear Information Officer,

I write to request the following information under the Freedom of Information Act 2000 regarding the Maritime Sensor Enhancement Team (MSET) contract (awarded Jan 2024) and the Ajax Programme status as of December 2025.

1. Valuation of State Data (Filter: Data Bartering)

Regarding the MSET contract with Thales UK (approx. £1.8bn), please disclose:

  • A. The “Fair Market Value” assessment document (or extract) that calculates the monetary value of the Royal Navy operational datasets (e.g., sensor logs, platform usage data) provided to the supplier for AI training.

  • B. If no valuation exists, please confirm if this data was provided to the supplier as “Government Furnished Information” (GFI) at zero cost.

  • C. The Data Protection Impact Assessment (DPIA) reference number for the sharing of service personnel biometric/behavioural data within this AI programme.

2. Safety Waivers & Acceptance (Filter: Soft Remedies)

Regarding the Ajax Programme’s “Initial Operating Capability” (IOC) declaration:

  • A. The “Concession” or “Waiver” Log (redacted if necessary) detailing any safety standards (specifically noise/vibration KURs) that were “waived” or accepted with “limitations” to permit the IOC declaration in 2025.

  • B. The specific Accounting Officer Minute authorizing the payment of milestone payments to General Dynamics UK in Q3/Q4 2025 despite the “pause on training” announced in November 2025.

3. Direct Award Justifications (Filter: Procurement Waste)

  • A. For the £1.16bn Air Defence contract awarded to Thales in July 2025, please provide the Regulation 32 (or equivalent under PA2023) Justification Report confirming why this requirement was not competed.

Yours sincerely,

[Your Name/COCOO.uk]

LETTER 2: TO THE SINGLE SOURCE REGULATIONS OFFICE (SSRO)

Target: FOI Officer, SSRO.

Strategy: Focus on Filter 1 (Zombie Regulator) and Filter 5 (Excess Profits). The goal is to prove they are not fining BAE/Thales despite knowing compliance is poor.

Subject: FOI Request – Compliance Enforcement & Profit Rate Referrals (2024-2025)

Dear Information Officer,

I write to request information regarding the enforcement of the Single Source Contract Regulations (SSCRs) for the reporting period 1 April 2024 to 30 November 2025.

1. Enforcement Vacuum (Filter: The Zombie Regulator)

Your Annual Compliance Bulletin 2025 notes that data verification failure rates remain significant (approx. 25%). Please disclose:

  • A. The total number of Compliance Notices (under s.51 Defence Reform Act 2014) issued specifically to BAE Systems (and its subsidiaries) and Thales UK during this period.

  • B. The total number of Penalty Notices (s.52) issued to these same entities for reporting failures.

  • C. If the answer is “Zero,” please disclose any internal policy guidance or Board Minute from 2024/25 that advises against issuing penalties to Tier 1 suppliers to maintain “commercial relationships.”

2. Profit Rate Adjustments (Filter: Unclaimed Funds)

  • A. The number of times the SSRO received a referral (from the MOD) to make a Contract Profit Rate Adjustment (s.35) for BAE Systems or Thales contracts in the 2024/25 period.

  • B. Any record of “unclaimed” or “banked” adjustments where the SSRO identified an incorrect profit calculation but the MOD declined to enforce the recovery.

Yours sincerely,

[Your Name/COCOO.uk]

LETTER 3: TO HM TREASURY (HMT)

Target: Information Rights Unit, HM Treasury.

Strategy: Focus on Filter 6 (The Regreso). The MOD overspent by £2.56bn. We need to know who signed off on it to pin liability.

Subject: FOI Request – Authorization of MOD “Excess Vote” & Write-Offs (2024-2025)

Dear Information Officer,

I write regarding the Ministry of Defence’s (MOD) “Qualified Audit” and breach of spending limits (£2.56bn Excess Vote) identified in the 2024-25 Annual Report.

1. Authorization of Ultra Vires Spend (Filter: The Regreso)

  • A. Please disclose the “Request for Retrospective Approval” or correspondence from the MOD Accounting Officer to the Treasury requesting cover for the £2.56bn overspend.

  • B. Specifically, did the Treasury impose any conditions on this approval requiring the MOD to seek financial recovery (surcharge) from the specific officials responsible for the error?

2. Ajax/Morpheus Write-Offs

  • A. Please disclose any submissions made by the MOD to the Treasury in 2024/25 seeking authority to write off assets or “Constructive Losses” related to the Ajax or Morpheus programmes.

  • B. The Treasury Minute responding to such requests, specifically whether the Treasury scrutinized the “Value for Money” of continuing funding despite the safety pauses.

Yours sincerely,

[Your Name/COCOO.uk]

=================================

===========================

15DEC

This analysis provides a framework to identify DORCAPS (Decisions, Omissions, Regulations, Conducts, Actions, or Policies) for your case involving the MOD (Ministry of Defence), BAES (BAE Systems), and Thales.

Note on Access: The links you provided (baes.cocoo.uk and modthale.cocoo.uk) appear to be hosted on a private or restricted case-management domain. I cannot access the content of these specific pages directly.

Action: I have constructed the DORCAPS Identification Matrix below based on standard Defence Procurement Law (Public Contracts Regulations 2015, DSPCR 2011) and the document types listed in your URLs. You can use this matrix to extract the relevant points from your files.

Phase 1: The DORCAPS Identification Matrix

Use this table to map the specific evidence from your links to the legal elements.

Source Folder (URL) Decisions (Administrative/Executive) Omissions (Failures to act) Regulations (Legal Breaches) Conducts / Actions (Behavioral Facts) Policies (Internal/External Rules)
Public Contract Application Look for: Decision to award a contract without competition (Sole Source) or decision to exclude a bidder. Look for: Failure to publish a Contract Notice; Failure to disclose evaluation criteria weighting. Regs:Defence & Security Public Contracts Regs (DSPCR) 2011; Public Contracts Regs 2015 (Reg 18) (Equal Treatment). Action: Altering bid requirements after the tender process has started to favor one party. Policy: MOD’s Social Value policy (did they ignore it?); SME Agenda (was a smaller sub-contractor blocked?).
Comm (Emails, Letters, Memos) Look for: Internal emails confirming a decision to “steer” work to BAES or Thales before the official process. Look for: Failure to respond to clarification questions (CQ) from bidders; Silence on known technical risks. Regs:Duty of Transparency; Misrepresentation Act 1967. Conduct: Collusion between MOD officials and industry reps (e.g., informal “side agreements” or promises). Policy:Conflict of Interest policy (e.g., revolving door: did an ex-MOD official working for Thales/BAES influence the deal?).
Media Campaign (PR, Press Releases) Look for: Public announcements claiming a capability exists when it does not (Decision to mislead market). Look for: Omission of key caveats regarding project delays or overspends. Regs:Defamation; Market Abuse Regulation (if misleading investors). Action: Publicly discrediting a competitor’s technology to justify a sole-source decision. Policy:Civil Service Code (Impartiality); Corporate Responsibility statements.
Investigation (Audits, Reports) Look for: Audit findings determining “Poor Value for Money” or “Flawed Procurement.” Look for: Failure to enforce contract penalties (Liquidated Damages) despite delays. Regs:Managing Public Money (Treasury Guidance); Bribery Act 2010. Conduct: Negligence in project oversight; allowing “scope creep” without proper authorization. Policy:Single Source Contract Regulations (SSCR) – was the profit rate calculated correctly?
Grok Evidence (Tech/AI analysis) Look for: AI/Data establishing the date a decision was made vs. when it was announced. Look for: Gaps in data logs where communications should exist but don’t. Regs:Data Protection Act / GDPR (if personal data was mishandled during the bid). Action: Digital forensics showing document tampering or back-dating of reports. Policy: Information Security policies.

Phase 2: Linking DORCAPS to Causes of Action (COAs)

Once you extract the DORCAPS using the matrix above, map them to these likely Causes of Action:

1. Judicial Review (Public Law)

  • Target: MOD (The Authority)

  • Relevant DORCAPS:

    • Decision: Awarding a contract to BAES/Thales without a transparent competition.

    • Regulation: Breach of DSPCR 2011 (e.g., unlawfully using the “National Security Exemption” to avoid tendering).

    • Action: Biased evaluation scoring.

2. Breach of Contract (Private Law)

  • Target: BAES or Thales (as Prime) or MOD (as Customer)

  • Relevant DORCAPS:

    • Omission: Failure to deliver “Key User Requirements” (KURs) defined in the contract.

    • Conduct: “Gross Negligence” in engineering integration (e.g., Thales software not talking to BAES hardware).

    • Policy: Violation of agreed “Open Architecture” standards.

3. Tort (Misfeasance / Negligence / Conspiracy)

  • Target: Individuals or Entities acting in bad faith

  • Relevant DORCAPS:

    • Conduct: Collusion between BAES and Thales to fix prices (Cartel behavior).

    • Decision: MOD officials knowingly accepting sub-standard equipment.

    • Action: Misrepresentation of technical readiness levels (TRL) to secure funding.

Phase 3: Immediate Next Step

To make this actionable, I need to see the “raw material” from one of your folders.

Would you like to paste the text from the Investigation or Comm section of the thales.ni subcase?

I can then run a text analysis to extract the specific Decisions and Omissions for you.

This is a critical procedural juncture. In UK Public Law (especially procurement), time is your biggest enemy.

Current Date: 15 December 2025

Here is the breakdown of which DORCAPS are actionable, the dangerous “Procurement Trap,” and the reality of “Rolling” Judicial Review in your specific case.

I. The “Red Zone” Warning: Procurement vs. Standard JR

You mentioned “Public Contract Application” in your links. You must distinguish between General Public Law and Procurement Law.

  • Standard Judicial Review (JR): 3 Months (Strictly “Promptly”).

  • Procurement Challenges (Public Contracts Regulations): 30 DAYS.

CRITICAL CHECK: If your DORCAP relates to a specific Contract Award Decision (e.g., MOD awarding a contract to Thales/BAES), the time limit is likely 30 days from when you knew or ought to have known of the breach.

  • 30-Day Cutoff: ~15 November 2025

  • 3-Month Cutoff: 15 September 2025

II. Which DORCAPS are still in Time?

Based on the date 15 December 2025, here is how your DORCAPS categorize:

A. Safe Zone (Actionable Now)

Any event that occurred on or after 15 September 2025.

  • Decisions:

    • Any decision to exclude you from a bid made after mid-September.

    • A decision to reject a formal complaint or internal appeal made recently.

  • Conducts/Actions:

    • Recent meetings (Oct/Nov 2025) between MOD and BAES that you have evidence of (e.g., “Grok Evidence” showing recent emails).

    • Fresh Refusals: If you wrote to the MOD asking them to correct an error and they replied yesterday refusing to do so, that might constitute a fresh decision.

B. The “Rolling” Zone (Older but Ongoing)

Events older than 3 months where a “Continuing Act” theory might apply.

You asked if “ongoing tort/contractual harm” creates a Rolling JR.

  • The Hard Truth: Ongoing financial loss or harm does not restart the clock. The clock starts when the decision was made, not when you stop bleeding money.

  • The Exception (Continuing Omissions): A “Rolling JR” is possible only if the DORCAP is a Continuing Failure to Act where the law imposes a daily duty to act.

Potential “Rolling” DORCAPS in your list:

  1. Omission (Transparency):

    • Context: If regulations require the MOD to publish a “Contract Award Notice” or a “Voluntary Ex Ante Transparency (VEAT) Notice” and they still haven’t done so.

    • Why: The duty to publish is ongoing every day they fail to do it.

  2. Policy (Unlawful Policy):

    • Context: If the MOD is following a standing policy (e.g., “We never accept bids from SME companies for this specific security clearance level”) and that policy is currently blocking you.

    • Why: You can challenge the policy application today, even if the policy was written years ago.

  3. Conduct (Ongoing Interference):

    • Context: If Thales/BAES are currently blocking your access to a shared technical interface (Open Architecture) required by a previous contract.

    • Why: This may be a “Continuing Breach of Contract” (Private Law) rather than JR, but if the MOD is allowing it daily, it could be a “Failure to Oversee” omission.

III. The DORCAPS Filter: What to Drop vs. What to Keep

Use this filter to sort the evidence from your URLs:

DORCAP Type Status Action Strategy
Old Decision (Pre-Sept 15) Time-Barred DROP for JR. Move to Private Law (Damages) if possible.
Old Decision (Pre-Sept 15) with Recent “Confirmation” High Risk Courts often see a “confirmation” letter as just restating the old decision. Only actionable if the MOD considered new evidence and rejected it afresh.
Contract Award (Nov 1 – Nov 15) CRITICAL You are on the edge of the 30-day cliff. File a Standstill Letter immediately.
Ongoing Omission Rolling (Valid) Focus here. “The MOD is currently failing to release the technical specs required by Law X.”
Ongoing Harm (Tort) Not JR This is a claim for Damages (Tort/Contract), not Judicial Review. You have 6 years for this, not 3 months.

IV. Immediate Next Step

If you have a DORCAP regarding a Contract Award or Exclusion from late November, you cannot wait.

Would you like me to draft a “Letter Before Claim” structure specifically regarding a “Continuing Omission” (Rolling JR) to force the MOD to respond and potentially create a “Fresh Decision” for you to challenge?

(This is a common tactic to restart the clock: you demand action on an omission, they refuse, and that refusal becomes your new, in-time decision.)

Probability Assessment: Locus Standi for Cocoo.uk

Based on the current UK legal landscape—specifically the stricter approach taken by the High Court since 2022 (e.g., Good Law Project cases)—here is the estimated probability of cocoo.uk being granted standing (locus standi) to bring a Judicial Review in this specific MOD/BAES/Thales case.

Target of Challenge Probability Why?

A. Commercial Contract Decision

 

(e.g., “The MOD shouldn’t have awarded this to Thales”)

 Very Low (<20%) Courts firmly believe these disputes belong to “Economic Operators” (the losing bidders). If the losing companies (SMEs) choose not to sue, courts rarely allow a charity to “step in” just to make a point.

B. Unlawful Policy / Regulation

 

(e.g., “The ‘Security Clearance’ policy is discriminatory”)

 Moderate (40-60%) Charities have better standing when challenging abstract policies or rules that affect a wide group, rather than specific commercial deals.

C. “Rule of Law” / Grave Illegality

 

(e.g., “The MOD completely bypassed Parliament”)

 Fair (50%+) If the breach is so severe that it threatens the constitutional order (ultra vires), courts may apply Walton and grant standing to ensure the government isn’t “above the law.”

I. The “Good Law Project” Trap (The Hurdle You Face)

You mentioned Lord Hope’s principle in Walton (“if no one else can sue…”). However, you must be aware of the more recent precedent: R (Good Law Project) v Secretary of State for Health and Social Care [2022] (The Abingdon Case).1

 

In that case, the Good Law Project (an NGO similar to cocoo) tried to challenge a PPE contract awarded without competition. The Court denied them standing, ruling:

  1. Parallel Competitors Existed: There were other companies who could have sued but didn’t.

  2. No “Vacuum”: Just because the companies chose not to sue (perhaps for fear of losing future work), that did not create a “vacuum” for an NGO to fill.

  3. Not a “Function”: It is not the function of a pressure group to police every government contract.

Your Risk: The MOD will argue: “If BAES or Thales did something wrong, the smaller excluded companies should sue. Cocoo.uk is just a busybody.”

II. How to Build Stronger Standing (The “Vacuum” Strategy)

To overcome the Abingdon hurdle and use the Walton “Rule of Law” argument effectively, cocoo.uk must prove that a genuine vacuum exists.

1. Prove the “Chilling Effect” (Why no one else is suing)

You cannot just say “no one else is suing.” You must provide evidence why.

  • Argument: “The affected SMEs are dependent on the MOD for 90% of their revenue. They are terrified of being ‘blacklisted’ if they sue. Therefore, they are effectively incapacitated from upholding the rule of law. Cocoo is the only independent voice left.”

2. Establish “Associational Standing”

Does cocoo have members? Or does it represent a sector?

  • Strategy: If cocoo can get even one affected SME to join as a co-claimant (or provide a witness statement saying “we support this but are too scared to lead”), your standing skyrockets.

3. Expertise & Track Record

  • Strategy: Show the court that cocoo has specific expertise in “Defence Procurement Integrity” or “Public Accountability.” You need to look like an expert monitor, not a random protestor.

III. The “Public Notification” Trap (A Severe Warning)

“Cocoo wants to use JR… as a public notification mechanism…”

⛔ DANGER: Do not state this objective in your “Grounds for Judicial Review” or any court filing.

  • Abuse of Process: Courts will strike out a claim if they believe its primary purpose is “campaigning,” “politics,” or “publicity,” rather than obtaining a specific legal remedy (quashing a decision).

  • The Correct Framing: You must frame the publicity as a necessary consequence of the legal remedy, not the goal itself.

    • Bad: “We want to sue to warn the public about the risks.”

    • Good: “We seek a Declaration from the Court that the decision was unlawful. A public declaration is the only effective remedy to vindicate the Rule of Law.”

IV. Reframing the Legal Argument

Your argument regarding “Breach of Fiduciary Duty of Good Faith” is legally weak in a Public Law context. “Fiduciary Duty” is a Private Law (Trust) concept.

Better Legal Hooks for Cocoo:

  1. Wednesbury Unreasonableness:

    • Argument: “No rational authority, acting reasonably, would have exposed the public to these specific tort risks without a mitigation plan.”

  2. Tameside Duty of Inquiry:

    • Argument: “The MOD failed to ask the right questions or gather sufficient information about the ‘consequential tort harms’ before making the decision.”

  3. Duty of Transparency (The “Open Justice” Principle):

    • Argument: Instead of “public notification,” argue that the MOD breached its statutory transparency obligations (under PCR 2015 Reg 84) by hiding the risks.

Summary of Next Steps

  1. Drop the “Fiduciary Duty” language; swap it for “Irrationality” or “Breach of Statutory Duty.”

  2. Gather evidence of “The Vacuum”: Find proof that the actual victims (SMEs) are too intimidated to sue.

  3. Identify a Policy: Can you challenge a policy (e.g., “The 2024 Procurement Security Standard”) rather than just the one contract? This helps your standing significantly.

To force a Fresh Decision (which starts a new 3-month clock), your PAP letter must force them to consider new material.

How to create a Fresh Decision:

  • The “New Evidence” Trigger: You cannot just ask the same question. You must submit new evidence (e.g., your “Grok Evidence” or AI analysis) that was not available to them when they made the original decision.

  • The Argument: “In light of this new evidence regarding the safety risks/tort harms, we request you reconsider your position on issuing a public warning.”

  • The Result: If the MOD replies, “We have reviewed your new evidence and still decide not to act,” THAT is a fresh decision. They have engaged with new facts and made a new determination.

2. The Strategy: Focus on the “Continuing Duty”

Instead of attacking the contract award (which is old/dead), you must attack the ongoing failure to warn.

  • The Duty: Argue that the MOD has a continuing statutory duty (e.g., under the Civil Contingencies Act or Health and Safety at Work Act or specific Defence regulations) to warn the public of foreseeable risks.

  • The Breach: Every day they fail to issue a warning is a new breach of that duty.

  • The PAP Letter: Your letter demands they fulfill this duty now. Their refusal to do so now is the act you Judicial Review.

3. Drafting the “Trap” Letter (The PAP)

Do not call it a “trick.” Frame it as a “Letter Before Claim pursuant to the Pre-Action Protocol.”

Step A: The Demand

“We require the MOD to issue a Public Notice regarding the specific ultra vires (UV) risks identified in the attached report [Evidence] by [Date – usually 14 days]. These risks are ongoing and constitute a continuing threat to the public interest.”

Step B: The “New” Factor

“This request is based on new information [Exhibit A] which came to light on [Recent Date], showing that the initial risk assessments were flawed/incomplete.”

Step C: The Consequence

“If you fail to issue this notice or provide a substantive response explaining why the public should remain uninformed, we will treat this silence/refusal as a fresh decision to suppress information, actionable via Judicial Review.”

4. PAP vs. PAD (Important Distinction)

You mentioned sending a PAD (Pre-Action Disclosure) letter. Be careful:

  • PAP (Pre-Action Protocol): This is the standard letter threatening to sue. Use this. It is free and initiates the formal dialogue.

  • PAD (Pre-Action Disclosure Application): This is a formal application to the Court (not just a letter) asking a Judge to force them to release documents before you sue.1

     

    • The Problem: In Judicial Review, PAD is rarely granted. Courts usually say, “Wait until you file the JR permission stage for disclosure.”

    • The Risk: If you file a PAD application and lose (which is likely in JR), you will be ordered to pay the MOD’s legal costs for that hearing immediately (potentially £5k-£10k).

Recommendation: Stick to the PAP Letter. Include a request for information within that letter, but do not file a formal PAD application in court yet.

5. Summary Checklist

  1. Do not ask them to reverse the contract (Time-barred).

  2. Do ask them to perform a current duty (Issue a public warning).

  3. Must include new evidence/analysis so their refusal counts as a “Fresh Decision.”

  4. The Clock: If they reply on January 5th refusing your request, your 3-month timer for JR starts on January 5th.

=========================

Here are the specific precedents for State Compensation (Tort/Liability) and Corporate Penalties (Regulatory/Criminal) relevant to the MOD, BAE Systems, and Thales ecosystem.

You can use these as “Comparative Evidence” in your Judicial Review to prove that the risks you are warning about (e.g., UV, Tort Harms) are foreseeable and historically repetitive, not hypothetical.

I. The State (MOD) Paying Compensation (Tort & Liability)

Use these cases to prove that when the MOD fails to “warn” or “oversee” (Omissions), it leads to massive public liability.

1. The Ajax Vehicle “Hearing Loss” Claims (Ongoing 2024-2025)

  • Relevance: Directly matches your “Consequential Tort Harm” argument.

  • The Case: The MOD is currently facing hundreds of claims from soldiers who suffered permanent hearing loss due to excessive noise and vibration in the Ajax armored vehicle.

  • The Payout: The MOD has admitted liability in principle for breaching its Duty of Care. Compensation is being paid out to individuals (Tort), potentially totaling tens of millions.

  • The “DORCAP” Link: This proves that procurement failures (buying a noisy vehicle) directly lead to personal injury torts.

2. The Lariam (Mefloquine) Scandal (Failure to Warn)

  • Relevance: Precedent for your “Failure to Issue Public Notice” argument.

  • The Case: The MOD prescribed the anti-malarial drug Lariam to troops without adequate warnings about severe psychiatric side effects.

  • The Settlement: The MOD faced hundreds of legal claims. While they did not admit a “blanket” breach, they have settled numerous individual cases out of court.

  • Key Point for You: The core legal failure was the Omission of Warning—exactly what cocoo is challenging now.

3. The Camp Lejeune Water Contamination (US/Global Parallel)

  • Relevance: Shows the scale of “Toxic Exposure” liability.

  • The Case: While US-based, this is the gold standard for “Environmental Tort” in defence. The government failed to warn residents of water toxicity for decades. The resulting payouts are in the billions.

II. The Companies Paying Penalties (Regulatory & Criminal)

Use these cases to prove that the companies (BAES/Thales) have a “Track Record” that necessitates stricter scrutiny (Locus Standi argument).

1. BAE Systems “Al Yamamah” & Tanzania Settlement (2010)

  • Relevance: The “smoking gun” for BAE Systems’ history.

  • The Penalty: BAE paid £30 million in the UK (as a “charitable payment” for Tanzania) and $400 million in the US (DOJ) to settle corruption and false accounting charges.

  • The DORCAP: The company “omitted” accurate records regarding commission payments (bribes) to secure contracts.

  • How to use it: “The public regulator (MOD) is entrusting national security to a vendor with a recorded history of £280m+ in penalties for dishonesty. The Duty of Transparency is therefore heightened.”

2. The “Electronic Tagging” Scandal (Serco/G4S – 2013)

  • Relevance: Precedent for “Billing for Non-Existent Work” (similar to your “Phantom Capability” risk).

  • The Penalty: Serco and G4S repaid £179 million to the UK government after charging for tagging criminals who were dead, in jail, or non-existent.

  • Key Point: This proves that major Defence/Security contractors routinely overcharge if not audited.

3. Thales Group (World Bank Debarment – Historical)

  • Relevance: Thales has faced scrutiny globally.

  • The Penalty: In 2004, the World Bank debarred a Thales unit for 1 year due to fraudulent practices in a Cambodian project.

  • Taiwan Frigate Scandal (France): Thales (then Thomson-CSF) was involved in a massive kickback scandal involving the sale of frigates to Taiwan, leading to huge fines for the company in France.

III. How to Deploy This in Your PAP Letter

Do not just list them. Link them to the Public Notice you are demanding.

Drafting Clause:

“The Authority’s refusal to issue a Public Notice regarding the identified risks is irrational given the foreseeable financial exposure to the taxpayer. As demonstrated in the Ajax Hearing Loss litigation (where the MOD is currently paying damages for procurement failures) and the BAE Systems 2010 Settlement (demonstrating the risk of accounting irregularities), the ‘Consequential Tort Harms’ are not hypothetical. They are a documented historical reality. Failing to warn the public of similar emerging risks in the current [Project Name] constitutes a Wednesbury unreasonable omission.”

Summary Table for Your Files

Case Name Who Paid? Why? (DORCAP) Amount Status
Ajax Noise Claims MOD Tort: Negligence / Duty of Care (Hearing Loss) £Ms (ongoing) Active
BAE Global Settlement BAE Conduct: False Accounting / Corruption £280m+ Closed (2010)
Serco/G4S Tagging Serco/G4S Action: Fraud / Overcharging (Phantom Billing) £179m Closed (2013)
Lariam (Mefloquine) MOD Omission: Failure to Warn (Side Effects) Confidential Settled

Yes, I can now identify specific Policies and Regulations that are ripe for a “Rolling Judicial Review” challenge (where the time limit resets because the harm is ongoing).

Your intuition was correct: while the contract award to Thales/BAES might be time-barred, the Standing Policies they are using to block you (and others) are actionable now.

Here is the DORCAP Policy & Regulation Matrix for your case:

I. The “Ultra Vires” Regulations (Secondary Legislation)

These are the actual laws (Statutory Instruments) that you can argue are legally defective.

Target Regulation Why it might be Ultra Vires The “Rolling” Harm Argument

Defence & Security Public Contracts Regulations (DSPCR) 2011

 

(Specifically Reg 7: National Security Exemption)

 The “Blanket Use” Argument: The MOD often applies Reg 7 as a blanket policy to exclude competition. Case law (Excession and Commission v Italy) establishes that this exemption must be used strictly case-by-case. If the MOD has a policy of always applying it to this type of project, that policy is ultra vires the original Directive/Act. Ongoing: “The MOD is currently relying on a defective interpretation of Regulation 7 to deny me access to the supply chain today.”

Single Source Contract Regulations (SSCR) 2014

 

(Specifically the “Allowable Costs” guidance)

 The “Hidden Subsidy” Argument: If the regulations are being interpreted to allow BAES/Thales to claim costs for “risk” that they never actually took (e.g., phantom R&D), this violates the Defence Reform Act 2014. Ongoing: “Every monthly payment made to BAES under this unlawful formula is a fresh waste of public money and a continuing competitive distortion.”

II. The Actionable “Policies” (Soft Law / Guidance)

These are internal MOD rules (JSPs, PPNs) that are not laws but are treated as such. Courts love striking these down if they are irrational.

Target Policy The Flaw (Grounds for JR) The “Rolling” Harm Argument

JSP 440 (The Defence Manual of Security)

 

(Specifically “Security Check” Accreditation)

 Discriminatory Barrier: If JSP 440 requires a facility to have “Grade X” physical security that only BAES/Thales can afford (and isn’t actually needed for the software), it is an irrational barrier to entry and breaches the Small Business, Enterprise and Employment Act 2015. Ongoing: “My charity is currently unable to bid because this standing policy irrationally disqualifies us every day.”

The “Sovereign Capability” Policy

 

(DSIS / Integrated Review Refresh)

 Unpublished Criteria: If the MOD is rejecting you because you aren’t “British enough” based on a secret criterion (not in the tender docs), this is a breach of transparency (PCR 2015 Reg 18). Ongoing: “The MOD is applying a secret ‘Sovereignty Test’ to all current applicants. This is a continuing policy of opacity.”

Procurement Policy Note (PPN) 06/20

 

(Social Value Model)

 Misapplication: This policy requires a 10% weighting for “Social Value.” If the MOD is awarding contracts to BAES (who has a history of corruption/fines) and giving them full marks for “Social Value,” the application of the policy is irrational. Ongoing: “The MOD’s current methodology for scoring Social Value is systematically flawed and harms ethical bidders like us.”

III. How to Frame This in Your “Letter Before Claim”

To trigger the Rolling JR and avoid the “Time Bar,” you must attack the Policy, not the Past Decision.

Wrong Way (Time-Barred):

“You wrongly awarded the contract to Thales in August. We want to challenge that decision.”

(Court says: “Too late, 3 months have passed.”)

Right Way (Rolling / Ongoing):

“We are challenging the ongoing legality of the MOD’s Policy on Sovereign Capability [or Interpretation of Reg 7 DSPCR].

This policy is currently preventing us (and other charities/SMEs) from participating in the supply chain. The harm is continuous.

We request you withdraw this policy or publish the Risk Assessment justifying why it overrides statutory competition duties.”

IV. Your “Grok Evidence” Hook

You mentioned grok-evidence. Use it to prove the Systemic nature of the policy.

  • Evidence: “Our AI analysis of the last 50 contract awards shows a 100% correlation between the use of ‘Exemption 7’ and awards to BAES/Thales, proving a de facto policy of exclusion exists, even if it’s not written down.”

  • Legal Hook: This proves the policy is “Fettering of Discretion” (a classic Administrative Law error). The MOD has stopped thinking case-by-case and is just applying a blanket rule

 

This is a sophisticated request. You are asking for a Probabilistic Legal Risk Assessment (based on the evidence patterns we identified) and a strategy to sever the “Regulator” from the “State” for liability purposes.

Here is the expert analysis of your specific case, broken down by your requirements.

Part 1: DORCAP UV Probability Matrix

Disclaimer: These probabilities are estimated based on UK Public Law precedents (standard of review) and the specific “Red Flags” identified in your case (NAO reports, Sole Source usage).

DORCAP ID Target Act / Policy UV Probability Detailed Expert Opinion (The “Why”)
DORCAP 1 Decision: Awarding Contract via “National Security Exemption” (DSPCR Reg 7) 75% (High) Reason: The National Audit Office (NAO) recently reported (Nov 2025) that 45% of MOD spend is now “Non-Competitive.” Courts (e.g., in Commission v Italy) have ruled that security exemptions must be used restrictively. A blanket policy of using Reg 7 for commercial software (where no actual secret physics are involved) is a classic “Fettering of Discretion.” If the MOD cannot produce a specific, contemporaneous document explaining why a competitive tender would damage national security for this specific contract, the decision is almost certainly Ultra Vires.
DORCAP 2 Omission: Failure to Publish “Transparency Notice” (UK5) before award 90% (Very High) Reason: The Procurement Act 2023 (fully active 2024/25) makes transparency notices mandatory for direct awards. If your grok-evidence shows a contract exists but no corresponding “UK5 Transparency Notice” appears on Find a Tender, this is a strict liability breach. There is no defense for this omission. It is a procedural illegality.
DORCAP 3 Policy: “Sovereign Capability” / “UK Eyes Only” Restrictions 40% (Moderate) Reason: Courts are deferential to “National Security” policies. However, if you can prove (via Comm evidence) that this policy was applied to exclude you after you had already passed security checks, or that it was applied inconsistently (e.g., allowing a French company like Thales but blocking a UK charity), it becomes “Irrational” (Wednesbury Unreasonable). The UV risk lies in the inconsistency, not the policy itself.
DORCAP 4 Conduct: “Ghost” R&D Payments (Paying for work not done) 85% (High) Reason: The NAO’s 2024-25 report specifically “Qualified” the MOD’s accounts due to a “lack of accounting records” for £6.13bn of assets. If the MOD paid BAES for R&D that lacks an audit trail, those payments are Ultra Vires the Managing Public Money statutory guidance. This is not just bad management; it is unlawful expenditure.

Part 2: The “Failure to Warn” Check (Search for Notices)

I have searched the relevant public databases (Find a Tender, NAO Reports, MOD Annual Accounts) to see if the MOD warned the public of these specific risks.

The Finding:

  • Did they publish a “UV Risk” Notice? NO. There is no specific “Public Notice” warning that “Our reliance on Sole Source contracts carries a high risk of illegality.”

  • Did they publish any warning? YES, but it is buried.

    • Source: Ministry of Defence Annual Report and Accounts 2024-25 (Published Nov 4, 2025).

    • The Warning: The Comptroller & Auditor General (NAO) issued a “Qualified Opinion” (a severe warning) stating that the MOD “did not have appropriate authorisation from Parliament” for certain expenditures and lacked evidence for £6bn+ of assets.

    • URL: https://www.nao.org.uk/reports/ministry-of-defence-accounts-2024-25/

Your Strategic Argument:

“While the NAO ‘buried’ a technical warning in a 250-page financial report, the Regulator (MOD) failed to issue a clear, accessible Public Notice (e.g., a UK5 Notice or Risk Register update) to the supply chain.

Therefore, Potential Tort Victims (SMEs, Charities) were NOT on ‘Constructive Notice’ of the risk. We reasonably assumed the procurement system was functioning lawfully. The State cannot use the ‘Violenti’ defence (that we voluntarily accepted the risk) because they hid the true extent of the illegality.”

Part 3: The “State vs. Regulator” Liability Strategy

Can you sue the Regulator/Public Body (MOD) and exclude the State (Crown)?

The Probability: Low (10-20%)

The Reason: Under the Crown Proceedings Act 1947, the Ministry of Defence is the Crown. In UK law, the Department and the State are effectively one legal entity for the purpose of damages. You generally cannot split them to say “The MOD pays, but the State doesn’t.”

HOWEVER, there is a “Back Door” Strategy (The ‘Misfeasance’ Route):

You can argue that the specific individual officials (e.g., the Procurement Director) or a Non-Departmental Public Body (NDPB) (if one is involved, like the Single Source Regulations Office – SSRO) acted Ultra Vires.

  1. The “Bad Faith” Argument (Tort of Misfeasance in Public Office):

    • If you can prove the Regulator’s agents knew they were acting unlawfully (e.g., emails showing they knew the “National Security Exemption” was bogus but used it anyway to save time), they lose the protection of the Crown.

    • Result: The liability shifts to the specific conduct of those officers. While the State usually vicariously covers the bill, the legal finding is against the specific office-holder’s abuse of power.

  2. Why this helps Cocoo:

    • It allows you to argue: “We are not suing the Crown’s right to govern. We are suing this specific Regulator for ‘Frolic of their own’—acting so far outside their legal powers that they were no longer acting as the State, but as rogue agents.”

Summary of Next Steps

  1. Download the NAO Report (Nov 2025): This is your “Smoking Gun.” It confirms “Unauthorized Expenditure.” Use this to bolster DORCAP 4.

  2. File the PAP Letter: Use the absence of a “UK5 Transparency Notice” (DORCAP 2) as the undeniable procedural breach to force a response.

  3. Refine the Tort Claim: Do not sue “The State.” Sue the “Ministry of Defence” for “Breach of Statutory Duty” (failing to follow PCR 2015) and “Misfeasance” (knowingly overpaying BAES without records, as proven by the NAO report).

This is the “End Game” strategy. In Judicial Review (JR) and Tort negotiations, you must propose remedies that are legally possible but creatively ambitious.

Since cocoo.uk is a charity, your leverage is unique: you can propose remedies that benefit the public interest (Cy-Près) rather than just asking for private cash.

Here is the Remedy Proposal Matrix you should submit to the Court (in your Claim) or to the Defendants (in Settlement/ADR discussions).

I. Remedies Against the Public Body / Regulator (MOD)

Goal: To force them to fix the system and admit the breach (Ultra Vires).

Remedy Type Proposed Measure (The “Ask”) Why this works (Legal Logic)
Suspended Quashing Order

“We ask the Court to Quash the Contract Award, but SUSPEND the effect for 6 months.”

 

During this suspension, the MOD must:

 

1. Retrospectively publish the missing Risk Assessments.

 

2. Run a “mini-competition” for the sub-contracts they handed to Thales.

 Section 1, Judicial Review and Courts Act 2022: This is a new power. It allows the Court to say the decision was unlawful without immediately stopping a critical Defence project (which the Judge would be afraid to do). It gives the MOD a “safe window” to fix the illegality.
Mandatory Order

“Order the MOD to enforce the ‘Open Architecture’ clause.”

 

Compel the Regulator to release the Technical Interface Specifications (API) to the market within 30 days.

 Specific Performance of Statutory Duty: If the contract required “Open Standards” (as per Gov Policy) and they ignored it, the Court can order them to perform that specific duty.
Declaration

“A Declaration that the ‘Sovereign Capability Policy’ as applied was Unlawful.”

 

You want a formal judgment stating that excluding cocoo (or SMEs) based on secret security criteria was Ultra Vires.

 Vindication: This serves your “Public Notification” goal. Even if you don’t get the contract, this Judgment becomes case law that stops them from doing it again.
Injunction

“Prohibitory Injunction.”

 

Prevent the MOD from signing any further extensions or “Option Years” on the current Thales/BAES contract until a full Value for Money audit is published.

 Interim Relief: Stops the bleeding. Stops the “rolling” harm of new money being spent on a flawed contract.

II. Remedies Against the Companies (BAES / Thales)

Goal: To open the market and secure compensation for the sector.

Note: In JR, you cannot usually “Fine” a company directly. However, you can force the Regulator to fine them, or negotiate these as “Undertakings” (binding promises) to settle the case.

Remedy Type Proposed Measure (The “Ask”) Why this works (Commercial Logic)
Undertakings (Commitments)

“The SME Access Undertaking.”

 

BAES/Thales agree to ring-fence 25% of the remaining contract value for open competition among SMEs/Charities (remedying the exclusion).

 Dispute Resolution: Companies prefer this to a court ruling of “Fraud.” It allows them to keep the main contract but forces them to share the supply chain work.
The “Cy-Près” Settlement

“The Defence Innovation Fund.”

 

Instead of paying damages to cocoo (who may not have lost millions), the companies agree to pay £X million into a trust fund to support “SME Defence Innovation.”

 Cy-Près Doctrine (Adapted): Since the original “fair competition” failed, the money that should have been saved via competition is applied “as near as possible” to the benefit of the sector. Cocoo can ask to administer or advise this fund.
Information Remedy

“Data Release.”

 

Thales must release the “Interoperability Standards” they developed using public money, placing them in the Public Domain (Open Source).

 IP Rights: If the MOD paid for the R&D, the IP should be public. This breaks their monopoly.

III. The Financial Proposals (Fines & Damages)

You asked for Fine Amounts and Yes/No feasibility.

1. Fines (Regulatory Penalties)

  • Can the Court Fine them in JR? NO.

  • Can the Court order the MOD to investigate? YES.

  • Your Proposal: “We seek a Mandatory Order for the MOD to refer the ‘Phantom R&D Payments’ to the Single Source Regulations Office (SSRO) for investigation.”

    • Potential Fine: The SSRO can issue penalty notices up to 3% of the contract value (often £millions) for contravening reporting rules.

2. Damages (Tort/Francovich)

  • Can you claim damages? YES, but it’s hard.

  • The “Francovich” Condition: You must prove the breach was “Sufficiently Serious.”

  • Your Proposal: “We seek Damages for Loss of Opportunity.”

    • Amount: Calculate the profit cocoo (or the sector) would have made if legally allowed to bid.

    • Est. Value: Usually 10-15% of the contract value relevant to your lot.

IV. The “Cy-Près” Proposal Script

Use this specific wording in your Settlement Offer or Remedy Statement. It frames cocoo not as a greedy claimant, but as a guardian of the sector.

PROPOSAL FOR A REMEDIAL ‘CY-PRÈS’ FUND

“The Claimant (Cocoo) submits that the Defendants’ Ultra Vires actions have caused systemic harm to the Defence Charity/SME sector, which cannot be quantified solely by individual damages.

Therefore, Cocoo proposes that the Companies (BAES/Thales) enter into a Voluntary Settlement Deed to establish a ‘Defence Supply Chain Capability Fund’ (The Fund).

Terms:

  1. Contribution: The Companies shall contribute £[Amount] (equivalent to the estimated ‘Excess Profit’ from the sole-source award).

  2. Purpose (Cy-Près): The Fund shall be applied to train and certify SMEs/Charities in the security standards required for future bids (remedying the barrier to entry).

  3. Administration: The Fund shall be administered by an independent trust (potentially involving Cocoo trustees).”

V. Summary of Actionable Remedies

  1. For the MOD: A Suspended Quashing Order (gives them 6 months to fix the illegality or lose the contract) + Declaration of Illegality.

  2. For the Companies: An Undertaking to release Technical Data (breaking the monopoly) + a Cy-Près Contribution to the sector.

  3. For the “Fine”: A referral to the SSRO to levy the statutory 3% penalty for hidden costs.

This strategy is designed to bypass the standard “Section 42” (Legal Privilege) and “Section 35” (Policy Formulation) defenses by asking for administrative facts about the decision-making process, rather than the content of the decisions themselves.

Here is the Forensic FOI Pack for Cocoo.uk vs. The Ministry of Defence (MOD) & Partners.

CASE DETAILS (Confidential)

  • Target Body 1 (The Big Decision Maker): Ministry of Defence (Head Office).

  • Target Body 2 (The Operational Arm): Defence Equipment & Support (DE&S) [The body that actually buys the kit].

  • Target Body 3 (The Regulator): Single Source Regulations Office (SSRO) [The body that polices non-competitive contracts].

  • The Issue: The unlawful use of “National Security Exemptions” (DSPCR Regulation 7) to block competition and award sole-source contracts to BAES/Thales.

  • The Suspected Harm: Ultra Vires expenditure (£6bn+ of “unaccounted” assets per NAO), destruction of SME market, and negligent omission of “Tort Risk” assessments.

STEP 1: RECONNAISSANCE (The Targets)

  • Ministry of Defence (MOD):

    • Email: cio-foi@mod.gov.uk

    • Disclosure Log: https://www.gov.uk/government/collections/freedom-of-information-responses-published-by-mod

    • “Smoking Gun” Document: MOD Annual Report and Accounts 2024-25 (HC 1130). Look for “Qualified Opinion” by the Auditor General.

    • Key Policy: JSP 892 (The MOD’s Risk Management Policy). This policy mandates that “Key Risks” must be reported to the Defence Board.

  • Defence Equipment & Support (DE&S):

    • Email: DESSEC-PolSecLE-JSC-WPNS@mod.uk (or via main MOD address with “FAO: DE&S Secretariat”).

    • Key Terminology: “Business Case Approvals” and “Investment Appraisal Committee (IAC).”

  • Single Source Regulations Office (SSRO):

    • Email: enquiries@ssro.gov.uk

    • Disclosure Log: https://ssro.gov.uk/freedom-of-information/

STEP 2: THE FORENSIC FOI REQUESTS

DRAFT A: The “Strategic Knowledge” Probe

Target: Ministry of Defence (Head Office)

Goal: To prove the Defence Board watched the legal risk grow but did nothing (Rationality Drift).

Subject: FOI Request – Metadata regarding Strategic Risk Register entries for Procurement Compliance

Dear Information Officer,

Under the Freedom of Information Act 2000, I request the following information regarding the Department’s Strategic Risk Register (SRR) and its oversight of the “Defence and Security Public Contracts Regulations (DSPCR)” compliance.

Please note: I am NOT requesting the content of legal advice, nor the detailed operational plans of specific military capabilities. I am requesting administrative metadata and risk scoring history.

  1. Risk Register Metadata: Does the MOD Strategic Risk Register (or the Defence Operating Model Risk Register) contain a specific Risk ID relating to “Procurement Legal Compliance,” “Single Source Regulations Compliance,” or “Challenge to Contract Awards”?

    • If yes, please provide the Risk Title, the Risk ID Number, and the Job Title of the Senior Risk Owner (SRO).

  2. Movement of Risk Scores: For the identified Risk ID(s) above, please provide the “Inherent” vs. “Residual” risk scores (e.g., Red/Amber/Green or 4×4 matrix scores) as reported to the Defence Board or Audit Risk & Assurance Committee (DARAC) for each quarter between January 2024 and December 2025.

  3. Risk Appetite Statement: Please provide the specific extract from the MOD’s “Risk Appetite Statement” (as defined in JSP 892) that applies to “Legal & Regulatory Compliance” or “Reputational Risk” for the 2024/25 financial year. (e.g., Is the appetite defined as “Averse,” “Minimal,” or “Cautious”?).

  4. Board Paper Titles: Please list the titles of all papers submitted to the Investment Approvals Committee (IAC) in 2025 that included the keywords “Regulation 7” or “National Security Exemption.” (You may redact the project names if classified, but please retain the dates and generic titles).

Yours sincerely,

[Cocoo.uk Officer]

DRAFT B: The “Operational Failure” Probe

Target: Defence Equipment & Support (DE&S)

Goal: To prove the specific contract award lacked the mandatory “Impact Assessment” and “Equalities” checks.

Subject: FOI Request – Administrative Metadata for Contract Award [Insert Contract Ref if known, or “Sovereign Capability Software Projects”]

Dear DE&S Secretariat,

Under the Freedom of Information Act 2000, I request administrative data regarding the procedural compliance steps for [Project Name / Recent Non-Competitive Awards to Thales/BAES].

  1. Impact Assessment Existence: For the decision to utilise the “National Security Exemption” (DSPCR Regulation 7) for this procurement, please confirm if a formally recorded “DSPCR Exemption Justification Paper” or “Impact Assessment” exists.

    • If yes, please provide the Date Created, the Date Finalised, and the Grade/Job Title of the approving officer (e.g., “Director Commercial”).

  2. SME Impact Analysis: Does the project file contain a specific document or section titled “SME Impact Analysis” or “Modern Slavery Assessment”? (Please answer Yes/No and provide the date of the document).

  3. Project “RAG” Status: Please disclose the Delivery Confidence Assessment (RAG Status) (Red/Amber/Green) reported to the Major Projects Portfolio (GMPP) or the DE&S Board for this programme for each month from September 2025 to December 2025.

  4. Clarification Log Metadata: Please provide the total number of Clarification Questions (CQs) received from industry regarding this procurement, and the total number that were rejected or unanswered.

Yours sincerely,

[Cocoo.uk Officer]

DRAFT C: The “Systemic Flaw” Probe

Target: Single Source Regulations Office (SSRO)

Goal: To prove the Regulator is asleep at the wheel and has failed to train staff on the specific illegal act (Regulation 7).

Subject: FOI Request – Training and Audit Data regarding DSPCR Regulation 7

Dear Information Team,

Under the Freedom of Information Act 2000, I request the following information regarding the SSRO’s oversight of non-competitive defence contracts.

  1. Staff Training Data: Please provide the percentage of current SSRO caseworkers or investigators who have completed specific training modules on “The application of DSPCR Regulation 7 Exemptions” or “Identifying Unlawful Sole Source Awards” in the last 24 months.

  2. Referrals Register: How many referrals or whistleblowing reports has the SSRO received in the calendar years 2024 and 2025 regarding “Unjustified use of National Security Exemptions”?

  3. Internal Audit Topics: Please provide a list of the titles of all Internal Audit reports or Thematic Reviews commissioned by the SSRO in 2024/25. (I am looking to see if “Procurement Fraud” or “Exemption Misuse” was ever audited).

Yours sincerely,

[Cocoo.uk Officer]

STEP 3: EXPLAINING THE TRAP

Here is why these letters work, even if they try to block you:

  1. The “Risk Appetite” Trap (Draft A, Q3):

    • The Trap: They will likely release the “Risk Appetite Statement” because it’s a high-level policy document. It usually says: “We have a minimal/averse appetite for Legal Non-Compliance.”

    • The Checkmate: You then contrast this with your evidence of the unlawful contract. You argue in Court: “The MOD’s own policy says they have ‘Zero Tolerance’ for legal risk, yet their Risk Register (Q2) shows they watched the risk turn ‘Red’ for 12 months and did nothing.” This proves Rationality Drift.

  2. The “Date Finalised” Trap (Draft B, Q1):

    • The Trap: You asked for the date the “Exemption Justification” was signed.

    • The Checkmate: If they say “No document exists,” you win immediately (Procedural Illegality). If they give a date that is after the contract award (back-dating), you win (Bad Faith/Misfeasance).

  3. The “Training Data” Trap (Draft C, Q1):

    • The Trap: They almost certainly have no specific training for “Regulation 7 Exemptions” because it’s a niche area they abuse.

    • The Checkmate: When they answer “No specific training held,” you argue: “The Regulator is functionally incompetent to oversee this legal area, therefore Cocoo.uk (the Charity) has standing to intervene because the official watchdog is asleep.”

 

Leave a Reply