FOIA Annual Report Data Compilation Worksheet

This worksheet gathers the core data points an agency needs to prepare its annual FOIA report. It is designed to compile request counts, backlog figures, processing times, exemption usage, fee waiver activity, appeals, and certification details in one place. Use it as the working file before finalizing the report for DOJ.

It is usually completed by the FOIA officer, records staff, or the person responsible for annual reporting. In larger agencies, one person may collect the numbers while another reviews the totals for accuracy. The submitter fields help document who prepared and sent the report package.

Use it once per reporting cycle, typically at year-end when annual FOIA reporting data is being assembled. Many agencies also update it periodically during the year so backlog and processing metrics are easier to reconcile later. That reduces last-minute cleanup and missing source data.

Pull from the FOIA case management system, tracking logs, appeal records, and any fee waiver or administrative notes maintained by the office. The data source confirmation field is there to document where the numbers came from. If a metric is estimated, note that clearly in the certification notes.

Common issues include mixing reporting periods, counting the same request twice, and using inconsistent definitions for pending, closed, or backlog. Another frequent problem is entering narrative notes without the underlying counts needed for the report. The worksheet works best when each field is tied to a single source and reviewed before certification.

Yes. The certification section creates a clear record of who confirmed the data and what sources were used, which helps with internal review and audit trail needs. It also supports data quality controls by separating raw counts from attestation and notes. That makes it easier to explain the report if questions come up later.

Yes. You can add fields for component-level rollups, internal reviewer sign-off, or links to source reports if your process requires them. Keep the structure focused on the final annual report inputs so the worksheet stays usable and does not become a second database. If you add custom fields, mark required versus optional clearly.

A dedicated worksheet reduces version confusion and makes it easier to see which numbers still need confirmation. It also keeps the reporting period, submitter details, and certification language in one place instead of scattered across emails. That usually leads to fewer reconciliation errors and a cleaner handoff to the final report.