Practical guide

Legal AI source verification: a review checklist.

A useful legal AI answer gives your team a way to check the record. Use this workflow to review the sources behind a summary, comparison or possible discrepancy before the result informs further work.

1. Define the question and the records in scope

Name the matter or contact, the time period and the information needed. “What changed in this matter since Monday?” has a different scope from “What is missing before the demand?” A reviewer needs to know which question the answer is attempting to address.

Identify the connected systems that were actually used. A summary based on a case record does not establish what happened in a separate CRM or phone system. Missing information should remain a visible open question.

2. Open the source behind a factual statement

Follow the available reference back to the original record. Confirm the matter identifier, the document or field, and the relevant passage. Check that the source supports the statement being made, including its qualifications and context.

A reference makes review possible; it is not proof of accuracy by itself. If the reference is unclear or the source cannot be located, treat the factual statement as unverified.

  • Does the source belong to the right matter, lead or contact?
  • Does it address the same event and time period?
  • Is the statement supported by the original record in context?
  • Are later updates or contradictory records relevant?

3. Separate recorded facts from interpretation

A source may record that a bill was requested. That is different from establishing that the bill was received, reviewed or complete. Look for the exact claim the record supports instead of allowing a concise summary to blur those steps.

When two records differ, keep both references available. A possible mismatch tells the reviewer where to look. The team must determine whether it reflects an error, a later update or two sources describing different things.

4. Keep gaps and open questions visible

List information that was unavailable, a source that could not be checked and differences that remain unresolved. A short answer can be useful while still being incomplete. The handoff should make that limitation clear to the next person.

For a repeated workflow, define what a reviewer must check before accepting the output. Use the same question and expected evidence when evaluating changes to the setup.

5. Decide the next step through professional review

MatterMind retrieves and compares information for review. Attorneys and staff decide what the record means and whether follow-up or a correction is needed. MatterMind does not provide legal advice.

Source verification is one part of evaluating a connected AI setup. Also establish what information the tools may retrieve, what actions are allowed and what data-handling terms apply. Refer to each provider’s current documentation for controls beyond those confirmed on this site.

Connected tools.
Human judgment.

Join the waitlist to get updates on access to MatterMind.

Join the waitlist

Illustrative · fictional matter

The record behind the answer

Fictional source excerpts for this website example. No client records are connected.

Filevine · Medicals

Matter #2024-0187. Harbor Orthopedics final bills: requested October 14, 2024; not received.

Filevine · Damages

Matter #2024-0187. Wage-loss documentation: employer letter outstanding.

Police_Report.pdf · page 2

Illustrative report excerpt: “Date of collision: March 12, 2024.” The fictional Filevine field reads March 14, 2024. An attorney must review the original evidence.