The Philippines closed its market to UK beef on 2 October 2026. The trigger was one cow in Dumfries and Galloway that tested positive for classical BSE in August. The animal was caught by routine surveillance, never entered the food chain, and Food Standards Scotland confirmed no risk to human health. The export door shut anyway. For anyone making animal feed in the UK, that gap between a well-run surveillance system and a closed export market is the point worth sitting with. Classical BSE is a feed-borne disease. The surveillance that found this case is verification that national controls are working. Prevention lives somewhere else, in the raw material and feed controls that keep the BSE agent out of the ruminant chain in the first place.
What happened
On 19 August 2026 the Scottish Government confirmed a single case of classical Bovine Spongiform Encephalopathy in a cow on a farm in Dumfries and Galloway. The case came to light through Scotland's BSE surveillance programme, under which every animal over four years of age that dies on farm is tested. The infected animal did not enter the human food chain.
Precautionary movement restrictions were placed on the animal's offspring and the rest of its cohort, the cattle that may have shared the same exposure. Those cohort animals are being traced, isolated and destroyed under legal requirement. The Animal and Plant Health Agency opened an investigation into the source, which has not yet been published. Weeks later, following a report to the World Organisation for Animal Health by Defra Chief Veterinary Officer Christine Middlemiss, the Philippines suspended imports of UK beef. One confirmed case, no sick consumers, and a market lost. You can read the Scottish Government notice here.
Classical BSE is a feed-control problem
The word "classical" is the part feed producers should read twice. Classical BSE is the feed-borne form of the disease. It occurs mainly when cattle consume feed contaminated with the BSE agent, an abnormal prion protein. That is the difference from atypical BSE, which is thought to arise spontaneously in older cattle and carries no feed link. A classical case in 2026, decades after the ruminant feed ban took hold, points back toward the feed chain. The gov.scot notice does not state a cause, and APHA's source investigation is still open, so the specific route here is not yet known. The pattern of the disease is, though. Where classical BSE appears, feed is the line of enquiry.
The prion is an awkward hazard. It is biological, but it behaves nothing like a vegetative pathogen. It resists the heat, time and pressure that destroy Salmonella or Listeria. There is no cooking step, no extrusion temperature and no pelleting cycle in a feed mill that reliably denatures it. That single fact decides how the hazard has to be controlled, and it is the heart of the HACCP logic below.
The HACCP perspective
Start with hazard analysis. Under Codex Principle 1 and BRC Issue 9 clause 2.7, a feed producer handling ruminant feed has to identify the TSE agent as a biological hazard and assess it on severity against likelihood. Severity is at the top of any scale. Likelihood is low because of the feed ban, but low is not zero, which is exactly why the hazard stays in the plan rather than being screened out.
Now CCP determination, Codex Principle 2 and BRC clause 2.8. Because no step in the process destroys the prion, there is no critical control point for it. You cannot set a validated critical limit on a kill you cannot achieve. The control therefore moves upstream and sits in the prerequisite programmes under BRC clause 2.2, specifically raw material control, supplier assurance and physical segregation. The legal prohibition on feeding processed animal protein to ruminants is the control measure. In a mill that produces both ruminant and non-ruminant feed, segregation and line sequencing are what stop cross-contamination from undoing it. This is a PRP question, not a CCP one, and getting that classification right is the difference between a plan that works and a plan that looks tidy.
Keep validation and verification apart here, because the BSE story shows why they are not the same thing. The feed ban was validated by outcome. BSE incidence in the national herd collapsed after the controls came in, which is the scientific evidence that the measure works when applied. Surveillance testing of fallen stock is verification. It confirms, case by case, that the national system is still catching what it should. Surveillance did not prevent this case. It caught it. The prevention had to happen earlier, in the feed.
What feed producers can check this week
None of this needs a consultant. It needs an hour with your own records.
- Raw material specifications and supplier declarations. Confirm that every ingredient going into ruminant feed carries a current declaration that it is free of prohibited processed animal protein, and that your supplier approval under BRC clause 3.5 holds evidence rather than a promise.
- Segregation and sequencing. If you make both ruminant and non-ruminant feed on shared lines, check the documented order of production, the flushing procedure between runs and the records that prove it happened, not just the procedure that says it should.
- Verification sampling. Review your testing regime for prohibited constituents and ask whether the frequency matches the risk of the lines you run.
- Fallen stock procedures. Confirm your on-farm and site procedures support the national surveillance scheme, including the over-four-years testing route.
- Your hazard analysis. Check that the TSE hazard is actually written into the plan with the feed ban named as its control, and that a confirmed national case counts as a trigger to review it.
Where SafetyCore fits
A confirmed classical BSE case is precisely the kind of external event that should start a review, and SafetyCore is built around that. The Triggered Reviews feature lets a feed producer open an incident-driven review of the feed hazard analysis and supplier controls, with evidence captured and every change timestamped in the Audit Trail. The Animal Feed Module is written against EC 183/2005 and Codex CAC/GL 80, so the prion hazard belongs in its Hazard Analysis as a biological hazard, scored on severity against likelihood, with a Hazard Library entry you can reuse across products. The feed ban and segregation controls sit in Prerequisite Programmes linked back to the risk assessments that justify them. None of this watches your mill in real time. It holds the plan, the reasoning and the records, so that when a question like this one lands, the answer is already documented and ready for an auditor.
Final thought
The surveillance system did its job, and the people who built it deserve the credit they are getting. The harder question a classical case always asks is whether the feed controls upstream are as tight as the paperwork claims. That answer is not written in a lab result after the fact. It is written in your raw material records, your segregation logs and your supplier files, and the only way to know is to go and read them.