Draft a Response to a USCIS RFE
Turn a USCIS Request for Evidence into a structured response by having Claude identify every issue, map your client's evidence, flag the gaps, and draft a cover argument you then verify.
When to use this
Use this when an RFE arrives on a deadline with its real demands buried in pages of boilerplate and you cannot afford to miss a single sub-request. Claude parses the notice into discrete issues, lines up the evidence already in your file against each one, and produces a first-draft response framework grounded in the current policy guidance you paste in. You keep every legal judgment and citation; Claude handles the organizing and the rough drafting.
A Request for Evidence is really a checklist disguised as a letter. USCIS folds the actual asks into pages of statutory recitation and template language, and overlooking one nested sub-request can cost you the case. Before you write a word of response, you have to extract exactly what the officer wants, decide what you can prove, and structure an answer that meets each point head-on. That organizing work is slow and unforgiving, and it is where Claude is most useful.
Claude doesn't decide your case. It produces a clean first draft of the scaffolding: the issue list, the evidence map, and the skeleton of your cover argument. This workflow runs in a single Claude conversation so that context carries from step to step, and by the time you reach the draft, Claude is writing from the issue list and evidence map it already built. If you paste the current USCIS policy guidance for the classification at the start, Claude analyzes against that text instead of its training data.
One caution runs through every step: AI can hallucinate. It may invent a regulation, misstate USCIS policy, or cite guidance that has been superseded. Treat everything Claude produces as a first draft to verify against current USCIS policy and the actual record, and confirm every legal and policy citation against a primary source before it goes near a filing. You are the attorney of record; the response goes out over your signature.
The Workflow
Paste the RFE and extract every issue
Start a fresh conversation and give Claude the full text of the RFE, plus (optionally but recommended) the current USCIS Policy Manual section or other guidance for the classification, copied from the USCIS website. Ask it to separate the substantive requests from the boilerplate and list each issue discretely, including the nested sub-requests that are easy to miss. Leave out client identifiers you don't need; you can refer to the beneficiary generically.
Prompt<document type="USCIS Request for Evidence" petition="[VISA/PETITION TYPE]" date="[RFE DATE]"> [PASTE FULL RFE TEXT HERE] </document> <document type="current USCIS policy guidance for [CLASSIFICATION]" source="[URL OR POLICY MANUAL CITATION]" retrieved="[DATE]"> [OPTIONAL: PASTE THE CURRENT POLICY MANUAL SECTION OR GUIDANCE TEXT] </document> I am a U.S. immigration attorney representing the [PETITIONER / BENEFICIARY] in a [VISA/PETITION TYPE, e.g., I-140 EB-2 NIW] petition. The first document is the RFE. The second, if present, is the current policy guidance I pulled for this classification. My goal is a complete, on-time response that answers every request. Read the RFE carefully and produce a numbered list of every distinct issue or request the officer is raising. For each one: - State the issue in one plain sentence. - Quote the specific RFE language that raises it. - Note exactly what category of evidence USCIS is asking for. - Flag any sub-requests nested inside a larger paragraph. - If I provided policy guidance, quote the part of it that sets the standard for this issue. If I did not, write "STANDARD: attorney to confirm from current guidance" rather than stating it from memory. Also extract: the response deadline stated in the notice, and any instructions in the notice about how to package or submit the response. Quote them. Separate genuine requests from boilerplate statutory recitation. Do not add legal analysis yet. If anything is ambiguous, say so rather than guessing. We will work through this in the same conversation.
What you get: A clean, numbered breakdown of each request with the triggering language quoted, the evidence category named, and (if you pasted guidance) the governing standard quoted, plus the quoted deadline and submission instructions and explicit flags on anything ambiguous.
Map the client's evidence to each request
Now tell Claude what is actually in the file. Give it a plain-language inventory of documents and facts and have it align each item to the issues from Step 1. This is where you see your coverage at a glance.
Prompt<evidence_inventory> [LIST DOCUMENTS AND FACTS, e.g., employment verification letter dated [DATE]; three reference letters from [FIELD] experts; published article in [JOURNAL]; pay records [YEARS]; degree evaluation. Paste key excerpts where the wording matters.] </evidence_inventory> Above is the evidence currently in the client's file. Map it against the numbered issues you identified. For each issue, create a short entry showing: - The issue number and one-line description. - Which of the available documents directly support it, quoting the relevant line where I pasted an excerpt. - How strong that support is: DIRECTLY RESPONSIVE, PARTIAL, or TANGENTIAL. Do not overstate what a document proves. If a document only partially addresses a request, say so plainly. If an issue has no supporting document yet, mark it UNSUPPORTED.
What you get: An issue-by-issue map linking each USCIS request to the specific documents you hold, each with an honest strength rating, so you can see where you are solid and where you are thin.
Flag the gaps and what you still need
Ask Claude to invert the map: which requests are not yet fully answered, and what additional evidence would close each gap. This becomes your client follow-up list and your pre-filing checklist.
PromptBased on the evidence map, identify the gaps. Keep your evidence suggestions appropriate for a [VISA/PETITION TYPE] petition and, where I provided policy guidance, tie each suggestion to the evidence types that guidance describes (quote it). List every issue that is NOT yet fully supported by the available evidence. For each gap: - State which request is under-supported and why. - Suggest concrete types of evidence that would strengthen the response (e.g., additional expert letters, contracts, citation records, organizational charts, media coverage). - Note where a sworn declaration from the beneficiary or employer could help fill a factual gap. Rank the gaps from most to least critical to address before filing. Frame these as drafting and evidence-gathering suggestions, not as conclusions about whether the petition will be approved.
What you get: A prioritized gap list (the specific holes in your response and concrete evidence ideas to fill each one) that doubles as a client and employer follow-up checklist.
Draft the response framework and cover argument
With the issues, evidence map, and gaps in hand, have Claude draft the skeleton of the response: a cover letter that walks through each request, a paragraph framework arguing how your evidence satisfies it, and a filing checklist. This is a first draft of structure and language, not a finished filing.
PromptNow draft a first-draft framework for the RFE response, using the issue list and evidence map above. PART A: Cover letter 1. A brief opening that identifies the petition, includes a [RECEIPT NUMBER] placeholder, and states that this responds to the RFE dated [DATE]. 2. A section for EACH numbered issue, in the RFE's order, with a clear heading, a short argument paragraph explaining how the attached evidence satisfies the request, and a bracketed list of the exhibits cited. 3. A short closing that requests approval. Use a professional, measured tone. Leave [BRACKETS] anywhere a specific fact, date, exhibit number, or figure is needed. Do NOT invent regulations, case citations, or USCIS policy references; insert [CITE: ___] placeholders instead, or quote the policy guidance I pasted with its section reference. Tie every assertion to a document from the evidence map; do not add facts that are not in the record. PART B: Exhibit index A numbered exhibit list mapped to the issues each exhibit supports. PART C: Filing checklist - Response deadline as quoted from the notice: [DATE FROM NOTICE] [VERIFY]. - Packaging and submission requirements as stated in the RFE instructions (for example, whether the RFE notice must be returned with the response), each marked [VERIFY against the notice and current USCIS instructions]. - Every open placeholder and UNSUPPORTED issue still to resolve.
What you get: A structured cover-letter draft with a section per issue, an exhibit index, [CITE: ___] placeholders wherever legal authority belongs, and a filing checklist with the deadline and packaging items marked for verification.
Verify against current policy and finalize
Do not file anything yet. This is the lawyer-in-the-loop step, and it is yours alone. Read the draft as the attorney of record and check it line by line against the source record and current law.
What you get: A response you can stand behind. Confirm every legal and policy citation against a primary source, since AI can fabricate authority that looks real; check the draft against CURRENT USCIS policy, which changes and may post-date the model's training; verify each exhibit reference matches the actual record; confirm the response deadline and packaging requirements against the notice itself; confirm no client fact was invented or overstated; resolve every UNSUPPORTED flag and bracketed placeholder; and rewrite the argument in your own voice where persuasion matters. The filing goes out over your signature.
Example Output
Illustrative example — names, facts, and figures are fictional.
ISSUE BREAKDOWN: RFE for I-140, EB-2 National Interest Waiver (illustrative, fictional) Deadline (quoted from notice): "[RESPONSE DUE DATE]" [VERIFY] 1. Substantial merit and national importance of the proposed endeavor RFE language: "The record does not establish that the beneficiary's proposed endeavor has both substantial merit and national importance." Evidence requested: Documentation describing the endeavor and its broader impact. Standard: quoted from pasted policy guidance, section [X]. [VERIFY current version] Available evidence: Personal statement (PARTIAL); one expert letter (DIRECTLY RESPONSIVE). Strength: PARTIAL. Impact described but corroborated by only a single letter. 2. Beneficiary is well positioned to advance the endeavor RFE language: "Submit evidence of the beneficiary's qualifications, record of success, and plan to advance the endeavor." Evidence requested: Degrees, record of achievement, a concrete plan. Available evidence: Degree evaluation; CV; two reference letters. Strength: DIRECTLY RESPONSIVE on credentials; the plan is thin. GAP LIST (most to least critical) - Issue 1: Add independent expert letters and any adoption or citation evidence. [CRITICAL] - Issue 2: Add a detailed forward-looking endeavor plan and a beneficiary declaration. [HIGH] DRAFT COVER LETTER (excerpt) Re: Response to Request for Evidence, Receipt No. [RECEIPT NUMBER] This letter responds to the RFE dated [DATE] regarding the Form I-140 filed on behalf of [BENEFICIARY]. I. Substantial Merit and National Importance The enclosed evidence establishes that [BENEFICIARY]'s endeavor in [FIELD] carries national importance because [FACT]. See Exhibits [A-C]. [CITE: ___] [VERIFY every citation and confirm the current standard before filing.]
Tips
- •Work in one conversation and go in order. Each step feeds the next; if you jump straight to the draft, Claude is writing without the issue list and evidence map it should be drafting from.
- •Paste the current USCIS policy guidance for the classification into Step 1. Claude then quotes the standard you supplied instead of reciting one from training data that may be out of date.
- •Never let Claude supply the law. Make it flag every authority as a placeholder, then confirm each regulation, policy section, and memo yourself. Fabricated or superseded citations are the biggest risk.
- •Calendar the response deadline from the notice itself the moment the RFE arrives, and treat the filing checklist in Step 4 as a draft to check against the notice and current USCIS instructions.
A note on confidentiality
RFEs and the supporting file carry immigration identifiers (A-numbers, receipt numbers, passport and visa details, dates of birth) and often employer payroll records and personal statements about the beneficiary's history. Refer to the beneficiary generically, redact A-numbers, passport numbers, and dates of birth before uploading, and paste only the excerpts of payroll or personal records that a specific issue requires. Run client work on a commercial plan (Team or Enterprise) whose terms exclude your content from model training. On Pro or Max, disable model training in Privacy settings; a commercial plan's contract terms are the stronger answer for client work. Confirm your handling meets ABA Model Rule 1.6 and ABA Formal Opinion 512. Every output is a draft for attorney review: verify every citation and policy reference against a primary source before filing.
Frequently Asked Questions
Can Claude tell me whether my RFE response will be approved?
No. Claude can organize the requests, map your evidence, flag gaps, and draft the structure, but it cannot predict an adjudication or substitute for your legal judgment about sufficiency. Whether the evidence meets the applicable standard is a call only you, the attorney of record, can make.
Why paste the USCIS policy guidance into the conversation?
Policy guidance changes, and the model's training data may not reflect the current version. When you paste the current text into a <document> tag, Claude can quote the standard you supplied and tie each argument to it. You should still confirm that what you pasted is the live version on the day you file.
Is it safe to paste a full RFE and client evidence into Claude?
Use a commercial plan (Team or Enterprise), where your data is not used for training by contract, or at minimum disable model training on Pro or Max. Minimize identifying detail: refer to the beneficiary generically and redact A-numbers, passport numbers, and dates of birth you don't need. This is a confidentiality question under ABA Model Rule 1.6 and ABA Formal Opinion 512.
How do I keep Claude from inventing regulations or case law?
Instruct it to insert [CITE: ___] placeholders instead of supplying authority, as the prompts above do, then confirm every citation against a primary source. AI can produce realistic-looking but fabricated or outdated authority, and USCIS policy changes, so independent verification against current sources before filing is required.
Prompts used in this workflow
Get New Workflows Like This Every Week
Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.