T
Tavrn
Tavrn is an AI case preparation platform for personal injury litigation, founded in 2022 and built around medical record retrieval, on the premise that records are where cases stall. Client Intake extracts facts from each lead and scores cases on a numeric scale with configurable thresholds. Medical Record Retrieval uses agentic workflows and AI voice agents that contact providers the same day a request is placed and keep going until all requested files, including bills and imaging, arrive.
It covers thousands of providers in all fifty states and delivers records into the case file already organized, named and tagged. MedChrons turns records into hyperlinked chronologies with page classification and Bates stamping, and demand letters are drafted from the same structured data using firm templates. Practice coverage spans personal injury, medical malpractice, workers compensation, SSDI and general liability.
Integrations are named with Filevine, Litify and Clio, among others, and API access is offered. Tavrn claims a SOC 2 Type II attestation and offers a business associate agreement for HIPAA workflows. Funding totals about $38m, including a $15m Series A led by Left Lane Capital in July 2025. A free trial is offered and pricing is not published.
Tavrn, head to head
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Alternatives to Tavrn
Vendors in the same categories as Tavrn whose graded profiles look most alike, with a line on what each product does.
Similar is not the same, so check that each one does the job you need. No vendor pays for placement.
- SSupioSupio is an agentic AI platform built only for plaintiff personal injury and mass tort firms, covering the case from intake through litigation.
- DDigitalOwlDigitalOwl analyzes medical records with AI for both legal and insurance professionals.
- EEvenUpEvenUp is a vertical AI platform built only for plaintiff personal injury firms, marketed as a Claims Intelligence Platform.
- LLegalyzeLegalyze is an AI medical record review and chronology platform for plaintiff personal injury, medical malpractice and workers compensation practices.
- AAnytime AIAnytime AI is an agentic AI platform sold only to plaintiff law firms, covering a case from intake through settlement.
- EEveEve is an AI platform for plaintiff law firms, covering the case from intake to resolution.
Ordered by how closely the graded profiles match across the 15 capability axes, inside the same categories. See how each axis is graded in the methodology.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
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.
Models have been at the center since founding, and the retrieval layer shows it most clearly. AI voice agents contact medical providers the same day a request is placed and keep calling until records arrive, across thousands of providers in all fifty states. That is a model acting in the world on the firm's behalf rather than analyzing documents it was handed, and it is the part of the product a firm cannot replicate without the models.
Downstream, page classification and indexing sort document types, chronologies are generated, intake scoring extracts facts and classifies injury severity, and demand letters are generated from the structured output of the pipeline. Remove the models and what remains is a fax inbox.
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 at page level, reinforced by owning the pipeline, and unmeasured. Chronology entries link back to the specific source page, output is stated to link directly to its source, and every page carries a Bates number. The vendor argues that because one platform retrieved the records, classified the pages and built the timeline, the structured data carries into the demand without manual rekeying. That avoids a model drafting from unstructured files and misstating what the records show.
Nothing is quantified: no extraction accuracy, page classification error rate, recall on treatment events, measure of whether retrieval obtained the complete file, or evaluation of any kind.
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.
Visibility is documented and boundaries are not. For retrieval, the vendor publishes complete oversight to create and track requests, real time status tracking on every request, all fax and email inbounds in one place, and real time editing control over generated demand letters. A firm can see what the system is doing at any moment, but not what it may do unattended. The voice agents call providers and persist until records arrive, acting on a firm's behalf toward third parties that hold a claimant's health information.
Nothing published says what an agent may say, whether it identifies itself as automated, what happens when a provider disputes a request, or where a person must step in. Tracking an action after the fact does not bound it.
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.
Operational figures are specific and no customer can be identified. Published figures include 50 to 70 percent reductions in record review time, average retrieval turnaround cut by 12 days and chronologies delivered in under 24 hours. No law firm is named anywhere in located material. The one return on investment claim, a reported 6x return on platform cost within a single quarter, carries the note that the testimonial is on file, so the vendor states the evidence exists and does not show it.
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.
A business associate agreement is offered for HIPAA workflows, and privilege itself is not addressed. A BAA is the contract HIPAA requires between a covered entity and a business associate handling protected health information, so offering one goes beyond stating HIPAA compliance: it is a document a firm can execute. The vendor also claims a SOC 2 Type II attestation and publishes its encryption standards. Nothing treats attorney client privilege or work product, or the confidentiality of the demand strategy and case valuation the platform generates.
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. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
No position is published on two features that raise the question. The platform scores incoming cases on a numeric scale with configurable thresholds, a machine assessment feeding the decision whether to accept a client, and nothing addresses the attorney's role in it. Generated demand letters go out under the firm's name to adverse insurers. No statement says output is not legal advice, and nothing addresses the supervising attorney's duty.
AI Governance and Bias Disclosure
Published governance over model behavior: 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 is published on how the models are governed, evaluated or monitored. There is no AI policy, model card, bias or fairness testing, evaluation method, accuracy monitoring, drift statement, named governance body or ISO 42001. Intake scoring shows why this matters: it assigns a numeric case score with configurable thresholds from extracted facts and injury severity, so a model helps decide which injured people a firm takes on.
Any systematic tendency in that scoring falls on prospective claimants who are never told a score existed, and nothing published shows it has been examined.
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 specified precisely, and use of the data is not addressed. The vendor publishes AES 256 bit encryption for stored data, TLS 1.2 for network traffic in transit and a secure upload portal. Training use, retention and deletion of the records it holds are not covered by any published statement. The vendor retrieves records itself, directly from providers, so it is the original recipient of claimant health information rather than a processor of files a firm already had.
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 position is published beyond the BAA, which allocates HIPAA obligations rather than product liability. Nothing was found on liability for AI output, warranty, service levels or remedy. The retrieval layer's failure mode is an incomplete file rather than a wrong sentence: a chronology built on records never obtained will look complete and consistent while omitting a whole course of treatment. Nothing published addresses what happens when retrieval misses a provider, and no service level commitment is published for a platform sold on turnaround time. The retrieval and products pages held nothing further.
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.
Four case management systems are named, among them Filevine, Litify and Smokeball, and the Smokeball link is confirmed by a listing in Smokeball's own partner marketplace. API access is offered for systems without a native connector. Records are delivered organized, named and tagged directly into the case file. No API documentation is published, nothing says what moves in which direction with any named system, and no authentication, permission or field mapping detail is published.
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.
No hosting provider, region, residency commitment or dedicated instance option is published. Security material refers in passing to a broader cloud environment without naming it. The platform retrieves claimant medical records from providers nationwide and holds them, and the BAA governs obligations, not where that data sits or how it is separated. Security material and navigation showed nothing more on 29 August 2026.
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.
A SOC 2 Type II attestation is claimed, and the vendor's own wording is inconsistent. One set of material states the Type II attestation; other material describes the same posture as a security program aligned with SOC 2 criteria and HIPAA compliance standards. Alignment with criteria is a self assessment, while a Type II attestation is an independent examination over a period, so the two statements describe different things.
No auditing firm, examination period or date is published, and no trust center or route to request documentation is published.
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.
No foundation model provider, model family or version is named, no subprocessor list was found, and nothing says whether outside models sit under any component. The product runs several distinct kinds of model work: voice agents making telephone calls to providers, page classification, chronology generation, intake scoring and drafting. No speech provider is identified for the voice agents. Under a BAA, every subprocessor touching protected health information is a party the covered entity is entitled to know about, and none can be identified from public material.
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 price is published at any level. A free trial lets a firm evaluate the product without a sales conversation, but a trial shows the product, not the price. No figure, range, tier structure or unit of charge is published, and nothing says whether pricing runs per record page, per request or per seat, which for a retrieval product are very different economics. Independent material describes the target as contingency fee practices that need predictable costs. In contingency work, an undisclosed cost per case is an undisclosed cost to an injured claimant.
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 wide and operational reach is stated in numbers, though the reach is asserted rather than characterized. Five practice areas are named, from personal injury and medical malpractice to SSDI, so disability and compensation work with different record profiles is included. Retrieval covers thousands of providers nationwide across all fifty states, at roughly 1,000 requests a day, through fax, email and portal channels.
Independent material puts the target firm size at roughly 10 to 75 professionals. No provider network is listed or described, no retrieval success rate is published, and nothing shows whether coverage is even across states.
1 public document
The public pages on file for Tavrn, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
tavrn.ai1 signal
Client Data in Training
Read Aug 29, 2026
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A published agreement or policy exists and none of it addresses the question either way, or the document that would answer it could not be read and the summary names the retrieval limit. The summary states which shape the silence takes: an improvement right granted that never names training, or no improvement right granted at all.
No statement was located in either direction on whether the records, chronologies, demands or intake data the vendor holds are used to train or improve any model. Its most specific data statement describes encryption at rest, not purpose. The BAA governs permitted uses and disclosures under the agreement and makes no public statement about model training. The vendor accumulates claimant records across every firm it serves.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
No located public material states how long prompts and outputs are retained.
No retention period is published for retrieved medical records, generated chronologies, demand drafts or intake scoring data, and nothing says whether a firm can require deletion at matter close or settlement. Because the vendor holds records it obtained from providers itself, deleting them from a firm's own case management system does not reach the vendor's copy. Checked on 29 August 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
No located public material addresses walls or matter level segregation.
No permission model, matter level access restriction or tenant segregation was described. The platform connects to four case management systems that carry their own permission models, and nothing says whether Tavrn inherits them or applies its own. Retrieval runs at volume for many firms through shared fax and email inbound channels, and nothing published says how inbound records are matched to the right firm and matter or what prevents misrouting. The retrieval page and product pages showed nothing on this as of 29 August 2026.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
No government or law enforcement request clause, commitment to notify a customer before producing data, or transparency report was located. A BAA governs permitted disclosures between the parties and is not a public notice commitment. Holding claimant medical records retrieved from providers in every state makes the vendor a single point of access to health information for many claimants at once. Checked as of 29 August 2026.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
No external legal source applies, since the platform works on the customer's own case records rather than published law. What the models were built on is not stated. Page classification, injury severity classification and chronology construction all work on clinical documentation, and no published statement says whether their training data was licensed, synthetic, publicly sourced or drawn from records retrieved for customers.
That last possibility is the one a claimant would care about, and it is neither confirmed nor excluded. Checked against the products and MedChrons pages and the blog on 29 August 2026.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
The question barely applies, because the outputs rest on facts rather than authority. Chronologies summarize treatment, and demand letters are said to draw on injuries, treatments and damages taken from the records themselves. No research provider or citator is named, and no legal authority appears in the described output. Demand letters in practice often cite authority on liability, and nothing published says whether this product does or where it would source it.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
No behavior is described for uncertain or incomplete output, and one published phrase gestures at it without substance. The vendor says that where doubt is expected, proof is embedded, but nothing states whether a low confidence extraction is flagged, a gap in the treatment timeline surfaced, an illegible page reported, or an answer declined. Nothing describes the result when a provider cannot be reached or returns an incomplete file, or whether the resulting chronology is marked as built on partial records.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
General web searches on 29 August 2026 combining the vendor and product names with court, order, sanction, fabricated citation and demand letter terms returned nothing, and no named docket database or court record tracker was searched. This states what that search found and is not a clearance. Output goes to insurers rather than courts, so the nearer risk is a misstated treatment fact, or a chronology entry attributed to a source page that does not support it.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
No ethics opinion, ABA Formal Opinion 512, state bar guidance or professional conduct rule is engaged. The vendor publishes a substantial blog library comparing tools and advising firms on adopting AI in personal injury practice, but it covers the buying decision, not the professional duties that attach to it. The blog index and main site pages were checked on 29 August 2026.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
Savings are claimed, and the claimant's side is not addressed. Beside its time savings figures, the vendor publishes a return on investment claim whose supporting testimonial it says is on file but does not show. Nothing says whether platform cost is a case expense or firm overhead in contingency work, no disclosure guidance is published, and no record shows what portion of a demand was generated by a machine.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The material exists behind a sales conversation or an executed agreement.
The BAA is the one instrument on offer, and nothing is open to read. A firm can obtain and sign it for HIPAA workflows. There is no subprocessor list, named model provider, trust center, downloadable summary or published route to request the SOC 2 report.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Some elements of the record are available, short of a document level export.
Bates stamping and source links make part of the record citable. Chronology entries link to specific source pages, and Bates stamping gives every page a stable identifier, the convention litigation uses to cite a document in a filing, deposition or production, so an opposing party or court can locate the page independently. Nothing indicates that output records which model generated it, and no human verification record is kept.
Nothing in the described output shows which providers were asked for records, which responded and which did not, so a party cannot show that the record set behind a chronology is complete.