Ian Schiller
A Request for Evidence (RFE) is not a writing assignment. It is an evidence problem that happens to end in a letter. The firms that respond well treat it as a structured process: docket the deadline, split the notice into separate issues, map every issue to what is already in the record, name what is missing, and only then start drafting.
This article walks through that workflow step by step, including the evidence matrix we recommend building for every RFE. It is written for immigration attorneys, paralegals, and the case teams who share RFE work between them.
A recent USCIS policy update has changed the stakes. As of August 5, 2026, USCIS officers have discretion to deny a benefit request outright when required initial evidence is missing, without issuing an RFE or a Notice of Intent to Deny (NOID) first. An RFE is now a second chance you may not get. When you do get one, it needs to be complete.
USCIS issued a policy update effective August 5, 2026 that applies to pending and newly filed benefit requests. The agency restored officers' full discretion to deny a filing without first issuing an RFE or NOID where required initial evidence is missing or the filing otherwise fails to establish eligibility. USCIS framed the prior approach as having contributed to incomplete filings and adjudication delays.
The regulatory backstop has not changed. Under 8 CFR 103.2(b)(8), USCIS has always had the authority to deny without an RFE where the record does not establish eligibility. What changed is the internal guidance about when officers should exercise it. This discretion applies unless a statute, regulation, or form instruction requires notice in a particular case.
Two practical consequences for a case team:
This is agency guidance, not a change in statute or regulation. Confirm the current Policy Manual language before relying on it in a filing.
Do this first, before anyone starts analyzing the substance.
Under 8 CFR 103.2(b)(8)(iv), the maximum response period for an RFE is 12 weeks, and 30 days for a NOID. Those are ceilings, not defaults. USCIS sets the actual response period on the notice itself, subject to the regulatory maximum. When a notice is served by mail, three days are added to the response deadline under 8 CFR 103.8(b). As of the August 5, 2026 policy update, USCIS no longer provides the additional 14 days previously allowed for notices mailed outside the United States.
Read the deadline off the notice, not off a memory of what RFEs usually give you.
Docket three dates, not one:
Under 8 CFR 103.2(b)(13), no response means the request may be denied as abandoned, denied on the record, or both.
Most RFEs raise more than one issue, and they are frequently written in a way that blends them. A single H-1B RFE paragraph can carry a specialty occupation challenge, a beneficiary qualifications challenge, and a wage level question in one block of text.
Number every distinct request. For each one, write down:
That last distinction drives everything downstream. An evidentiary gap gets solved by collecting a document. A legal argument gets solved by briefing. An inconsistency gets solved by explanation, and often by an amended or corrected document. Handling all three the same way is the most common reason a response comes back thin.
This is the core artifact. One row per issue, and nothing moves forward until every row is filled.
The matrix does three things a narrative outline does not. It makes gaps visible instead of implied. It assigns ownership, so items do not sit unclaimed. And it forces you to identify what is already in the record before you go collect more, which is where a surprising amount of duplicated work comes from.
Keep the matrix in one place that the whole case team can see. If it lives in one person's notes, it is not a workflow.
It is the same artifact used in the pre-filing audit, built after the notice arrives instead of before. Firms that run both end up with one method rather than two.
A meaningful share of RFEs ask for evidence you already submitted. USCIS may not have located it, may not have credited it, or may not have found it responsive as presented.
For each issue, sort the evidence into three buckets:
Be candid in the matrix about the second bucket. A resume is not independent proof of prior employment. An offer letter is not proof of a worksite arrangement. Writing "resume, submitted" in the evidence column when the request asked for third-party verification is how a response fails.
The missing-evidence column becomes a request list — but not a copy of that column. Clients and employer contacts do not read internal work product.
A usable request groups items by source and, for each item, states:
The most useful field is the alternative. When a prior employer no longer exists or the supervisor has left, the case does not stop — it moves to secondary evidence. Naming that up front saves a week of email.
Track the status of each request against the matrix. An item is not closed until the document is in hand and reviewed.
Every row in the matrix needs a stated theory. Not a paragraph — a sentence or two that answers: what is the government's concern, and what makes the record now sufficient?
Three tests for a workable argument:
Where an original filing position turns out to be wrong rather than under-documented, that is an attorney judgment call about whether to defend it, narrow it, or address it directly. It is not a drafting question.
Structure the response letter the way the matrix is structured: issue by issue, in the order USCIS raised them.
For each issue:
Then the mechanical checks, which are where avoidable problems live:
The sign-off column is the last thing filled in, and it is filled in per issue, not once for the package. An attorney confirms for each row that the evidence supports the argument, the legal standard is stated correctly, and nothing in the response contradicts the original filing.
This is not a formality. Cross-document inconsistency is one of the most common substantive problems in RFE responses, and it is easiest to catch when someone reviews issue by issue rather than reading the letter end to end.
AI is useful in the parts of this process that are analytical and repetitive: reading a long notice and separating it into discrete requests, searching a case file for what is already there, comparing documents for inconsistency, and producing a first structured pass at an issue-by-issue plan.
In Visalaw AI, that work happens inside a Project holding the case files, so the analysis runs against the actual record rather than a generic description of it. Our Skills library — prompt sets built by immigration attorneys — includes an RFE analysis and response skill that returns a summary of each requested item, examples of adequate evidence for each, and potential counterarguments. Teams also run the reverse before filing: predict the most likely USCIS RFE issues for this case, and recommend evidence to add now to reduce RFE risk. Given the August 2026 change, that pre-filing prediction is the higher-value use.
What does not change: an adjudicator's concern, a decision to concede a weak position, and the sufficiency of the record are attorney judgments. AI can populate the matrix. It cannot sign it.
For a related workflow, see O-1 evidence mapping: catching RFE risks before filing and our EB-1A evidence mapping pre-drafting workflow. For H-1B specifically, our practical H-1B prompts cover SOC mapping and consistency checks that prevent the most common specialty occupation RFEs.
USCIS challenges the specialty occupation, questions the beneficiary's qualifications based on foreign experience, and flags a wage level inconsistency. Three issues, three rows.
Issue 1 — Specialty occupation.
Standard: the position must require a bachelor's degree or higher in a directly related specific specialty, meaning a degree field with a logical connection to the duties, and must meet at least one of the regulatory criteria for a specialty occupation.
In the record: job description, offer letter. Missing: duty-by-duty percentage breakdown tied to O*NET and OOH language, an expert opinion letter, or evidence supporting one of the other regulatory criteria.
Owner: paralegal, with employer input.
Argument: the duties require specialized knowledge in a defined field, evidenced by the duty chart and industry practice.
Issue 2 — Beneficiary qualifications.
In the record: resume, degree certificate.
Missing: prior employer letters describing duties, hours, and tools. Where an employer no longer exists, secondary evidence — colleague declarations, tax or payroll records, project documentation.
Owner: client contact. Argument: education plus verified experience satisfies the specialty requirement.
Issue 3 — Wage level.
In the record: Labor Condition Application (LCA).
Missing: a wage-level memo reconciling the level selected with the seniority described in the job description.
Owner: attorney.
Argument: counsel should assess whether the selected wage level can be reconciled with the duties and defended, or whether a separate procedural step is required. Materially changing the proffered position to cure the inconsistency can raise eligibility-at-filing and amendment concerns. That judgment belongs to the attorney, not a template.
Note what the matrix surfaces immediately: Issue 2 depends entirely on third parties and should start on day one, while Issue 1 is largely internal work. Without the matrix, both look like "gather evidence."
How long do I have to respond to an RFE? The period is set on the notice, subject to the regulatory maximum of 12 weeks for an RFE and 30 days for a NOID under 8 CFR 103.2(b)(8)(iv). Where the notice is served by mail, three days are added under 8 CFR 103.8(b). Shorter periods are possible. Always work from the date printed on the notice.
Can I file a partial response and supplement later? No. Under 8 CFR 103.2(b)(11), submission of only some of the requested evidence is treated as a request for a decision on the record. Do not assume USCIS will provide another opportunity to cure an unresolved deficiency.
What happens if we do not respond? Under 8 CFR 103.2(b)(13)(i), the request may be denied as abandoned, denied based on the record, or both.
Does the August 2026 policy update mean RFEs are going away? No. Officers retain discretion to issue an RFE where the record could plausibly be cured. What changed is that a deficient filing may now be denied without one. Plan filings as if there will be no RFE.
Should I still submit affidavits? Generally, only where primary and secondary evidence are unavailable. Under 8 CFR 103.2(b)(2), affidavits are a last resort: an applicant or petitioner must first show that the required primary document does not exist or cannot be obtained, then that secondary evidence also does not exist or cannot be obtained, and then submit two or more affidavits from persons who are not parties to the petition and who have direct personal knowledge. Do not use affidavits to substitute for evidence that is obtainable, and check for any classification-specific evidentiary rules.
The RFE response workflow is the same discipline as pre-filing evidence mapping, applied under a deadline. Break the notice into issues, map each issue to the record, name what is missing, assign it, argue it, and sign off on it one row at a time.
Since August 5, 2026, the same discipline needs to run before you file, because the RFE may never arrive. That is the other half of this system: the pre-filing evidence and consistency audit.
See how Visalaw AI can organize an RFE response workflow
Prefer to see it live first? Our team walks through RFE analysis and pre-filing risk prediction 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
