Attorney Practice Guide
A Workflow for Responding to RFEs Without the Last-Minute Scramble
A repeatable RFE workflow for capturing the deadline, starting client evidence work early, assembling the response, and preserving attorney review.
Updated
The Request for Evidence is where a lot of immigration cases are quietly won or lost — not on the strength of the response, but on whether the response goes out clean and on time. The deadline is fixed and unforgiving, the evidence ask is often broad, and the response tends to land on your desk in the middle of everything else. Handle RFEs reactively and every one becomes a fire drill. Handle them as a defined workflow and they become routine.
You know how to answer an RFE. This is about the process around it so the clock never beats you.
Capture the deadline the moment the RFE posts
The single most important step happens first: the day the RFE appears, the response deadline goes into your system — calendar and task list — not your memory. Everything downstream keys off that date. If you're tracking case status continuously, the RFE shows up as a status change you're alerted to rather than something you discover late.
Work backward from the due date with real milestones
A fixed deadline is only safe if you've reserved time before it. Set internal checkpoints that sit well ahead of the hard date: evidence requested from the client, evidence received, draft assembled, your review, final assembly and filing. The point is to be done with days to spare, not racing the deadline at 11 p.m. — because the things that go wrong (a client who's slow to produce a document, a translation you forgot you'd need) always eat the buffer you didn't build in.
Turn the evidence ask into a client-facing checklist immediately
RFEs often ask for a specific list of documents. Translate that into a plain checklist for the client the same day, so the slowest part of the process — waiting on the client — starts as early as possible. The earlier the request goes out, the more runway you have when something they send back is wrong or incomplete.
Draft from the case record, not from scratch
A lot of the response restates facts and evidence already in the file. Starting from the case record rather than a blank page gets you to a working draft faster, leaving your time for the part that actually needs your judgment — the argument and the framing. A first draft you refine is faster than a blank document you fill.
Keep your review as the last gate, always
However the draft gets assembled, it goes out on your signature and your judgment. Build the workflow so your review is a deliberate final step with time around it, not a rubber stamp you do while the filing clock shows minutes. The system's job is to get a complete, organized draft in front of you early enough to actually review it.
The payoff
RFEs stop being emergencies and become a process you run. The deadline is captured automatically, the client is working their list early, the draft is assembled from what you already have, and your review happens with room to breathe. The response is better, and the week is calmer.
DocketBuddy flags RFEs as they post, tracks the response deadline automatically, and assembles a first-draft response from the case record for your review — built for solo and small immigration firms.