EvenUp

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 models are the entire product and the company was built around a proprietary dataset to feed them. Piai is named as EvenUp's own AI engine and the vendor's central technical claim is that it is trained on a large personal injury specific dataset rather than adapted from a general model, which is the same shape as Jhana.ai: build the corpus first, then the models, then the interface. Every deliverable is model output. Medical chronologies are generated from raw records with treatment timelines and ICD extraction, demand letters are generated end to end, case valuations are derived from a settlement repository, and analytics sit on top of the extracted data. Remove the models and nothing remains but a document store the firm already had. Independent review material reaches the same conclusion from outside, describing it as a vertical drafting engine trained on injury cases rather than a general legal assistant. Fourth A on this axis in the pull, after Reveal, Jhana.ai and Descrybe.

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 structural and visible in the deliverable, and no measured figure is published by the vendor. Medical chronologies carry citations back to source documents so a reviewer can verify any entry against the underlying record, which is the correct architecture when the output is a factual account of someone's treatment. Demand packages cite comparable verdicts drawn from the settlement repository, so the valuation argument is traceable to named prior outcomes rather than asserted, and a Thomson Reuters and Westlaw integration supports legal citation. Held at B on two gaps. Two accuracy figures circulate in third party material and neither was located in vendor material with methodology attached: that chronologies capture over 90 percent of relevant medical information on first pass, and that demands are 69 percent more likely to reach policy limits. Both are the kind of number this axis exists to test and neither is published with a sample, baseline or definition, so neither is credited. And nothing states what the system does when a record is illegible, contradictory or missing, which in medical record work is the common case rather than the edge case.

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.

Oversight is sold as a product tier, which makes it inspectable rather than aspirational. Demands are offered across tiers running from instant AI generation through Express Demands to an expert reviewed tier where an in house team quality checks the document before delivery, and independent material notes the human quality assurance step adds turnaround time, which is the honest trade off made visible in the pricing structure. Output is consistently positioned as a draft with attorney review required. Held at B because the mechanics are not published: no statement of what the in house reviewers check or against what standard, no description of what distinguishes the tiers beyond speed, no confidence indication on generated content, and no account of what happens in the instant tier where no human sits between generation and the attorney's inbox. Same shape as Mitratech Managed Bill Review, where a documented human layer exists for customers who buy it and the unattended path is undescribed.

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.

Outcome claims are specific, named firms appear, and the strongest source available flags the whole class as vendor supplied. Reported: Lundy Law increasing output from about 30 to about 110 monthly demand packages after adopting AI tooling without adding staff, and J. Chrisp Law reclaiming 80 hours per case in paralegal time. Those are named firms with quantified operational change, which is better evidence than most of this index carries. The vendor level claim that demands are 69 percent more likely to reach policy limits is the most consequential figure attached to this product because it speaks to case outcome rather than throughput, and it carries no methodology, comparison group or sample. The independent guide reporting these figures states plainly that most such benchmarks come from vendor marketing and that results depend on case complexity and record volume. Held at B and recorded as Third Party Estimated on that footing: the adoption story is credible and consistently reported, and none of it was located as a vendor published case study with methodology on 29 Aug 2026.

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.

The strongest confidentiality evidence in this category and the first record on the index where a health specific credential is the load bearing one. This product ingests complete medical records, billing statements and treatment histories for injured claimants, so the confidential material is not only the client's legal matter but a third party's protected health information. Against that: an independently assessed HIPAA compliance attestation validating implemented safeguards for PHI, and a SOC 2 Type 2 examination whose named scope includes confidentiality and privacy as well as security and availability. The vendor also states it supports customers handling sensitive information through contractual, technical, organisational and compliance measures, which acknowledges the business associate relationship a plaintiff firm needs. Held at B rather than A because nothing addresses legal professional privilege or attorney work product specifically: a demand package is work product, the case strategy embedded in a valuation is privileged, and the published posture speaks to health data protection and general security without reaching the legal dimension at all.

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.

Not located in vendor material. The product generates the demand letter a firm sends to an insurer, which is an advocacy document making legal and valuation arguments on a client's behalf, and it generates the case valuation that shapes settlement advice. Independent material states consistently that output is a draft requiring attorney review, and that framing was not located as a vendor published position. Nothing addresses the supervising attorney's duty over machine drafted advocacy, the professional responsibility of relying on a machine generated valuation when advising a client whether to settle, or any bar guidance. The gap matters more here than on a research tool because the output goes out under the firm's name to an adverse party. Checked the product and blog material, the trust centre summary and the site navigation on 29 Aug 2026.

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 or evaluated. No AI policy, no model card, no bias or fairness testing, no evaluation methodology or result, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001. The untested risk on this product is specific and serious: case valuation is generated from a settlement repository of past outcomes, and historical personal injury settlements carry the demographic and geographic patterns of who was compensated well and who was not. A valuation engine trained on that history can reproduce those patterns for a new claimant while presenting the result as a data backed figure, and nothing published indicates whether that has ever been examined. Checked the product material, the blog including the compliance announcements, the trust centre summary 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.

Handling is credentialed and the training question is unanswered. The HIPAA attestation and the SOC 2 Type 2 privacy and confidentiality scope establish that safeguards over protected health information have been independently assessed, which is real stewardship evidence and more than most of this index carries. What was not located is any statement on whether medical records, demand drafts, case files or settlement outcomes submitted by firms are used to train or improve Piai, how long client content is retained, or whether a firm can require deletion. The question is unavoidable for this vendor rather than incidental: its central technical claim is a proprietary model trained on a large personal injury specific dataset, and nothing published states where that dataset came from or whether customer matters continue to feed it. A credential covering how data is protected is not a statement about what it is used for. Checked the trust centre summary, the compliance announcements, the product material 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 exposure profile is unusually concrete here: a missed injury, a misread treatment date or an omitted provider in a generated chronology flows straight into a demand letter and can understate a claim, and an understated demand that settles is a loss the claimant never learns about. A generated valuation that anchors a firm low has the same shape. No published vendor position addresses any of it, and the risk sits with the firm and ultimately the injured claimant. Checked the product material, the blog, the trust centre summary and the site navigation on 29 Aug 2026. Enterprise agreements govern this and are not public.

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.

One substantive integration is named and the connections this buyer needs most are not. Named: Thomson Reuters and Westlaw integration supporting legal citation inside generated demand packages, which is a real and unusual integration for a plaintiff side drafting tool and gives the citation layer an established source. What was not located: any named case management system integration, which for a personal injury firm is the connection that matters, since the practice runs on a case management platform holding intake, treatment tracking and deadlines. No API or export documentation was located either, and nothing describes how records get in or how a finished demand returns to the matter file. Independent comparison material in this category treats case management integration as a primary evaluation criterion, which makes its absence from located vendor material notable. Checked the product material, the trust centre summary 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.

Nothing located. No hosting provider is named, no region or data residency commitment is published, and no single tenant or dedicated instance option is described. For a platform holding protected health information for injured claimants, the location and tenancy of that data is a question a firm's own compliance review would ask directly, and the HIPAA attestation establishes that safeguards were assessed without stating where the data sits. Checked the product material, the trust centre summary, the compliance announcements and the site navigation on 29 Aug 2026. Correction candidate: the Trust Center operates a request access route which was not entered in this pass and is the surface most likely to hold residency detail.

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.

Scope, currency and a self serve route, which is the combination this axis rewards. A dedicated Trust Center operates at trust.evenuplaw.com describing security, privacy and compliance practices and offering a request access route to available documentation, which under the three tier test is a request flow rather than a sales gate. The attestation is named with its scope stated: a SOC 2 Type 2 examination covering security, availability, confidentiality and privacy, four of the five Trust Services Criteria and materially broader than a security only scope. Currency is addressed and dated, with recertification announced April 2026 rather than an undated claim. Alongside it a HIPAA compliance assessment and attestation, independently conducted, which is the credential this product actually needs given it processes protected health information, and the vendor correctly explains that HIPAA has no formal certification and that what exists is a third party attestation, which is an accurate distinction most vendors blur. Held short of a perfect record on one point: the auditing firm is not named for either the SOC 2 or the HIPAA assessment. Consistent with Lexis+ AI at A on scope, currency and portal, and below Exterro, whose FedRAMP status is verifiable in a public registry without any request at all.

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. Piai is named and claimed as proprietary, trained on a personal injury specific dataset, and that is a statement about ownership rather than about supply chain. No foundation model provider is named, nothing states whether third party models sit underneath Piai or process any part of the pipeline, no subprocessor list was located, and the Thomson Reuters and Westlaw integration establishes at least one external data relationship without any accompanying disclosure of what flows to it. For a product handling protected health information, the identity of every party in the processing chain is a question a firm's HIPAA business associate review asks directly and it cannot be answered from public material. Checked the product material, the compliance announcements, the trust centre summary 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. Independent review material describes the model as case based rather than seat based, which is a meaningful structural fact for a plaintiff firm because cost then scales with caseload rather than headcount, and notes that the platform only earns its keep at sufficient injury volume. None of that comes from the vendor: no price, no range, no per case figure, no tier structure and no indication of what a demand package costs. Every route is a sales conversation and an annual contract. The absence is heavier in this category than most, because contingency fee firms carry case costs themselves and a per case charge is a direct deduction from a claimant's eventual recovery. Checked the product material, the pricing navigation and independent review material 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.

Depth in one practice area, stated plainly, with the boundary acknowledged rather than obscured. The vendor is explicit that it builds for plaintiff side personal injury and nothing else, and independent review confirms it is not a general legal assistant. Within that scope the coverage is genuinely deep: police reports, medical records, billing statements, photographs and intake notes as inputs, demand letters, chronologies, case valuations, negotiation preparation and caseload analytics as outputs, and a settlement repository supporting jurisdictional comparables. Single practice specialisation is a design decision rather than a coverage failure and is credited as such. Held at B rather than A because the corpus behind the differentiator is not characterised: no statement of how many verdicts or settlements the repository holds, which jurisdictions it covers, what date range, how often it updates, or whether coverage is deep enough in a given venue for a comparable to carry weight, which is exactly what an attorney relying on that citation in negotiation needs to know.