How to Track Public Records Requests: Deadlines, Follow-Ups and Drafts

Task: Keep Every Request Accounted For

A small newsroom may have several public records requests open at once, each sent to a different agency and each at a different stage. One request may receive an acknowledgment within days. Another may be delayed by a search, transferred to another department or answered with a partial release. When correspondence is spread across individual inboxes, follow-ups are easy to miss.

A public records request tracker provides one shared view of the work. It should show what was requested, where it was sent, when the request was submitted, what response has arrived and what action comes next. The purpose is administrative control, not a substitute for the agency's official process or the legal rules governing access.

• Record each request from submission onward.
• Identify the responsible agency and contact.
• Make upcoming follow-ups visible.
• Preserve the history of correspondence and releases.

Inputs: Set Up a Shared Records Request Log

A records request log spreadsheet can be maintained in an approved shared office environment. Limit editing access to staff who need it, and establish a naming convention that keeps requests distinct. For example, a newsroom might use RR-2026-001 for its first request logged in 2026. The identifier belongs to the newsroom's internal system and does not replace an agency reference number.

Create separate columns for the request's subject, recipient agency, submission date, acknowledgment date, applicable response deadline, latest contact date, status, next action and next-action date. Include links or internal file references to the original request and response where the storage system permits. Avoid putting sensitive personal information into a broadly accessible sheet.

• Request ID.
• Subject and description of records sought.
• Agency and contact details.
• Submission and acknowledgment dates.
• Applicable deadline and source of deadline.
• Current status and next action.

Separate Dates That Are Often Confused

The submission date, acknowledgment date, statutory response deadline, estimated production date and newsroom follow-up date are different fields. Combining them in one deadline column creates uncertainty. An agency acknowledgment may confirm receipt without establishing when records will be produced. An estimated production date may also change after a search or consultation with another department.

Public records rules vary by jurisdiction and by the type of request. Some establish a deadline for acknowledgment or an initial response, while others address production, extensions or permissible delays differently. Check the current statute, regulation or official agency guidance before entering a deadline. If interpretation is disputed, consult an appropriate legal professional or press freedom organization.

For example, if a request is submitted on October 30 and the applicable rule requires an initial response within five business days, the tracker should calculate the date using the relevant local counting rules and applicable holidays. The example does not establish a universal five-day deadline. Record the rule and source alongside the date so another editor can understand the calculation.

• Submission date: when the newsroom sent the request.
• Acknowledgment date: when the agency confirmed receipt.
• Response deadline: the date established by applicable rules.
• Production estimate: the agency's stated expected release date.
• Follow-up date: the newsroom's next planned contact.

Tool Steps: Maintain the Log and Draft Follow-Ups

Enter a new request immediately after sending it. Copy its subject and agency name exactly, preserve the submitted text in the correspondence folder and add the agency's confirmation number when one arrives. Set the status to Submitted, then update it to Acknowledged, In Progress, Partially Fulfilled, Completed, Denied or another clearly defined category as correspondence changes.

A spreadsheet can highlight upcoming dates using conditional formatting. For example, a newsroom might flag follow-ups due within two working days and separately mark requests whose applicable response deadline has passed. These are internal workflow thresholds, not statements about legal deadlines. Make the color coding understandable in a written legend so another staff member can use the sheet.

An AI assistant can turn a row's existing information into a draft follow-up. Provide the request ID, agency, original submission date, previous correspondence and the specific unanswered question. Ask for neutral language that requests a status update and identifies any outstanding records. Require the assistant to leave missing dates and legal references blank rather than supplying plausible details.

• Create the request entry on submission.
• Save the original email and attachments.
• Update status after every substantive reply.
• Set a dated next action for every open request.
• Review flagged entries at the beginning of each workday.

A Records Request Follow-Up Template

A consistent records request follow-up template makes correspondence easier to prepare and review. It should identify the original request, acknowledge any response already received and state exactly what information is still needed. Keep the tone factual. Avoid treating an internal newsroom reminder as proof that an agency has missed a legal deadline.

For example, a draft can begin: 'I am following up on the records request submitted on [date] concerning [subject]. Please confirm the current status of the request and whether the records are expected to be released together or in stages. If additional information is needed to process the request, please identify the specific information required.' The brackets should be replaced using the original correspondence before sending.

A text assistant can adjust the wording for a partial production, an unanswered acknowledgment or a request for clarification about fees. The editor must compare the draft with the correspondence history and the applicable rules. Do not send an AI-generated assertion that an agency violated a deadline without establishing the relevant dates and legal requirements.

• Identify the original request and submission date.
• State what response or records have arrived.
• List the outstanding question or material.
• Request a status update or clarification.
• Retain a copy of the sent follow-up.

Human Checkpoint: Review Replies and Close Requests

Every agency response should be read by a person. Determine whether it acknowledges receipt, requests clarification, estimates a production date, releases records, withholds material or denies access. A short summary can help an editor scan correspondence, but the original message determines what the agency actually said.

When records arrive, compare the release with the scope of the original request. If the request sought emails, attachments and text messages, a production containing only emails may be partial. Record what was received and what remains outstanding. If an agency cites an exemption or denies access, preserve the exact explanation and consult the relevant legal or professional guidance before deciding on an appeal or other response.

Close a request only when its status is clear under the newsroom's own definition of completion. A final production may resolve the request, while a partial release or unresolved clarification may require further action. Keep the full correspondence and released documents in the newsroom archive even after the tracking row is marked complete.

Known Failure, Timing Notes and Slip Sheet

Shared spreadsheets can develop duplicate entries, inconsistent status labels and incorrect dates. A staff member may update the email thread without updating the tracker, leaving the next editor with an outdated picture. Protect formula cells, use a controlled list of status labels and assign responsibility for updating the log after each response.

Another common administrative risk is treating a calculated date as a legal conclusion. Holidays, weekends, extensions, request categories and local rules may affect deadlines. The person responsible for the request should confirm the applicable rule before a follow-up is characterized as overdue.

Author's stopwatch log: No personal timing result is claimed. Record the time required to enter new requests, review open items and prepare follow-ups during an ordinary workday. Note the number of active requests and the spreadsheet configuration. This gives the newsroom a local baseline for deciding whether the shared log is reducing administrative effort.

Slip Sheet: Record actual corrections when they occur, including duplicate request IDs, missed acknowledgments, incorrect deadline calculations and drafts that contain unsupported statements. Include the affected row, the correction and any workflow change needed to prevent recurrence. The following entries are preventive examples, not reported incidents.

• Duplicate request: retain one active ID and document the duplicate.
• Incorrect deadline: recalculate using the applicable primary source.
• Unrecorded partial release: update status and list outstanding material.
• Unsupported legal language: remove it and check the relevant rule.
• Missing follow-up owner: assign a named newsroom role and date.

Questions readers ask