Using Legal AI When the Matter File Is Incomplete
Use a partial record without making it sound complete. Define the supplied material, preserve unknowns and turn gaps into specific document requests.
A first document packet is often enough to start useful work and insufficient to finish the factual account. The problem is allowing a fluent answer to make that boundary disappear.
You can organize the available material, identify what it supports and prepare targeted requests for more records. You should avoid turning the absence of a document into a conclusion about what happened.
This article concerns work at the start of a partial record. When additional records arrive after you have already prepared work, use the separate new-document review guide.
Define the supplied record before asking for a summary
Write a short scope note. Name the packet, its received date, the relevant period and any known limits. Keep a file list or other record that lets a reviewer understand what was available.
Distinguish what was supplied from what was usable. An unreadable attachment, inaccessible link or unprocessed scan should not be counted as material the answer has assessed. Check the service's actual file status and verify important passages yourself.
A fictional scope note
Place the scope note before the findings and keep it with the account when the work is reused.
Choose a task the partial record can support
An initial packet can support an inventory, a list of attributed accounts, a chronology of events recorded in the supplied material or a set of questions for the next discussion.
It may not support a final factual conclusion, a complete liability analysis or an assurance that no relevant event occurred. Choose the output accordingly. A useful first note can say what is known and identify the records needed next.
The ABA's July 2024 opinion keeps professional judgment and task-appropriate review with the lawyer. NIST's July 2024 generative AI profile addresses confabulation and the need to account for system limits. The method here applies those concerns to a partial factual record; it is not a regulator's prescribed checklist. 1 2
Separate support, disagreement and absence
Keep three kinds of finding distinct. Supported findings describe what a supplied record establishes, with attribution and qualifications where needed. Contested findings show competing accounts. Unknowns identify what the available material cannot establish.
Do not put every unknown into a chronology as if it were an event. Do not let “no record found” become “did not happen.” A search result describes the search and available material; it may not describe the full history of the matter.
The example below uses fictional records. The faulty draft sentence is authored for this article, not taken from a product test.
Fictional example: missing signed version
This preserves the lead provided by the email without inventing the contents of the missing record.
Turn a gap into a specific request
“Need more documents” is difficult to act on. Identify the question, the record that may answer it, who may hold it and why it matters to the next piece of work.
For the missing signed version, a useful request names the email and attachment: obtain the attachment sent with the 7 October email, together with any available execution record. The purpose is to check the version, signatories and dates before stating which terms were executed.
Sometimes you will not know the document title or custodian. Record that uncertainty rather than guessing. Ask the responsible person to identify the relevant record or confirm what search was made. Do not describe the request as proof that the document exists.
Prioritize gaps that could change the immediate decision. A missing executed agreement may matter before drafting an account of the agreed terms. A minor naming inconsistency may be resolved later, provided it is not confused with a different person or entity.
Ask for a bounded answer
Use a prompt that limits the account to supplied records and makes unknowns visible. A prompt is an instruction to the tool, not proof of retrieval coverage or compliance.
Work within the supplied packet
Check the answer against the packet. Check its file list as well as its conclusions. A tool may fail to identify a missing attachment or may present a narrow search as though it covered every document.
Keep the available record and open questions together.
Decide what must stop
Before using the note, identify the conclusions that depend on unresolved material. Keep those conclusions out of an external draft, or qualify them appropriately after professional review. A clear scope note does not cure an unsupported statement later in the document.
If the missing material affects the purpose of the task, pause that part of the task and request it. Continue work that the available record can support. Record who owns the request and when the position will be reviewed.
The same boundary matters when delegating work to another lawyer or an AI-enabled workflow. The assignment should name the permitted inputs, unresolved questions, expected output and the conditions requiring escalation. The legal AI agents article explains those assignment and permission limits.
Preserve the boundary when the note travels
A working note can become misleading when copied into an email, meeting pack or handover without its limits. Keep material unknowns beside the relevant finding. Make the scope note visible wherever the account is reused.
For a structured output, use the source-linked matter brief guide. For a handover, include the outstanding record requests and their owners, using the matter handover guide.
When more material arrives, assess which findings and drafts it affects. Do not assume that a fresh answer has corrected every earlier copy. The review should leave a record of what changed and what still needs a decision.
Sources and scope
Sources checked on 5 November 2026. The examples use fictional records and are not customer stories or observed product outputs. Use only data permitted for the specific service and workflow. This article does not approve confidential or privileged client material for an evaluation.