Ian Schiller
The cheapest Request for Evidence (RFE) is the one that never gets issued. A pre-filing evidence and consistency audit is a single structured pass over a completed case file, run before signature, that answers three questions: does every element of the legal standard have evidence behind it, does that evidence hold up as primary evidence, and do the documents agree with each other?
This article gives you that audit as a repeatable process: the claim map, the cross-document consistency check, and the exception log for immigration attorneys, paralegals, and whoever owns quality control at your firm. It works across case types, not just H-1B.
The urgency is new. As of August 5, 2026, a USCIS policy update allows officers to deny a benefit request without issuing an RFE or a Notice of Intent to Deny (NOID) first when required initial evidence is missing. The filing is now the whole case.
Until recently, an incomplete filing usually produced an RFE. That RFE was expensive and slow, but it was recoverable.
That assumption no longer holds. The USCIS policy update effective August 5, 2026, applying to pending and newly filed requests, restores officers' full discretion to deny where required initial evidence is missing or the filing otherwise fails to establish eligibility.
The agency described the previous approach as having contributed to incomplete filings and adjudication delays. This discretion applies unless a statute, regulation, or form instruction requires notice in a particular case.
Three regulations set the boundary, and none is new:
Read together: eligibility is fixed at filing, and the RFE — if one issues — only lets you document it. The audit below is how you make sure it is documented before you send it.
This is agency guidance layered on existing regulations, not a statutory change. Verify the current Policy Manual language before relying on it.
The audit runs after the file is assembled and before the attorney signs. It should take a trained paralegal a focused hour on a routine case, and it produces one artifact: an exception log the attorney clears.
Four steps.
Start from the legal standard, not from the documents. Write out every element the filing must establish, then attach evidence to each one.
The discipline is the Strength column. Most weak filings are not missing documents. They contain documents that assert a fact rather than establish it — a resume that describes prior duties, an offer letter that describes a worksite, a support letter that characterizes a role without independent corroboration. Those belong in the "asserts" row, and an element supported only by "asserts" evidence is a likely RFE issue — and, where the element requires initial evidence, now a denial risk.
Any element with no row, or with only "asserts" evidence, is an exception. It goes in the log.
This is where otherwise careful filings are quietly weak, and it is governed by regulation rather than preference.
Under 8 CFR 103.2(b)(2)(i), the non-existence or unavailability of required evidence creates a presumption of ineligibility. If a required document does not exist or cannot be obtained, the applicant or petitioner must demonstrate that and submit secondary evidence. If secondary evidence also does not exist or cannot be obtained, they must demonstrate the unavailability of both and submit two or more affidavits, sworn to or affirmed by persons who are not parties to the petition and who have direct personal knowledge of the event and circumstances. Secondary evidence must overcome the unavailability of primary evidence, and affidavits must overcome the unavailability of both.
Where a record does not exist at all, 8 CFR 103.2(b)(2)(ii) requires an original written statement on government letterhead from the relevant government or other authority establishing that the record does not exist, explaining why it does not exist, and indicating whether similar records for the relevant time and place are available.
Three checks per element:
An affidavit submitted without the unavailability showing is not a weaker version of the required evidence. Under the regulation, it does not substitute for it. Also check for classification-specific evidentiary rules, which can be stricter than the general standard.
Inconsistencies are the second failure mode, and unlike gaps they are invisible unless someone looks for them deliberately. They also compound: two documents that disagree invite a question about a third.
Check these fields across every document in the packet — forms, support letter, Labor Condition Application (LCA), labor certification, or classification-specific equivalent where applicable, offer letter, corporate documents, resume, and exhibits:
For each mismatch, record which documents disagree and which one is correct. "Correct" is a factual determination, and sometimes the answer is that the underlying fact needs to be confirmed with the client before either document is right.
Two cautions on resolution, and both belong to the attorney rather than the person running the audit:
The exception log is the output of the audit. It is short by design.
Every line needs an attorney decision before the case is signed. "Accept with reason" is a legitimate outcome — some risks are worth taking, and some documents genuinely cannot be obtained. What is not legitimate is an unlogged risk that nobody decided about.
The log is also the beginning of the RFE response file. If an RFE does issue, you already know which issues were flagged, which were accepted, and why. That connects directly to the RFE response workflow, which is the same evidence matrix run after a notice arrives instead of before.
The final pass is adversarial. Read the packet the way an adjudicator would, and write down the three most likely challenges.
For each predicted issue, ask:
Then make the decision explicitly: strengthen now, or file and accept the risk. Under the current policy, "file and respond to the RFE" is no longer a reliable third option.
The audit is analytical and repetitive, which is where AI earns its place — and it is also the part firms skip when the filing deadline is tomorrow.
In Visalaw AI, the case file lives in a Project, so analysis runs against the actual documents rather than a description of them. Three prompts cover most of the audit:
Our Skills library holds prompt sets built by immigration attorneys for these recurring tasks, and teams can save their own firm-specific versions so the audit runs the same way every time regardless of who is on the case.
What AI does not do: decide whether a risk is acceptable, determine which of two conflicting documents states the true fact, or sign the filing. The exception log has an attorney column for a reason.
Case-type versions of this audit are already published for two categories: O-1 evidence mapping and EB-1A evidence mapping. For H-1B, our practical H-1B prompts cover occupational classification and consistency checking in more detail.
An employment-based petition arrives for final review. The audit surfaces four exceptions in under an hour.
1 — Gap. Found: the claim map shows the beneficiary's three years of foreign experience supported only by a resume. Risk: experience is a required element, and a resume asserts it rather than establishes it. Resolution: obtain employer letters; where the employer has dissolved, document that the primary evidence cannot be obtained and submit payroll or tax records as secondary evidence. Owner: paralegal. Due: two weeks before filing.
2 — Inconsistency. Found: the support letter lists a job title that does not appear on the form or the offer letter. Risk: suggests the position was described differently to different audiences. Resolution: confirm the correct formal title with the employer. If this is a drafting error, conform the documents. If the title reflects a genuinely different position, counsel must assess eligibility-at-filing and amendment implications before anything is changed. Owner: paralegal, with client confirmation and attorney decision.
3 — Weak evidence. Found: the worksite arrangement is described only in the offer letter. Risk: no independent corroboration of where the work will be performed. Resolution: obtain a client letter or worksite agreement. Attorney decision: resolve before filing.
4 — Accepted risk. Found: one prior employer has dissolved, its records are genuinely unobtainable, and relevant secondary evidence also does not exist or cannot be obtained. Resolution: document the unavailability of both the required primary evidence and relevant secondary evidence, then submit two or more affidavits from non-parties with direct personal knowledge under 8 CFR 103.2(b)(2)(i). Attorney decision: accept, with the reasoning recorded in the log.
Three of the four would likely have been RFE issues. Under current policy, one or two could have been denial issues.
What counts as "initial evidence"? Under 8 CFR 103.2(b)(1), it is the evidence required by the regulations applicable to the specific benefit request and by USCIS's filing instructions for that form. Start with the form instructions and the governing regulation for the classification, not with a firm checklist that may be out of date.
Can we still submit affidavits? Yes, but only in their regulatory place. Under 8 CFR 103.2(b)(2), affidavits must overcome the unavailability of both primary and secondary evidence, and there must be two or more from persons who are not parties to the petition and who have direct personal knowledge. Where primary evidence is obtainable, an affidavit is not a substitute. Check for classification-specific evidentiary rules as well.
If USCIS issues an RFE anyway, can we fix a gap then? Only if the underlying eligibility existed at filing. Under 8 CFR 103.2(b)(12), a benefit request is denied where the evidence submitted in response does not establish filing eligibility as of the time the request was filed.
Who should run the audit? A trained paralegal or case manager should run it, and the attorney clears the exception log. Separating the two is the point — the person who assembled the file is the worst person to audit it alone.
How long does it take? On a routine case with a complete file, a focused hour. On a complex or document-heavy case, longer — but far less than an RFE response, and far less than a refiling.
Since August 5, 2026, an incomplete filing may simply be denied. The pre-filing audit is the control that replaces the RFE as a safety net: map every element to evidence, test that evidence against the primary, secondary, and affidavit hierarchy, check the documents against each other, and make an attorney clear every exception before signature.
If a notice does arrive anyway, the same matrix carries straight into the RFE response workflow.
Explore a pre-filing RFE-risk review workflow in Visalaw AI
We walk through pre-filing risk prediction and document consistency review on real case files in our upcoming sessions.
This article describes practical workflows and general legal standards for immigration professionals. It is not legal advice for any specific matter, and it does not substitute for independent verification of current USCIS policy.
View all blogs
Subscribe below to receive tips for using AI in immigration law, product updates, and relevant news in immigration.
Memphis, TN
