How to Save Text Messages for Public Records

Most guides on saving text messages are written for people rescuing a personal conversation before switching phones. Government offices face the same mechanical problem with entirely different stakes: texts about public business are public records, records laws require them to be kept on a schedule and produced on request, and "the message was on someone's phone and the phone is gone" is a compliance failure, not an excuse. This guide covers how to save texts properly when the audience is a records officer, an auditor, a requester, or a judge.

The Legal Baseline: Texts Are Records

The rule is now settled across essentially every American jurisdiction: a record is defined by its content, not its container. Under the Federal Records Act, federal electronic messages are records when they document agency business, and 44 U.S.C. 2911 specifically prohibits officers and employees from creating or sending records on non-official messaging accounts unless the message is copied to an official account promptly. State public records acts reach the same result for state and local government: a text about agency business is a public record whether sent from a government phone or a personal one. Our companion piece on whether government texts are public records walks the case law; this article assumes the answer, which is yes, and turns to execution.

Two distinct duties follow:

1. Retention: keep the record for the period your records schedule assigns to that type of content, whether that is a transitory notice kept briefly or substantive correspondence kept for years.
2. Production: find and produce it when a public records request, subpoena, or audit asks, within statutory response deadlines.

Saving methods must serve both. A screenshot in someone's camera roll technically preserves a message and completely fails production, because no one can find it.

Method 1: Capture at the System Level (the Real Answer)

The only approach that scales is conducting official texting on a system that records itself. An organizational texting platform used for agency communication gives you:

• Automatic capture of every message, inbound and outbound, with sender, recipient, timestamp, and delivery status, no employee action required.
• Central search across all conversations by keyword, number, date range, or staff member, which is what turns a records request from a device roundup into a query.
• Retention rules applied by policy, so transitory and substantive messages are kept per your schedule rather than per each employee's deletion habits.
• Clean export to PDF or CSV for productions, with metadata intact; our walkthrough on exporting text message transcripts covers the production step in detail.

Purpose-built government texting platforms are designed around exactly these duties. System-level capture also solves the hardest problem in this domain, which is not technology but behavior: employees will text because texting works, and if the official channel is convenient, the texting happens where it is recorded.

Method 2: Saving Messages From Individual Phones

Until a managed channel exists, or for the personal-device messages that predate it, offices fall back to device-level capture:

1. Screenshot and file, for short threads. Capture the full conversation including the contact header, verify timestamps are visible, then move the images out of the camera roll into the records system, named and dated. On both iPhone and Android you can select screenshots and print or save them to a single PDF, which files better than loose images.
2. Backup and extract, for long threads. Back the phone up to a computer and use extraction software to export conversations to PDF or CSV with metadata. This is the defensible route for anything beyond a few screens.
3. Forward-to-official-account, for stray messages. When public business lands on a personal phone, the federal model in 44 U.S.C. 2911, copying the message to an official account within 20 days, is a sound template for any government: get the content into an official, searchable repository promptly, then conduct the rest of the conversation on the official channel.
4. Printing. Records offices and courts often want paper. Print from the exported PDF, not from photographs of a screen held at an angle; the export preserves legibility and metadata.

Building the Policy Around the Mechanics

Saving messages reliably is a program, not a favor. The elements, drawn from state archives guidance and the National Archives' rules for federal electronic messages:

• Classify texts in your records schedule. Most schedules treat messages by content: transitory (a "running late" note) with short retention, substantive correspondence with the retention of its paper equivalent. Write down which is which, with examples employees will recognize.
• Designate the official channel. Policy should name the system for official texting and prohibit conducting agency business over personal messaging apps, especially disappearing-message apps, which are functionally incompatible with records law.
• Cover departures. Offboarding must include confirming the departing employee's messages are captured before devices are wiped or turned in. Lost-at-departure is among the most common ways agencies end up unable to answer requests.
• Address legal holds. When litigation or an investigation is anticipated, preservation duties override ordinary deletion schedules. The policy should say who issues holds and how texts are frozen.
• Train annually, briefly. The whole policy fits on a page: business texts are records, use the official channel, copy strays over promptly, never use disappearing messages for public business.

The rules such a policy has to satisfy are laid out in our guide to government SMS compliance requirements.

Pitfalls That Generate Findings and Headlines

• Relying on carriers. Carriers retain billing metadata, not message content, beyond brief windows. They are not your records system.
• Assuming personal phones are out of reach. Courts have repeatedly ordered searches of personal devices for public-business messages, and refusing to look is its own violation in many states.
• Auto-delete settings. Phones set to delete messages after 30 days to save storage will destroy records on schedule. Official-channel capture makes the phone setting irrelevant; without it, the setting can put the office in ongoing conflict with its retention obligations.
• Disappearing-message apps. Using ephemeral messaging for public business has produced litigation, sanctions, and scandal across jurisdictions. Prohibit it in writing.
• Saving without indexing. A folder of ten thousand unnamed screenshots preserves nothing anyone can produce within a statutory deadline. Storage has to be searchable to satisfy production duties.

This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your own obligations with qualified counsel or the relevant regulator.

Frequently Asked Questions

How do I print out text messages for records purposes?

Export the conversation first, then print the export. On iPhone, back up to a computer and use extraction software to produce a PDF; on Android, use an SMS export app; on an organizational texting platform, use built-in export. For short threads, screenshots combined into a PDF and printed also work. Ensure timestamps and participant names appear on the printout.

Are text messages on personal phones public records?

When they concern public business, generally yes. State supreme courts and attorneys general across the country have concluded that content, not device ownership, controls, and the federal rule in 44 U.S.C. 2911 requires copying business messages from non-official accounts into official ones. Agencies should require official-channel texting so personal devices stop accumulating public records.

How long must government text messages be kept?

As long as your records retention schedule assigns to that content type. Transitory messages may be kept briefly; substantive correspondence typically carries multi-year retention matching its paper equivalent. The schedule is set by your state archives or records authority, and legal holds suspend deletion regardless of schedule.

What is the best way for a government office to save text messages?

Conduct official texting on an organizational platform that captures every message automatically with searchable logs, policy-based retention, and export. Device-level methods, screenshots, backups, forwarding, are fallbacks for stray messages, not a program. Capture that depends on each employee remembering to save is capture that fails.

Can deleted text messages be recovered for a records request?

Sometimes, through forensic examination of the device, and agencies under litigation holds may be obliged to attempt it, but recovery is uncertain and expensive. The compliance posture is prevention: capture messages at the system level so deletion from a handset does not destroy the record.

Recordkeeping That Happens Automatically

FRANSiS records every official text as it is sent and received, with searchable logs, retention aligned to your schedule, and an AI Powered Helper managing routine resident replies. Contact us to put your texting on the record, effortlessly.