Casepoint targets public records sector with dedicated software release

Public authority document requests place relentless operational pressure on legal and governance departments. Whether dealing with Freedom of Information requests, Environmental Information Regulations, or Subject Access Requests under data protection rules, public bodies face statutory deadlines alongside heavy document volumes. Handling these exercises using standard office software or basic email search creates severe risks of missed deadlines, incomplete retrieval, or accidental disclosure of exempt material.

Specialist review tools originally developed for civil litigation disclosure offer an obvious answer to these data challenges. Legal technology providers have increasingly sought to package their core discovery tools into purpose-built platforms for statutory compliance. As reported by Doug Austin on eDiscovery Today, provider Casepoint has announced the launch of Casepoint Public Records, a release designed specifically for state, local, and education organisations.

The reported development

According to the report published by eDiscovery Today on 19 October 2026, Casepoint announced the launch of a new product offering named Casepoint Public Records. The product is aimed directly at public sector and educational entities managing public records requests.

The published reporting is brief. The notice confirms the market availability of the product and notes that it targets state, local, and education bodies. The extract does not provide technical specifications, detailed feature lists, pricing models, or jurisdictional availability outside the United States. It is not yet clear from the published information whether the release incorporates specific integrations with public records tracking portals, automated redaction engines, or modified review interfaces distinct from Casepoint's standard litigation review platform. What is clear from the announcement is that another major discovery software vendor is formally packaging its platform for public sector administrative records workflows rather than confining itself to court dispute discovery.

Public records requests versus traditional civil disclosure

From a practitioner perspective, public records handling shares core technical requirements with civil litigation disclosure under Practice Direction 57AD or civil inquiries. In both settings, legal teams must ingest multi-custodian data collections, process modern file types, deduplicate records, filter out irrelevant files, and run rigorous document review exercises.

However, statutory requests present operational constraints that differ markedly from standard dispute disclosure:

• Statutory time limits: In civil claims, parties can agree procedural extensions or apply to court for case management relief. Under statutory regimes like the UK Freedom of Information Act 2000, public authorities face strict twenty working day deadlines. There is no counterparty to negotiate procedural relief with.
• Proportionate processing: Cost-shifting mechanisms differ. Civil litigation permits arguments regarding proportionality and cost budgeting under CPR rules. In public records processing, public authorities must establish whether cost limits apply before undertaking extensive manual review.
• Granular exemption redaction: In litigation, redaction is typically confined to legal professional privilege or direct commercially sensitive third-party terms. Public records review demands granular redactions based on statutory exemptions, personal data of junior staff, or public interest balances, often requiring clear audit notes for every redacted box.

What this means in practice

For UK practitioners, in-house local authority solicitors, and forensic specialists advising public institutions, this vendor movement highlights practical steps to modernise information request handling.

1. Move statutory requests into structured review environments

Many public bodies still conduct information request review inside standard email clients or network file folders. This practice is dangerous. Documents are easily overlooked, attachments get detached, and metadata is frequently altered during handling. Applying structured review workflows - standard practice in commercial litigation - provides immediate defensibility. Case teams should process files through standardised indexing engines that generate MD5 hash values, preserve original parent-child relationships, and extract hidden system metadata.

2. Implement repeatable redaction workflows

Redaction failure is the most common cause of regulatory breach in public records handling. Staff who attempt to redact documents by drawing black rectangles in standard PDF viewers risk catastrophic data leaks if underlying text layers remain intact. Practitioners should demand that any review software applied to statutory requests flattens redactions completely upon export, strips underlying vector text, and retains an internal audit log of which reviewer applied each redaction code.

3. Standardise deduplication across repeat requests

Public authorities regularly receive overlapping requests targeting the same underlying subject matter, such as procurement exercises or planning decisions. Traditional filing systems force teams to re-collect and re-review identical documents repeatedly. In a modern discovery database, teams can retain document repositories where previous exemption calls and redaction templates are saved. This eliminates redundant manual review and ensures consistency across successive responses.

Evaluating vendor platforms for statutory workflows

As litigation software providers introduce offerings tailored to public sector workflows, legal and procurement teams must evaluate products against strict operational standards. A platform designed primarily for complex civil litigation may carry interface complexity that administrative teams find unwieldy.

When assessing products in this category, practitioners should test whether the platform supports rapid intake from modern collaboration tools, including Microsoft Teams chats and cloud storage repositories. They must also verify whether data hosting complies strictly with domestic data protection requirements, particularly for public bodies processing sensitive citizen information. The entry of established discovery platforms into this sector provides public sector teams with a viable route away from chaotic manual review, provided the underlying workflows are configured correctly from day one.