A Controlled RFE Response Workflow for Small Immigration Firms

An RFE should enter the firm as a controlled evidence project, not as a deadline and a PDF attachment. The notice itself determines what USCIS is asking, where the response must go, and when it must arrive. The response file should therefore begin with a complete, page-counted copy of that notice and preserve the connection between each request, the evidence used to answer it, and the final packet.

The attorney owns the reading of the notice and the legal response. Staff and software can make the surrounding work far more reliable: capture the record, turn each request into a discrete evidence row, send precise client instructions, check replacements, assemble the exhibit set, and preserve proof of submission.

Create the notice record before creating tasks

Do not build the workflow from a status alert, client email, or paraphrase. Confirm that the firm has every page, including any response cover sheet, barcode page, mailing instructions, and enclosure list.

The notice record should include:

• receipt number, form, petitioner or applicant, and beneficiary;
• notice date, response date exactly as printed, and time zone or receipt rule if material;
• page count and a quality check for missing or unreadable pages;
• response address or electronic path shown on the notice;
• the source page for every extracted request; and
• the staff member and attorney who verified the record.

USCIS explains that an RFE should identify the missing evidence, and its filing-location guidance tells the filer to follow the address on the notice because a response location may differ from the original filing location. The USCIS Policy Manual section on RFEs and filing-location guidance belong beside the firm runbook, but the actual notice remains the source for the particular matter.

Work from two dates

Record the response date from the notice without silently recalculating it. Then set a firm completion date early enough to leave room for client delay, translation, attorney revision, signature, packet assembly, delivery, and a failed first attempt.

A small firm can run five internal milestones:

1. Notice verified and requests itemized
2. Client and third-party evidence requests sent
3. First evidence review complete
4. Attorney draft and exhibit review complete
5. Final packet delivered with receipt preserved

Each milestone needs an owner and an exception state. “Client evidence due Friday” is not enough when the client sends one of six requested items. The workflow should show which request remains open and why.

Build a request-by-request evidence matrix

One broad task called “answer RFE” hides the work. Use one row for each numbered demand or distinct evidentiary issue.

The matrix is not a substitute for legal analysis. It prevents a requested item from disappearing inside a narrative draft and gives the attorney a fast way to test whether the packet actually responds to the notice.

Send client requests that can be followed

“Please send financial evidence” creates another review cycle. The client message should identify the person, document, period, completeness requirement, and any obvious quality issue.

For example:

Please upload all pages of your 2025 federal tax transcript for Jordan Lee. We have the first two pages of a tax return, but the notice asks for the complete federal record. Please use the IRS transcript PDF if available. Do not send a state return in its place.

If the client sends the wrong year, a screenshot, an unsigned declaration, or one side of an identity document, the replacement request should explain the exact defect. Repeating the original checklist is not follow-up.

Check evidence against the row it is meant to satisfy

An upload should not become “received” merely because a file exists. Check the name, period, page completeness, legibility, signature where required, translation, and whether the document answers the corresponding request.

Keep attorney decisions separate from client-fixable defects. A missing page can return to the client. Whether evidence is legally sufficient, whether an explanation is credible, and how to answer an inconsistency stay with counsel.

Assemble the response from the evidence matrix

Draft only after the request rows and evidence set are stable enough to review. The packet control sheet should show:

• response cover sheet or barcode treatment;
• attorney response by numbered request;
• exhibit name and page range;
• signature and translation checks;
• factual statements that still need source confirmation;
• attorney approval; and
• delivery method, tracking, receipt, and retained copy.

The final quality check should compare the packet with the complete notice, not merely with the draft outline. It should also verify the current form edition and form-specific instructions when a replacement form is included. USCIS maintains the official forms index, which should be checked at the time of filing rather than copied into a permanent internal checklist.

Keep the operational receipt

After submission, preserve what was sent, when and where it was sent, delivery evidence, the final exhibit index, and the next status check. A response marked “done” without the submission record leaves the firm unable to reconstruct the event when status, delivery, or later evidence becomes disputed.

Where DocketBuddy fits

DocketBuddy can preserve the notice source, break requests into an evidence matrix, prepare exact client follow-up, track corrected uploads, hold legal issues for attorney review, and keep the final response record on the matter. It does not decide sufficiency, invent authority, select strategy, or file an unreviewed response.

The practical result is a matter where the attorney can see the request, evidence, remaining gap, client communication, and filing receipt without reconstructing the RFE from tasks and email.