Evidence completeness

Evidence Completeness Checks for Immigration Case Preparation

A source-linked evidence checklist that detects missing, duplicate, unreadable, or conflicting records before an attorney reviews an immigration case packet.

By WhichAI. Published 2026-07-12. Updated 2026-07-12.

Methodology: Editorial synthesis of workflow design patterns and implementation constraints. Public control references provide context, not proof of a deployment or legal advice. Where a versioned evidence pack appears, its evidence class, method, and limitations govern what the artifact can support. Read the full method. Report a correction.

Built for

Immigration paralegals, attorneys, case preparers, and quality reviewers

The decision

Decide how to detect packet gaps earlier without allowing a checklist to determine legal sufficiency.

Answer first

Build completeness checks around an attorney-approved requirement matrix and a live evidence inventory. The system can flag gaps and conflicts, but an attorney decides legal relevance, sufficiency, and any response.

Self-serve workflow planner

Start with this article's task

For Immigration paralegals, attorneys, case preparers, and quality reviewers. Start a brief for this task: Decide how to detect packet gaps earlier without allowing a checklist to determine legal sufficiency.

Start this brief

The capacity leak

What the team is doing before anyone calls it a systems problem

Headcount pressure rarely starts with one giant task. It starts when ordinary work is split across inboxes, tabs, handoffs, and undocumented judgment calls. These are the signals to map first.

SIGNAL 01

Requirements live in templates while the actual evidence inventory lives in folders and case notes.

SIGNAL 02

The same document is uploaded in several versions without a clear accepted copy.

SIGNAL 03

Unreadable pages, translation gaps, date conflicts, and identity mismatches are found late in preparation.

SIGNAL 04

A completed checklist can create false confidence even when the submitted evidence is not legally sufficient.

The implementation

The system should prepare the decision, not pretend the decision disappeared

A complete implementation connects the intake, context, transformation, review, and record. The output of one stage becomes the controlled input to the next. A human owns the exceptions and the final consequence.

Stage	Current drag	System responsibility	Human responsibility	Evidence kept
1. Requirement matrix	Preparers rely on memory and disconnected templates for expected evidence.	Load an attorney-approved matrix with item definitions, conditional branches, and review status.	Approve the matrix and interpret which requirements apply to the specific matter.	Matrix version, approving attorney, effective date, and matter mapping.
2. Evidence register	Files are visible in folders but not tied to individual requirements.	Register every file and associate its proposed coverage with one or more matrix items.	Confirm or reject the proposed association when legal context is required.	File checksum, proposed links, reviewer disposition, and accepted version.
3. Technical checks	Unreadable or incomplete files reach substantive review.	Check file integrity, page presence, legibility signals, duplicates, and required metadata.	Review uncertain scans, translations, and exceptions that automated checks cannot resolve.	Check result, tool version, exception reason, and replacement history.
4. Conflict queue	Inconsistent dates and identities remain scattered across documents.	Compare selected fields and route differences into a source-linked conflict queue.	Determine whether a difference is benign, requires client clarification, or affects legal analysis.	Compared values, source pages, disposition, and follow-up owner.
5. Completeness review	A checked box is treated as proof that the case is ready.	Present matrix status, unresolved gaps, conflicts, and evidence links in one review surface.	Decide legal sufficiency and authorize the next preparation step.	Attorney decision, rationale, unresolved risks, and review timestamp.

What the human keeps

The goal is not zero humans. It is zero avoidable preparation around the judgment only a responsible owner should make.

Attorneys define requirement logic and determine legal relevance and sufficiency for the specific matter.
Case staff resolve document quality, translation, identity, and client follow-up exceptions.
A reviewer records why a flagged gap or conflict was accepted, corrected, or left unresolved.

Controls before volume

A workflow is not ready because the happy path worked once. It is ready when access, review, fallback, and evidence are explicit.

Version the requirement matrix and keep the approving attorney and effective date.
Link every completeness status to the exact evidence file and accepted version.
Block review completion while technical failures or undisposed conflicts remain open.
State clearly that completeness checks do not determine legal sufficiency.

Control references

National Institute of Standards and Technology: AI Risk Management Framework National Institute of Standards and Technology: Privacy Framework

The scorecard

Measure capacity, not activity

A system can produce more messages and still make the operation worse. Measure movement through the workflow, the quality of review, and the load that still reaches a person.

Pre-review gap rate

Share of missing or defective evidence items identified before attorney substantive review.

False completeness rate

Share of system-complete packets returned by attorneys for a missing or misclassified item.

Conflict resolution time

Elapsed time from a detected field conflict to a recorded disposition.

Evidence linkage

Share of matrix statuses linked to the accepted file version and reviewer action.

What a fake implementation looks like here

These patterns create an AI demo while leaving the labor, risk, and accountability in the same place.

Treating an attorney-approved template as universally applicable to every matter.
Calling a packet legally sufficient because required file categories are present.
Comparing extracted fields without retaining the source page and original file.
Silently choosing one of several conflicting values instead of opening an exception.

Two ways to act

Use the path that matches the decision

Task-specific workflow brief

Plan this recurring task.

Start with this task draft, then complete the three-question brief:

Design an immigration evidence completeness workflow with an attorney-approved requirement matrix, file inventory, technical checks, conflict queue, and attorney sufficiency review. Preserve source files and versions.

Choose a paid plan after reviewing your brief. WhichAI creates a plan and does not set up tools or accounts.

Start the brief

WhichAI Solutions

The workflow is becoming a company problem.

Use Solutions when requirement logic varies by matter type, evidence lives across several systems, or current packet gaps are driving repeated rework and staffing pressure.

Bring one bottleneck. We map the work under it, separate consequential judgment from mechanical drag, and decide whether the next move is a hire, a tool, or a rebuild.

See company solutions

Questions

What operators ask before they build

Is an evidence completeness check a legal sufficiency review?

No. It can verify that expected categories and technical requirements are present. An attorney must decide whether the evidence is legally relevant and sufficient.

What should the requirement matrix contain?

Include the item definition, conditional trigger, acceptable technical formats, source authority, review owner, matrix version, and a place for matter-specific attorney interpretation.

How should conflicting evidence be handled?

Show both values with exact source links, prevent silent resolution, and assign the conflict to a person who can request clarification or make the appropriate legal assessment.

Primary references

Controls should come from the specific operating environment

These are broad public control references, not article-specific evidence, vendor endorsements, or legal advice. Validate the current rules, contracts, system configuration, and organization-specific risk before deployment.

National Institute of Standards and Technology

AI Risk Management Framework

A voluntary framework for mapping, measuring, managing, and governing AI risk.

Accessed 2026-07-14