National Police Chiefs’ Council (NPCC)

Chronology and catalogue links — assessed 10-10-2026: See the Institutional Involvement Roadmap (1877–2026) for the date-ordered institution, people and evidence sequence. Related heritage-file lead: GHF-E152 — reported Cadw letter to the Minister (1988; original awaited).

Scope: National Police Chiefs’ Council (NPCC), its present-day records-search involvement, and the evidential question concerning any surviving national-policing records about Great House Farm, BP Properties Ltd v Buckler [1987] EWCA Civ 2, and the 1988 possession-enforcement/demolition events.

Assessment boundary: This review separates (1) documented present-day records-access decisions, (2) historical events about which information was requested, and (3) evidence of actual historical operational involvement. As at 10 October 2026, the three NPCC letters establish present-day records-access activity. They do not establish a historical NPCC operational role in 1988; this assessment is limited to these letters and evidence reviewed to date. Inclusion here is not a finding of wrongdoing, concealment, or historical deployment. ^{🕒10-10-2026}

Institutional appearance timeline — direct evidence links

Select an event to open the Wiki evidence page containing the relevant source. Entries distinguish an institution’s own act or response from a historical event that was merely the subject of a later records request.

Forensic control points

• Search-term reconciliation: 3156 states ACPO catalogues showed no references to the farm, case or operation; 3065 reports the terms “Great House Farm” and “Llandough”. The disclosed wording does not establish whether searches also used “Buckler”, “BP Properties”, the case citation, or operational descriptions. ^{🕒10-10-2026}
• Q4/Q5 record distinction: 3065 states no information is held for search logs/instructions or recorded results, but supplies a retrieval email and states results were captured by email and disclosed through previous responses. Clarify whether this means there was no formal search log/consolidated result schedule, and identify the individual response emails that make up the recorded results.
• Custody trail: the NPCC states it holds no transfer, archive, retention or disposal information. This is a statement about NPCC holdings, not proof that records never existed or are not held by a local force/archive. ^{🕒10-10-2026}
• Institutional boundary: the retrieval email names NaCTSO and NPCC functions as current search leads. As at 10 October 2026, the retrieval email shows modern records-search involvement; it does not establish historical counter-terrorism or military participation. This is limited to the material reviewed to date. ^{🕒10-10-2026}
• Review boundary: review 3157 concerns whether the original 2 September correspondence was a sufficiently identifiable FOI request; review 3176 concerns the substantive 3156 response. Keep the issues separate.

Cross-links to related institutional and source records

• NCTSO — Forensic Assessment
• South Wales Police — Forensic Assessment
• FOI & Public-Authority Reply Register
• Source Conflicts Register
• Missing Records Register

Current finding

The NPCC’s present-day searches and decisions are now documented by primary-source links. As at 10 October 2026, the records reviewed do not establish an NPCC operational role in 1988, the non-existence of all relevant historical policing records, deliberate concealment, or the identity of an alternative current custodian. This is a dated evidential status, not a assertion that contrary evidence cannot later emerge. The next tests are to inspect and catalogue every individual retrieval response, verify the linked WhatDoTheyKnow message and attachments, and pursue the relevant local force/archive record trail independently. ^{🕒10-10-2026}

Records-access register appearances — direct row links

The three entries below are the NPCC’s own responses and review letter in the project register. Select a row to open the corresponding entry. This records modern records-access involvement; it does not establish historical operational deployment. ^{🕒10-10-2026}