Once Texts or Electronic Messages Are Assessed as Being Official Records: How Long Do You Have to Transfer Them to the Office Repository?

There is no single statutory transfer deadline that applies to every organization. Once a text or electronic message has been formally assessed and designated as an official record, the transfer window is set by the records retention schedule, the records management policy, or the specific legislative framework governing your jurisdiction and sector. In most public-sector environments, the practical expectation is transfer to the official repository at the point of designation or within the current reporting cycle, not months later. For regulated industries, that window can be as short as 24 hours for certain high-risk communications and as long as several years for low-risk administrative messages.

The key condition is this: the clock starts when the assessment decision is documented, not when the message was originally sent or received. That distinction matters more than most guidance admits.

Why the Transfer Clock Starts at the Assessment Decision, Not the Message Date

Records management theory separates the moment of creation from the moment of declaration. A text message sitting on a staff phone is not yet an official record in the formal sense, even if it contains information that will later become one. It becomes a record the instant an authorized person assesses it against the definition in the relevant standard and records that determination.

The ISO 15489 records management standard, maintained by the International Organization for Standardization, frames records as information created or received and maintained as evidence by an organization in pursuance of legal obligations or in the transaction of business. The designation is an act. Once that act is completed and logged, the record enters the custody chain, and custody rules apply.

This is why the common assumption that you have 30 days from receipt is unreliable. A message received in January but assessed in September has a transfer obligation that begins in September. The January date is an evidentiary fact about the record's origin, not the trigger for transfer.

Practically, organizations that confuse the two dates create gaps in the audit trail. A regulator asking why a critical message sat on a device for eight months after it was flagged will not accept "we were within the retention period" as an answer if the assessment log shows the designation happened in month one. The assessment date is the defensible anchor.

One more boundary: assessment is not the same as a casual review. An IT administrator scrolling through messages for technical reasons has not assessed them as records. The assessment must be performed by someone with the authority to make that determination, and the outcome must be documented in a way that survives staff turnover.

The Four Governing Frameworks That Set Your Actual Deadline

Four distinct sources of authority set transfer deadlines, and they frequently conflict. Knowing which one binds you requires reading your own instrument, not a generic guide.

The statutory layer is usually the floor, not the ceiling. A public body subject to a national archives act may have a general obligation to transfer records of enduring value within a defined period, but its own retention schedule can be stricter. The sector regulation layer often overrides both for specific message categories.

Financial conduct regulators in several jurisdictions require firms to capture and retain electronic communications relating to regulated business, with supervisory expectations that captured messages are transferred to the firm's official recordkeeping system promptly rather than held on individual devices. The exact number of days varies by regulator and has been revised repeatedly. Confirm the current figure with your own supervisory authority before relying on any published summary.

Litigation holds are the sharpest edge. Once a preservation notice is issued, the transfer obligation typically collapses to "immediately" and any delay becomes a spoliation risk. Courts in several common-law jurisdictions have sanctioned organizations for failing to preserve text messages after a hold was reasonably anticipated, even where no formal notice had yet been served.

How to Determine Your Specific Deadline in Five Steps

Follow these in order. The output is a single number in days, plus a documented exception path.

1: Locate your approved records retention schedule and find the entry for the record class your message falls into (for example, "executive correspondence," "contract negotiation records," or "case management communications"). Note the transfer instruction, which is often separate from the retention period. 2: Check whether a sector-specific instrument applies to your organization and record class. Search the supervisory authority's published rules for the phrase covering electronic communications capture and transfer, and record the version date of the rule you are using. 3: Compare the schedule figure against the statutory minimum in your jurisdiction's archives or records act. Where they differ, the shorter period governs unless your legal counsel advises otherwise in writing. 4: Confirm whether any preservation obligation is active: a litigation hold, an investigation notice, a freedom-of-information request, or a complaint. If any applies, the deadline is immediate regardless of the schedule. 5: Document the resulting deadline in the assessment record itself, alongside the assessor's name, the date of designation, and the repository destination. This record is your defense.

Handle failure this way: if the deadline has already passed when you discover the omission, transfer the record immediately rather than waiting for the next cycle, log the late transfer with the reason, and notify the records manager. Do not backdate the assessment. A documented late transfer is manageable; a falsified assessment log is a disciplinary matter in most organizations.

If your organization has no approved retention schedule covering electronic messages, the answer is that you have no defensible deadline, and that gap is itself a compliance finding. Escalate to whoever owns records management before the next assessment.

Public Bodies vs. Private Firms: A Side-by-Side Transfer Comparison

The two environments diverge sharply, and staff moving between them routinely carry the wrong assumptions.

Public bodies face a particular trap with personal devices. When a staff member uses a personal phone for official business and the message is later assessed as a record, the transfer obligation applies even though the device is privately owned. Several information commissioners have ruled that such messages are subject to access requests and must be transferred into the official system, and the practical difficulty of extraction is not an excuse for delay.

Private firms face the opposite problem: platforms with default deletion settings. A messaging tool configured to erase messages after 30 days will destroy records before the transfer deadline arrives unless the retention setting is changed at the point of designation. The fix is procedural — change the setting when the assessment is logged — but it requires someone to remember.

The comparison row most guidance omits is accountability. In a public body, an unexplained delay can become a formal finding against the institution. In a private firm, the same delay typically surfaces only in litigation, which means the risk is invisible until it is expensive.

Retention Period vs. Transfer Deadline: The Distinction That Trips Most Teams

These are two different clocks running in parallel, and conflating them is the most common cause of late transfer.

The retention period governs how long the record must be kept before authorized disposal. The transfer deadline governs how quickly it must reach the official repository after designation. A record can have a seven-year retention period and a 30-day transfer deadline. Nothing about the longer figure extends the shorter one.

Think of it as the difference between when a parcel must arrive at the warehouse and when it may be destroyed. Missing the arrival deadline does not change the destruction date, and staff who hear "seven years" often assume the record can stay where it is.

A worked example using figures from a typical retention schedule: suppose a message is designated on 3 March, the schedule requires transfer within 30 days, and retention is 7 years from the end of the financial year of creation. The transfer deadline is 2 April. The disposal eligibility date falls 7 years after the financial year end, which for a March creation would be 31 March seven years later. Between those two dates lies more than 2,500 days during which the record must sit in the repository, not on a phone.

The test is simple. If the record is not in the repository by the transfer deadline, it is not being retained in a controlled way, regardless of whether it still exists somewhere. Existence is not custody.

Defensible Evidence: What the Assessment Record Must Contain

When a regulator or court asks why a message was or was not transferred on time, the assessment record is the document that answers. Its contents determine whether the organization's position is defensible.

At minimum, the record should identify the message by a stable unique reference, the date and time of the assessment, the name and role of the assessor, the record class assigned, the resulting transfer deadline calculated from the applicable instrument, the repository destination, and the date the transfer was completed. Without the calculated deadline, there is no way to demonstrate the organization knew what it had to do.

The version of the governing instrument matters too. Retention schedules are revised, and a transfer completed under an outdated schedule may not satisfy a current one. Recording the version date of the schedule or rule applied at assessment time allows the organization to show it followed the instrument in force on that date.

Avoid the temptation to reconstruct assessment records retrospectively. Several tribunals have treated contemporaneous documentation as materially more credible than records created after a dispute arose, and reconstructed logs tend to contain inconsistencies that undermine the whole file. If records are missing, the stronger position is to acknowledge the gap and describe the remediation.

For high-stakes categories — legal advice, regulatory correspondence, disciplinary matters — the assessment record should also name the repository system, not just the department. "Transferred to records" is not evidence. "Transferred to the case management system, reference number recorded" is.

Where Deadlines Get Missed: Five Recurring Failure Cases

Failure is rarely dramatic. It usually looks like a message that everyone assumed someone else had moved.

The first case is the handover gap. A designated record sits on the phone of an employee who leaves the organization, and the device is wiped as part of offboarding before the transfer happens. The assessment log shows a designation and no completion. This is the most common failure in organizations without device management controls tied to the assessment process.

The second is auto-deletion before transfer. A chat platform configured to remove messages after 30 days erases the evidence before the 30-day transfer deadline is reached, particularly where the deadline runs from the end of a reporting period. The record class exists in the log; the record does not.

The third is the personal-account problem. Messages sent from personal accounts are often excluded from capture systems, and the assessment may occur only after a complaint surfaces them. By then the original may be unavailable, and the transfer obligation is impossible to satisfy.

The fourth is the wrong repository. A message transferred to a shared drive rather than the official repository satisfies nobody's definition of custody. The record exists, but it is not under the controls that make it retrievable and trustworthy.

The fifth is the litigation-hold override. Staff continue applying the routine schedule after a preservation notice has been issued, and messages are transferred late or, worse, disposed of under the schedule. This is the failure case most likely to attract sanctions.

Each of these is preventable with a single control: an exception report that lists designated records with no matching transfer completion, reviewed weekly. The report takes minutes to read and catches every one of these cases before the deadline passes.

When "Immediately" Applies: Triggers That Override the Schedule

Four triggers collapse the routine deadline to same-day or next-business-day transfer, and staff should recognize them without waiting for legal advice.

A litigation hold is the first. Once a preservation notice is issued or litigation is reasonably anticipated, every designated record touching the matter must move to the repository immediately, and any auto-deletion must be suspended. The deadline is not "soon"; it is before anything can be lost.

An active regulatory investigation is the second. Supervisory authorities in several sectors expect firms to be able to produce communications on request, and a message still on a device when the request arrives creates an immediate problem. Transfer on notice.

A freedom-of-information or access request is the third, in public bodies and in jurisdictions with access regimes covering private entities performing public functions. Once a request covers a class of messages, designated records in that class should be transferred and logged so the search is defensible.

A complaint or grievance is the fourth. Internal dispute processes frequently turn on message evidence, and the transfer obligation should be treated as immediate from the date the complaint is logged.

In all four cases, document the trigger, the date it was recognized, and the transfer completion. If the routine deadline would have allowed more time, the record should state why the shorter path was taken. That note demonstrates that the organization's controls worked rather than merely that nothing went wrong.

FAQ

Does a text message become an official record the moment it is sent?

No. Sending a message creates a communication, not a record. It becomes an official record only when an authorized person assesses it against the definition in the applicable standard or legislation and documents that determination. Until then it is a candidate, and no transfer deadline runs. This is why organizations that rely on device-level archiving alone often cannot show when the designation occurred.

What happens if the transfer deadline passes before anyone notices?

Transfer immediately and document the late completion with the reason and the discovery date. Do not backdate the assessment record. In most jurisdictions and organizational policies, a promptly remediated late transfer is treated as a process failure, while an altered log is treated as misconduct. Notify the records manager the same day so the exception is visible rather than buried.

Can I keep a designated record on my phone if the retention period is seven years?

No. Retention period and transfer deadline are separate clocks. A seven-year retention period does not authorize seven years on a device; it specifies how long the record must be kept once it is in controlled custody. Keeping it on a phone means it is not in custody at all. The transfer deadline applies regardless of how long the record must ultimately be retained.

Is there a universal number of days that applies to all organizations?

No universal figure exists. Statutory archives regimes, sector regulators, and internal retention schedules each set different windows, and they frequently conflict. Financial and health regulators tend to impose the shortest periods for specified categories, sometimes measured in hours. The only reliable answer comes from reading your own governing instrument and confirming the version in force on the assessment date.

How does a litigation hold change the transfer deadline?

It overrides it. Once a preservation notice is issued, or litigation is reasonably anticipated, the routine schedule stops applying and designated records covering the matter must be transferred immediately. Auto-deletion settings must also be suspended. The transfer becomes part of the preservation obligation, and delay carries spoliation risk rather than a simple process finding.

Do messages on personal devices need to be transferred?

Yes, if they were used for official business and have been assessed as records. Ownership of the device does not change the status of the message. Information commissioners have treated such messages as subject to access requests, and the practical difficulty of extraction does not excuse delay. The organization should extract and transfer promptly, then document the method used.

Who is accountable if a designated record is lost before transfer?

The accountable officer depends on the environment: in public bodies it usually sits with the accounting officer or records manager under the archives act; in private firms it sits with the board and the compliance function. The individual assessor is responsible for logging the designation and flagging exceptions. Responsibility for the control gap sits higher than the person who happened to hold the phone.

What should the assessment record contain to be defensible?

At minimum: a stable message reference, assessment date and time, assessor name and role, record class, the calculated transfer deadline and the instrument version used to derive it, the repository destination, and the completion date. Records naming the specific system, rather than a department, survive scrutiny far better. Contemporaneous entries are materially more credible than reconstructed ones.