Eve vs EvenUp: how they compare in 2026

AI native from founding and now architecturally explicit about it. The company was founded in 2020 to build this and has no preceding product to attach models to. The January 2026 relaunch as an AI Workforce is built around three coordinated agent roles, Agents, Auditor and Analyst, and the June 2026 EveOS launch positions the platform as an AI native operating layer for the firm rather than a tool inside one. Every deliverable is generated: intake evaluation, medical overviews, demand letters, complaints and discovery responses on both sides of the request. The system is also stated to adapt to a firm's writing style with use, which is model behaviour rather than configuration. Remove the models and nothing remains. Sixth A on this axis in the pull and the third consecutive one in this category, which now looks structural rather than coincidental: every plaintiff side vendor built so far was model first, because the underlying task of reading medical records at volume was never automatable any other way.

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.

Grounding is architectural, verification is built into the interface, and no measurement is published. The vendor states that all sources for Eve's answers are referenced with links back to the firm's own documents, that the system proactively validates its responses, and that a user can verify a response in one click. Proactive validation is a stronger claim than passive citation because it describes the system checking itself rather than only showing its work, and the Auditor agent role introduced in the January 2026 AI Workforce release suggests that checking is a named component rather than a background behaviour. Held at B because none of it is quantified or specified: no accuracy figure, no extraction recall on medical records, no hallucination rate, no evaluation, no description of what proactive validation actually tests or what happens when validation fails, and no statement of behaviour when the underlying records are incomplete or contradictory. A named auditor agent with no published output is a claim about architecture rather than evidence of accuracy.

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.

The most autonomous product in this category and the most explicit about it, with the oversight built as a role rather than asserted as a principle. The AI Workforce is described as three coordinated agents that advance cases proactively rather than waiting for attorney prompts, which is a real autonomy claim stated plainly rather than hedged, and EveOS extends that to an operational layer. The Auditor role is the notable design decision: a checking function is a named part of the workforce rather than a caveat, which is the correct architecture for autonomous case advancement. Held at B because the boundaries are entirely undescribed. Nothing states what an agent may do without attorney approval, whether anything is sent or filed unattended, what triggers Auditor review, what standard it applies, what happens when Agent and Auditor disagree, or how a firm configures the limits. Proactive advancement of a live case is the highest autonomy claim on this index and it arrives without a single published bound.

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.

The first A on this axis in the pull, and it is earned on the combination rather than on any single item. Scale is published and dated: more than 450 firms, more than 350 added in eight months, more than 200,000 legal cases processed annually, and firms collectively recovering more than $3.5 billion in settlements and judgments, all stated in a dated September 2025 funding announcement. Named customers with quantified outcomes and attributed comment: Frontier Law Center, with managing partner Manny Starr quoted by name in a named publication in March 2026, reporting intake conversion rising from 10 percent to 35 percent, intake process time falling by 50 minutes per call, and average case value increasing 90 percent. James Scott Farrin attorneys completing medical chronologies in minutes that previously took weeks. A separate verified user report of case capacity increasing up to 2.5 times without adding staff. An outsider can name the firm, name the partner, find the publication and check the date without contacting the vendor, which is the bar this axis sets. The figures still carry no methodology or baseline, and the $3.5 billion recovery total is a sum over customer outcomes rather than a demonstrated causal contribution, so the note records what the numbers are and are 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.

THE FIRST RECORD IN 42 TO ADDRESS ATTORNEY CLIENT PRIVILEGE DIRECTLY. Every other vendor on this index, including the two plaintiff side competitors already built, graded C or B here on general security credentials with privilege simply unmentioned. Eve states that the platform is built with attorney client privilege as a first principle, that case data is never used to train shared models, and that data is kept strictly isolated to the firm at organisation, user and workflow levels. Three named isolation levels is a specification rather than an assurance, and workflow level isolation in particular addresses the case where one matter's content should not surface inside another. Paired with the credentials this category actually needs: SOC 2 Type 2 certification, HIPAA compliance for the claimant protected health information the product ingests, and AES-256 end to end encryption. Graded A because it is strictly more than the B records in this category, which carry the same class of credential without any privilege position at all. The isolation architecture is asserted rather than documented and no privilege specific attestation exists, which is why the note says so, but the ladder has to reward a vendor that answers the question over vendors that do not acknowledge it.

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.

Not located, and the gap is wider here than on any other record in this category because the autonomy claim is larger. Agents are stated to advance cases proactively without waiting for attorney prompts, and the product drafts complaints and discovery responses, which are filed documents bearing an attorney's signature and certification. Nothing published addresses the supervising attorney's duty over proactively advanced casework, what an attorney is certifying when signing a machine drafted pleading, the professional responsibility dimension of generated discovery responses, or any bar guidance. The Auditor agent is a quality mechanism inside the product and not a statement about the lawyer's own obligations. Checked the home page, the working with Eve page, the product material, the press coverage of both 2026 launches and the site navigation on 29 Aug 2026.

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.

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 or result, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001. The category risk flagged on EvenUp and Supio applies here with an additional dimension: this product performs case evaluation and identifies missed case value, so it makes judgements about what a claim is worth, and it does so inside an agent architecture that advances cases proactively. A systematic tendency in valuation would propagate through 200,000 cases annually without an attorney necessarily prompting the judgement that produced it. The Auditor agent checks output within the system and is not an independent evaluation of the models. Checked the home page, the working with Eve page, the press coverage and the site navigation on 29 Aug 2026.

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.

A genuine stewardship position, disclosed with a qualifier the vendor did not have to admit. Stated: case data is encrypted with AES-256 end to end, never used to train shared models, and kept strictly isolated to the firm at organisation, user and workflow levels. Separately and openly stated: the system learns a firm's tone, preferred language and style and adapts further with use. Those two statements are consistent and together describe a specific architecture, being firm scoped adaptation with no cross customer pooling, and disclosing the second alongside the first is more candid than the vendors who state a training commitment and leave the learning behaviour unmentioned. Held at B rather than A because the specification stops short: no retention period is published for case content or generated output, no deletion right at matter close is described, nothing states whether firm scoped adaptation can be disabled, and nothing describes what happens to an adapted model when a firm terminates. HIPAA compliance covers protection of the claimant health data rather than its use.

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.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. The exposure is the largest in this category because the autonomy is: agents that advance cases proactively can act on a matter without an attorney initiating the step, and the product drafts pleadings and discovery responses subject to filing deadlines and certification requirements. A missed deadline, a defective discovery response or an understated case valuation all carry consequences that fall on the firm and ultimately on the injured claimant, and no published vendor position addresses any of them. Checked the home page, the working with Eve page, the press coverage and the site navigation on 29 Aug 2026. Enterprise agreements govern this and are not public.

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.

Nothing located, and this grade carries the weakest research basis on the record. No case management system integration, no document management connector, no records retrieval integration, no research provider and no API documentation were found across the home page, the working with Eve page, the product material, the press coverage of the AI Workforce and EveOS launches and the site navigation checked on 29 Aug 2026. The positioning offers one possible explanation and is not treated as an answer: EveOS is described as an AI native operational platform for the firm, which suggests the product intends to be the operating layer rather than a component that plugs into one, and a system positioned to replace the operational stack has less need to integrate with it. That is inference and is not credited. Recorded as a documented absence across the surfaces actually checked and flagged as the strongest correction candidate on this record. Compare Supio at B, which names Litify, MyCase and CasePeer.

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.

Nothing located beyond a generic phrase. Secure cloud infrastructure is stated and names no provider, no region and no residency commitment, and no single tenant or dedicated instance option is described. The firm level isolation the vendor does describe is a logical separation claim rather than a deployment or residency statement, and the two should not be conflated: isolated to your firm says nothing about which jurisdiction the data sits in. For a platform holding claimant protected health information at the scale of 200,000 cases annually, residency is a question a firm's own compliance review asks directly. Checked the home page, the working with Eve page, the press coverage and the site navigation on 29 Aug 2026. Compare Supio at B, which states data centres in three named countries.

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.

Named certifications with an annual cadence stated, and no route to anything underneath them. Published: SOC 2 Type 2 certification, HIPAA compliance, AES-256 end to end encryption, secure cloud infrastructure, and the statement that policies are vetted annually by independent audits, which addresses currency in a way most records in this category do not. Held at B rather than A on the familiar three absences: no auditing firm is named, no examination period, scope or certificate date is published, and no trust centre, security page or self serve documentation request route was located, so under the three tier test the artifact is absent rather than gated. One claim recorded and not credited: the vendor describes itself as the first legal AI to be SOC 2 Type 2 certified. That is a priority superlative rather than a security fact, it is not checkable from any published source, and it says nothing about the current scope or rigour of the examination. Calibration within this category: EvenUp reaches A on a Trust Center with a request route and a dated recertification; Eve and Supio both sit at B with claims and no route.

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.

Nothing located. No foundation model provider, model family or version is named, nothing states whether third party models sit underneath the agent architecture, and no subprocessor list was found. The commitment that case data is never used to train shared models establishes that a distinction between shared and firm scoped models exists in the architecture without identifying what either is built on. For a platform processing protected health information across 200,000 cases annually, the identity of every processor in the chain is a question a firm's HIPAA business associate diligence asks directly and it cannot be answered from public material. Checked the home page, the working with Eve page, the press coverage of both 2026 launches and the site navigation on 29 Aug 2026.

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.

No pricing published at any level. No price, no range, no unit of charge, and no indication of whether the model is per seat, per case, per matter or per firm, which matters because the product is positioned as an operational platform rather than a per document tool and the pricing unit would signal which. Independent material notes that the target segment is small to medium plaintiff firms without any published attorney count, revenue band or case volume threshold defining it, so a firm cannot self assess fit either. The contingency fee point recorded on EvenUp and Supio applies equally: case costs are advanced against a claimant's recovery, so undisclosed pricing is undisclosed cost to an injured person. Checked the home page, the pricing navigation, the working with Eve page and independent review material on 29 Aug 2026.

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.

Lifecycle coverage is the broadest in this category and the practice boundary is stated honestly. Coverage runs intake through resolution rather than centring on one document type: intake and case evaluation, medical overviews and chronologies, demand letters, complaints, and both propounding and responding to discovery, which is wider than either competitor built so far and includes the litigation phase rather than stopping at the demand. Practice areas named are personal injury as the primary vertical with medical malpractice, employment and general litigation, and independent review confirms no evidence of family, criminal, intellectual property or transactional work, so the scope claim holds. Held at B rather than A because the firm segment is asserted without definition, with independent material noting that the small to medium target is stated with no attorney count, revenue band or case volume threshold, and because nothing characterises depth: no record types or formats handled, no jurisdictional scope for the drafting, and no indication of whether discovery coverage extends across state and federal practice.

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.

Policy never for shared models, with firm scoped learning disclosed rather than hidden, which is the most fully specified position on this signal in the pull. READ THE QUALIFIER, then read what the vendor volunteers next to it. The quoted commitment is scoped to shared models, and the same page separately states that Eve learns a firm's tone, preferred language and style and adapts further with use. Those two statements are consistent and together describe firm scoped adaptation with no cross customer pooling, which is a real architecture rather than a hedge. What separates this from the LinkSquares pattern is candour: LinkSquares scoped its never to third party and public models and said nothing about its own, while Eve scopes its never to shared models and then openly describes the learning that happens inside the firm boundary. Isolation is specified at organisation, user and workflow levels. Held short of a stronger value because it is policy rather than contract, no opt out from firm scoped adaptation is described, no retention period is published, and nothing states what happens to an adapted model when a firm leaves.

Silent. The quoted phrase is the stated scope of the SOC 2 Type 2 examination and it is the strongest data protection evidence on this record, but an examination of controls is not a statement of purpose: it establishes that safeguards over customer content were assessed, not what that content is used for. No statement was located in either direction on whether medical records, demand drafts, case files or settlement outcomes submitted by firms are used to train or improve Piai. The silence is conspicuous rather than ordinary here, because the vendor's 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. Recorded as silent, not as a negative commitment. Correction candidate: the Trust Center request access route was not entered in this pass. Checked the compliance announcements, the trust centre summary, the product material and the site navigation on 29 Aug 2026.

Not addressed. No retention period is published for case files, medical records, generated demands, complaints or discovery responses, and nothing indicates whether a firm can require deletion at matter close. Retention has an extra dimension on this record because the vendor states the system adapts to a firm's writing style with use, which implies persistence of something derived from the firm's content beyond the individual matter, and nothing describes what that derived state is, how long it lives, or whether it can be reset. Checked the home page, the working with Eve page, the press coverage and the site navigation on 29 Aug 2026.

Not addressed. No retention period is published for uploaded medical records, generated chronologies, demand drafts or case valuations, and nothing indicates whether a firm can require deletion at matter close. Retention has a statutory dimension on this product that it does not have elsewhere on the index: the content is protected health information belonging to a third party claimant, and HIPAA safeguards address how it is protected rather than how long a business associate keeps it. Nothing published closes that. Checked the trust centre summary, the compliance announcements, the product material and the site navigation on 29 Aug 2026.

Claimed and not documented, and it is the most specific claim of its kind in the pull. The vendor states that data is kept strictly isolated to the firm at organisation, user and workflow levels, which names three distinct boundaries rather than asserting isolation generically, and workflow level isolation is the one that speaks to matter separation directly. That specificity is why this records as claimed rather than as not addressed. What is missing is any documentation behind it: no description of how the boundaries are enforced, whether user level isolation means retrieval respects the asking user's permissions, whether a matter can be walled from other users within the same firm, or how the agent architecture interacts with those boundaries when agents advance cases proactively across a caseload. No document management system integration exists to inherit permissions from. Checked the home page, the working with Eve page and the press coverage on 29 Aug 2026.

Not addressed. No permission model, matter level access restriction or tenant segregation description was located. The question has an unusual edge on this product: the settlement repository is a shared benchmarking asset drawn from past outcomes, and nothing published describes the boundary between one firm's case data and the pooled comparables sold to every other firm, including opposing firms working the same venues. A plaintiff firm's settlement history is competitively sensitive as well as confidential. No document management system integration exists to inherit permissions from. Checked the product material, the trust centre summary and the site navigation on 29 Aug 2026.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The vendor holds claimant protected health information, unfiled pleadings and discovery work product across more than 450 firms and 200,000 cases annually, so a request served on the vendor rather than on a firm would reach material a firm would otherwise be positioned to resist producing. Checked the home page, the working with Eve page, the press coverage and the site navigation on 29 Aug 2026.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The stakes are higher than the usual case because the vendor holds protected health information and unfiled demand material for claimants in active disputes, and a subpoena to the vendor rather than the firm would reach work product the firm would otherwise resist producing. Checked the trust centre summary, the compliance announcements and the site navigation on 29 Aug 2026.

Not addressed, and largely inapplicable in the usual sense with one live residue. The platform operates on the firm's own case files, medical records and documents rather than on a published law corpus, so there is no external legal source to name, license or date. The residue is what the underlying models were built on. The product drafts complaints and discovery responses, which requires familiarity with pleading conventions and procedural rules, and it performs case evaluation, which implies exposure to outcome data, and nothing published states what corpus supports either. Unlike EvenUp, no settlement or verdict repository is named as a distinct asset, so the basis for case value identification is unstated as well as unsourced. Checked the home page, the working with Eve page, the product material and the press coverage on 29 Aug 2026.

Named without a licence basis, and the named corpus is the product's differentiator. The Settlement Repository is described as a database of past settlements used for benchmarking and case valuation, and comparable verdicts from it are cited directly inside demand packages, so the corpus is not background infrastructure but the substance of the argument sent to an insurer. What is absent is everything a practitioner relying on that citation would check: no count of verdicts or settlements held, no jurisdictional coverage, no date range, no update frequency, and no statement of the basis on which the outcomes were obtained, whether public court records, customer contributed results, or licensed data. Piai is separately claimed as trained on a large personal injury specific dataset whose provenance is also unstated. Two corpora, both central, neither sourced.

Not addressed, and applicable rather than a scope fact. The product drafts complaints and discovery responses, which cite legal authority and are filed with courts, so a currency question genuinely arises and the stakes are higher than for the demand only products in this category since the output reaches a docket. Nothing published names a citator, a research provider or any treatment checking step, and unlike EvenUp and Supio no Thomson Reuters or Westlaw integration was located, so it is not clear from public material what source supports legal citation in generated pleadings at all. Third record in this category where this signal is live and the third to leave it unanswered. Checked the home page, the working with Eve page, the product material and the press coverage on 29 Aug 2026.

Not addressed. The product does cite legal authority, through a Thomson Reuters and Westlaw integration supporting citation inside demand packages, so unlike TrialView or Exterro this signal is applicable rather than a scope fact. Nothing published indicates whether cited authority is checked for current treatment, whether an overruled or superseded case would be flagged before it reaches a demand letter, or whether the Westlaw integration includes KeyCite treatment data or only citation retrieval. Comparable verdicts drawn from the settlement repository are outcomes rather than authority and carry no treatment question, but the legal citations in a demand do. Checked the product material, the integration references and the site navigation on 29 Aug 2026.

Not addressed, with one architectural component that gets close and stops short. The vendor states that Eve proactively validates its responses and enables one click verification, and the January 2026 AI Workforce release names an Auditor agent as one of three coordinated roles. Both describe checking rather than uncertainty behaviour: nothing states what happens when validation fails, whether the system declines to answer, flags low confidence, surfaces a gap in the medical record, or proceeds and marks the output. For an architecture where agents advance cases proactively without attorney prompting, the behaviour under uncertainty is the load bearing question, because an unprompted action taken on a weak inference is the failure mode a lawyer would never see coming. Checked the home page, the working with Eve page and the press coverage of both 2026 launches on 29 Aug 2026.

Not addressed. Nothing published describes an explicit no answer path, abstention behaviour or confidence signal. The gap is specific to medical record work: records arrive illegible, contradictory, incomplete or out of order as a matter of routine, and nothing states whether the system flags a gap in the treatment timeline, marks a low confidence extraction, or silently produces a clean looking chronology from an incomplete file. Independent material notes that missed items and misinterpretations occur in complex cases with extensive treatment histories, which confirms the failure mode exists without the vendor describing how it is surfaced. A chronology that looks complete and is not is the most dangerous output this product can produce. Checked the product material, the trust centre summary and the site navigation on 29 Aug 2026.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, fabricated citation and pleading terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. Recorded as a statement about what this search found and not as a clearance. The exposure shape is the broadest in this category: this product drafts complaints and discovery responses that are filed with courts under an attorney's signature rather than demand letters sent to insurers, so a defective citation would reach a docket directly and become part of the public record. Flagged as the strongest candidate in this category for a proper docket search on a later pass.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, fabricated citation and demand letter terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. Recorded as a statement about what this search found and not as a clearance. Worth flagging the exposure shape for a later pass with a proper docket instrument: this product generates documents citing both legal authority and comparable verdicts, sent to adverse parties, so both a fabricated case and a fabricated or misdescribed comparable would be discoverable in the record if either had occurred.

Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located. Relevance is at its highest in this category: the product drafts pleadings and discovery responses filed under an attorney's certification and operates an agent architecture that advances cases without prompting, which engages competence, supervision and candour duties simultaneously. Checked the home page, the working with Eve page, the product material, the press coverage and the site navigation on 29 Aug 2026.

Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located. The relevance is direct rather than theoretical: the product drafts the advocacy document a firm sends under its own name and generates the valuation informing settlement advice to a client, both of which sit squarely inside the competence and supervision duties bar guidance on AI addresses. Checked the product material, the blog, the trust centre summary and the site navigation on 29 Aug 2026.

Savings claims only, and the published figures reach further than throughput. Reported: intake conversion rising from 10 percent to 35 percent and intake process time falling by 50 minutes per call at a named firm, case capacity increasing up to 2.5 times without added staff, and average case value increasing 90 percent. The last of those is a claim about client recovery rather than firm efficiency, which is unusual and consequential, and it carries no methodology, baseline or comparison group. Nothing appears on the client's side of the equation: no position on whether platform cost is a case expense or firm overhead in contingency work, no disclosure guidance, and no record a firm could produce showing what portion of a demand, complaint or discovery response was machine generated. Checked the home page, the working with Eve page and independent review material on 29 Aug 2026.

Not addressed, and the omission carries more weight in this category than any other on the index. Personal injury work is contingency fee work: the firm advances case costs and recovers them from the claimant's settlement, so a per case charge for AI generated demand packages is money that comes out of an injured person's recovery. Nothing published addresses whether the platform's per case cost is treated as a case expense or firm overhead, how it should be disclosed to a client, or what record a firm could produce showing what portion of a demand was machine generated. Reported time savings of 80 hours per case describe the firm's side of the equation only. Checked the product material, the pricing navigation and independent review material on 29 Aug 2026.

Not addressed. Certifications are claimed, being SOC 2 Type 2 and HIPAA, alongside AES-256 encryption and annually audited policies, which gives a firm citable content for a client questionnaire. No route to anything underneath was located: no trust centre, no security page, no request path for the SOC 2 report, no subprocessor list, no named model provider and no business associate agreement material. A firm could repeat the claims and could not evidence them or answer which third parties process claimant health data. Recorded as not addressed on the same basis as Supio, and the distinction from EvenUp at on request remains the existence of a request route rather than the strength of the claims. Checked the home page, the working with Eve page and the site navigation on 29 Aug 2026.

On request, through a real route with the credential this buyer actually needs. The Trust Center at trust.evenuplaw.com offers a request access path to available documentation, and behind it sit a SOC 2 Type 2 examination scoped to security, availability, confidentiality and privacy, recertified April 2026, and a HIPAA compliance attestation. For a plaintiff firm that must satisfy itself about a business associate handling claimant protected health information, that is the pack the diligence actually calls for and there is a defined place to request it. Held at on request rather than higher because nothing is published open: no subprocessor list, no named model provider, no downloadable summary and no business associate agreement template were located outside the gate, and the gate itself was not entered in this pass so the contents are unverified.

Partial record. The source trail is real: all sources for Eve's answers are stated to be referenced with links back to the firm's own documents, with one click verification, so a party can show what a factual assertion rests on and open the underlying record. The two familiar limbs are missing and one of them matters more here than anywhere else in this category. Nothing indicates that output records which model generated it, and no human verification record is captured, so a firm cannot evidence that an attorney reviewed a machine drafted pleading before filing it. That is the exact question a standing order on AI use in court filings asks, and this is the only product in the category that drafts complaints and discovery responses reaching a docket rather than demand letters reaching an insurer. The Auditor agent performs checking inside the system and no artifact of that check is described as reaching the customer or the court.

Partial record, strong on the source trail and silent on the machine's own involvement. Medical chronologies carry citations back to source documents so any entry can be verified against the underlying record, and demand packages cite comparable verdicts from the settlement repository, so a firm can show what a factual assertion or a valuation argument rests on. That is the sources retrieved limb answered properly. The other two limbs are absent: nothing indicates that output records which model generated it, and no human verification record is captured, including for the expert reviewed tier where an in house team demonstrably does check the document before delivery and no artifact of that check appears to reach the customer. A demand package is a pre litigation document, so the forum here is a claim file or a subsequent suit rather than a standing order, and the same question applies in either.