News & Insights

Retention Schedules 101

Zasio, Your Complete Information Governance Partner, in white over a purple-tinted city skyline

Whether you’re new to records management or just want to brush up on records and information management awareness for yourself and teammates, this webinar, Retention Schedules 101, will guide you through the fundamentals of records retention schedules and highlight the core principles and theory behind their construction and use. During this webinar, we cover such topics as:

  • What is a records retention schedule, and how do they function within an organization?
  • Why do organizations need to create one, and what benefits do they provide?
  • How do I go about designing one from the ground up?
  • How can I apply legal research to set retention periods
  • How can I keep my schedule up to date as recordkeeping regulations change in the future?

Key takeaways: Retention Schedules 101

  • Destroying records regularly in the ordinary course of business, under a carefully vetted retention policy, gives you a defensible basis and leaves less to discover in litigation.
  • Record series descriptions and example records should be broad and inclusive, acting as guardrails rather than an exhaustive list, so the schedule can absorb new kinds of records.
  • Functional retention schedules are more flexible than departmental ones, because a reorganization or merger doesn't force you to rebuild the schedule every time the org chart changes.
  • Statutes of limitation should inform retention decisions, but they are not hard recordkeeping requirements that oblige you to keep every potentially relevant record that long.
  • Don't let the tail wag the dog: if one long requirement covers a single record, use a record-specific exception or its own series instead of extending the whole series.
  • Isolating personal information in its own record series lets you give it a short retention period without shortening retention for related records, such as payroll records needed for tax.

Browse all Zasio webinars

Audio-described version
Transcript: Retention Schedules 101

Duration: 0:54:52

Speakers: Frank Fazzio, analyst and licensed attorney, Zasio Consulting Division (title slide: Frank J. Fazzio III, CIPP-US, IGP, CRM, Analyst, Zasio Enterprises)

Lightly edited machine transcript. Slides are summarized where they carry information not spoken aloud.

Frank Fazzio: Okay. I suppose let's go ahead and get rolling then. First off, hello to everybody, and thank you all for joining me for today's webinar, Records Retention Schedules 101. My name is Frank Fazzio, and I'm an analyst and a licensed attorney with Zasio's Consulting Division, where I've worked on designing and updating retention schedules for the last five years. Today we're going to have a quick crash course about records retention schedules. We're going to cover the basics of how they operate, and also walk you through designing and building one from the ground up.

The intent is that whether you're completely new to records management, or if you just want to have a refresher to help with records and information management awareness for yourself and the rest of your team, today we will walk through the fundamentals of records retention schedules, and look at some of the best practices for creating and managing them. And when we're done, you'll have the tools that you need to create or update your records retention schedule for your enterprise.

[Slide: Agenda items: Records Retention Schedule Basics; Retention Schedule Mechanics; Designing a Retention Schedule; Applying Recordkeeping Citations; Retention Schedule Pain Points.]

So let's dive in. We'll start with just a quick road map of a couple of the topics that we're going to be discussing today. We'll begin by first talking about some of the retention schedule basics. What is a retention schedule? What is the purpose of a retention schedule? And why do we need to bother putting in the time and effort to design and create and manage one?

From there, we're going to look at the various components and moving pieces that together are going to form the building blocks of our retention schedule and allow it to mechanically function the way that we're intending. Next, we'll move on and take those concepts and put them all together into a working retention schedule. And then, once you have that working retention schedule, you want to apply some recordkeeping citations to bring your schedule into compliance with recordkeeping laws and regulations, and also keep it in compliance as those rules change and get updated over time. And then finally, building a retention schedule is not without its challenges. There's a number of common pitfalls and inefficiencies that frequently crop up in retention schedules, and we'll talk about some of the ways to mitigate and remediate those pain points to make your retention schedule more effective.

Okay, so let's start from the beginning then. Let's talk about retention schedule basics. What is a retention schedule even all about, and what does it accomplish for the enterprise? Let me start by saying that for those in our audience who are seasoned records management professionals, this is going to be a little bit basic and remedial. However, it's important that we get everybody on the same page from the get-go, so that we all know the same terminology and key concepts, and that way even folks who are new to records management will understand the later parts of the presentation.

So first of all, what is a retention schedule? A records retention schedule is a corporate policy, and it governs the retention and disposition of records and information. It fulfills three key roles in the organization. Firstly, companies use it to organize their retention and disposition. It sets the rules for the life cycle of every piece of information in the enterprise: how long the information is retained, and when and how that information ultimately gets disposed of once it reaches the end of its life.

Secondly, it provides a framework for operational controls over information operations. When you have a retention schedule in place, it gives you a yardstick against which you can measure the compliance of various business departments and judge whether they're fulfilling their obligations. And then finally, it's a source of legal authority and risk management for the business. There's risks associated with retaining information for too long, and similarly, you get other risks associated with keeping it for too short of a time. So by balancing these two competing interests and hitting the sweet spot in a record life cycle, a business can minimize its risk profile. And in addition, having a well-developed and carefully considered policy in place creates a defensible basis for information operations that you can rely on if those are ever called into question.

So let's dig a little bit deeper into each of these three bases for having a retention schedule. First, organizing retention and disposition. Companies need and must stay organized, and that's even more true for a really large organization. Information is often the company's most valuable asset, and as time passes this becomes ever more true; it's become more of a services and intellectual property based economy. Some tech companies, really their intellectual property is their greatest asset. So all companies need a process to systematize their records and information processes and manage that valuable asset and protect it.

To that end, information is really too important for employees to be left on their own, left to their own devices to manage it. If everyone does their own thing, you end up with irregularities and inconsistencies. We've all seen what happens to our desktops after a while. It gets cluttered up with different icons and saved documents and becomes a mess. So if everybody does their own thing with files and data and records, you get a huge disorganized hodgepodge, and you might not even know what you've got.

So instead, you need a way to eliminate irregularity and inconsistency and get everything organized. A rules-based approach to governing records and information is the best way to go, and that's what a records retention schedule does. A business has to develop a system to control the flow of records and information so that every piece of information has its place in the larger picture, and that system gives a prescription for how that information should be managed. A rules-based approach is the best way to go. And then lastly, companies typically have huge amounts of redundant, obsolete or trivial information that really just doesn't serve a purpose, except it just exists, clogging up systems, living on shared drives and filling them up and exposing the company to risk. We call that redundant, obsolete and trivial information ROT, and sometimes it can be as much as 70% of a company's records in a typical enterprise; they can be ROT.

This information really doesn't serve any purpose, except to take up space and cost money for storage. And in the event of litigation, it's potentially discoverable. So having your records retention schedule in place gives us a system that will slowly but surely reduce and eliminate that ROT.

So next, let's talk about operational controls. It's important for a business to exercise a high degree of control over its operations, and a retention schedule provides a clear set of guidelines that everyone can follow and removes ambiguity about what's expected of each person. The responsibilities are clear, and each person knows their role in the process. It's easier to get to the outcome that you're actually looking for. Next, the retention schedule is administrable. By that I mean we can control it from a central location, create subsequent different versions of it and track changes, and we can put a manager or some other control person in charge of it.

And lastly, it's a way to keep employees accountable. If a rogue employee decides to go and delete things, or decides to hold a secret hoard of data on their personal workstation, the retention schedule can be used as the basis for discipline, and you can bring the hammer down on that individual.

All right, and then next, let's discuss legal authority and risk management. When something goes wrong, you want to be prepared and protected, and retention schedules help you do that. The first way that it does that is it gives you a defensible legal basis for why you've destroyed a record, or alternatively why you've retained it. When you dispose of a record in the ordinary course of business, pursuant to a well-defined policy containing a records retention schedule, it gives you a high degree of protection against accusations that records are destroyed because of an improper purpose. Particularly, you want to avoid any suspicion that records are destroyed to hide something improper or wrongdoing. If a court decides that records were destroyed improperly, or in bad faith, or to cover something up, the results can be truly devastating.

Now, the classic horror story is the case from many years ago with Enron and Arthur Andersen, where there were suspicions of accounting irregularities. And unfortunately, the accounting firm Arthur Andersen shredded the documents, and the court slapped them with an adverse inference, which means that the jury was instructed to just assume the worst about whatever records they were shredding, and assume them in the light most favorable to the prosecutors. So consequently, Arthur Andersen lost their license to operate, and the company was destroyed, and everybody lost their jobs. So that's really the worst-case scenario from a records management perspective. But even if you don't get to the point of an adverse inference in a court case, if you don't manage your records and information properly, you can still get hit with a regulatory sanction, civil liability, or even criminal charges in some cases.

So the way to protect yourself against this is to destroy information regularly, not in response to some bad event, but in the ordinary course of business, pursuant to a policy that's been carefully constructed and fully vetted. So even if you don't get hit with an adverse inference, or any of those other horrific financial or criminal consequences, the less you have, the less that's discoverable in the event of litigation or investigation, and the better off you are. E-discovery costs can run into the tens of thousands of dollars for companies with a large volume of data. And when you destroy records in the ordinary course of a policy that's been vetted and researched, that data is just no longer discoverable, which puts you on a very good legal footing.

Okay, so now we understand why we need a retention schedule. Let's dig into the mechanics of how they work. We want to have a look at each of the different components and look at how all those components work together to form a fully operational records retention schedule.

[Slide: Retention Schedule Mechanics: Function/Department; Record Series; Record Code; Description; Example Records; Retention Period; Retention Trigger.]

So let's dive in. First of all, the basic concept behind a retention schedule is that we want to group similar records together, and then set a life cycle period called the retention period. It's based on your unique business needs and legal requirements that are applicable to each different type of record and piece of data or information. A retention schedule should use sort of a hierarchical categorization system to help you keep it all organized and logical. At the highest level, you have functions or departments that correspond to either big business activities, or the big business divisions of the enterprise.

However, once you have those highest levels, you want to break each of them up into smaller pieces that are more manageable, to give us some flexibility. We call those record series. That's a group of related records that all correspond to a single business process. A record code is a call sign that we use as a shorthand description for a record series, and it's a short string of letters and numbers that serve that function. So instead of calling the record series General Accounting, for example, we might call it ACC 100, or Accounting 100.

We'll see how this works in a later section. And then we want to give the folks who are going to be using a retention schedule some guidance about what's inside each record series. For that, we give each record series a brief, succinct description that tells them what the purpose of that record series is and what kind of records go in it. And then we give them some example records that are related. For example, if we have a record series on recruitment of new employees, we might have examples such as resumes, background checks, and that sort of thing.

Example records should be thought of as an illustration of the kinds of records that go into a record series, but they just act as guardrails. They should not be used as a comprehensive list of every single record that goes into a series, because that's not what we should be trying for. Your records and information will change over time, as time passes and the business changes. You want your retention schedule to be flexible enough to accommodate new pieces of information, new documents, as they come along. So lastly, you're going to have the retention period. The retention period is the rule that the record series and what it contains must follow.

The retention period is composed of two parts: trigger plus a period of time. The most common triggers for a retention period are creation or active, but you can have other retention triggers that are possible, depending on the activity. For example, if you are dealing with human resources records that cover employees, a common trigger to use is duration of employment, or the termination of employment, because those records are still going to be relevant for however long a person works at the company, usually. Similarly, for contracts, you might use a trigger like expiration of contract to determine your retention period, or for litigation records concerning a case or controversy, you might want to wait until the final settlement of that controversy, etc. So by having those two components, you give yourself a degree of flexibility in determining just how long the life cycle of a particular record is going to be, and you can suit it to the particular use of that record.

[Slide: Retention Schedule Mechanics: documents mapped to three functions with retention periods: Accounting (ACC), X Years; Legal (LEG), Y Years; Human Resources (HUM), Z Years.]

Okay, so let's take a look at all those components, or a couple of those components, in action in this dramatically simplified example. Here we have three different functions: accounting, legal, and HR, human resources. And you can see that for each of these, we have a shorthand abbreviation: ACC for accounting, LEG for legal and HUM for human resources. These will be the letters that go into the record code, the shorthand for each record series that we're going to organize under these functions. When we want to break each of these up later into individual record series, we would add some numbers to them, and we'll see that in the next example.

The idea here is that each record owner is going to take their documents and say, okay, this one goes here, that one goes there, as the case may be, so that based on the content of the record, we can have them organized according to the schedule. So in this simplified example, we have these three functions, and we also have some retention periods, but we don't have record series or record codes. So let's have a look at how that looks.

[Slide: Chart: ACC function split into ACC100 Series (Budgets), ACC200 Series (Invoices) and ACC300 Series (Statements); purple bars show each record's age in years (0 to 10), red markers show the retention periods at about 3, 7 and 10 years.]

If we take that accounting function, ACC, and break it up a little bit, we have some smaller individual record series created. We've added three: we have Accounting 100 for budgets, then we have Accounting 200 for invoices, and then we have Accounting 300 for financial statements. Each record series again gives us an additional layer of detail that helps our retention schedule be more accurately a reflection of the business, and it lets us have more delicate control. We have some retention periods for each one of these, and I've represented those with a red bar. On this chart you can see that the red bars are at about three years for Accounting 100 and seven years for Accounting 200, and we have 10 years for Accounting 300.

Now, the purple bar shows where a particular record is in its life cycle. For invoices and statements, you can see that if the purple bar is the life cycle, those records are old, but they're not quite there yet. However, for Accounting 100, our purple bar has reached the end of its three-year life cycle, which means it's time for that record to be disposed of. Okay, so that's really a simple example of that. Now let's look at an actual records retention schedule sample.

[Slide: Sample retention schedule table (Function, Record Code, Record Series, Description, Examples, Baseline Retention Period): Accounting & Finance, ACC100, Corporate Accounting Records, examples include accounts payable, NAIC invoices, check requests, credit card charge slips, 1099-Misc, accounts receivable, ledgers, balance sheets, journal entries and trial balances, 7 Years; Accounting & Finance, ACC110, Capital Assets Records, examples include capital property accounting, acquisitions, depreciation, improvements, tax credit, depletion and depreciation schedules, Life of Asset +10 Years.]

Here we have a more detailed sample, but again, this is just two record series, a small snippet of a retention schedule. In reality, you're going to have many, many more record series once you have a completely built retention schedule. As you can see, we have our function, and we have a record code, and we have a record series and some examples, along with a description. The function we're dealing with here is Accounting and Finance. The two record series we have here are Corporate Accounting Records and Capital Assets Records.

And for each, we have a record code: ACC 100 for corporate accounting and ACC 110 for capital assets. And then we have our description: "Records related to the processes associated with the management of payables and receivables, as well as the reporting on the financial position and performance of the company." That's corporate accounting. And for capital assets, we have "Records related to the purchase or sale and improvement of real property and equipment, otherwise known as fixed assets, depreciation, amortization and authorizations." Note that those are written in a deliberately broad way: "records related to." Having that sort of broad, expansive language in there gives the user some flexibility to say, okay, I think that this is related to this, and it should go here.

You want to avoid trying to list out particular records or make it exclusive. You want to make it an inclusive rather than exclusive description. And then we have our example records. As you can see, we have accounts payable, invoices, check requests for accounting. And then for capital assets, we have property accounting, acquisitions, depreciations and improvements.

Again, we aren't really trying to list every single conceivable record to generate an exhaustive list. We're just giving a representative example that will work as guardrails for our users. Okay, and lastly, we have our retention period. For ACC 110 we've given it a flat seven years. For ACC 110, however, we have a more complicated trigger.

We have life of asset plus 10 years, and we use that trigger because records for property might still be relevant long into the future. A building might have a 30-year useful life. So rather than trying to pick a fixed period, we use the trigger life of asset, so that way we can keep the records at least as long as we own the asset, plus a period of years; in this case, we've selected 10.

Okay, so now we've seen a simplified example and a short snippet of a retention schedule. Now let's talk about how you can go about creating one. So what goes into actually creating a retention schedule from the ground up? Building one from scratch is a significant undertaking, and can certainly be a daunting task, whether you're making one for a large organization, or even for a small organization. It can be a significant undertaking.

[Slide: Records Inventory: Questionnaires; Data Mapping; Interviews.]

Let's see. The first thing that you're going to want to do if you are going to be building a retention schedule is to organize the company's records. You need to know what you have. The way to go about this is to take a records inventory exercise, to get a picture of what records and information you're going to be responsible for managing and governing. The purpose is to get a handle on every record owned by the various departments.

And there's a couple of key information collection strategies that you can use to help put together your records inventory. The first strategy to look at is distributing questionnaires. This is sort of an easy, hands-off way to get information from folks in different parts of the business, and it lets you get a large volume of information about what records and data each person has visibility on, and also determine what are the core documents they use to fulfill their job responsibilities. You can make the questionnaire very detailed, or you can make it very simple. Sometimes, actually, having a more detailed questionnaire can be counterproductive, because nobody likes to have to go through a 20-page thing.

Instead, sometimes the most successful questionnaires are simple and just give the respondent the ability to answer in an open-ended way and give you as much or as little as they feel comfortable. Another go-to strategy you might use is a data mapping exercise. With a data mapping exercise, you're running analytics and using software tools to scan and crawl through your workstations, shared drives and network resources. And this is great because it's largely automated, so it's a very low-touch activity to undertake, and it uses very little in the way of time and human capital. So data mapping is a great strategy for getting a grip on what records and information you have. And lastly, you can directly interview folks at different departments within your organization, which is a lot more time-intensive for a big organization.

For a large organization, sometimes it's really impractical to have interviews with a significant number of people. However, when you do take the time to sit down and get on the phone or have a Zoom meeting, you often get some of the best information, which helps you ultimately, as you're building the retention schedule, to get a better final product when you're all done. So those are often worth the time, but you need to use all three of those tools, or some combination of them, to get a good picture.

[Slide: Planning: Scope & Complexity; Departmental vs Functional; Granular or Big-Bucket.]

Now, once you have that picture of what information and data you've got, then you need to plan how to proceed. You need to set a game plan for what kind of schedule you're going to create, and you want to set some goals to make sure your schedule's going to hit all those points and achieve those goals. But you want to be realistic about it. We had a colleague who once said that perfection is only possible in records management heaven, but you can get pretty close. David Stevens was his name. So first off, you want to decide the scope: just how comprehensive you want to make it, how complex, and how big of a time investment you're going to put into both initially creating it and maintaining it, and ultimately making sure that employees and colleagues are complying with it.

Some retention schedules run into the hundreds of record series and cover every conceivable piece of information in the business, and others can be very short. Actually, some are less than 100 record series, but they're still able to adequately cover and manage very large and diverse business organizations' records and information. The first big decision is whether you want to make the schedule's overall organizational hierarchy be departmental or functional. Departmental or functional: these are sort of the two big overarching paradigms for how to build a retention schedule. With a departmental schedule, you're trying to mirror the business organization and its departments.

In a functional schedule, you're not so concerned about departments; you're really just trying to track the big activities and where they fit into the overall picture of the organization. For example, your organization may have a billing department, it may have an accounting department, and it might have a corporate treasury too. A departmental schedule would give each one of those their own section of the schedule for themselves. But in a functional schedule, on the other hand, you might group all of those together into a single financial management function, a large umbrella that they could all live under, because they're all related activities dealing with money and finances. Similarly, you might have a call center department and a sales department, separate departments of the organization, but in a functional schedule, you might group those together into client services and sales, because they're both dealing with the function of reaching out to customers to develop business opportunities or respond to their needs. Functional schedules are sort of the gold standard now, because the advantage is that a functional schedule is more flexible and more logical, and so you can adapt it as the organization grows or changes.

When you have a reorganization of the business, or if you merge with another company, or some other big change happens, it doesn't necessarily have to upend your retention schedule if you use a functional schedule. But with a departmental schedule, you would have to give the retention schedule a facelift every single time there's any change to your organization structure. But the advantage on the other side of a departmental schedule is it's obviously pretty easy for an employee to understand the structure, as long as they work there. Next, you have to decide how granular you want to go. More record series gives you more flexibility. The more granular you are, the more options you have to keep some records longer and some records shorter.

But the more comprehensive you make it, the more record series you have, the harder it is for everyone to understand it. And it's also a lot trickier to administer it, monitor it and control it. Some of these retention schedules can run into the hundreds of pages, and it's really a complete mess. And ultimately, it doesn't serve the objectives, because when it becomes so large that people can't use it, it's lost a lot of its utility for the organization.

[Slide: Key Design Factors: Industry Common Practices; Tax Requirements; Known Legal Citations; Litigation/Investigation.]

Okay, so once we have a structure decided on, and we have everything in an organizational hierarchy, the next thing we have to do is pick some appropriate retention periods for how long the life cycle of each of these pieces of information is going to have. There's a few main factors that go into making those decisions. The first thing is common practice. In a number of industries, there's usual and customary practices or conventions for how things are done, including how long to keep records and information. When everybody in your industry is doing things a certain way, you certainly don't want to be the one who does it differently. So it's sometimes good to go with the flow, and this is certainly a case where that's true.

For example, video surveillance images: those are commonly kept for no longer than two weeks to a month at the longest, except in the case of an investigation of the commission of some crime. In some countries they have strict rules and laws on that, and in others it's less clear, but as a common practice there, you don't want to keep video surveillance records very long because of privacy concerns. Another example of a common practice is environmental records of hazardous environments, when you have employees who are working in conditions where they're potentially subject to exposure to physical hazards. Those records are often kept for very long periods because of the possibility of latent health effects that occur years later. So think asbestos and mesothelioma; or lead poisoning is another example of latent health effects that can crop up years later.

And for that reason, it's common practice to keep those records for a long period. Okay, so the next biggest driver that you're going to look at for determining your retention periods is taxes. They say that the only things that are certain in life are death and taxes, and so we all have to pay our taxes; everyone has to do it. But you want to make sure you have the records you need to prove the amount that your organization is claiming. And so this is very important.

Different countries have different tax recordkeeping periods. Typically those range from about five to 10 years, depending on the jurisdiction. A wide variety of your business records, like invoices and checks, might be important for proving your tax burdens. And so you want to make sure that you're complying with tax and accounting recordkeeping laws for every jurisdiction that you're in. And we'll talk about this a little bit more in the next section on recordkeeping citations.

That brings us to recordkeeping citations. You want to look at whatever... beyond tax, there's lots of other rules and regulations out there for recordkeeping requirements, and you want to be aware of as many of those as you can. This can sometimes be a daunting task, because, as you know, in the United States, the Code of Federal Regulations goes into the thousands of pages for the United States alone, and there's a huge body of regulations with lots of recordkeeping rules, recordkeeping citations, buried in there. And after all, that's just for the United States. For a multinational organization, it really becomes a large volume of different, overlapping and sometimes conflicting legal citations and recordkeeping rules. That's why Zasio, for example, has a database of... we have over 120,000 different recordkeeping citations in over 130 countries, and they're adding more all the time. So that can be a huge effort, getting a grip on the legal citations that apply to your operations. And then lastly, you want to have visibility of whether there's going to be a case or a controversy or litigation or investigation about certain records. You want to keep those records for as long as the litigation or the claim is going to be going on.

For example, this is really common in the insurance industry, where you have a contract for insurance. It has a defined period, and you kind of know that you're going to get claims on that policy; that's sort of the whole point. And so really, anytime that you're suspecting or anticipating that records are going to be needed in court to prove something, you want to hold on to those for a period that's adequate to be responsive to those legal proceedings. And so those are the biggest factors that you're going to put into determining what retention periods you use for your different records.

Okay, so now we know a little bit about retention schedules. It's time to undertake some research to compile some recordkeeping citations.

[Slide: Determine Regulatory Status: Business Profiles; Company Website(s); Business Licenses; SEC Filings; Questionnaires; Google.]

The first step you want to take when you're going to look at recordkeeping citations is you want to figure out how the company is regulated. Certain industries, like health care or banking and financial services, have their own industry-specific regulators. For example, the FDA, Food and Drug Administration, or the SEC, Securities Exchange Commission, or the Federal Reserve. Those are some of the big regulators in the United States. And each one of these has a portion of the federal regulations that they cover, and contained in those regulations are some recordkeeping rules.

Other industries may not have their own unique regulators that cover them, but every industry is still going to have to follow the basic employment laws and tax laws and privacy laws that exist for each jurisdiction. Sometimes, for a really large company with a diverse set of business or industrial activities, there's a wide variety of different areas where you're subject to recordkeeping requirements. And sometimes it can be hard to get a handle on everything that your business does, even if you work for the company. So sometimes you want to take a look at whatever publicly available information you've got out there about the company, such as websites, government filings, a company's annual report, the 10-K submission or the 10-Q. Those are great resources. Sometimes they can be a bit lengthy to read, but that usually will give you everything you need to know about your particular business.

Also, questionnaires can sometimes be helpful: which regulators do you have to answer to? You can ask different folks from the organization. But sometimes, of course, the best way to just get a broad overview of what regulated industries the company is active in is just to go ahead and Google yourself. Sometimes that's the quickest and easiest approach.

[Slide: Apply/Map Citations: Match Best Fit; Identify Gaps; Strategy for Consistency With Broad Requirements (Privacy; SOLs; Broad Commercial/Accounting).]

Okay, so once you know where to look, and you have your list of recordkeeping citations compiled, you have to compare these recordkeeping requirements to the schedule and make sure that it's meeting all of those requirements. What we're trying to do is we're trying to take a recordkeeping requirement and match it up to the records in the retention schedule that that requirement covers. And the goal is to find the very best fit for each requirement. Sometimes you're going to have requirements that cover records that live in two different record series, or you may have a requirement that covers multiples. For example, tax recordkeeping requirements might cover employee payrolls, customer billing, purchasing: one single tax requirement that says to retain records relevant to determining your tax basis.

It could impact lots of different places in your schedule. Sometimes you'll come across a requirement where it's not clear where the records are located in your schedule. And so if you can't find a match for a recordkeeping requirement in your schedule, this might mean that your schedule is missing something, or it just might mean that your schedule is too confusing and you can't find it. So looking over the recordkeeping citations is a good exercise; that's a good way to stress-test your schedule and potentially identify any gaps. The best example of requirements that are hard to map are the broad requirements that potentially apply all over the schedule in different places.

We talked about the tax laws. There's also privacy laws, for example, and those can affect everywhere in the schedule that has personal data. Tax and accounting, and what we call broad commercial laws, affect everything that involves revenue or expense that impacts the financials of the company. And then statutes of limitation, we call those SOLs for short: those set a maximum period that a claim can be brought for things like a contract. And those can impact your retention decisions wherever you have records and information that touch on a contractual relationship with a customer or a supplier or any other third party.

So for those big categories that impact multiple parts of our retention schedule, we have to figure out a methodology for which record series hit on those issues, and then follow the recordkeeping requirements consistently. If we decide that a certain collection of different record series all have records that are relevant to tax, we want to make sure that we keep all those records for at least as long, long enough to comply with the tax laws. We want to give them all a uniform treatment, all the record series that are relevant for a broad requirement like a tax requirement.

Okay, so once we have our recordkeeping citations in place, and we have mapped and applied those to our schedule, we often encounter a problem when we're comparing the recordkeeping rules to the retention periods in our schedule.

[Slide: Identify Compliance Issues: Retention Requirements; Compelled Destruction; Statutes of Limitation*; Handling Requirements*.]

A requirement may say to keep records for X years, but the schedule says we're only keeping those for Y years, and it's not long enough. And so we're out of compliance with that rule. Now, that's the most common issue you're going to come up with. But there's some other variety of flavors of problems that you can have. Often, it's not that we aren't retaining the records and information long enough to comply, but more and more with personal data, the issue is that the requirement is to destroy the records quickly. Sure, most folks are familiar with the GDPR out of the European Union, which generally says that you have to retain personal information for customers and employees no longer than necessary to achieve the purposes for why you collected it.

So those are the two most common issues that come up when you're vetting your retention schedule against recordkeeping citations; then you can really identify and zero in on and fix: retention requirements that want you to retain longer, and compelled destruction requirements that want you to destroy or delete or anonymize before a certain time passes. But the other ones that come up a lot are statutes of limitation, which we talked about earlier, and those set the limit on how long a claim can be brought. Once the statute of limitations has expired, no more claims can be brought. So potentially, in the case of a contract, any records that could be related to that contract or any potential claim could be relevant, and you might make the argument that, okay, we should keep all those records for just as long as the potential for a claim exists, as long as that statute of limitations is still running. But if you think about every possible contingency, every possible lawsuit, every piece of different information that could potentially be relevant to some type of issue that could come up later, it starts to get really kind of metaphysical, and you start thinking in the butterfly effect, and you end up wanting to retain everything for a really long time.

So it ends up being a bit of a slippery slope when you start down that line of thought with statutes of limitations. So really, it's not correct to think of statutes of limitations that way. SOLs do not imply that you really have to keep every relevant record that long. And if you do destroy some soon that might be relevant sooner than the statute of limitations, you're usually okay. But the statute of limitations should still be a factor that you take into account as you're designing your retention schedule; you just shouldn't think of them as a hard recordkeeping requirement, like a legal recordkeeping citation is.

And then another one that's sort of a soft consideration are handling requirements. These are qualitative recordkeeping citations: things that say to keep records in a secure location, keep records in a particular language. For example, in Quebec, you want things in the French copy, in the French language. Many retention schedules don't have a field where they specify the handling requirements. It's very rare that you have... for example, there's a lot of handling requirements that allow electronic records; some allow only paper, but those are very, very rare. And so most of the time, we don't express those on a retention schedule. Some do choose to do that, but in most cases that's managed outside of the retention schedule.

So one common handling requirement that does come up is WORM requirements. That's an acronym for "write once, read many," and it prevents information from being erased or altered without leaving evidence or a trail that it's been altered. These requirements and handling are important, but it just adds an extra layer of complexity that's usually not really actionable for somebody who's using the schedule, and that's why most choose not to put it on their schedule.

[Slide: Draft Schedule Updates: Regulated Records; Increase/Decrease/Trigger; Record-Specific; Vetting/Quality Check.]

Okay, and then next, once we are aware of any issues, we want to go ahead and have an administrator, that's you, make a decision on how to update and fix the schedule and address and comply with the issue. Before you consider making a change to your schedule, you want to make sure that you're fixing the correct record series, the one that contains the right regulated records that the rule is covering. You just want to double-check that you've got the right regulated records, and then you want to document what you're going to do, whether that's an increase to the retention period or a decrease to the retention period, or just changing the trigger. Sometimes, all you need to do is modify the trigger in order to bring yourself into compliance with the requirement. Sometimes you get a really onerous requirement that says to keep something for a really long period, or in some cases permanently, but it's just one record in an entire record series.

That's bad, because you don't want to let the tail wag the dog, where just one requirement for one record causes you to keep the entire collection of records for a really long time. So there you might need to consider making a record-specific exception that just applies to that one record, or else even maybe letting that record live in its own record series, a brand-new record series just for that record. And the last thing you want to do is double-check that a law still remains valid. Sometimes the most onerous and painful regulations eventually get repealed after enough people complain about them, and the lobbyists get on the case trying to persuade the legislators to roll them back and pare down the requirements. So before you move heaven and earth to comply with something, make sure to check that the one that you're aware of is still on the books and is still valid.

Okay, so now we've walked through building a retention schedule and some of the basics of maintaining it. The last thing we're going to talk about today before we wrap up is just to briefly touch on some of the most common retention schedule pain points and the pitfalls that folks commonly run into once they dive into a retention schedule, and also how to help triage and apply first aid to these kinds of problems to remediate them and improve the retention schedule's effectiveness. So let's just have a quick look at those.

[Slide: Pain Point Remediation: Overly Complex (Schedule Simplification; Global Harmonization); Lacks Support (Conduct Recordkeeping Research); Privacy Compliance Concerns (Privacy Risk Analysis; Intelligent Granularization); Implementation/Adoption Issues (Compliance Auditing; Collaborative Schedule Design).]

In terms of pain point remediation, the first problem we touched on is that a schedule can be too complex. We touched on this before, but if you really have too many record series, too many retention periods, it can be a nightmare for people to understand and comply with it. If this is the case for your schedule, there's a couple things you can do. In the first place, you can simplify the retention schedule and look for ways to group similar records together and get it to a more manageable size with more streamlined categories. This can make it much easier to digest for employees, and also easier for them to follow.

Another big problem that you might have is that you're in too many different countries, and you've got too many different retention rules for different countries. You might have different... responding to accounting requirements, you may say, okay, some countries five years, some countries 10 years. But the more you customize retention periods for different areas of the business or different countries where you're in, the more complicated it gets. And this can also lead to confusion and mistakes.

One solution is to harmonize, we call it, where you pick a retention period that works for most or all of your different countries where you're operating, and then use that as your global retention policy, instead of having a hodgepodge of different rules for each country. This does tend to cause things to end up, when you pick one that works for everyone, it's usually a longer one. So in the case of accounting, maybe you would just say, let's keep accounting records 10 years everywhere, which does increase your storage costs a little bit, but sometimes it can be worth it in terms of how much more simple it makes your operations, and how much simpler complying with the retention schedule is. So look for opportunities to use fewer country-specific exceptions in your schedule. That can make it a lot smoother and cleaner and easier to use.

Okay, the next big pitfall is that your schedule lacks legal support, because your list of recordkeeping citations is either nonexistent or outdated. To remedy this, you need to do homework and recordkeeping research of the sort that we just discussed. It's usually a good idea to refresh on a regular basis. If you have the resources and the time, the best practice would be to refresh your recordkeeping citations every six months or so. But for a lot of folks that's not practical. What you do want to do is at least do it every two years or so, to have a degree of updating to your schedule and keep it evergreen, as recordkeeping requirements do change, because those will change as the years and months pass.

And then another huge one is privacy. As we all know, privacy is now a huge issue. We have the EU GDPR and the California CCPA. It's possible, and in fact very likely, that there will be more privacy laws coming down in the future. And so you want to have a robust strategy in place to deal with the personal information that's contained in your schedule.

Usually, for personal information, your goal is going to be to delete this information after a shorter period of time. And what you can do to ready yourself for the privacy laws we have now, and also ones that might come in the future, is to conduct a privacy analysis, where you identify all the places in your schedule where personal information exists. And then once you know where the personal information is in your schedule, you can look for ways to reduce those retention periods and get them down to the point that they're no longer than the bare minimum operational need that you need in order to fulfill the purposes for why you have that information. But sometimes this is not practical, because in a lot of cases you group together personal information along with other records that have to be kept for a long period. And so just reducing is a problem. For example, those payroll records might be relevant to tax, but at the same time, they have personal information about your employees on them.

So in some cases, you might want to separate record series from other records in order to isolate personal information, so you can manage it without interfering with other records. In this way, if you take the sensitive personal information and let it live in its own record series, and granularize your retention schedule and add a few record series, it gives you the flexibility to assign as long or as short a retention period as you need for that sensitive personal information. And so in this way, you are adding record series and you are granularizing, but you're doing it in an intelligent way that responds to a specific need, in this case privacy.

And then lastly, it's often the case that you put a ton of work and time into designing a retention schedule, but you're having a hard time making sure that people are actually following it. There's a couple of different levers you can pull to try to fix this and get folks in your organization to follow it once the schedule is already out there and has been communicated. Sometimes you need to resort to enforcement to get people going, and you can use some different tools, like compliance auditing, where you make the retention schedule a hard requirement for everybody. You put it into people's job description, and their list of job responsibilities includes complying with the retention schedule. And then you do audit checks to make sure that people are actually complying. And if they aren't, you might have to resort to some discipline.

But that method, of course, is not very much fun for anybody involved. A better way and a more fun way to entice people to follow the schedule is to include them when you're building it, so they participate in the design and construction of the schedule. During those interviews and surveys we've talked about, when you give folks interviews and surveys, or some role to play in the process, it gets their own concerns baked into the schedule, and they're certainly more aware of the retention schedule and more likely to follow it. In some cases, people who have a lot of input in the schedule become departmental champions for the schedule. And so involving a lot of people in a collaborative effort to build the schedule does pay dividends later on in terms of adoption.

But of course, the downside is the time investment it takes to take into account everyone's concerns. And so you can either involve people at the outset, when you're first building the schedule, or you can involve people in an effort to update or streamline the schedule. Those are your two big opportunities to include people.

[Slide: Contact info: Frank J. Fazzio III, Zasio Enterprises, Inc.; phone 800.513.1000 x802; frank.fazzio@zasio.com; www.linkedin.com/in/frankfazzio123]

Okay, we're just about out of time now. Obviously, that's just a brief overview, and I want to thank you all for your kind attention. This does bring me to the end of the presentation. So I want to thank everybody for bearing with me, and I'll open the floor to questions. You can write a few in the comment section here in the GoToMeeting.

Now, if you're interested in records management, information governance, software, consulting, make sure to reach out to our sales team. Our sales folks would be delighted to walk you through our product and service offerings and find something that works for what your business needs. Also, our consulting team, which I'm a member of, offers a full suite of assessments and services to design and update and improve your retention schedules, and assist you in each of the topics that we discussed today. If you have any other questions, of course, you can certainly call me or email me, frank.fazzio@zasio.com, or you can reach me at my direct line there. And so, thanks, everybody.

Questions answered in this webinar

What is a records retention schedule?

It is a corporate policy governing the retention and disposition of records and information. It organizes how long information is kept and how it is disposed of, provides a yardstick for operational controls and compliance, and serves as a source of legal authority and risk management. Answered by Frank Fazzio.

What goes into creating a retention schedule from the ground up?

Start with a records inventory using some combination of questionnaires, data mapping and interviews. Then plan the scope, decide between a departmental or functional structure and how granular to go, and set retention periods based on industry common practice, tax requirements, known legal citations and anticipated litigation or investigations. Answered by Frank Fazzio.