ProPlaintiff

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.

AI native by construction and explicit about the distinction. The vendor states it is built from the ground up as an AI native platform and is not layering AI onto outdated software, and the product surface bears that out: every named feature is generative or analytical rather than a form with a model attached, spanning demand letters, medical chronologies, document generation, summaries, review, media analysis, case analysis and a conversational assistant. The agentic framing is applied to case management itself rather than to a single document type, so the model layer is the operating logic of the system rather than a capability within it. Remove the models and what remains is a file store with a calendar. Sixth consecutive A on this axis in this category, and the pattern is now unbroken across every plaintiff side vendor built. Note the vendor's own framing of the AI as a force multiplier and digital assistant handling repetitive data heavy work, which is a centrality claim and a substitution disclaimer in the same breath.

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.

Grounding is claimed clearly and nothing behind it is published. The vendor states that demand letters cite specific medical records, bills and reports automatically, and that smart citations pull directly from the firm's uploaded files, which is the right architecture and describes citation to the case file rather than to invented sources. The vendor also publishes, in its own practitioner guidance, that good platforms log what data was used, what was generated and who approved it, and that this is the firm's defensibility. What is absent is any measurement or any specification of its own implementation: no accuracy figure, no extraction error rate, no evaluation, no description of what smart citations resolve to or how a user verifies one, and no statement of behaviour when records are incomplete or provider names are inconsistent, a failure mode the vendor's own content identifies as where platforms fall apart. Held at C rather than B because the peers graded B in this category publish a citation mechanism a reader can see operating, being page level links, hyperlinked navigation or a table of authorities, and here the mechanism is asserted rather than described. Checked the home page, the demand letters page, the blog library and the G2 listing on 29 Aug 2026.

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.

The clearest published oversight position in this category, stated as a rule rather than as reassurance. The vendor's own guidance states that attorney oversight is non negotiable, that AI drafts and attorneys approve, and that no compliant workflow skips that step. It further states that the firm owns the output and that a good platform logs what data was used, what was generated and who approved it. Alongside that, the product ships permission management and system activity logs, which are the mechanisms an approval record would run on. Separately the vendor disclaims substitution, framing the AI as a force multiplier freeing paralegals and attorneys for client communication, negotiation and trial preparation. Held at B rather than A because the rule is published as advice to the profession rather than as a specification of this product: nothing states that ProPlaintiff enforces an approval step, whether any generation can be sent without one, what the activity log actually captures, or whether the approval record the vendor says firms need is one this platform produces. A vendor that names the right standard and does not claim to meet it has done half of the work visibly.

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.

Nothing located. No customer or firm is named anywhere in vendor material, no case study, no usage figure, no time saving or outcome claim with or without methodology, no funding announcement, no independent analyst placement and no award. That is unusual for this category rather than typical: every other record built here publishes at least throughput figures, and three name customers or independent recognition. A G2 listing exists and carries vendor supplied product description rather than verified customer outcomes located in this pass. The vendor publishes a substantial practitioner content library and none of it contains a customer result. Checked the home page, the demand letters page, the case management page, the blog library, the G2 listing and the site navigation on 29 Aug 2026. Recorded as a documented absence across those surfaces rather than as a judgement about adoption, which cannot be assessed from public 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.

Basic protections are stated with one useful specific, and no privilege position exists. Published: HIPAA compliance with industry standard safeguards, encryption, storage in the United States, and access limited to authorised users at the firm, supported in product by permission management, system activity logs and secure case sharing. Naming United States storage is a concrete locational commitment most peers in this category do not make and it is credited. Against that: no SOC 2 or any independent attestation was located, no business associate agreement is offered despite the vendor's own guidance telling readers to choose HIPAA compliant platforms under a BAA, and no treatment of attorney client privilege or work product appears. Held at C rather than B because the peers at B in this category carry an independent attestation, a BAA, or both, and this record carries a self declared compliance posture with product features supporting it. Checked the home page, the case management page, the compliance and security references, the blog library and the site navigation on 29 Aug 2026.

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.

THE BEST POSITION ON THIS AXIS IN THE CATEGORY AND ONE OF THE BEST IN THE PULL. The vendor publishes, in its own practitioner guidance, that ABA Model Rules on competence and supervision apply to AI assisted drafting, that the firm owns the output, that attorney oversight is non negotiable and no compliant workflow skips the approval step, and that firms must verify jurisdictional variation in damages language, statutory references and negligence framing because those differ by state. It separately disclaims substitution, stating the AI does not replace human judgement and frames it as a force multiplier. Naming the specific rules that apply, identifying who carries the professional obligation, and flagging jurisdictional variation as the user's responsibility together constitute a real professional responsibility position rather than a disclaimer. Held at B rather than A because it is published as market education in a blog library rather than as a product commitment or a term: nothing binds the vendor to it, it is not surfaced in the product or in any agreement located, and no named bar authority beyond the ABA Model Rules is engaged. Every other record in this category grades D here.

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.

Nothing published about how the models are governed, evaluated or monitored. No AI policy, no model card, no bias or fairness testing, no evaluation methodology, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001. The vendor's own content acknowledges that AI medical record analysis accuracy has improved for platforms trained specifically on clinical and legal documents, which is an accuracy claim about the field rather than a disclosure about this system. The category risk applies unchanged: the platform generates demand letters anchoring damages including a justified pain and suffering valuation, by the vendor's own description, and any systematic tendency in how that valuation is framed falls on claimants. Sixth consecutive D on this axis in this category. Checked the home page, the product pages, the blog library, the G2 listing and the site navigation on 29 Aug 2026.

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.

Protection is stated with a locational specific and use is unaddressed. Published: data is encrypted, stored securely in the United States, accessible only to authorised users at the firm, with HIPAA compliance and industry standard safeguards. United States storage is a real commitment and is the concrete element here. What was not located: any statement on whether uploaded medical records, case files, generated chronologies or demand drafts are used to train or improve models, any retention period, any deletion right at matter close, and any description of what happens to firm saved templates and preferred language, which by the vendor's own description accumulate a firm's drafting patterns over time. Held at C rather than higher because the peers at B publish either an exercisable control such as manual deletion or an independent attestation covering the handling claims, and neither exists here. Checked the home page, the case management page, the compliance references and the site navigation on 29 Aug 2026.

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.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. The vendor's own guidance states that the firm owns the output, which is a clear allocation of responsibility to the customer and is the closest thing to a liability position in public material, and it is advice to the profession rather than a contractual term. Nothing addresses what happens when a generated demand misstates a treatment, when a citation resolves to the wrong record, or when a deadline generated by the AI calendar feature is wrong, which on a case management platform is a malpractice exposure rather than a drafting one. Checked the home page, the product pages, the blog library and the site navigation on 29 Aug 2026.

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.

Nothing available, and the vendor says so, which is why this is recorded as disclosure rather than silence. Published material describes future API integration, stating the capability as planned rather than delivered, and data migration is offered, which is a one time import path rather than an integration. No case management system, document management system or records retrieval integration is named, and the reason is structural rather than an oversight: this product is itself the case management platform, so it competes with Filevine, Litify, Clio and CasePeer rather than connecting to them. That positioning is coherent and it leaves a firm with no route to move data between this system and anything else on an ongoing basis. Compare Tavrn at B, naming four case management systems plus live API access. Checked the case management page, the home page, the product pages and the site navigation on 29 Aug 2026.

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.

A real residency statement with nothing behind it, and a deployment option named without detail. The vendor states that data is stored securely in the United States, which is a jurisdictional commitment rather than a gesture at secure cloud infrastructure and is more than most records in this category publish. Custom deployment is separately named as available for firm wide automation supporting hundreds of attorneys, which implies something beyond standard multi tenant provisioning and is not described. What is absent: no hosting provider named, no region or availability zone detail, no statement of whether custom deployment means dedicated infrastructure, a private instance or configuration, and no data processing description. Credited at C for the United States commitment and held there because a country is the beginning of a residency answer rather than the whole of it. Compare Supio at B, which names data centres in three countries against three matching regulatory regimes.

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.

No independent attestation of any kind was located, and the vendor's own guidance shows it knows what the standard is. Located: HIPAA compliance claimed with industry standard safeguards, encryption, United States storage, permission management, system activity logs and a stated secure and HIPAA compliant workflow. Not located: any SOC 2 of either type, any ISO certification, any named auditor, any examination scope or date, any business associate agreement offer, and any trust centre, security page or documentation request route. Under the three tier test the artifact is absent rather than gated. The gap is measured against the vendor's own published advice, which tells readers evaluating platforms to look for SOC 2 Type II, HIPAA compliance and GDPR adherence, and to safeguard privileged communications by choosing HIPAA compliant platforms under a BAA. On its own criteria this record would not clear the bar it sets for others. Fourth instance in the pull of a vendor advising buyers to demand what it does not publish, after LinkSquares, FinregE and DigitalOwl.

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 located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. The vendor's own practitioner content discusses general assistants including named commercial models and advises that firms require approved confidentiality controls before those touch case files, which demonstrates awareness that the identity of the model matters and stops short of identifying its own. For a platform processing protected health information under a claimed HIPAA posture, every processor touching that data is a question a firm's diligence asks and none can be answered from public material. Checked the home page, the product pages, the blog library, the G2 listing and the site navigation on 29 Aug 2026.

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 published at any level. No price, no range, no tier structure and no unit of charge, and no indication of how custom deployment for hundreds of attorneys prices relative to a solo practitioner, despite both being named as target buyers, which is a wide span to leave entirely unpriced. No independent estimate was located either, unlike several peers in this category where third party reconstructions exist. The contingency fee point recorded across this category applies: case costs are advanced against a claimant's recovery, so undisclosed cost is undisclosed cost to an injured person. Checked the home page, the product pages, the pricing navigation and the site navigation on 29 Aug 2026.

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.

Functional breadth is wide, practice scope is narrow and honestly stated, and the coverage that matters for a case management platform is not characterised. Functional coverage is the broadest claimed in this category, running from intake through litigation across case management, calendaring and deadlines, document generation and review, media analysis, chronologies, demands and analytics in one system. Practice scope is plaintiff side personal injury, stated plainly, with solo attorneys, paralegals and firms of hundreds of attorneys all named as buyers. Held at C rather than B because nothing is characterised at the level a buyer checks: no jurisdictional coverage is stated despite the vendor's own guidance warning that damages language, statutory references and negligence framing vary by state, no statement of which record types or formats the medical analysis handles, and no indication of practice sub areas such as mass tort or medical malpractice. For a platform that is the firm's system of record, coverage claims need boundaries and none are given.