What a clean RFE response package should look like on your desk

A Request for Evidence (RFE) lands, and the response deadline printed on the notice sets the pace for everything that follows. The legal question (what the officer is really asking, and how to answer it) is yours. Almost everything around that question is preparation: reading the notice line by line, finding what’s already in the file, chasing what isn’t, and assembling a response that an officer can follow without hunting.

That preparation decides whether an RFE response goes out on time and reads clearly. Here is what a clean RFE response package should look like when it reaches your desk, and what to ask your team for at each step.

First: the point-by-point map

Before anyone requests a single document, ask for a map of the notice. It’s a short working document that breaks the RFE into every separate point it raises, in the officer’s own words, and lines each one up against the file.

For each point, the map should show:

  • The request, quoted exactly. Paraphrase is where requests get quietly narrowed. The officer’s wording stays visible.
  • What the original filing already contains that speaks to it, with the exhibit reference.
  • What appears to be missing, stated plainly.
  • Who has to supply it: the client, an employer, a third party, or your own records.
  • The response deadline, taken directly from the notice and written at the top of the map, along with the internal date your team is working toward so you have time to review.

This is the document you’ll use to decide the approach. It should take you minutes to read, not an afternoon. If a point in the notice is ambiguous, the map should say so and leave the interpretation to you rather than settle it quietly.

Next: one complete document request

Once you’ve read the map and confirmed the approach, your team can go to the client. Ask for it to go out as one complete request, not a series of partial ones. A single list, organized by the RFE point each item answers, tends to get answered more completely than three emails spread over two weeks.

A good request:

  • Explains in plain language what each document is and why it’s needed
  • Says which items are essential and which would only strengthen the response
  • Gives the client a clear date to send everything by, well ahead of your filing date
  • Comes from your firm, under your firm’s name

Then ask your team to track what comes back against the map, so at any point you can see which points are fully supported and which are still waiting.

When the evidence is in: the response package

The response package that reaches you for review should be complete, organized and easy to check against the notice. It should include:

  • A draft cover letter that walks through the RFE point by point, in the same order the notice raises them, with each point’s evidence referenced by exhibit. Your team drafts it; you revise it and make the arguments.
  • A response index listing every exhibit, numbered and labeled with the RFE point it supports.
  • The evidence itself, in index order, with clear exhibit tabs or separator pages, and translations paired with their originals.
  • A copy of the RFE notice, placed where USCIS instructions for that notice call for it. Ask your team to confirm the current instructions on the notice itself rather than relying on habit.
  • A short flag list: anything that came back incomplete, anything inconsistent with the original filing, and any point where the evidence is thin. Each flag should be stated plainly, not buried.

The test for the whole package is simple. Pick any point in the RFE and you should be able to find, quickly, the paragraph that answers it and the exhibits that prove it.

What stays with you

An RFE response is not the place to blur roles. The decisions that belong to you stay with you:

  • How to read what the officer is actually asking, and the legal theory of the response
  • Whether to submit additional arguments beyond the specific points raised
  • What to do if a requested document can’t be obtained, including whether secondary evidence or a declaration is appropriate
  • The final review and signature, as the filer of record

Your team’s job is to make those decisions faster to reach and easier to carry out. A good package hands you the questions in a form you can answer, rather than answers you then have to check.

A few habits that keep RFE responses calm

  • Make the map the first thing you ask for. Most of the stress in an RFE comes from learning late that something is missing.
  • Ask for one working folder per RFE. The notice, the map, the client request, everything received and every draft live together, with dates.
  • Record what the RFE taught you. If a type of evidence keeps getting requested for a case type, ask your team to add it to the original intake checklist for that case type. The best RFE response is the one a future case never needs.

Where Immigration Paralegals fits

At Immigration Paralegals, RFE response support is part of the case preparation our team does for immigration law firms, alongside document follow-up, packet assembly and cover letter drafting. Legal strategy stays with your firm, and you review and sign every response as the filer of record.

The takeaway

When an RFE arrives, ask your team for a point-by-point map of the notice before anything else, then one complete document request organized by RFE point. The package that reaches you should answer the notice in its own order, index every exhibit to the point it supports, and flag anything thin or inconsistent. That leaves you with the part that needs an attorney: deciding how to answer, and signing the response.

Scroll to Top