Harvey AI Review: UK Legal Research, Vault and Workflow Risks

JSH LAW / LEGAL AI PRODUCT RESEARCH

England and Wales perspective · Sources reviewed 23 October 2026 · Documentary assessment

What Harvey is—and what a practice would be buying

Harvey is developed by the specialist supplier Harvey. It is a professional platform, with its own document repositories, interfaces and contractual arrangements. It should not be treated as another name for a consumer ChatGPT account, even where underlying language-model technology overlaps.

The official getting-started guide, updated on 7 October 2026, describes Assistant, Vault, Workflows, History and Library. The current Harvey website also presents a wider platform spanning agents, knowledge, collaboration and business workflows. Those descriptions establish the vendor’s current proposition; they do not establish that every module is included in a particular quotation.

A sensible procurement exercise starts with a named task and an agreed scope. “We want Harvey” is less useful than “we need to review recurring disclosure collections without losing the connection between each proposed fact and its source”. The latter gives the supplier something testable to demonstrate.

The difference between Assistant, Vault and a workflow

This distinction matters because a fluent response can conceal the wrong tool selection. The getting-started guide expressly cautions that Assistant is optimised for extracting relevant information rather than detecting inconsistencies across documents. It directs version-change work towards the redline-analysis workflow. A buyer should therefore resist a demonstration that treats ordinary chat as proof of comprehensive contradiction detection.

The guide also cautions about numerical work. Financial extractions need a separate calculation check; a retrieved number is not a verified computation. That is particularly important where a table of values could influence a commercial decision or a financial-remedy position.

How credible is the England and Wales research proposition?

Harvey documents selectable knowledge sources alongside uploaded material and web search. The decisive question is the actual collection available to the proposed users: judgments, legislation, procedural rules, commentary, update frequency and any separate publisher entitlement.

We could not independently inspect the complete regional knowledge-source inventory because that linked help page required authentication. We therefore do not certify comprehensive English or Welsh coverage. Ask for a dated source schedule and demonstrate a research question that needs both the controlling rule and its exception. A source catalogue is more useful than an assurance that the system “knows UK law”.

Keep four checks separate: does the authority exist; is the cited passage accurate; does it support the proposition; and is it still applicable? An answer can pass the first check and fail the other three. A tool that retrieves a genuine case about a different procedural setting has not completed the legal analysis.

For domestic work, specify England and Wales rather than the UK alone. Scotland, Northern Ireland and overseas jurisdictions have different legal systems. Cross-border material can be useful, but it needs to be identified as comparative material rather than quietly presented as binding domestic law.

Two realistic workflows worth demonstrating

Hypothetical 1: a portfolio of commercial agreements

A legal team receives forty invented supplier agreements, a current procurement playbook and several amendments. The proposed exercise is to extract renewal dates, liability caps, change-of-control wording and departures from the approved position. Each table entry must identify the clause and the relevant agreement version.

The difficult cases should include a renewal term changed by an amendment, an unsigned draft and a liability provision with different caps for different losses. The human baseline records those exceptions before the AI run. Otherwise, a neat table may appear accurate simply because nobody has checked the awkward documents.

Success would mean a reviewer can open the source quickly, understand the qualification and correct the table without reconstructing the whole exercise. It would not mean accepting every suggested redline or allowing a commercial concession to become the firm’s standard position automatically.

Hypothetical 2: organising a litigation record

Use a wholly synthetic file with dated emails, a later account of an earlier event, an undated note and a document that records an allegation. Ask for a chronology with separate columns for event date, document date, source location, evidence status and unresolved questions.

This is a proposed pilot, not a claim that Harvey completed it. In particular, the team should test whether the selected workflow preserves the difference between a contemporaneous record and a retrospective assertion. An AI-generated sentence saying an event “happened” is unacceptable if the source only says one party alleges it happened.

Integration, collaboration and getting the work back out

The current platform overview advertises connected workflows and collaboration. A procurement team should map those claims to its own document-management system, identity service and existing information barriers. A connector that works in a demonstration may require a different licence, administrator consent or additional implementation work.

Ask the supplier to export the actual pilot deliverable. Does the spreadsheet preserve source links? Does a Word document retain usable citations and changes? Can another reviewer distinguish a generated draft from an approved version? Can a matter be archived and reopened without silently relying on outdated instructions?

Do not substitute a universal file-count claim for a proper capacity test. Document size, scans, tables, image-only pages, language, processing failures and the selected workflow all affect usability. We have not verified a single file limit that applies to every Harvey configuration; that belongs in the written specification.

Confidentiality: a strong supplier promise still needs a defined scope

Harvey’s security page describes SSO, audit logs, retention controls, regional hosting options and information-barrier enforcement. It states that inputs, outputs and uploaded documents are not used to train underlying models. These are supplier statements; JSH Law has not examined the underlying audit reports or negotiated the contractual commitments.

The useful follow-up is not another security badge. It is a data-flow account covering uploaded documents, prompts, outputs, support access, connected sources and subprocessors. Ask where processing occurs, which regional options apply to the purchased service and what survives deletion in backups or logs.

Where a tool can search across a firm’s knowledge, permissions become part of the legal workflow. A restricted matter should not be retrievable through a different client’s query, shared workspace or saved example. Test an unauthorised account as well as an authorised one.

For family proceedings, confidential court material and children’s information require particular care. A lawful reason to possess papers is not automatically authority to transmit them to another processor. Use synthetic material for evaluation; assess the applicable court rules, orders and data-protection position before any live deployment. The research hub’s governance section explains the common checks.

Pricing and the implementation cost that a seat price misses

We did not verify a generally applicable public UK tariff in the official material reviewed. Treat Harvey as a quotation-based purchase and request the actual commercial schedule. Do not rely on an unattributed internet estimate of a monthly seat price.

The quotation should separate user licences, knowledge-source entitlements, integrations, onboarding, storage or processing allowances, support, minimum commitments, renewal terms and exit assistance. Ask whether a trial includes the same features that would be delivered after purchase.

Measure value using completed, checked work. An illustrative calculation is: reviewer time avoided, less correction time, training time and ongoing administration. Any hourly value used in that calculation is the buyer’s assumption, not a demonstrated Harvey saving. A platform can be impressive yet uneconomic where the practice has too little repeat work to recover implementation costs.

A trial that could justify a purchase

1. Select one recurring document task and one research task with known answers.
2. Build synthetic inputs with amendments, missing dates and deliberately conflicting accounts.
3. Record the product modules, source selections, permissions and configuration.
4. Check every material output against the original source and log omissions as well as inventions.
5. Repeat with a changed governing-law clause or revised factual document.
6. Export the result, test access restrictions and demonstrate deletion.
7. Compare total reviewed effort with the existing method before expanding use.

An invented authority, an undisclosed processing failure or access across a prohibited matter boundary should stop that part of the pilot. A good result on a small sample supports a limited next stage; it does not certify every future matter.

Alternatives and JSH Law’s assessment

Legora is a relevant comparison where collaborative, table-based review is the main problem. CoCounsel Legal and Lexis+ with Protégé deserve consideration where a particular publisher’s UK research collection is central. Compare the actual licensed configurations rather than their most ambitious marketing pages.

Our assessment: Harvey merits a controlled professional pilot where repeated, high-volume analysis and drafting justify the governance effort. The purchase case is weaker where the need is occasional writing assistance, a small bundle or an individual’s understanding of family procedure. Its value depends on a functioning chain from input to source to human approval—not the confidence of the prose.

Can Harvey replace a legal database?

Only the available sources and the work required can answer that. Confirm the research entitlements and maintain a way to inspect authoritative originals. We have not verified universal replacement coverage.

Does a source link establish that an answer is correct?

No. It makes checking possible. The reviewer still needs to read the source, its qualification and the surrounding legal context.

Sources and methodology

This review uses the Harvey getting-started guide, platform material and security disclosures, checked on 23 October 2026. Feature descriptions are documentary evidence of the supplier’s offering; performance and security claims have not been independently tested here. The regional source inventory and customer-specific contract were not accessible. Recheck after a material source, model, workflow, pricing or security change.

For common legal safeguards, see the SRA’s AI warning and our research hub and its full evaluation methodology. The examples above are invented test designs, not real client matters or completed demonstrations.

If your immediate problem is an AI-produced chronology or draft that needs organising against the original family-court papers, JSH Law’s court-document support may be relevant. Book a Consultation to identify a defined task; do not send a case file through a public enquiry form.