Case Status

AI Centrality

How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.

The product was a client portal before it was an AI product and the portal still stands on its own. Real-time case status, the branded passwordless app, secure messaging, document upload, stage videos and NPS-driven review prompts are all conventional software, and the CMS sync that feeds them is an integration rather than a model. On top of that sits a named set of model-driven features the vendor sells individually: Agentic AI Translation, Agentic AI Case Summary, Agentic AI Response and Prioritization, an AI Triage Agent, AI Automation Agents and Client Sentiment Tracking. That is the B band: the models power a core capability layered on a product that would still function without them as a communication and status system. Pages read 1 September 2026.

Citation Accuracy and Hallucination Disclosure

Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.

Nothing published on accuracy or grounding for a system that drafts and translates messages sent to represented clients. The home page, the security commitment page, the Terms of Use and its Limitation on Liability subpage and the privacy notice were read on 1 September 2026; no accuracy figure, no evaluation, no test set, no error rate and no description of how a drafted reply is grounded in the case record was located. The exposure is specific rather than theoretical: Agentic AI Translation renders a firm's message into another language for a client who by definition cannot check it against the original, and Agentic AI Case Summary condenses a matter for a lay reader. D rather than C because C requires accuracy to at least be asserted or grounding to be claimed, and neither was found; the individual AI feature pages were not opened and are the rebuttal route.

Autonomy and Oversight Model

What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.

A review point is published and the rest of the control structure is not. The home page states that Case Status uses case context to suggest responses that staff can review and send in seconds, which places a human between the model and the client on the drafting path, and the Agentic AI Response and Prioritization feature is described as ranking messages by urgency for staff rather than acting on them. Against that, the product also markets AI Automation Agents and a claim that up to 80% of routine client communication is handled automatically, which implies messages reaching clients without a per-message review, and nothing published reconciles the two or says which categories run unattended. No threshold, no escalation route and no statement of what happens after a wrong message is sent were located on 1 September 2026. B on the strength of the stated review-before-send point, held there by the unexplained automation claim.

Operational and Outcome Evidence

Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.

One named firm with a dated figure, and everything else anonymised. Pond Lehocky is named on the home page with close to 15,000 active clients using the app across its workers compensation and social security disability departments, and a before-and-after review metric with a stated window: 4.6 with 417 reviews before, 4.8 with more than 3,000 reviews within 24 months. Shawn Lehocky, Chief Executive Officer at Pond Lehocky Giordano, appears on record. The three growth case studies are deliberately unattributed, identified only by practice and city: an SSD firm in Charleston WV doubling caseload in a year, a PI firm in Chicago at 40% year-over-year growth, a large PI firm in Kansas City with a 35% increase in case velocity. Firm count is internally inconsistent, 600-plus in the page header and more than 500 in the body. B: real deployment evidence with substance, short of full attribution. G2 ratings, badges and review quotes were excluded as directory material.

Privilege and Confidentiality Posture

How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.

Confidentiality is asserted in general terms while the instrument that would carry it is absent. The security commitment page describes multiple layers of encryption, least-privilege development, mandatory two-factor authentication, background checks and ongoing security training, and the GDPR section states plainly that Case Status acts as a data processor for law firms. But no law firm customer agreement is published anywhere: the only agreement on the site is End User Terms of Use binding the firm's clients. Nothing addresses training on client content, matter or tenant segregation, or privilege and work product, which matters here because the platform carries attorney-client communications by its own description. The privacy notice also grants the app access to contacts, microphone, calendar, reminders, SMS messages and continuous geolocation, a permission scope wider than a case-status app needs, and nothing published explains why. C.

UPL and Professional Responsibility Posture

Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point.

Nothing published on the advice line for a product that generates and translates messages to represented clients. This is the category where that matters most, because the reader is a claimant who cannot judge whether what arrives is legal advice. No disclaimer of any kind, no statement that AI-generated or AI-translated content is not legal advice, no requirement that a firm disclose AI involvement to its client, and no reference to ABA Formal Opinion 512 or any state bar guidance was located across the home page, security commitment page, privacy notice, the Terms of Use and its Limitation on Liability subpage on 1 September 2026. The End User Terms do address the reader as a client, and they use that space to disclaim liability rather than to explain what the technology does. The individual AI feature pages were not opened and are the rebuttal route.

AI Governance and Bias Disclosure

Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

No governance position located. There is no responsible AI page, no named accountable owner for the AI, no pre-release testing regime and no ISO 42001 or equivalent across every surface read on 1 September 2026. The security commitment page names a Chief Technology Officer, Charles Lane, and the privacy notice names a Data Protection Officer, Andy Seavers, but both are framed around information security and privacy rather than model governance. Nothing addresses whether sentiment scoring, urgency ranking or translation quality behaves evenly across languages or client populations, which is the live question for a product whose clients include immigration and workers compensation claimants communicating in languages the firm may not read. Security certifications are a different subject under this band and are graded on Security Certifications.

AI Safety and Data Stewardship

Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.

A generic privacy notice plus a narrative security page, with the operative details missing or blank. What is published: multiple layers of encryption, least privilege, mandatory two-factor authentication, password and lockout policies, employee background checks, ongoing security training, AWS hosting, and continuous compliance monitoring through Secureframe. What is not: no subprocessor list of any kind, no incident or breach notification practice, and no retention period. The retention section is the specific finding, and it is unusual enough to name. Under the heading on how long information is kept, the privacy notice of 17 July 2025 reads that no purpose in the notice will require keeping personal information for longer than, and the sentence simply ends. The number is missing from the published document. Deletion is committed to once no legitimate business need remains, with an exception preserved for backup archives. C.

AI Liability and Recourse

What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.

A published allocation that is total, uncapped, and pointed at the wrong party. The Limitation on Liability subpage excludes liability for damages of any kind under any legal theory arising from use or inability to use the service, direct or indirect, whether in negligence or contract and even if foreseeable, expressly naming personal injury, pain and suffering, emotional distress, loss of data and loss of goodwill among the excluded categories. There is no cap, because there is no fee: these are End User Terms binding the law firm's client, not the firm. That the excluded heads of damage are personal injury, pain and suffering and emotional distress, in a product sold into personal injury, workers compensation, disability and mass tort practice, is worth a buyer reading twice. No firm-facing agreement, indemnity, warranty on output or insurance position is published. C rather than D because a specific and readable allocation exists; C rather than B because nothing runs toward either the firm or its client.

Practice Systems Integration Depth

How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.

The integration set is the strongest part of the product proposition and is named in full. Thirteen case management platforms are listed with individual integration pages: Clio, Litify, MyCase, Neos by Assembly, Filevine, CASEpeer, SmartAdvocate, SmokeBall, PracticePanther, CoCounselor, Meruscase, Docketwise and Salesforce. Eight of those are systems this index already covers, which tells a buyer the product genuinely sits in the plaintiff and small-firm stack rather than beside it. The positioning is explicit and useful: Case Status describes itself as the communication layer living inside the case management platform, with staff working where they always have and everything syncing automatically, and one published customer account describes it running inside Litify in a frame. B rather than A because what syncs, in which direction and what a firm must configure is not described on any page read on 1 September 2026; the individual integration pages were not opened and are the rebuttal route.

Deployment Model and Data Residency

Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.

Cloud delivery is named and neither dimension a buyer needs is stated. The security commitment page states that Case Status runs on Amazon Web Services and describes the reasoning as scale and redundancy rather than as a tenancy architecture. The privacy notice states that servers are located in the United States and that information from users outside the US will be transferred to and processed there, which fixes a default location but is not a residency offering. No tenancy model is published, no region option is offered, and processing location is not distinguished from storage. For a product whose stated practice areas include immigration, and whose users therefore include clients outside the United States, the absence of any region choice is worth noting. C on the band's words: cloud delivery is evident and neither the tenancy model nor a selectable region is stated.

Security Certifications and Trust Center

Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.

The best attestation particulars located in this pull, with no way to obtain the report. The security commitment page names the auditor, Modern Assurance, describes it as an independent third-party accounting and auditing firm, states the scope as all five trust services criteria by name (security, confidentiality, availability, privacy and processing integrity), and gives completion dates for both audits: SOC 2 Type I in September 2023 and SOC 2 Type II in July 2024. HIPAA compliance is claimed on the basis that legal practices serve clients who are also patients, and Secureframe is named for continuous monitoring. Two things hold this at B. There is no trust centre or portal and no stated route by which a buyer could request any report, so the evidence is described rather than accessible. And the most recent attestation stated is now over two years old, with the commitment to ongoing audits expressed as intention rather than as a published subsequent report.

Model Supply Chain Disclosure

Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.

Nothing published about the model supply chain a customer inherits. The product markets six separately named AI capabilities and an entire Data and Agentic AI solution page, and across every surface read on 1 September 2026 no model, no model provider, no inference location and no change-notification commitment appears. There is no subprocessor list of any kind on the site, which is the ordinary route to this disclosure and which several vendors in this pull publish openly. AWS is named on the security commitment page but hosting answers where the software runs rather than whose model reads client messages, and cannot be spent here. D rather than C because C requires the vendor at least to refer to the models underneath in some form, and no reference to a model layer was located at all.

Commercial Transparency

Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.

No pricing information at any level. There is no pricing page: the navigation, the footer and the resource menus were checked on 1 September 2026 across the home page, the security commitment page, the terms index, the Limitation on Liability subpage and the privacy notice, and none carries a pricing entry. No tier names, no packaging structure, no unit of charge and no figure are published, and every commercial route is a demo booking, a tour or a calendar link. D rather than C because C requires the shape to be visible with only the number withheld, and here neither is. Under the pricing-row rule there is no published structure, so no VendorPricing row was written.

Firm and Practice Coverage

Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.

Practice coverage is unusually specific and firm segmentation is not. Eight practice areas each have their own page with copy describing the work: personal injury, workers compensation, immigration, employment, disability, mass tort, estate planning and criminal. That is a real statement of where the product is aimed, and it is coherent, since all eight are high-volume matters where a client waits a long time with little news. What is missing is the other half of the band: no firm-size segmentation, no in-house or government position, and no statement of where the product stops. The customer evidence points at plaintiff-side and claimant-side firms of varying size but the vendor never says so directly. B rather than A because the limits are not stated.