GDS publishes alpha review of DEFRA livestock information service
GDS rated the service green on all 14 standards; private beta depends on spend-control approval and public beta requires another assessment.
Event / data period:
Published: · Updated:

The Government Digital Service (GDS) published its alpha-stage assessment of DEFRA’s Livestock Information Service on 22 October. The assessment took place on 9 September and rated the service green against all 14 government service standards. The report says livestock keepers currently report births, movements and deaths through different systems; the new service aims to let keepers view and manage animals on their holdings through one system. A green result means the service met the criteria for alpha; it does not mean a public service has launched or that a completed system covers every species.
GDS says the service can move to private beta, subject to approval from the GDS spend-control team. Before public beta, it must meet the standard at a beta assessment. The report includes further advice on user research, connections with third-party software, a possible paper route for farmers with low digital literacy, accessibility testing and defining operational baselines for success. These are development considerations at alpha; the assessment does not create a new livestock-recording requirement.
The fragmented reporting system and service goal
The assessment says livestock keepers currently use three separate services to report animal births, movements and deaths to government. The legacy systems were built by different companies to different standards and design approaches, and require different login credentials. GDS says some are struggling to cope with demand and becoming prone to failure. The Livestock Information Service aims to replace that fragmented experience with one consistently designed system through which keepers can view and administer animals on their holdings.
The goal involves the work of multiple user groups, not only farmers. The report lists keepers making legally required reports; support teams viewing and changing records; Animal and Plant Health Agency teams tracing animal disease; inspectors comparing what is present with what has been declared; and market and abattoir staff registering movements and deaths. These are needs identified in the report. They do not establish that every function has been completed in the current service.
Continuity of movement information across contact points is central to traceability. Market administrators need to register animals entering and leaving market premises, while abattoir administrators record movements and, sometimes in volume, animal deaths. APHA teams need to know where animals came from, where they may have moved and which other animals they may have encountered to help slow or prevent disease spread. These use cases explain why the service is being considered as more than an online form for an individual keeper.
A positive assessment at alpha stage
GDS rated the service green against all 14 standards at its 9 September 2026 alpha assessment; the result page was published on 22 October. The report says the team had taken a comprehensive approach to performance analytics and embedded it in agile working. It also identifies use of the Common Development Platform, GOV.UK components, DEFRA patterns and open standards, rather than bespoke solutions, as strengths, alongside API-led integration, automated testing, monitoring and security foundations.
GDS notes that the team had designed a specific part of the user journey for cattle births while considering how cattle movements and other species might be integrated later. This wording shows that work on part of the alpha design was in progress and that multi-species integration was a future consideration. Because the intended user group covers different kinds of livestock, designing one cattle birth journey does not show that all species have already been integrated with the same capabilities.
The green assessment means the service met the standard at alpha stage. The report also lists research and testing recommendations for later development. It should not be interpreted as proof that a finished product is already operating as a public service or that farmers have moved from the legacy systems. GDS says the next step can be private beta, subject to spend-control approval, and that a further beta assessment is required before public beta.
Farmer access and service channels
GDS advises the team to consider recruiting research participants beyond its panel if access needs or user contexts are not adequately represented. As the service moves toward production, it recommends testing with accessibility software and tools such as colour-contrast checkers, to identify problems before audits and research with users who have access needs. These recommendations concern future research and design; they are not a claim that all accessibility testing has already been completed.
The report also asks the team to consider retaining a paper route for farmers with low digital literacy, while using the online service to reduce duplicate effort required by legislation. This advice concerns more than switching everyone to a digital channel: it recognises different skills and connectivity conditions among farmers. GDS also recommends role-playing or testing the interactive voice response route to see whether it works for users.
Third-party software is identified as a significant entry point for farmers. GDS says the journey from that software into the government service should be tested. This matters because farm-management systems can be part of daily recordkeeping, but the report does not say integrations are complete or that a particular supplier has been connected. It recommends testing this hand-off with users as the service is developed.
The assessment also suggests adding explanations for acronyms such as CPH and other terms new keepers may not know, to create a consistent self-help experience. That recommendation highlights the language used by different user groups. The report says the team should consider clearer labels; it does not say that such labels have already been implemented.
Security, measurement and open technology
GDS says the service met the standard on privacy and security, while advising the team to consider challenges in digital knowledge-based verification for a sector where users may represent varied business types, ownership arrangements and roles. That diversity means a verification process should not assume a simple single-owner farm. The report identifies a design consideration; it does not report a security breach.
The service team was credited with establishing performance analytics early. GDS advises it to work with operational areas to define meaningful baselines for success. The ability to measure processing times or errors does not by itself establish which user outcome counts as success; the advice is to develop measurable baselines with people who understand operations. The assessment does not publish a performance target or usage rate.
GDS viewed the use of common components and open standards positively. It also advises the team, where possible, to link to open repositories for new source code and to share design iterations that may interest other government teams, perhaps through a design history. These points appear as good practice and future advice. The report does not provide a public code repository, so it would be inaccurate to say the service source code has been released as open source.
Conditions for private beta
According to GDS’s next-steps section, the service may move into private beta if the GDS spend-control team approves. That stage could support testing with a limited group, but the assessment does not say that private beta has started or give a date. The green alpha result does not remove the approval condition. GDS also states that the service must meet the standard at beta assessment before it can launch public beta.
These stage gates limit what the alpha assessment establishes. User research, end-to-end journeys, accessibility, third-party software hand-offs, verification and operational measurement are areas for continuing work. GDS’s advice points toward development priorities but does not supply a completion schedule, the scale of a public pilot, a full species list or dates for retiring legacy systems. The article should not add a plan the report does not contain.
The service is intended to support livestock traceability and legal reporting; the alpha assessment itself is not an animal-health alert or a new duty for farmers. It explains why records matter for APHA tracing and inspection, but reports no disease counts, outbreak outcomes or movement restrictions. The story is about the government service’s assessment stage and the conditions that remain before further beta testing.
Data
Livestock Information Service alpha assessment
GDS service-standard alpha assessment dated 9 September 2026 and next steps published 22 October.
| Assessment date | 9 September 2026 |
| Publication date | 22 October 2026 |
| Alpha service standards | Green against all 14 standards |
| Next stage | Private beta subject to spend-control approval |
| Public beta condition | Must meet the standard at beta assessment |
Methodology
Assessment result, stage and progression conditions are transcribed from the GDS report. A green alpha result does not mean the public service has launched.
Updated:
Subjects and places
Subject proposals
- AgricultureSuggested
- Preserved editorial category/topic; broad candidate onlywww.gov.uk ↗
Geographic references
Only source-provided geographic references are shown. Opening an external map is optional. Optional story maps use OpenStreetMap. Opening a map sends your IP address and this site’s address to the map provider; location data remains readable as text without loading the map.
- United Kingdom · Place role: Coverage · Place type: Country or area · Location precision: RegionalEvidence
- Explicit preserved editorial country/region; no city or national centroid inferredwww.gov.uk ↗