Clearbrief

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 product, and the architecture choice is itself the differentiator. Citation detection across a document, the patented semantic scoring that measures how well a sentence is supported by the page it cites, and concept search across uploaded discovery are all machine learning and natural language processing. The vendor deliberately does not use generative models for the checking function, stating that classic AI means the checking tool cannot itself introduce hallucinations, while shipping separate generative features for drafting. Remove the models and nothing remains but a Word toolbar. Worth recording plainly since the index grades AI centrality: not being generative is not the same as not being AI, and the distinction is the point of this product.

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 real, documented and mechanised, short of published measurement of the checker itself. The retrieval method is described concretely: citations are detected in the Word document, matched against caselaw databases through LexisNexis where the user holds a subscription and Fastcase and vLex where they do not, with proprietary Westlaw citations mapped across to those databases, and where a source cannot be displayed automatically the product still reports that the citation is verifiable and accepts a manual upload. Output grounds to sources the reader opens directly, with hyperlinks from every citation to the specific page and text. The failure mode is named rather than implied, and named unusually well: the vendor states that because the checking runs on classic AI rather than generative models there is no risk of the checker introducing hallucinations of its own, which is a disclosure about its own architecture that most vendors never make. What keeps this off an A is measurement of the product's own performance: searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no published false positive or false negative rate for citation detection, no accuracy figure for the semantic score, no test set and no independent evaluation.

Autonomy and Oversight Model

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

A real published commitment with concrete review surfaces, and the product exists to serve oversight rather than to reduce it. The vendor states that source linked outputs keep humans in control and the evidence in view, and the Cite Check Report is explicitly built for the partner signing a filing, listing every citation with hyperlinks so each flagged issue can be reviewed in context. The founder frames the problem as partners being sanctioned for citation errors they did not personally make, which is a supervision argument. Not located as of 29 Aug 2026: the threshold at which a semantic score is treated as low, whether that threshold is configurable, and what the vendor commits to when its own checker misses something. That last matters here more than for most, because a verification tool that fails silently leaves a lawyer more confident than before they used 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.

User categories and testimonials stand in for deployment evidence. The vendor states the product is used by courts, Am Law firms, government agencies, arbitrators and legal teams handling high stakes matters, which is a notable set because courts and arbitrators are adopters rather than customers in the ordinary sense, and an attributed testimonial describes the LexisNexis backed hallucination detection in practice. Searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no named organisation paired with figures and a date, no case study, and no assessable method. Categories of adopter are not the same as a named deployment.

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.

Substantive commitments resting on an architectural choice, short of the full picture. The strongest element is Bring Your Own Storage, an enterprise option under which all uploaded documents remain inside the organisation's own cloud storage environment, which answers the confidentiality question by removing the vendor from custody rather than by promising to be careful with it. The vendor states the product is built for sensitive privileged legal work with enterprise grade security, privacy and access controls, and that work stays in the environment the team and IT already trust. A policy of not using client data for model training is reported, though located in third party review material rather than on a vendor page reached in this pass. Two gaps hold this off an A. Retention and deletion terms for customers not using Bring Your Own Storage were not located. Attorney client privilege and work product are invoked as a description of the work rather than addressed as a handling question, and no segregation model between users or matters was located.

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.

Substantive engagement with the professional duty the product exists to serve, short of the specific limbs an A requires. The vendor publishes material on how large firms operationalise responsible AI through citation checking policies, describes the norm courts expect that every sentence carries a verifiable citation in a standardised format, and frames the risk in terms of sanctions and reputational damage to the signing partner. That is engagement with candour to the court and with supervision of others' work, which is more than a disclaimer and more than most records here manage. The audience is professional throughout, spanning litigators, in house teams, courts, arbitrators and government agencies, with no consumer surface located. Short of an A because competence is not addressed as such, no statement on the advice line was located, and no jurisdiction limits are stated beyond references to Bluebook and local style rules.

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.

A published position on responsible AI without a governance mechanism a buyer could audit. The vendor publishes on how firms should operationalise responsible AI through citation checking policies, and its architectural decision to keep generative models out of the verification path is a real governance choice with a stated rationale rather than a slogan. Searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no published AI governance framework, no AI management certification such as ISO 42001, no named owner of model governance, no pre release testing regime, and nothing on uneven output across matter types, parties or populations. For a scoring product the last is a live question: a semantic score that behaves differently across drafting styles or document types would be invisible to a user and nothing published addresses it.

AI Safety and Data Stewardship

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

A general posture with one strong architectural element and little published detail. Bring Your Own Storage is real and material, letting an organisation keep uploaded documents in its own cloud, and the vendor states it works with customer security and IT teams through procurement and review. Beyond that the published material is general: enterprise grade security, privacy and access controls that IT and security teams can trust. Searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no retention period, no deletion control, no encryption specifics, no named subprocessor list, and no incident or breach notification practice. Note also that published filings are hosted in the vendor's secure cloud for judges and clients to read, which is a second data location with no published terms attached to it.

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.

Searched the vendor site navigation, the blog, the sandbox site and trade coverage on 29 Aug 2026. No published indemnity, liability cap, carve out, warranty on output or insurance position was located, and no customer terms of service was located as published on the property. Recorded as a pure absence on the surfaces reached. The shape of the gap is worth naming: this product is bought specifically to prevent sanctionable citation errors reaching a filing, and it publishes nothing about what happens if it misses one. A verification tool carries a different recourse question from a drafting tool, because its value is the assurance itself.

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.

CORRECTED 29 Aug 2026 during the trust portal sweep. The previous note stated that no named document management connector such as iManage or NetDocuments was located. That was wrong. The vendor names four document repository integrations in its own published material: Relativity, iManage, NetDocuments and Clio, describing them as letting a firm leverage existing secure infrastructure while adding the verification layer on top. For a litigation verification product that is the right connector set, spanning the two dominant law firm document management systems, the dominant ediscovery platform and the dominant small firm practice management system, and it is a materially stronger position than the note previously recorded. The rest of the row stands and is why this remains B rather than A. Delivery is a native Microsoft Word add in rather than a connector alongside Word, which is where drafting and signing happen. Research integrations are named individually with their commercial terms stated: LexisNexis where the customer holds a subscription, Fastcase and vLex where no subscription is required, with proprietary Westlaw citations mapped across so they remain checkable. Not located as of 29 Aug 2026: an integrations index page, and per integration documentation describing what each connector moves, in which direction, and what an administrator configures. Named connectors without that documentation is the B band.

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.

Deployment model is stated clearly with a genuine customer controlled option, short of residency detail. Two models are published and the difference is meaningful: the standard cloud service, and an enterprise Bring Your Own Storage option under which uploaded documents remain in the organisation's own cloud storage environment, which the vendor presents as giving additional control over data residency and confidentiality. Customer held storage is a stronger answer than a region selector because the customer keeps custody. What is missing is the rest of the picture: searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no hosting provider for the standard service, no named regions, no tenancy model, and no statement of where processing happens as distinct from where documents are stored, which matters because processing occurs even when storage is the customer's.

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.

CORRECTED 29 Aug 2026 during the trust portal sweep. Previously recorded with the certification claim attributed to third party review material and the note stating it was not located on a vendor page. That was wrong: the vendor states SOC 2 Type 2 certification on its own blog, describing it as demonstrating that it meets rigorous data protection standards and helping a lawyer fulfil the duty to protect client confidentiality through verified security controls. Source basis corrected from third party to vendor published accordingly. Also stated by the vendor in the same material: the Bring Your Own Storage option, framed explicitly as letting a firm control where client data is stored to meet jurisdictional requirements or firm retention policies, which is the vendor connecting that feature to professional obligations rather than to convenience. The grade nonetheless remains C for the reasons originally given, none of which the correction touches: no coverage period, no audit scope, no report date, no named auditing firm, no trust portal and no published request route were located, and the vendor's stated diligence path is to work with a customer's security and IT teams through procurement, which is a sales linked route rather than a self serve one. A certification asserted on a marketing page without scope, currency or an evidence route is the C band.

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.

The architecture is described more clearly than most and the components are not named. Published and unusually specific: the verification path runs on classic machine learning and natural language processing rather than generative models, with a patented scoring system, so a buyer knows the checking function does not depend on a third party foundation model at all. Generative features exist separately for drafting. Searched the vendor site, the blog, the sandbox site and trade coverage on 29 Aug 2026 and located no named model or provider behind the generative features, no statement of where models run, no subprocessor list, and no commitment to notify customers when the supply chain changes. Knowing that the critical path avoids generative models is genuinely useful and is not the same as knowing what the rest of the stack is.

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.

Checked the vendor site navigation, the blog and the sandbox site on 29 Aug 2026. No pricing page was located, no rate is published, no unit of charge is stated and no tier structure appears on the surfaces reached. Third party review material states that pricing is custom quoted, which confirms the absence rather than filling it. Every commercial path located terminates in a demo or contact request. One published commercial fact worth recording, though it is not pricing: a recipient of a hyperlinked filing, including a judge or a client, does not need a Clearbrief subscription to open it.

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.

Segment coverage is described with substance and the practice focus is unusually well defined. The stated user set spans litigators, in house legal teams, courts, arbitrators and government agencies, and the inclusion of courts and arbitrators is distinctive: this is the only record on the index whose published adopters include the tribunal as well as the advocate. Practice focus is stated narrowly and consistently as fact intensive litigation documents, with named use cases covering briefs, tables of authorities, exhibit management, investigation reports for in house compliance teams, and real time trial support including cross examination outlines. Not located as of 29 Aug 2026: firm size segmentation, jurisdictional coverage beyond references to Bluebook and local style rules, and any statement of which document types or practice areas the product is not built for.