What Are Employee Responsibilities per Policy When Receiving a FOIA Request Directly From the Requester: A Deep-Dive Explainer

When an employee receives a FOIA request directly from a requester, agency policy generally requires the employee to route the request to the agency's designated FOIA office without delay, avoid substantive commitments about release, preserve all potentially responsive records, and log the date and manner of receipt. Individual employees rarely have authority to grant, deny, or negotiate a request on their own; their duty is preservation, prompt transmittal, and documented handoff.

That answer sounds simple, but the machinery behind it is where thin explainers fall apart. The Freedom of Information Act imposes duties on agencies, not on individual employees. What binds an employee is a layered stack of agency FOIA regulations, internal standard operating procedures, records-management rules, and in some cases litigation-hold obligations. This explainer walks through the mechanism behind those duties, where the real thresholds sit, which edge cases trip people up, and what a conscientious employee actually does in the first hour.

The mechanism: why the employee is a conduit, not a decision-maker

FOIA, at 5 U.S.C. § 552, creates a right of public access to agency records. It assigns the response obligation to the agency as an institution. Every federal agency implements that obligation through its own published FOIA regulations in the Code of Federal Regulations, and nearly every agency delegates request handling to a centralized or component-level FOIA office staffed with trained specialists and, often, attorneys.

This delegation is the reason employee duties look the way they do. A program analyst, contracting officer, or field supervisor cannot lawfully "answer" a FOIA request because the agency has not given them that authority. The agency has given them a narrower role: recognize the request, preserve the records, and hand it to the people who hold the authority. Think of the employee as the intake valve, not the pump.

The mechanism operates through three parallel tracks that start at the moment of receipt.

The first track is procedural. Most agency regulations define what counts as a proper FOIA request, typically a writing that reasonably describes the records and complies with published submission rules. Many agencies accept requests by mail, fax, email, and online portals. Some require submission through a specific portal. When a request arrives in the wrong channel, policy usually still treats the receipt date as the date the employee received it, which is why prompt forwarding matters.

The second track is preservational. FOIA's guarantee is hollow if records vanish between receipt and search. Agency policies therefore require employees to suspend routine destruction of potentially responsive records once they learn of a request. This overlaps with Federal Records Act obligations and, in litigation-adjacent situations, with spoliation doctrine.

The third track is communicative. Policy typically requires a neutral acknowledgment, not a substantive answer. The employee confirms receipt, provides the FOIA office's contact information, and avoids characterizations of what will or will not be released. The reason is legal, not bureaucratic: informal statements about release can be treated as unauthorized commitments and can complicate the agency's later response.

Quantified context: timelines, volumes, and the cost of a slow handoff

FOIA runs on clocks, and the clocks start at receipt, not at the FOIA office's convenience. The statute establishes a 20-working-day baseline for an agency determination, with a 10-working-day extension in unusual circumstances such as voluminous records or consultations with other agencies. Those numbers are statutory floors, not performance guarantees; backlogs routinely push actual processing well past them.

The volume context matters for understanding why intake discipline exists. Federal agencies received roughly 1.1 million FOIA requests in recent fiscal years, with a handful of departments absorbing the majority. The Department of Homeland Security alone has handled well over 400,000 in a single year in recent reporting. At that scale, a request that sits in an employee's inbox for two weeks is not a rounding error; it is fourteen days subtracted from a 20-day clock before processing even begins.

Preservation failures carry their own price. When records are destroyed after receipt, agencies face litigation risk, court-ordered re-creation efforts, and in some cases adverse inferences. Reconstructing destroyed electronic records can cost an agency tens of thousands of USD in staff time and forensic work per incident, before any litigation costs. A single deleted email folder is rarely a single-folder problem.

The counterintuitive detail worth internalizing: the fastest way to slow a FOIA response is for a helpful employee to try to answer it. Informal partial releases, off-the-cuff scope negotiations, and promises like "I'll send you what I have" create records that must themselves be reviewed, can waive exemptions, and force the FOIA office to reconcile inconsistent positions. Speed comes from clean handoffs, not enthusiastic improvisation.

Timeline: the first 30 days from an employee's perspective

The exact intervals vary by agency. The sequence does not. Preservation starts before search, search starts before review, and review happens only in the FOIA office.

Edge cases: when the request is not what it appears to be

Several scenarios routinely confuse employees because they look like FOIA requests but are governed by different rules or different duties.

A request that arrives as part of litigation is usually a discovery request or a subpoena, not a FOIA request. Those go to agency counsel, not the FOIA office, and different deadlines and privileges apply. Forwarding a subpoena to the FOIA office can cause both delay and legal exposure.

A request for the employee's own personnel file from the employee themselves may be handled under Privacy Act procedures rather than FOIA, and some agencies route both through the same office. The practical duty is identical: forward it, do not self-serve it.

A request that arrives via social media, a phone call, or an in-person visit may not qualify as a proper FOIA request under agency rules, which often require a written submission. The trap is assuming an improper request can be ignored. Most policies still require logging and routing so the FOIA office can decide whether to treat it as proper or to help the requester perfect it.

A request from a member of Congress or a journalist can trigger additional protocols, including congressional liaison notification. Employees should follow the most specific policy that applies, and when two policies conflict, escalate rather than choose.

A request that names a specific employee as the subject of an investigation or complaint requires care. The employee should not search their own records for records about themselves, and should not communicate with the requester about scope. That is an automatic conflict-of-interest referral.

Misconceptions: what employees wrongly believe about FOIA duty

The most common misconception is that only the FOIA officer has responsibilities. In practice, agency policies almost universally impose intake, preservation, and cooperation duties on every employee who touches a request. Ignorance of the request is a defense only until someone tells you about it.

A second misconception is that acknowledging receipt equals promising release. Policy language typically distinguishes acknowledgment from commitment, and employees should use neutral phrasing: "Your request has been received and forwarded to the FOIA office." Nothing about what will be released.

A third misconception is that deleting routine email is fine because the request is "about something else." Preservation obligations attach to potentially responsive records, and the scope judgment belongs to the FOIA office and counsel. When in doubt, preserve and let reviewers decide.

A fourth misconception is that records can be released directly to a requester who happens to be a colleague, friend, or reporter. Direct release bypasses exemption review and, in many agencies, constitutes an unauthorized disclosure with disciplinary consequences.

Red-flag warnings to treat as stop signs:

Any instruction, even from a supervisor, to delete, alter, or backdate records after a request is received. Requests that arrive with a deadline attached, such as "I need this by Friday," which employees cannot accept or reject. Requests that ask the employee to describe what records exist rather than to produce them. A requester who asks the employee to confirm whether specific records exist before filing a formal request. Any request involving the employee's own conduct, complaints, or personnel matters.

Practical actions: what to do in the first business day

The concrete playbook is short enough to memorize and specific enough to audit.

Step one: capture the receipt. Record the date, time, channel, and requester identity in whatever intake log your office uses. If no log exists, send yourself a dated email describing the receipt. This timestamp is the single most litigated fact in FOIA timing disputes.

Step two: freeze destruction. Send a short preservation notice to custodians you know or reasonably suspect hold responsive records. Name the request, describe the categories at issue, and state that routine deletion is suspended until further notice. Copy the FOIA office.

Step three: forward, do not answer. Route the request to the FOIA office through the channel your agency requires, which is often a portal rather than email. If the requester is standing in front of you, provide the portal address or mailing address and do not take the request verbally.

Step four: acknowledge neutrally. Send a one-paragraph acknowledgment if policy assigns that duty to you, confirming receipt, providing the FOIA office contact, and making no substantive statements.

Step five: answer scoping questions factually. When the FOIA office asks what systems you use, how records are stored, or who else might hold responsive material, answer in plain descriptions. Do not speculate about what the requester "really wants."

Step six: document the handoff. Keep a copy of what you sent, to whom, and when. If you are later asked whether you complied, the answer should be a forwarded message, not a memory.

Thresholds to reconcile explicitly: the 20-working-day statutory clock and the 10-working-day extension are agency-level deadlines, not employee deadlines. The employee deadline is effectively same business day for forwarding and immediate for preservation. When internal policy sets a shorter forwarding window, such as 24 hours, the shorter window controls for the employee, while the statutory clock continues to run against the agency regardless.

Limitations: what this explainer cannot tell you, and why

Agency FOIA regulations differ in specifics. Some require requests to be submitted through a specific portal to be considered received. Some assign acknowledgment duties to the FOIA office alone. Some define "record" more narrowly or broadly than the statutory baseline. This explainer describes the common architecture, not your agency's binding text. Your agency's published FOIA regulation and internal standard operating procedures control.

The counterintuitive caveat worth carrying: over-compliance has costs too. Employees who forward every email thread mentioning a topic, or who issue preservation notices to hundreds of custodians for a narrow request, create review burdens that slow the actual response. Calibrate preservation to records you reasonably believe are responsive, and let the FOIA office widen the scope if needed.

This article is general educational information about FOIA intake practices, not a legal opinion or a substitute for your agency's official FOIA policy or counsel's advice. Do not rely on it to resolve a specific request, disclosure decision, or preservation dispute; consult your agency's FOIA office, records officer, or legal counsel. If you face a demand to destroy records or to release material outside established channels, escalate to counsel immediately.