All prompts

Draft

Outline an RFE response that answers what was asked

Turns a USCIS Request for Evidence into an issue-by-issue response outline (regulation first, existing record cited by exhibit, new evidence tagged to the request it answers) that never concedes the original filing was short.

About 18 minintermediateImmigration, Solo / small firm

Your prompt5,001 characters

Still to fill in: Adjudicating office, channel, and deadline, Form and classification, The RFE, verbatim, What is already in the record

RoleYou are an immigration attorney who has answered hundreds of RFEs and learned that the officer is not looking for advocacy: they are looking for the specific thing they asked for, in the order they asked for it. You lead with the standard before the evidence, you cite the existing record instead of retelling it, and you will not write a sentence admitting the original filing fell short.What I needA response outline for the Form and classification petition, answering every request in the RFE below. It goes back to Adjudicating office, channel, and deadline.InputsThe RFE, verbatim: The RFE, verbatim Already in the record: What is already in the record New evidence I can obtain: New evidence you can obtain Form and classification: Form and classification Office, channel, deadline: Adjudicating office, channel, and deadlineHow to work this1. One heading per request, in the officer's sequence, in the officer's own phrasing. Never merge or reorder. 2. Under each heading, state the governing standard first (regulation, Policy Manual chapter, any AAO or federal precedent) before a single exhibit. If you cannot verify the cite, name the standard and mark it. 3. Cite already-filed material by exhibit tag and brief page in two sentences maximum. No retelling. 4. Tag each new exhibit, describe it in one line, and name the sentence of the request it answers. Drop any exhibit that answers nothing. If New evidence you can obtain is thin, list what to obtain, ranked by the request it would move. 5. Write each argument as application: standard, then the specific fact, then why that fact meets it. A paragraph that only describes exhibits is not an argument. 6. Scrub for inadvertent concession. Flag every place you rewrote "the filing did not include" into "the petitioner provides further evidence establishing ___." 7. Name the doubt the officer did not write down: one-time versus sustained recognition, collaborator-only support, a role that is not actually specialized, and answer it inside the argument.Close with these four sections, every time, without being askedAssumptions I made. Every legal and factual assumption, marked [verify] or [safe]: which Policy Manual version you applied, whether you treated the record summary as complete, whether the deadline in Adjudicating office, channel, and deadline is the operative one. Where this is weakest. The two or three responses an officer would still call non-responsive, by request number, with the reason: evidence that proves a nearby point rather than the one asked, a standard stated but not applied, a gap the new exhibits do not reach. What only you can decide. Options with tradeoffs, not flags. At minimum: answer strictly what was asked (clean, fast, keeps the record narrow, but leaves the unstated doubt sitting there) or re-brief the underlying prong (heads off a NOID, but reopens ground the officer had accepted); and file now with what is in hand (shorter pendency, preserves the premium clock) or use the full window to chase the missing independent letter (you get exactly one response, and a thin one cannot be supplemented later). What would make this materially better. Ranked by impact: the RFE PDF rather than a summary, the original brief's page numbers, the receipt notice, confirmation of which experts have never co-authored with the beneficiary.Output formatA cover brief in outline form. Header: receipt number, beneficiary, classification, due date. Contents list in the officer's order. Then per request: the officer's heading; Standard; Already in the record; New evidence, tagged, one line each; Argument, one to three paragraphs. Close with the approval request and a new-exhibit index.Never do this- If this response would fit any petition in any category, it is too generic. Rebuild it from this officer's actual words and this beneficiary's record. - No hedging filler. Cut "arguably," "it should be noted," and "it depends." Do not tell me to consult an attorney. I am the attorney signing this. - Every regulation, Policy Manual chapter, and AAO or federal decision must come from my inputs or be marked [UNVERIFIED - check before filing]. Never invent a citation or a chapter number. - Where you do not know the current standard for this classification, say you do not know and tell me where to look. Do not smooth over the gap with fluent prose. - Do not pad. A two-request RFE gets a two-request response. Length is not value, and volume reads as weakness to an adjudicator.Before you answer- One heading per request, in the officer's order, in the officer's words? - Does every section state the standard before the first exhibit? - Does any sentence concede that the original filing was incomplete? - Is every new exhibit tied to a specific sentence of a specific request?

Adds driver's-seat tunes: options instead of answers, questions before work, every citation flagged. Your values come with it.

2

Pressure-test it

Makes the AI switch hats and attack its own answer.

Fourteen files left in the queue on a Friday afternoon, a supervisor tracking approval rates: that is the officer who issued this RFE and who will read the response. Take the outline as the officer takes it, on one pass. Name the three points where you would issue a NOID anyway, and quote the sentence in the response that fails to close each one. Then rewrite those sections to satisfy the officer on a single read. Finish by naming the one piece of evidence that would move this file from a coin flip to an approval, and who would have to sign it.
3

Go deeper

Pushes the work further once the basics are right.

Nothing goes in the envelope by itself. Produce the two documents that go out with the response: (a) a cover sheet for each new exhibit: title, bates range, the request it answers, the regulatory point it supports, and the declarant's qualifications where applicable; and (b) a request letter I can send to each independent expert, specifying the paragraphs their letter must contain to be usable: how they know the beneficiary's work and that they have never collaborated, their own standing in the field, the regulatory standard applied to specific work, and a conclusion that does not read as drafted by counsel.

Before you run it

What to gather first

  • The RFE letter itself, every request, in the officer's wording
  • The receipt notice: number, service center, response due date
  • The original filing's brief and exhibit index with page numbers
  • What new evidence you can realistically obtain inside the window
  • Whether premium processing is running and what the clock looks like

Watch for

  • RFE response windows are typically 87 days from issuance and are not extendable. Calendar the date off the notice itself, confirm the filing channel, and keep proof of transmission.
  • You get one response. Evidence you could have submitted and did not is generally unavailable later without a motion or a refiling. Do not send a partial response to save a week.
  • Expert letters from co-authors and collaborators are heavily discounted. Confirm the absence of a publication or funding relationship before you request the letter, not after.
  • The USCIS Policy Manual is revised frequently and the model will cite chapters confidently from an older version. Verify every volume, part, and chapter against the current text before filing.
  • Never write that the original filing omitted or failed to include something. That sentence follows the file into an AAO appeal and into any later inadmissibility or misrepresentation question.

What comes back

A cover-brief outline: header with receipt number and response due date, a one-page table of contents in the officer's order, then per request: the officer's heading, the governing standard, the existing record cited by exhibit and page, tagged new evidence, and an argument that applies the standard to the facts. Ends with the approval request and a new-exhibit index. Closes with Assumptions / Where this is weakest / What only you can decide / What would make this better.

See an example of what you’ll get
Re: Response to Request for Evidence, Form I-140 (EB-2 NIW), Receipt No. WAC2604123456 Beneficiary: Anika Patel, Ph.D. | Response due: July 14, 2026 | Filed via myUSCIS Contents. I. National importance of the proposed endeavor (Dhanasar prong 1), p. 3. II. Well-positioned to advance the endeavor (prong 2), p. 7. --- I. "Evidence that the proposed endeavor has national importance beyond the beneficiary's publication record." *(officer's wording)* Standard. Matter of Dhanasar, 26 I&N Dec. 884, 889 (AAO 2016): national importance looks to the broader implications of the work, not the beneficiary's standing; USCIS Policy Manual Vol. 6, Pt. F, Ch. 5(D)(1) [UNVERIFIED - confirm chapter against the current Manual]. Already in the record. Original brief pp. 4–6; Ex. B-3 (research statement), B-4 (USDA award), B-5 (FEMA collaboration memo). New evidence. - *RFE-1.* FEMA Region 9 implementation memo, March 17, 2026: adopts Dr. Patel's coastal-flood modeling protocol as the planning standard for nine California counties. Answers the officer's request for impact beyond publication. - *RFE-2.* Letter of Dr. Linnea Borg, Director, NOAA Coastal Risk Center; no co-authorship or funding relationship with the beneficiary. Answers the same request from an independent vantage. - *RFE-3.* National Academies Climate Resilience Roundtable proceedings, 2025: the framework is cited in two of the three working-group reports. Answers the request for reach beyond a single agency. - *RFE-4.* Wired (Dec. 14, 2025) and New York Times (Feb. 8, 2026) coverage. - *Dropped:* the departmental newsletter profile. It documents recognition inside her own institution, which is the opposite of what the officer asked for. Argument. The request asks for national importance shown by something other than papers, so the response does not lead with papers. A federal agency has taken the protocol out of the literature and made it the operating standard for flood-resilience planning across nine jurisdictions (RFE-1). The director of the relevant NOAA center, who has never worked with Dr. Patel, states that the framework is now used by planning bodies outside her institution (RFE-2). *The unstated doubt:* the officer's boilerplate recitation of prong 1 suggests a concern that this is one agency's local pilot rather than work of national reach. RFE-3 answers it: the National Academies Climate Resilience Roundtable cites the framework in two of three working-group reports, which is adoption at the national scientific level, independent of FEMA. Concession scrub. Rewrote "the initial filing did not address agency adoption" to "the petitioner provides further evidence establishing adoption of the endeavor by federal and national scientific bodies." --- --- Assumptions I made. - That Matter of Dhanasar supplies the operative framework for this classification and that the officer applied it [verify - the boilerplate you pasted tracks prong 1, which is consistent, but confirm nothing has superseded it]. - USCIS Policy Manual Vol. 6, Pt. F, Ch. 5(D)(1) [UNVERIFIED - confirm volume, part, and chapter against the current Manual before filing]. - That your record summary is complete, and in particular that nothing beyond Ex. C-1 and C-2 speaks to prong 2 [verify]. - That Dr. Borg has never co-authored with or shared funding with Dr. Patel [verify - you listed her as independent, and the officer will check]. - That July 14, 2026 is the date printed on the RFE rather than a calculated one [verify against the notice]. - That the FEMA Region 9 memo is an adopted planning standard rather than a draft circulated for comment [verify - this single fact carries Request I]. Where this is weakest. Request II. The officer asked whether Dr. Patel is well-positioned going forward, and the strongest new item (the updated citation count) is backward-looking. RFE-7 (USDA funding confirmed through FY27) is the only forward-facing exhibit, and it is a program officer's letter rather than an award document. Get the award modification notice. Second: the argument under Request I proves the endeavor has national reach without separately proving Dr. Patel is the person advancing it. An officer can accept prong 1 on this record and still doubt prong 2. What only you can decide. - *How wide to answer.* Respond to the two requests exactly as written: the officer gets what they asked for on one read, the record stays narrow, and the unstated prong-2 doubt sits there unanswered. Or re-brief prong 2 from the ground up: it forecloses the NOID that Request II is pointing toward, and it reopens ground the officer did not challenge and hands them a second surface to deny on. - *When to file.* File now on RFE-1 through RFE-7: shorter pendency, and the paused premium clock starts running again on receipt [verify against the receipt notice]. Or hold for the USDA award modification notice, which the program officer says is three weeks out. You get exactly one response and cannot supplement, and that notice is the only document answering Request II prospectively. If it slips past your internal cutoff, filing without it is the safer of two bad options. Which risk you take depends on the beneficiary's I-485 timing and travel, which I cannot see. - *What to do about Ex. C-1 and C-2.* Leave the two collaborator letters where they sit, or add a line characterizing them as collaborator letters and directing the officer to Dr. Borg for independent support. Volunteering the relationship takes the discovery out of the officer's hands and costs you a sentence; saying nothing keeps the discount from being highlighted, until the officer highlights it. What would make this materially better. Ranked by impact: (1) the RFE PDF rather than pasted text: the officer's boilerplate and the checkbox headers show which prong is actually in doubt, and Request II is currently being answered from inference; (2) the USDA award modification notice, the only prospective exhibit available for Request II; (3) the original brief with page numbers, so the pp. 4–6 record cites are exact rather than approximate; (4) written confirmation from Dr. Borg that there is no co-authorship or shared funding, which is the load-bearing independence claim in Request I.
Why this prompt is built the way it is
## Framework 1. **The officer's order, the officer's words.** One heading per request, in sequence, using the officer's phrasing. Never merge two requests or reorder them for narrative flow. 2. **Standard before evidence.** Regulation cite, USCIS Policy Manual chapter, and any AAO or federal precedent, then the exhibits. An officer reading evidence without the standard has to do your work. 3. **Cite the record, do not retell it.** Already-filed items get an exhibit tag and a brief page cite in two sentences maximum. 4. **Every new exhibit earns its place.** Tag, one-line description, and the sentence of the request it answers. An exhibit answering nothing comes out of the index. 5. **Argument is application.** Standard, then the specific fact, then why that fact satisfies the standard. Not a summary of what the exhibits contain. 6. **Concede nothing.** Never "the original filing did not include." Always "the petitioner provides the following further evidence establishing ___." Passive admissions do real damage on appeal. 7. **Answer the unstated doubt.** Every request has a suspicion behind it: one-time recognition rather than sustained, collaborator-only support, a job that is not really specialized. Name it and answer it even though it is not on the page. 8. **Deadline and channel at the top.** Receipt number, response due date, and whether it is e-filed or mailed, on page one.