Text Message Archiving for FOIA Requests: A Compliance Guide for Government Agencies

FOIA became law in 1966, long before officials ran city business from a smartphone. But the law was written to be format-neutral. Courts and agencies have applied that same logic to modern communication channels. In 2014, the Federal Records Act’s definition of a record was amended to cover “all recorded information, regardless of form or characteristics.” That change brought text messages and instant messages as records too.

The numbers show why this matters now.

Federal agencies received over 1.7 million FOIA requests in Fiscal Year 2025 and processed most of them at the cost of $661 million. Requests aren’t just growing in number. They’re growing in scope. Requesters now ask for “any and all” communications across every channel and multi-year date ranges. Email alone can’t cover that anymore.

State and local governments feel this most. Text messaging has become the default channel for daily government work. Some examples are council members texting before a vote, school staff discussing a disciplinary case, police relaying dispatch details. Most agencies still have no way to find those records when a request comes in.

Text messages are no longer a gray area in records law. The question isn’t whether they count, but whether your agency can find them when asked.

The Federal Standard: Content Determines Status, Not the Device

Under the Federal Records Act and FOIA, a communication is a federal record if it documents the agency’s organization, functions, policies, decisions, procedures, or operations. This is regardless of what device or account was used to create it. Under the National Archives and Records Administration (NARA), text messages sent or received by federal employees on official business are federal records and must be preserved accordingly. NARA has pushed agencies to designate “capstone” officials and adopt capture methods rather than relying on employees to self-report or manually forward messages.

State Sunshine Laws

Every state has its own public records laws. Most states define a “record” broadly enough to include text messages. Courts have reinforced this repeatedly. In Illinois, an appellate court ruled that texts about public business sent from personal accounts of a mayor and a city health director still qualified as public records under FOIA. The court rejected the idea that a personal device could be used to dodge disclosure rules. In Michigan, a circuit court order forced a third-party carrier to hand over text messages. Those messages became central to a high-profile public corruption case.

This same reasoning shows up in case after case, regardless of state. Courts look at the content of a communication, not the device or account it moved through. A personal phone offers no legal shield once a message touches public business. That standard puts the burden on agencies to have a process for finding these records.

BYOD

Bring-your-own-device policies are common in government because they save money and reduce IT overhead. But they also create one of the most difficult compliance gaps in public sector records management. When an employee uses their personal phone to discuss official business, the message is considered a public record, but the device itself belongs to the employee, not the agency. This raises real operational questions: Can the agency search the phone? Does the employee need to submit a sworn declaration about their search efforts? What happens if the employee deletes the thread before the search happens?

Most agencies have no clear answer, because most BYOD policies were written for security and cost control, not records compliance. That gap leaves records officers relying on employee cooperation and good faith, which is not a defensible position in litigation. A better approach is capturing messages automatically at the point of transmission, rather than depending on an employee to hand over their phone later.

The Increase in Backlogs, Lawsuits, and Processing Delays

FOIA lawsuits against federal agencies hit record levels several years ago and have continued climbing as backlogs grow.

• Agencies have received a record-setting 1,707,197 FOIA requests in FY 2025, up 13.7% from the year before.
• Processed a record-high 1,635,055 requests in 2025.
• Administrative appeals jumped 59.38% year-over-year, reaching 32,059.
• Requests and processing volume have both climbed for five consecutive years running.

This is a clear signal that requesters are increasingly willing to escalate when they believe an agency’s response was incomplete. If a request for “all communications” only returns emails because texts were never archived, that’s an incomplete response waiting to become an appeal, and potentially litigation.

Processing time is the other pressure point. Simple requests that should take a matter of weeks routinely stretch far longer once an agency has to manually chase down text messages from individual employee devices. Agencies that archive and index messages automatically skip the hours of manual reconstruction entirely.

Spoliation Risk

When a public records request or litigation hold is issued, and responsive text messages have since been deleted, an agency faces real legal exposure. The deletion might come from carrier retention policies, a device reset, or an employee simply clearing their inbox, but the agency can still face spoliation sanctions, adverse inference instructions from a judge, and separate public records violations.

Most wireless carriers do not retain the content of text messages for any length of time, and several major carriers keep messages on their own systems for only a few days at most. Relying on the carrier for retention isn’t a real safeguard, because most keep content for only a few days.

Not all archiving tools are built for the specific demands of public records compliance. A solution designed for FOIA readiness needs to do more than store messages.

Capture Every Channel and Every Ownership Model

Public employees don’t limit themselves to standard SMS. They use iMessage, WhatsApp, and other messaging platforms, often from personal phones under BYOD, CYOD, COPE, or COBO ownership models. A compliant text message archiving program has to capture all of it consistently, not just the channel that’s easiest to intercept.

iMessage is a special case because Apple’s end-to-end encryption and lack of native archiving tools historically made it nearly impossible to capture in a compliant, evidentiary format. That’s a real problem given how common iPhones are among public sector employees. An iMessage archiving solution needs to preserve full conversation threading and native formatting, rather than breaking messages into fragmented 24-hour chunks.

Preserve Messages in an Evidentiary, Tamper-Proof Format

For a text message to hold up as evidence in litigation or to satisfy a records officer that a production is complete and unaltered, it has to be preserved in a format that demonstrates authenticity. This means it can be verified as genuinely sent and received by the claimed parties, with metadata intact, and without the possibility of editing. Screenshots don’t hold up, since they strip out metadata and can be edited. A proper archive digitally signs and timestamps content on capture, creating an unalterable record from day one rather than trying to reconstruct authenticity after the fact.

Enable Fast, Defensible Search Across Every Channel at Once

A records officer facing a statutory response window (federal) or a state-specific deadline can’t afford to run five separate searches across five separate systems. The most effective programs consolidate email, SMS, iMessage, WhatsApp, and social media into a single searchable index, so a single query returns the full picture of a conversation regardless of which channel it happened on.

Support Redaction and Legal Hold

FOIA and its state equivalents all permit redaction of legitimately exempt content including personnel records, ongoing investigations, personal identifying information. But manual redaction across thousands of text messages is slow and error-prone. A compliant system needs built-in redaction tools that let a records officer hide sensitive content before release without altering the underlying archived record. It also needs automated legal hold functionality, so that once litigation or an investigation is reasonably anticipated, responsive messages are locked from deletion immediately, rather than relying on someone remembering to flag them.

Retention schedules for text messages follow the same logic as retention for any other record type: the content and purpose of the record determines how long it must be kept. A text message discussing routine scheduling may have a short retention window, while a message documenting a policy decision, a personnel action, or a matter later relevant to litigation may need to be preserved indefinitely.

This is where a written, format-neutral retention policy becomes essential. Retention schedules should be built around records categories (budgeting, personnel, permitting, correspondence, litigation-related) rather than around the communication channel. Text messages should be mapped into the same categories your agency already uses for email and paper records. NARA’s guidance to federal agencies takes exactly this approach.

The core FOIA obligations are the same across the public sector, but the practical challenges shift depending on the type of agency.

School districts —  face a complex compliance problem because text messages between teachers, administrators, and staff about students often intersect with FERPA protections at the same time they’re subject to state open records law. A district can’t withhold a message because it references a student. But it also can’t release personally identifiable student information without proper redaction. Records officers need to be able to isolate and redact FERPA-protected content without altering the broader archived record.

Law enforcement and public safety agencies —  generates a high volume of sensitive text traffic (dispatch coordination, witness communication, internal case discussion). Most of the information is usually relevant to a criminal case, a civil rights lawsuit, or an internal affairs investigation. For these agencies, the difference between a defensible record and a spoliation finding that can affect a prosecution or expose the department to liability.

Financial regulators —  sit at the intersection of FOIA-style public records obligations and separate federal recordkeeping rules like SEC 17a-4 and FINRA requirements for regulated communications. Any public agency that also manages investments, bonds, or pension funds may need an archiving approach that satisfies both sets of rules simultaneously. The same message can be subject to a records request and a separate regulatory retention rule at once.

City councils and elected officials’ offices —  frequently named in high-profile public records disputes, largely because council members and executives often use personal phones for genuinely public business. This is where a “no personal devices” policy is least likely to be followed in practice, which makes systematic, network-level capture far more reliable than a policy that depends on individual compliance.

Getting from policy to practice takes a clear plan. Here’s how to build a text message archiving program when a real request comes in:

Step 1: Audit your current exposure. Before buying any technology, find out how many employees use mobile devices (personal or agency-issued ) to conduct official business by text. Identify which departments are highest-risk (public safety, elected officials’ offices, anything customer-facing) and whether any of those employees have already received or anticipate a records request touching their text messages.

Step 2: Write a format-neutral retention and archiving policy. Your policy should state explicitly that text messages about official business are public records subject to the same retention schedule as email or paper records, regardless of the device used to send them. Set clear expectations for BYOD employees about separating personal and business communications.

Step 3: Choose an archiving solution built for evidentiary integrity and multi-channel capture. Look specifically for a platform that captures SMS, iMessage, and other messaging channels in one system, supports your agency’s device ownership models, and produces content in native or standard formats acceptable for both FOIA production and litigation.

Step 4: Train staff on the policy. Most compliance failures come down to employees not realizing a text from their personal phone still counts as a public record, not the software itself. Training should specifically address the misconceptions that using a personal device or deleting the thread removes the record from FOIA scope.

Step 5: Test your response process before a real request arrives. Run a mock FOIA request internally. Time how long it takes your records officer to locate, review, redact, and produce a complete set of responsive communications across every channel. If it takes days instead of hours, that gap will show up publicly the first time a real request comes in.

• Assuming a device policy solves the problem. A “no personal devices for work” policy sounds clean on paper, but it’s nearly impossible to enforce in practice. It doesn’t retroactively fix years of unarchived messages already sent from personal phones.
• Relying on the carrier for retention. Most carriers retain message content for only a few days. Treating carrier storage as a backup archive is one of the most common and most dangerous assumptions agencies make.
• Searching manually, employee by employee. Asking each staff member to individually search their own phone and self-report responsive messages introduces inconsistency, delay, and legal risk if a message is later found to have been missed or even unintentionally withheld.
• Ignoring iMessage and third-party apps. Agencies that archive SMS but not iMessage or WhatsApp create a partial, indefensible record, especially given how iPhone-dominant most government workforces are.
• No legal hold process. Without an automated way to freeze deletion on relevant messages once litigation is reasonably anticipated, agencies risk spoliation claims even when the failure to preserve was unintentional.

Intradyn built its platform around the reality that public records requests now span multiple communication channels. Our FOIA request software consolidates Email, SMS/text messaging, iMessage, and Social Media into one secure, centralized archive, so records officers can search across every channel simultaneously using keyword, phrase, wildcard, proximity, and range queries rather than running separate searches in separate systems.

• Every message is captured in real time, digitally signed, and timestamped to preserve evidentiary integrity
• Built-in redaction tools let your team prepare records for release without altering the underlying archived original
• Automated legal hold functionality protects responsive content the moment it’s needed, not after someone remembers to flag it
• Secure, scalable cloud infrastructure with unlimited storage means agencies don’t have to ration what they archive based on storage costs, one factor that quietly drives many agencies to under-archive

• Text messages about official business are public records under FOIA and every state’s sunshine law. The device or account used to send them has no bearing on that status.
• The Federal Records Act’s 2014 amendment and NARA guidance both confirm that federal agencies must preserve text messages the same way they preserve email and paper records.
• FOIA requests and appeals both hit record highs in FY 2025, and agencies that can’t produce text messages alongside email are structurally unable to fulfill a growing share of requests.
• BYOD policies save money but create real operational gaps. Most were written for security, not records compliance, and most agencies have no clear process for searching an employee’s personal phone.
• Deleted text messages create spoliation risk. Carriers typically retain message content for only a few days, so relying on the carrier as a backstop means an agency has no real retention at all.
• A compliant archiving solution needs to capture every channel, including iMessage, in a tamper-proof, evidentiary format, with built-in redaction and automated legal hold.
• Compliance challenges shift by sector: FERPA complicates school district records, criminal cases raise the stakes for law enforcement, and elected officials’ offices face the highest risk from personal device use.
• Building a defensible program takes five concrete steps: audit exposure, write a format-neutral policy, choose the right archiving solution, train staff, and test the response process before a real request arrives.

Are text messages considered public records under FOIA?

Yes. If a text message documents official business, it is treated as a public record under FOIA and every state’s equivalent sunshine law, regardless of whether it was sent from a government-issued or personal device.

Does using a personal phone protect a public official’s text messages from disclosure?

No. Courts in multiple states have ruled that using a personal device or personal account does not exempt communications about public business from disclosure requirements. The content of the message determines its status as a public record, not the device.

How long must government agencies retain text messages for FOIA purposes?

Retention periods depend on the content of the message and the records category it falls under, exactly as with email or paper records. Some categories carry short retention windows. If the message is tied to policy decisions, personnel matters, or anticipated litigation, it will be preserved much longer or indefinitely.

Can screenshots of text messages be used to satisfy a FOIA request or serve as evidence?

Screenshots are generally considered unreliable because they strip out metadata and can be edited or fabricated relatively easily. A defensible response typically requires messages preserved in their native or evidentiary format through a proper archiving system.

What happens if an agency doesn’t have a text message archiving system in place?

The agency risks incomplete FOIA responses, appeals, litigation exposure including spoliation sanctions if relevant messages were deleted, significant staff time lost to manual, or device-by-device searches.