FOIA Request Intake and Tracking Log (Federal Agency)
Track each FOIA request from intake to final determination, with deadline monitoring, assignment, search, review, fees, and closure in one federal agency log.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Federal Government · Public Administration · Records Management · Legal And Compliance
Overview
This FOIA Request Intake and Tracking Log is a case-management template for federal agencies that need to record incoming requests, assign ownership, monitor the statutory response deadline, and document the path to final determination. It gives you one place to capture the request summary, scope, receipt method, requester contact details, search offices, review status, fees, exemptions applied, and closure notes.
Use it when your agency receives FOIA requests through multiple channels and you need a consistent record of what happened, who owns the case, and what still needs to be done. The log is especially useful when several offices must search for records, when extensions may apply, or when you need an audit trail for later questions about timing and response decisions.
Do not use this template as a substitute for your agency’s legal review process or records retention rules. It is not meant for informal complaints, general public inquiries, or requests that do not require FOIA processing. If your workflow is very simple and handled by one person end to end, you may need fewer fields; if your cases involve consultations, appeals, or expedited processing, you may need to add those fields with conditional logic. Keep the form focused on the minimum necessary data, and avoid collecting PII that is not needed to process the request.
Standards & compliance context
- This template supports an audit trail for FOIA processing by capturing receipt, assignment, search, review, determination, and closure milestones.
- The deadline fields help staff monitor the 20-business-day statutory response window and document when an extension reason is recorded.
- Requester contact fields should follow data minimization principles and collect only the PII needed to process and respond to the request.
- If the log is used in a public-facing intake workflow, it should include clear consent or disclosure language for any PII collected and meet WCAG 2.1 AA accessibility expectations.
- Agency-specific FOIA rules, records retention requirements, and consultation procedures should govern any added fields or status values.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Intake and Tracking Details
This section captures the request as it arrives so the agency can identify the case, understand the scope, and preserve the receipt record.
-
Tracking Number
Unique case identifier for audit trail and status tracking.
-
Date Received
Date the FOIA request was received by the agency.
- Receipt Method
-
Requester Name
Optional. Collect only if needed to process the request or send a response.
-
Requester Email
Optional. Use only if email is needed for correspondence.
-
Requester Affiliation or Organization
Optional. Organization or media affiliation, if provided by the requester.
-
Request Summary
Brief summary of the records requested. Avoid collecting unnecessary personal data.
-
Scope of Request
Describe the record types, date range, offices, or systems implicated by the request.
Deadline and Case Status
This section keeps the statutory clock, extension status, and current case stage visible so deadlines do not get lost.
-
20 Business Day Statutory Deadline
Calculated or entered deadline for the initial FOIA response under the 20 business day rule.
- Does a statutory extension apply?
- Extension Reason
- Current Status
-
Status Update Date
Date the status was last updated.
- Priority Level
Assignment and Search
This section shows who owns the work, which offices searched, and what was found so the search effort is traceable.
-
Assigned To
Name or team responsible for processing the request.
- Assigned Date
- Offices or Components Searched
- Search Start Date
- Search Completion Date
- Records Found?
-
Search Notes
Document search locations, custodians, and any limitations encountered.
Review, Fees, and Determination
This section documents the disclosure decision, fee handling, exemptions, and closure so the final response is defensible.
- Fee Status
- Review Status
- Exemptions Applied
- Final Determination
- Determination Date
- Response Sent?
-
Closure Notes
Summarize the final response, release package, referral, or closure reason.
How to use this template
- 1. Create a new log entry as soon as a FOIA request is received and enter the tracking number, receipt date, receipt method, requester details, and a concise request summary.
- 2. Record the request scope and set the statutory deadline so the case has a clear response window from the start.
- 3. Assign the case to the responsible staff member or office, note the assignment date, and list every search office that must look for responsive records.
- 4. Update search start and completion dates, record whether records were found, and add search notes that explain where the search was conducted and any limitations.
- 5. Track fee status, review status, exemptions applied, final determination, response sent, and closure notes until the request is fully closed.
Best practices
- Use a date picker for receipt, deadline, assignment, search, determination, and closure dates so the log stays consistent and sortable.
- Mark only the fields you truly need as required, and keep requester contact fields limited to the minimum necessary for processing.
- Use conditional logic to show extension_reason only when deadline_extension_applies is selected, and hide review fields until a search is complete.
- Standardize current_status values such as received, assigned, searching, reviewing, awaiting fees, responded, and closed so reporting stays clean.
- Record the search offices by name and note the search method or repository used, not just a generic statement that a search occurred.
- Document exemptions and fee decisions as soon as they are made so the final determination reflects the actual review path.
- Add a clear what happens after I submit note if this template is exposed to requesters or used as an intake form, including who receives the submission and how it is processed.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this FOIA intake and tracking log cover?
It covers the full lifecycle of a federal FOIA request: intake details, statutory deadline tracking, assignment, search activity, review status, fees, exemptions, and final determination. The template is designed to create a clear audit trail from receipt through closure. It is useful when multiple offices may need to search for records or when deadline management matters.
Who should use this template?
FOIA officers, paralegals, records staff, program offices, and supervisors who coordinate responses can use it. It is especially helpful when one team receives requests and other offices perform the search or review work. The log also supports handoffs, so a request does not stall when staff change.
How often should the log be updated?
Update it at intake, whenever the status changes, after each search or review milestone, and again when the final determination is sent. For deadline-sensitive requests, daily review is a practical cadence. The goal is to keep the current status and next action visible without relying on email threads.
Does this template help with the FOIA 20-business-day deadline?
Yes. The statutory deadline field and deadline extension fields make it easier to track the response window and document when an extension applies. That said, the log should reflect your agency’s actual FOIA process and any applicable tolling or extension rules. It is a tracking tool, not legal advice.
What are the most common mistakes when using a FOIA log?
Common mistakes include leaving the receipt date blank, failing to assign an owner, not recording which offices searched, and updating the status only at the end of the case. Another frequent issue is documenting exemptions or fees too late, after the response has already been drafted. A good log keeps those fields current as the case moves.
Can this template be customized for different request types or agencies?
Yes. You can add fields for request tracking numbers, component offices, consultation status, expedited processing, or appeal handling if your workflow needs them. Agencies can also rename status values to match internal case stages. Keep the form focused on the data you actually use so it stays easy to maintain.
How does this log fit with records systems or case management tools?
It can sit alongside a records management system, shared drive, or case management platform as the operational log for the request. Many agencies use it to capture the working status while storing responsive records and correspondence elsewhere. If you integrate it with notifications or task assignments, make sure the fields still support a clean audit trail.
What should be included in the request summary and scope fields?
Capture enough detail to identify what the requester is seeking, the date range, subject matter, and any limiting language that narrows the search. Avoid collecting unnecessary PII in the summary if it is not needed to process the request. Clear scope notes reduce misrouting and help search offices understand exactly what to look for.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
-
Overcome enterprise-wide AI deployment challenges with scalable GenAI strategies that cut costs, boost adoption, and deliver measurable ROI.
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
Ready to use this template?
Get started with MangoApps and use FOIA Request Intake and Tracking Log (Federal Agency) with your team — pricing built for small business.
