{"id":22692,"date":"2025-10-15T10:18:27","date_gmt":"2025-10-15T15:18:27","guid":{"rendered":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/?p=22692"},"modified":"2026-01-12T10:12:23","modified_gmt":"2026-01-12T16:12:23","slug":"email-auto-deletion","status":"publish","type":"post","link":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/2025\/10\/email-auto-deletion\/","title":{"rendered":"Strategies for Developing Email Auto-Deletion Policies"},"content":{"rendered":"
\n
\"Person<\/figure>\n<\/div>\n\n\n

How long should government entities in Texas keep email? It’s one of our most frequently asked questions<\/a>, and like all our favorite questions here at TSLAC, the answer is, “it depends.” Though TSLAC has traditionally recommended the “sort and file” method<\/a>, these days many agencies are hoping to simplify their operations by establishing an auto-deletion policy for email. Can such a method work? Yes! But, there are important factors to consider before going down this path.<\/p>\n\n\n\n

Determine a Reasonable Auto-Deletion Time Period<\/h2>\n\n\n\n

As mentioned above, there is no standard retention period for email. Instead, just like with paper records or digital files on a computer, the retention period for each email will be based on the contents of that particular email. We often say that the TSLAC retention schedules are \u201cmedia neutral,\u201d which means that they are based on content, not format. This is based on the statutory definition of a \u201clocal government record\u201d (Local Government Code \u00a7201.003(8)<\/a>) and “state record” (Government Code \u00a7441.180(11)<\/a>). For example, if the normal practice in your office is to ask for time off by sending your boss an email, those emails would likely be considered leave records (GR1050-54b for local governments, 3.4.007 for state agencies) with a retention period of \u201cFE+3\u201d (fiscal year end + 3 years).<\/p>\n\n\n\n

Realistically, though, most employees only create emails that fall into a handful of categories, so it may be possible to set an entity-wide email auto-deletion policy that will cover the maximum retention period of most emails sent and received by your employees. To do that, you\u2019d need to first consider all the potential record series that could apply to your employees\u2019 emails. Once you\u2019ve made a list of potential record series that could apply, choose the longest retention period from that list. That way your blanket auto-deletion policy will meet the minimum retention periods of most of your employees\u2019 emails. <\/p>\n\n\n\n

One option is the “capstone” approach, which is what the National Archives and Records Administration (NARA) recommends<\/a> for federal government entities. With this approach, the auto-deletion time frame is adjusted based on an employee’s role or position. For example, a government entity could establish a longer auto-deletion time frame for executives, managers, or certain departments like legal. This tailored strategy can help target specific groups of people who may need or benefit from a longer email retention period, while allowing the majority of employee emails to be disposed of on a shorter time frame.<\/p>\n\n\n\n

For more tips on classifying email see: FAQ: How Long Do I Keep Email?<\/a>, FAQ: Is Email Always Correspondence?<\/a>, and our webinar series on email management<\/a>.<\/p>\n\n\n\n

Account for Outliers<\/h2>\n\n\n\n

Inevitably, some emails will need to be retained longer than the auto-deletion policy allows. To account for those cases, you’ll need to educate your employees on how to identify emails that need to be retained longer than your auto-deletion policy and establish a retention strategy for how you\u2019d like those emails to be saved.<\/p>\n\n\n\n

For example, let\u2019s say you\u2019ve analyzed the types of emails typically sent by your employees and set your government entity’s email client to delete any email older than a certain number of years. If one of your employees negotiates a contract with a vendor over email, that employee would need to be aware that any emails capturing contract negotiations likely fall under Contracts, Leases, and Agreements (GR1000-25) for local governments or Contract Administration Files (5.1.001a\/b) for state agencies and universities. Either way, the retention period applies to correspondence and similar records relating to contract negotiation and the retention period is based on the length of the contract. Since the contract may be in place for a varied or undetermined amount of time, that employee would need to identify those emails and save them according to your government entity’s policy. For example, they might be saved on a shared drive or in the cloud in a folder with the contract itself.<\/p>\n\n\n\n

Evaluate Your Government Entity’s Risk Tolerance<\/h2>\n\n\n\n

Keep in mind that any auto-deletion policy has an element of risk. Because emails will not be evaluated one by one, there is a risk that emails may be mis-classified and under-retained. It\u2019s up to your government entity to determine your risk tolerance and what steps you will take to mitigate the risk of under-retention. Before implementing an auto-deletion policy, consult with key stakeholders such as your Records Management Officer, IT staff, legal staff, and upper management.<\/p>\n\n\n\n

Record Disposition<\/h2>\n\n\n\n

Disposition logs<\/a>, or other methods of recording disposition, are required for state agencies and strongly recommended for local governments. With an email auto-deletion policy, a traditional disposition log where employees individually request destruction for groups of records may not be feasible. Instead, consider alternative ways to record the disposition of auto-deleted emails. For example, your email client may be able to produce a report of disposed records on a periodic basis.<\/p>\n\n\n\n

For state agencies, keep in mind that disposition must be recorded in keeping with 13 TAC \u00a76.8(b)(3)<\/a>. If you’re unsure whether your plan for recording disposition is appropriate, consult your legal counsel.<\/p>\n\n\n\n

Establish Policies and Educate Employees<\/h2>\n\n\n\n

Having a policy in place is crucial to ensuring that the auto-deletion procedures are done in a regular and consistent manner. A good policy will also outline how to handle various contingencies such as records that need to be retained longer than the auto-deletion period and how to account for destruction holds<\/a>.<\/p>\n\n\n\n

With an auto-deletion policy in place, your employees will need to be able to recognize emails in their own inbox that need to be retained longer than the auto-deletion period and save them appropriately as they come up. We recommend that government entities spend time educating their employees about the types of records they make and how long they\u2019re required to keep them. See our training page<\/a> for educational resources you can share with your staff.<\/p>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

Email auto-deletion policies are possible to achieve with appropriate guardrails in place. By identifying the record series and minimum retention periods that apply to your employees’ emails, you may be able to assign an appropriate auto-deletion time frame for email accounts as a whole. Be sure to keep track of outlier records and establish robust policies to ensure proper retention and disposition that meets your entity’s risk tolerances. If you are thinking of establishing an email auto-deletion policy, feel free to reach out to your analyst<\/a> to talk it through.<\/p>\n

\r\n
\r\n \r\n \"Like\r\n <\/a>\r\n 1 <\/span>\r\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"

How long should government entities in Texas keep email? It’s one of our most frequently asked questions, and like all our favorite questions here at TSLAC, the answer is, “it depends.” Though TSLAC has traditionally recommended the “sort and file” method, these days many agencies are hoping to simplify their operations by establishing an auto-deletion…<\/p>\n","protected":false},"author":200,"featured_media":22943,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"","footnotes":""},"categories":[10],"tags":[128,43,157,362,548,6,57,7],"class_list":["post-22692","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tips","tag-electronic-records","tag-email","tag-email-management","tag-email-records","tag-katherine-hoffman","tag-local","tag-retention","tag-state"],"_links":{"self":[{"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/posts\/22692","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/users\/200"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/comments?post=22692"}],"version-history":[{"count":15,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/posts\/22692\/revisions"}],"predecessor-version":[{"id":23050,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/posts\/22692\/revisions\/23050"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/media\/22943"}],"wp:attachment":[{"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/media?parent=22692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/categories?post=22692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tsl.texas.gov\/slrm\/blog\/wp-json\/wp\/v2\/tags?post=22692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}