News & Insights

Breaking It Down — Best Practices for Simplifying Your Retention Schedule

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

Get ready to roll up your sleeves! In this co-sponsored webinar with ARMA International, we dig into a series of specific examples so you can see, firsthand, how to simplify an overly complicated retention schedule. The webinar considers common pain points and opportunities for retention schedule simplification, including:

  • Addressing common sources of vertical and horizontal record series sprawl
  • Optimizing “bucket size” to match your organization’s risk appetite
  • Carving out exceptions when required
  • Considerations in wording new record series
  • Simplifying the use of triggers
  • Harmonizing a global schedule
  • How technology can help
  • And more…

Key takeaways: Breaking It Down - Best Practices For Simplifying Your Retention Schedule

  • Similar records spread across several departments, such as policies and procedures, can often be consolidated into one series, with a column tagging which departments use it.
  • Do not let the tail wag the dog: when one related series needs a far longer retention, such as permanent, keep it separate rather than over-retaining everything else.
  • If policies are typically superseded within a year, adding a year and replacing the superseded trigger with a fixed retention period makes disposition easier for people and systems.
  • In practice, the risk of over-retaining a record by a year or two is often weighed against the risk that event-triggered records never get destroyed at all.
  • High-risk personal information, such as non-hire applicant records and biometric data, is a candidate for staying separate and for keeping retention as short as requirements allow.
  • A global schedule can use one baseline retention period, typically the most common one, plus jurisdictional exceptions, and should keep country-specific terms out of titles and descriptions.

Browse all Zasio webinars

Audio-described version
Transcript: Breaking It Down - Best Practices For Simplifying Your Retention Schedule

Duration: 1:02:09 · Recorded: 2021-05-20

Speakers: Ann Snyder, Director of Content & Education, ARMA International (guest moderator); Jennifer Chadband (Masingill), Senior Analyst and Licensed Attorney, Zasio; Rick Surber, Senior Analyst and Licensed Attorney, Zasio; Warren Bean, Senior Sales Engineer, Zasio

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

Ann Snyder: Welcome to ARMA International's webinar, Breaking It Down: Best Practices for Simplifying Your Records Retention Schedule. I'm Ann Snyder, your guest moderator for today's session. This is my first civilian session. Today's webinar is sponsored by the great folks at Zasio Enterprises. For those of you who have attained your IGP, the Information Governance Professional certification, today's webinar counts toward one continuing education credit.

So today's webinar is actually building on a webinar that we did with Zasio in December of last year, that was Get Your Records Retention Schedule Under Control and Keep It That Way. And in that webinar, we walked through a step-by-step process used to assess the current state of your records retention schedule and how to build out a roadmap to close any gaps that you identified in that schedule. If you haven't seen that, I suggest you go back and check that out on the ARMA website, and hopefully we can include a link to that directly in the email that's a follow-up to this one. So we'll start quickly with some quick introductions to the subject matter experts who are on our panel today from Zasio, and then we're going to dig right into some actual examples. So this is going to be actual words on a page, not abstractions.

It's going to have a little bit, I think, of a workshop feel. Our SMEs from Zasio and I are going to walk you through the examples. We'll identify what we see, where there are opportunities for consolidation and simplification, and consider considerations that you should weigh in the process of that simplification. And then we'll take a look at what that modified retention schedule looks like. And we're going to take a look at some common examples of vertical and horizontal sprawl in record series. We'll discuss optimizing bucket size to match your organization's risk appetite.

We'll talk about carving out exceptions where required, considerations in the wording of the new record series, simplification of the use of triggers, harmonizing global schedules, how technology can help. At a couple points, Warren could come in and show us the VR tool, and much more. Then we'll open it up to a Q&A at the end. But let's get started quickly with some introductions to our panelists. We're excited to welcome back Jen and Warren, and now we're joined by Rick. So if you guys can just say a few words about yourselves.

[Slide: Panelists: Jenn Chadband Masingill, Senior Analyst, Licensed Attorney, CRM, IGP, Zasio Enterprises, Inc.; Rick Surber, Senior Analyst, Licensed Attorney, CRM, IGP, Zasio Enterprises, Inc.; Warren Bean, Senior Sales Engineer, CRM, Zasio Enterprises, Inc. Moderator: Ann Snyder, IG Practitioner.]

Jennifer Chadband: Sure, I'll start. Thank you, Ann. Hi, Jennifer Chadband here, senior analyst, licensed attorney with Zasio. I've been with Zasio for nearly 10 years. I'm really enjoying seeing all of the messages in the chat and hellos from all over the world. I'm seeing Hungary, I'm seeing Canada, I'm seeing California, Colorado, Iceland.

Shout-out from the Zasio headquarters here in Boise, Idaho, proud members of the Mountain time zone. Thanks for joining, everybody.

Rick Surber: I'll go next. My name is Rick Surber. I'm also a senior analyst at Zasio. I co-manage the consulting division with Jen, and I also manage the research division. And I've been with Zasio for nearly 12 years now.

Warren Bean: Hello, everyone. I'm Warren Bean, and I am not an analyst nor an attorney, and I don't play one on TV. I am, as you can see there, the senior sales engineer. I also head up the management of the developers and sort of lead the product development cycle here at Zasio. So I'll be talking about the technical aspects of the retention schedule management process. And I've got you all beat: I'll be here for 21 years as of this July.

Ann Snyder: Wow. Thank you. Thank you, everyone, for being here. Thank you so much. This is a really great panel that you've assembled for us, Zasio. Thank you so much.

So let's just start digging right into this. We have a lot to cover today, so we're going to look at some common examples. A common problem we've discussed a couple times in the previous webinar was about sprawl of record series.

[Slide: Example #1: Vertical - collapsing functions and record series across multiple functional areas. Nine policy and procedure series from IT, corporate governance, administrative, public/media relations, HR, technical products, pharmaceutical and customer relationship management, retained Until Superseded + 3, 5 or 6 years, or Current + 5 years.]

Now, I understand there can be both vertical and horizontal sprawl, and each of those types of sprawl in series offers an opportunity for consolidation. But before we get into our first example here, which is vertical sprawl, can you tell us a little bit about what we mean by those two things, and what are some common examples that you see out there in the wild?

Speaker: Yeah, absolutely, I can take that one. And don't get too caught up in the designation of vertical versus horizontal, because I think people think of it or term it differently. But essentially, what we're terming as vertical sprawl, which we'll give an example of first, is sprawl that relates to processes that cross departmental lines. So conceptually, we're considering similar records found in multiple departments. I think some good examples of that would be something like employee expense reports, annual employee reviews, contracts, and then procedures, you can see here, is our first example. But these are things that multiple departments may have, and may very well have their own terminology for, that we can look to consolidate through various functions into one. Whereas the second type of sprawl, horizontal sprawl, would be consolidation within a function itself or department itself, so multiple related categories that can be consolidated in one category, with processes within one department or function.

Ann Snyder: Okay, so in this first example here, we're calling this one vertical sprawl. This is the collapsing across functions. What do we see here? Walk us through this.

Speaker: Yeah, so just to kind of set it up, and we'll follow a similar format, so I'll only have to really explain this basic part of it once. On the far left we've got the departments and/or functions: IT, corporate governance, HR. There's even some industry-specific stuff down there, pharmaceutical industry stuff, customer relationship management. And so you can see that in the second column, these are kind of different terminology for very similar records: policies, procedures, how-to manuals, etc. The next column gives you a kind of brief description about each, to give more context for what they are. And then the column on the far right gives retention periods for each, which do vary a bit per series, but are all within a two- to three-year range, roughly, of each other, so very similar retention periods.

And then moving to the next one. Oh, and actually, going back, I just wanted to mention that we've kind of taken some legwork to get these all together so that they're easy to see and easy to understand, but keep in mind that when you're looking at these in your retention schedule, they're going to be spread all over the place in the different functions, and so this is simplifying it for the purpose of this example. One kind of help tip to get you here from your retention schedule is, I find that key term filtering helps a lot with this. If you've got your whole retention schedule open and you key term filter on something like policies, if you're key term filtering your granular schedule title on a key term like that, it can help you kind of identify these and help you get started moving from your current state into something like this that's simplified.

Ann Snyder: So this is, there's a heavy lift. So we want to make sure that people understand there's a heavy lift that occurred before we got to this, but we needed to simplify it somewhat so you could look at it in the time frame that we have here.

Warren Bean: Absolutely. And if I can throw in a plug for having a software tool in this space: this is something you can do within a software tool, and that is to search for common terms like that and see things in a consolidated view, pretty much like you see here. Whereas that's really difficult to do in a spreadsheet. You can search for terms and go next to each example, but it's hard to get them in a consolidated view, and manually pulling them together is a bit of a challenge too.

Ann Snyder: All right, so let's take a look. So we see several series here, just to summarize, several series across multiple functional areas that are basically the same types of materials. And so this is an opportunity for consolidation. We see sort of a mixed bag of the retention. Again, they're pretty close to one another here.

It's three years at the biggest of the spread. Some of the language is a little bit different. Can you just, I know we're going to look in a moment, just as a prelude to that, we're going to look at consolidating or simplifying triggers, but we can talk just for two seconds here about the difference between these types of triggers.

Speaker: Yeah, so, and this will come up in another example where we kind of hit it home a little bit more, but policies and procedures usually have a superseded-type trigger. And so for the ones that don't here, there's still things like that Current one for the talking points. Essentially, it's either going to get superseded or it's going to be something that essentially expires. And so when we look to consolidate and look at the consolidated version, we'll see that we've tried to use language, I mean, you have to be cognizant of the trigger and making sure that the trigger works for the records that you're dealing with. And so, yeah, we see multiple triggers here. In the consolidated version, we'll see something that is designed to account for all of those.

Ann Snyder: Okay. All right, so let's look what happens here. So you've taken all of those, and what was the number, we were at two, four, six, eight, nine different series that are consolidated into one. Do you want to walk us through that, Rick?

Rick Surber: Yeah, absolutely. So we've collapsed them all into one category that covers the different variants. Essentially, we distilled all of the duplicative language, with representative examples listed there in the second column from the right. You can see that we landed on a superseded/retired plus six retention. It is a slight increase to some of the legacy categories, and it's always going to be a risk-based determination as to whether that type of an increase is acceptable.

It's not always going to be acceptable in every category. We use this one because most clients are okay with that type of increase for policies and procedures, and the simplification outweighs any risk of over-retention for these.

Ann Snyder: Well, we'll discuss, a big thing that impacts this is privacy. Privacy kind of limits the way that we can increase or decrease, potentially. And so we'll talk about that; we've got an example dedicated to that in a few slides. And I know we're going to talk about, in an example, these are relatively close to one another, and again, because of the nature of them, it allows that sort of a little bit of over-retention for some of the records. But we are going to talk about some of the more extreme outliers in a few of our examples, where we don't really want to let the tail wag the dog. In those instances you want to carve out maybe an exception, consolidate the ones that are closer to one another. But we'll get into that example in just a minute.

Rick Surber: One more point: we've also gone with the consolidated function, which is a shared function in compliance, regulatory, risk management. And some people may be thinking, well, how do departments know which records are theirs? People are going to want to be able to pull up their retention schedule and tell, these records are relevant to me. And the way that we deal with that, we don't have it shown here, but we will add another column where we tag the different departments that utilize that schedule, so that people are able to pull up the schedule titles relevant to their department by using that tag.

[Slide: Example #2: Horizontal - collapsing record series within the function. Ten accounting and HR accounting series with retentions of Creation + 6 or 7 years, Payment Submitted + 6 years, Payment Received + 6 years, Check Clear + 6 years, Report Submitted + 5 years and Payment + 5 years.]

Ann Snyder: All right, thank you. So the next example we're looking at is, we're calling this horizontal sprawl. And again, don't get hung up on that term. When we were discussing it, I kind of flipped them mentally in my brain. So the first one was similar records across different functions, and now we're looking within a function here, and some kind of sprawl within that given function. So would one of you just walk us through this, tell us what we're seeing?

Jennifer Chadband: Yeah, I can go ahead and walk us through this one. So horizontal function here, we have, I think a really good example is oftentimes within financial accounting, HR down here too, right? Yeah, yeah, there's a couple sneaky ones in there too. But yeah, across financial accounting, looking at all the different processes, you oftentimes see very similar retention periods, similar event triggers. Even a sub-process here for your financial accounting record series may also have kind of some unique event triggers associated with them.

However, I think we often find that for payment submitted, for example, payment received, these really can kind of be simplified and kind of rounded out to a calendar year or a flat retention period. So this is a kind of analysis that you can go through. This is supposed to be an example of horizontal, going within one function. We have a couple sneaky ones that we pulled in here from HR, but that's just another example of not necessarily collapsing two entire functions together vertically, but kind of pulling in things that are related to these higher-level processes. So I think that when you get into some of these functions and you go through, the focus really should be on where are these more granular processes interrelated or similar, and where do they have similar retention periods. Those are the two, I think, main areas for focus when you're trying to determine record series that would be appropriate for combining.

Ann Snyder: Okay. So let's look at what happens once we consolidate these. Can you walk us through this?

Jennifer Chadband: Yes. So this is a big bucket retention period, or record series, excuse me, for general accounting. So you'll see that we were able to kind of collapse all of these processes. The key being that now, instead of here at the sub-function or the sub-process level, where it was describing a very specific, kind of more granular process, the key here is that we have consolidated it, and you have to make sure that our description is really all-encompassing and at that higher-level process for the description. So anytime that you're simplifying, combining record series, the details of the description are really what are going to help kind of define that record series for the end users.

They can see, these are the processes involved here, I understand what the outputs are. The examples are also important. For a records retention schedule, of course, it's really not ideal to make it 100% inclusive and include all of the examples; that's just not very manageable, and it's unwieldy. But combining those examples, removing duplicate examples across these functions, so that this is really still also searchable. So hand in hand, having that really kind of comprehensive, robust record series description, and the consolidation of the examples. The consolidated retention period now, you'll see, is simplified. It's creation plus seven years. We were able to determine that, based on the life cycle of some of these records that had very specific event triggers, it really was feasible to kind of round it out to a flat retention period.

Ann Snyder: And so here is our simplified record series for general accounting. You can see how these are different: with this one, creation plus seven, payment, and then report submitted have all sort of been simplified. And we'll be looking at a simplified trigger period and discussing that specifically a couple examples from now. But you can see how that was consolidated here. So we're actually going to take a quick look at this in Versatile Retention, but before I do so, I just want to make sure that people understand that you could keep some of this information so people could search on these functions, right? So they could look for the specific types of documents. So people should not worry as much. If you do this right, you get the benefit of the simplification by consolidating these disparate record series, but can still maintain the findability of that information for people who are used to looking for that information using specific terms.

So let's take a look. I'm going to hand this over to Warren. He's going to talk to us a little bit about what this looks like in Versatile Retention.

[Slide: Example #2, software example: a Versatile Retention "Merge into New Schedule" screen. Software can save clicks, auto append, deactivate merged series, and provide an audit trail.]

Warren Bean: Yeah, and so what you're seeing here is just one screenshot from our software, Versatile Retention, where we have a function, it's just a toolbar button that says Merge, and you're able to either merge multiple schedules into one new schedule, like you're seeing here, or into an existing one. And the idea is that instead of having to, say, in a spreadsheet, copy and paste multiple cells into one and kind of sift through things and kind of do that manual process of moving things around, we try to just simplify that process, save you some clicks, so that you can essentially say, well, this is the one I want, and I want to select some other ones to join in with that. And you can see that at the top of the columns there, we've got Source Schedule 1, and it says, if there's a conflict with the things that we're merging, what do you want to do? So in one column we've said we'll use these as the primary, and in another case we say, well, if there's a conflict, try to append the information. So if you have large descriptions or those examples fields, that just saves you from having to retype or to copy and paste. We just try to blend that together, and then you get the option to edit that data in that final column on the right there, where it says Merge Into That Schedule. So saving some clicks, saving some copying and pasting. But also, once you finalize that with the Save button there, those two original schedules that are in the view will be set as inactive, or deactivated, so that you don't have to worry about those still existing.

But you'll have those as a reference in your audit trail. You'll be able to still see them if you have the ability to see the inactive schedules. But it just really saves a lot of the time and the headache of that consolidation.

Ann Snyder: Is that view typically seen by, so the source schedule, is that viewable just by the admins, or by end users? Can you adjust that?

Warren Bean: You mean once it's consolidated? Once you have consolidated, then it's just a matter of who you've assigned permissions to that can view the inactive schedules. So with the role-based permissions, you can determine who gets to see those and who doesn't. And you also have just the ability to check a box on the main view to say whether you want to see the inactive schedules.

Ann Snyder: And of course, then here we see the examples, so people, again, would be able to search on those, is that correct?

Warren Bean: Exactly. In fact, one of the things that really makes a big bucket schedule work is that ability to search across those different fields, those different examples, as opposed to older times, when you had to rely on the structure to find what you were looking for. Now you can have a much more consolidated structure and be able to search for those terms throughout the schedule.

Ann Snyder: Just, what does that conversation look like? So we've looked at the examples and the opportunities we see for consolidating, but when you're having that conversation about bucketing, when you're sort of doing the risk appetite analysis, what does that convo look like with the client?

Warren Bean: Yeah, that's probably more of a Rick or Jen question, so I'll toss that one back to them.

Speaker: Sorry, I'm embarrassed to say that I was answering questions.

Ann Snyder: Oh, so terrible. No, it's just a question. It was a high-level question, sort of how do you start that conversation. So we've looked at some of the examples and some of the considerations, but, I'm just getting some sense of, you know, do you get pushback from people? What are the pushback points, those kinds of things?

Speaker: Oh yeah, there's definitely pushback on consolidation. But that pushback is great, because what I just typed, actually, in the chat is, this whole process needs to be balanced and reasonable, and it can't result in over-retention, and it can't result in impacting people's operational needs for the records. And so the pushback usually helps you guide maybe deconsolidating some stuff where granularity is appropriate and reasonable. But there are also some situations where maybe it's based on some misunderstandings of what the retention schedule is and how it operates, and how it's not a file plan. It's not something that's telling you where to keep your records; it's telling you for how long to retain your records. And so a little bit of education will sometimes also help with that pushback.

Ann Snyder: Just, I wanted to ask a quick question about this before we move on to the next example. There's the image we have on the screen here. We had talked, when we were prepping for this, about the value of legacy mapping. And so I think we're seeing a little bit of that here, at least. Warren, you were looking at this mostly from a consolidation perspective, that using the tool makes it easier to see what you're consolidating; you can do it by a click of the mouse, as opposed to cutting and pasting and so on.

But there's also some advantage to this sort of legacy mapping, and even the exercise of doing the legacy mapping.

Warren Bean: In fact, what we often see is that when you're creating the new consolidated schedule item, like what we have on the right-hand side there, we can have a field, maybe one of the user-defined fields, that says, it might say something like legacy reference. So it might have the record code or record title of the items that were consolidated into this one, so that if someone searches on what was the old code, they come up with the new one, and they can see that it was at some point consolidated.

Rick Surber: Another kind of stress test you can do with the new retention schedule is not give users that legacy mapping. So you're of course going to be doing that legacy mapping when you're consolidating; it's all going to be built into what you're doing. But if you then kind of socialize the new simplified retention schedule out and say, okay, as you guys's first task, align where you think your records go to this retention schedule, you'll know whether you did a good job of creating kind of intuitive categories of records that people understand, and it gives you an opportunity to kind of revise and clarify where people are misunderstanding where their records could go within the retention schedule.

Ann Snyder: So you would have everyone, so the stress test is that you would have everyone just match all of their records, their old series, to the new series, or designated subject matter experts, if you don't want to make everyone do it. Right, maybe, I don't think you get buy-in from everyone. I meant, I meant every sort of department having some, yeah, whoever your project lead is with each department.

[Slide: Examples #3 & 4: related process record series to exclude (trigger and retention period). Six environmental air and water quality series (EHS100 to EHS150) retained Current + 5 or Current + 7 years; Hazardous Substances and Waste Management highlighted in red: Permanent, No Consolidation.]

All right, let's move on to the next kind of example of sprawl here. I think, Jen, you've touched on the term sub-processes here, but this is a specific one that's looking at those sub-processes. Can you walk us through this one?

Rick Surber: Yeah, so here we've got different types of pollution monitoring, and they're all within the same function. Oftentimes they'll be within the same department, if you're in a departmental schedule. So it's what we're terming horizontal sprawl again, so it's similar to the last one that Jen just described. However, the difference here is that we have an outlier to kind of demonstrate. While the air and water related monitoring categories have a similar retention period, ranging from five to seven years, the series highlighted in red has a permanent retention period.

So if that retention period is valid, which is kind of a different subject matter and a different story, but if it's valid, to consolidate we would need to over-retain the air and water monitoring records significantly. So I think this provides a good example where, even though there are similar processes going on, it's all related to pollution and pollution monitoring broadly, because hazardous substances requires a significantly longer retention, we don't recommend consolidating it with the other categories.

Ann Snyder: And here, this one's permanent, so you'd basically be over-retaining forever on all of these others. [Rick Surber: Exactly.] So, all right, let's look at what that looks like. And also, can you just talk a little bit about, so we'll get to the example of the, as we switch slides, just the language, and there's some art in crafting that language.

Rick Surber: Right. And so what we try to do, addressing your question, Ann, is we try to go broad with our description and our title. And the reason we do this, instead of being more precise, is because we want the retention schedule to be able to be evergreen and stay valid even when slight naming conventions and slight changes to the processes happen. Now, this doesn't work for every industry, because there are industries where the preference is to have exact, precise language. So this is kind of the example for the majority of our clients.

[Slide: Examples #3 & 4 consolidated: EHS105 - Environmental Testing and Monitoring (Environmental, Health, Safety, and Facilities), Creation + 7 years, with a note excluding hazardous waste records covered by the Hazardous Substances and Waste Management series, which stays separate at Permanent.]

And you can see with this one, it's broadly described in that description to cover monitoring for all types of pollution, day-to-day environmental impact resulting from company actions, that type of thing. And then we've termed it representative examples, because we don't want to mislead or make the users think that every record that they've got will be listed there. We just want to give them context so that they can figure out where their records go. Now, there are specific industries that don't want that, that want every single one of their records listed. I think nuclear is a great example of that. I've worked with some nuclear clients to try to use representative examples, and almost every single one, they've said, well, we actually want every single one of our records listed, and it's an exact process, and so it's understood that way. But yeah, looking at what we've got here, we see that all but the hazardous series has been consolidated into that top one.

And then we've also added that guidance in red to point users out to the fact that, even though it's related, this hazardous category has its own series. And so this type of guidepost is something that we often use to call out related series, where series or processes interact or are related. And that would go in the description in the tool, if you're using it that way, or you have another category dedicated to related categories, another user-defined field, or another column. Yep.

[Slide: Example #5: simplify or eliminate triggers. Nine policy and procedure series (IT100 to SER240) retained Until Superseded + 3, 5 or 6 years, or Current + 5 years (PUB110 Issues Management / Talking Points).]

Ann Snyder: All right, let's take a look at the next example. We're returning now to simplification or elimination of triggers. So what do we see on this one? So we see some complexity. I can see that's until superseded, current plus five.

So I'm seeing differences in the retention period length, of course, but then also what the trigger would be as well. Which one? Walk us through this one.

Speaker: And so we're back to our policies, procedures, guidelines series for this example. And most of them, as we already discussed, have a superseded trigger, which is really common for this type of category. And to take a step back, we've been talking about this term trigger, but just to kind of explain it a little bit, it's an occurrence that must take place before the number of years or months specified starts to run. So in this example here, the three- to six-year retention periods would start to run once the policy, procedure, guideline is superseded, which would happen as soon as a new version of that same document is published, replacing that old version. There was a question on that, and so I wanted to make sure to hit on it. So in working with clients, we found that most policies and procedures like this are superseded within a short span. Clients are updating their code of ethics, their IT policies and procedures, their employee manuals, for example, on usually an annual basis, if not sooner than that. And so this is the type of trigger where we evaluate it and we say, is it really necessary to keep that level of complexity of having a trigger in it, or can we add a year, get rid of the trigger, and just have a fixed retention period, which is much easier to calculate for systems, and really for people, because you're not having to worry about documenting when the policy was superseded. You've got a date of when the policy was created, and you know, okay, I can set a date this many years off in the future, and this can be disposed of at that time. So especially for systems, getting rid of triggers is a major initiative in trying to simplify clients' retention schedules.

Ann Snyder: So this requires some initial investigation to see what they're like, how often they update these things. What do you, I mean, what do you do? Sometimes, certainly, I've run into this issue where people say X is supposed to be updated every X period, and it doesn't always happen. So what about that kind of scenario?

Speaker: You've got to add a little buffer into it if you need to. If you're not confident that it's going to be updated within that time period, you need to add an additional year, maybe. And again, that's one of those things where you have to evaluate the risk of something not being superseded within a year with the risk of over-retaining for an additional year, and pick the spot that you're most comfortable with, if you're even comfortable doing this type of exercise at all.

Rick Surber: I was going to say, for example, using that air emissions example, back to that one that we just did, another one that you could group with that potentially would be the permits that go along with that process. The problem, though, is that those permits may last for a number of years, and they're different. They vary between five years, three years, some of them are annual.

[Slide: Example #5 consolidated: CMP15 - Policies, Procedures, Guidelines and Directives (Compliance, Regulatory, and Risk Mitigation). Until Superseded/Retired + 6 years is struck through and replaced with Creation + 7 years. Comment: "If superseded annually, can we add a year and change to a fixed retention?"]

So that's one where you can't really get rid of that expiration trigger with those air permits to normalize at a fixed retention period. And so we're going to break those out and not consolidate them with those air emissions records.

Ann Snyder: And I think it's another just reminder that before you pull the trigger on the deletion, you actually have to have these things reviewed. [Speaker: Yes, absolutely.] All right, so what do we see here? So the consolidation here now becomes creation plus seven years?

Speaker: Yep. And if any of these don't supersede within one year, this won't work, of course. That creation, we had another question touch on this: creation is kind of the default retention period that is assumed if nothing is there. So that could just say seven years, and most people would think of that as creation plus seven: when the record is created, plus seven years.

Ann Snyder: All right, and we've had lots of questions on those triggers. We might have to, at the end, kind of spend a little bit of time discussing that.

[Slide: Example #6: simplify retention period with a calculable, flat retention period. M&Q105 - Batch Manufacturing (Manufacturing & Quality); examples: analytical results, batch production record and packaging record, certificates of analysis; retention: Drug Expiration + 1 Year, or Distribution + 3 Years, Whichever is Longer.]

All right, so here's another trigger example, or simplification of the retention schedule, that we're looking at here. So what do we see in this one?

Jennifer Chadband: Yeah, I can explain this. So here's an example of a pharmaceutical record series that relates to batch manufacturing for drug products. Now, this is, I think, a really great quintessential example. This might be a bigger bucket record series; it might relate to a lot of different types of drug products. All of them really can have different event triggers. It might be, for APIs, five years after the qualified person signs off, or there might be a drug expiration event trigger in there. There might be, as we have here, an example, distribution plus three years, whichever is longer. And it might even get more convoluted if you're considering devices, expected life of the device. So one approach is to see if you can determine a calculable retention period. And this isn't just for batch manufacturing records. I think there's a lot of different instances where you can potentially go from multiple relevant event triggers, retention periods, and see if you can't find something that is calculable but also reasonable, understanding, of course, that if we were to be adhering to disposition precisely with the requirements, we would have to separate and create a separate series for every single product. And is that realistic?

Is that manageable? So what we want to do is see what we can do. For some of our clients, it depends on what products are involved. Maybe a five-year retention period really kind of covers all of these potential event triggers. And so if we can go to the next slide, we'll see what it kind of turns into.

[Slide: Example #6 result: the hybrid retention period is struck through and replaced with a flat 5 Years.]

So here's a flat retention period. Now, is it always so simple to figure this out? You'd have to be able to know what's potentially the shelf life involved for the drug; if you're looking at devices, what is the actual expected life of the device, plus is there some additional time we want to consider in there for risk considerations that relate to various liabilities for these products? So maybe it's longer. But nonetheless, kind of taking all of this together, rather than having potentially a complicated hybrid retention period, or many different record series that make the retention schedule become a little bit more unwieldy, you have a simplified retention period. And the feedback we get from clients is retention periods like this, a flat, calculable or calculated retention period, is much easier to implement across the organizations and in systems.

Warren Bean: Okay, to add to that, Jen, what I see on the operational side, when people are trying to implement these kinds of schedules, is that the risk of over-retaining really ends up being compared to the risk of just never destroying it at all. So you might be concerned, oh, am I keeping this a year or two longer than I should? But most of the time it just means it never gets destroyed, because no one ever goes back to figure out what those event triggers are and actually apply them to the records.

Jennifer Chadband: That's absolutely true. That's a really good point, Warren.

[Slide: Example #7A: strategic privacy consolidation. Eight HR series (employee development plans, employee assistance, employee award records, performance reviews, personnel files, personnel actions, and applications and background checks for hires) retained Duration of Employment + 3, 5 or 7 years.]

Ann Snyder: Okay, now, people, we've had a couple of questions, I think, that touch on privacy, but also we've touched a little bit on privacy considerations as well. So let's move to an example on that. So this is strategic privacy consolidation. I know historically we've dealt with this idea of minimum retention periods, but the privacy requirements are actually cutting in the opposite direction. So can you walk us through this one?

Speaker: Yeah, yep, I can do that. So what we have here is several record series that are essentially coming from personnel-related functions, human resources, and kind of all divided up into specific sub-processes. But you will see that we have event triggers here. They all relate to the duration of employment. So, kind of looking at this, we see that all of these really relate to employees that have been hired, essentially, and we can kind of start to see that maybe there's opportunities here to consolidate. Now, when I think, one thing, obviously, the privacy question in the back of all of our minds is, what really, how aggressive can you go? You don't want to be unnecessarily over-retaining personal information.

Our clients across the spectrum, they're definitely kind of managing privacy in different ways, and whether or not this information that's being retained is being sanitized, for example, at a certain point in time, how is it being treated. These are all different kind of unique considerations, but I think that we can all agree that to whatever extent possible and reasonable, you would want to make sure that you're kind of separating out like processes that can be retained for a shorter period of time versus those that can be retained for a longer period of time.

Ann Snyder: Okay. All right, so let's take a look at what happens here. So these are ones that are open to consolidation?

Speaker: Sure. Yeah. And so what we see from our clients, and this actually could just be its own presentation, maybe next time, but there's definitely kind of a legitimate basis for kind of keeping certain records for a certain period of time. There's differing opinions coming out from data protection authorities that relate to statutes of limitations. But what our clients are also looking at is, what are the business and operational needs supporting this? And so that's something to keep in mind when you understand how you're handling the privacy information, what that risk profile is: where can I group records together and potentially lengthen retention periods for some records in the name of administrative ease, and ensuring that these records are actually being destroyed on a timely basis and not being over-retained because people can't follow a very, very granular, complicated retention schedule, on the other hand.

[Slide: Example #7B: strategic privacy consolidation. Applicants Declined/Withdrawn: Closure of Position + 3 years; Applications, Resumes, and Inquiries for Employment - Not Hired: Current + 3 years; Background Checks/Investigations - Not Hired: Closure of Position + 3 years (these three bracketed together); Fingerprint Records: Until Superseded + 3 years.]

Ann Snyder: Now here's our next privacy consideration. What do we see here, Jen?

Jennifer Chadband: Yeah, so these are kind of what we would consider kind of separate high-risk records. These are very much records that you'll see. We've got non-hires here, we've got biometric information. These are certainly, I think, very, very much regulated, increasingly, domestically in the United States and also the European Union. You want to be very careful about how you potentially consolidate, and really try to minimize the retention for these in line with what we call compelled privacy, or the maximum privacy requirements, are providing, and also no longer than what those legitimate business needs for the business are. So these are, I would say, candidates for not combining and not increasing the retention period.

It's an opportunity, when you're doing the simplification, to kind of re-examine these retention periods, refresh your research, see what these jurisdictions are saying, and try to tailor that retention period as short as possible.

Ann Snyder: Okay.

[Slide: Example #7B consolidated, with a comment column: consider keeping these separate based on known compelled privacy requirements, citing a Utah Code provision that requires employers to dispose of information collected in an initial selection process two years after the applicant provides it, and a Texas Business & Commerce Code provision that requires destroying a biometric identifier no later than the first anniversary of termination of the employment relationship.]

So this is the consolidation. It looks like you've reduced both buckets: this group, these three that you are grouping, and then the last one.

Jennifer Chadband: Yeah, so we see through our simplification this was an opportunity. We've got non-hire records. This is a potential global retention period. We've got an example here from Utah that's putting a shorter retention period for these records. We have kind of tailored it to two years. Now, several international jurisdictions are going to stay shorter, in an international schedule.

You will look at much shorter retention periods in some instances. Biometric information, same thing. Right here we have it tailored to a Texas requirement, biometric, kind of compelled privacy or maximum retention requirement. But it's the same scenario as well, if you are looking at international jurisdictions. You will likely want to keep this much shorter. And so, even with a retention period as presented here, and making sure that you're complying with all of the requirements, you might even consider, how low can I go with my baseline, and maybe even create exceptions for the US or certain US jurisdictions, and ensure that it's as low as possible for all of the jurisdictions.

Ann Snyder: Okay. All right. Now we need to pick up the pace a little. We have a ton of questions we want to get to, and a little bit more meat in this to get through. So we're going to look now at globalizing, sorry, global records retention schedules. And I think, Rick, I think you were going to lead us through this one. Can you just lead us through these? Tell me when to advance the slide, because you want to point out a couple things on here.

[Slide: Example #8: global records retention schedule, shown as a separate country-specific schedule per country (Austria, Bahrain, Canada, Denmark and others), with the retention periods that differ from the rest highlighted.]

Rick Surber: Yeah, we can go quick here. We've got a lot of slides that mostly duplicate information here, but illustrate an approach that's commonly taken. Many organizations have country-specific retention schedules. Our experience is that most companies still have similar, if not identical, processes in different countries. So even though the naming conventions are different, usually the records are similar. A lot of times the retention periods are different, and so that's the thing that's really changing.

And so as you scroll through these, you can see, here's Bahrain, and it's got a creation plus eight; that's a little different than the rest. If you go to the next one, Canada has a creation plus 15; that's a little different, for environmental monitoring. Denmark's got a creation plus 11; that's a little different, for their accounting. And so we've kind of highlighted the ones that are different. And all of the other information is repeating.

And so if we keep going through, this one's an interesting one: exposure plus five years max. Yeah, so there's a privacy requirement that's impacting that one. Fairly long one there. And then that 11-year one is typical of accounting records in Europe, so you'll see that repeated in all the European jurisdictions. And then, yeah, we've got an exposure requirement that's requiring duration of employment plus 30 for the US there.

So what's this? So yeah, you can kind of see that here we have taken all the duplicate information, and we've kept it on the far left, and we've created columns for each country, so that you can see the differences for each country. It's a little better when you do it this way, because instead of completely repeating each schedule, you're only kind of repeating the retention periods for each country. So we took essentially eight slides' worth of information here, and we boiled it down into one slide that is, admittedly, still kind of complex. If we go to the next slide, it's even better.

We've taken that complex slide, and yeah, this is what we'll term the best slide, in Excel at least. And we've created a default global baseline retention period, which is the retention period that was the most common between the jurisdictions. And then we have listed jurisdictional exceptions off to the right for each country where they're relevant. And so it's really just a duplication of information game with that, but I mean, getting rid of pages and pages' worth of retention schedules, essentially.

Ann Snyder: So potentially dozens of dozens of series, potentially, right? [Rick Surber: Yeah, absolutely.]

Warren Bean: And part of the driver for that, I think, Rick, is that a lot of times there's a need to produce the schedule for a given country, and so without having a specific column or worksheet for that, it's necessarily complex to display that in a spreadsheet, usually involving multiple spreadsheets or multiple worksheets within a single spreadsheet.

Ann Snyder: So, Warren, would you walk us through this one also?

Warren Bean: Sure. This is just taking one of those examples, that general accounting, and what you're seeing here is basically, on the left-hand side, we're showing that single retention schedule item, the single record category. And then on the right-hand side, showing you what the country exceptions look like. So it's sort of another way to display what Rick showed in that sort of best example, from a spreadsheet point of view, but showing it as it would look in our software tool, where you have the various countries listed and showing the retention periods that exist there. But there's actually even more going on than just the exceptions, because you'll notice too that it has a column there for which countries are included.

So for this example, we're saying that everything in this list of countries is included, with the exception of China. So maybe in this example, China doesn't keep those kinds of accounting records, and so you would know that that particular record category doesn't apply to China.

Ann Snyder: So now we're looking at it here. This view is allowing me to see where this record series applies and how it's handled in each of the countries. Can I produce a Brazil-specific retention schedule if I want to? I'm in Brazil, and I just want to see that view.

Warren Bean: Yeah, so not shown on this screen is the ability to do a search by a specific country, and it would only show those record categories that have that Included check mark, and it would show both the baseline, like in this case the creation plus seven years, plus the country-specific retentions. You'd be able to easily see those side by side and understand where those exceptions are.

[Slide: Example #9A: globalize the retention schedule language. Function: Tax; Title: U.S. Federal and State Income Tax; Description: records that represent original tax returns and workpapers for U.S. federal and state taxes; Examples: Federal Income Tax Returns, Federal Tax Workpapers, State Income Tax Returns, 1099 Reports, IRS Correspondence; Retention Period: 10 Years.]

Ann Snyder: Okay. All right. In the interest of time, let's move on to the next example. So this is another issue related to globalizing the retention schedule, but here we're looking at the language and sort of generalizing the language. Can you explain what's happening here?

Speaker: Yeah, I can explain this. I think we can go through this actually just fairly quickly. But an example here: simplifying your retention schedule, making sure that it speaks to all end users for a global retention schedule. So rather than including within the title anything that's jurisdictional-specific, or the description that's just jurisdictional-specific, make sure that it really does speak to everybody globally. Lots of opportunities there.

It's okay, I think, to have jurisdictional-specific examples, but keep them out of the titles and the descriptions.

Ann Snyder: So we have genericized: instead of IRS, we have the tax authority, to cover everybody. Okay. And here's another globalization example.

Speaker: Yeah, there's another kind of jurisdiction-specific one. It's not all about the US here. So making sure that now, instead, we've kind of transitioned this to be a very specific kind of jurisdictional-specific immigration process that is now more encompassing and would relate really to any jurisdiction that would be using the schedule. Again, we still have retained, I-9 would be a very popular search term with some end users, so it's okay to keep that, but keep it out of the title and the description.

Ann Snyder: Okay. I'm trying to advance this, give me one second. So this is handling country exceptions; this is sort of that wag-the-dog issue that we were talking about earlier.

Speaker: Yep. Yeah, here we've got a mostly globalized retention schedule that lists a default retention period at seven years for general accounting records, and then lists several country exceptions. One final exercise we can take to globalize is to evaluate all the countries, evaluate the risk of over-retention, and land on a strategic default retention period that limits over-retention while also limiting the number of jurisdictional exceptions.

Ann Snyder: So what went into the thought process here? So you're one year off for Croatia. Is there some rule of thumb that you use as a cutoff?

Speaker: Here we've just normalized at the mode, the most commonly occurring retention period. And we're assuming that for Switzerland, over-retention of one year is acceptable. We're not letting the tail whack the dog with Croatia, maybe because the operations aren't as heavy in that country, or it's kind of an outlier jurisdiction, essentially. But if Croatia were the main country where operations were occurring, maybe it would be the retention period, and there would be no jurisdictional exceptions. So this is really situational, based on where you have your headquarters, where you have most of your operations, how much over-retention you're comfortable having, all those things.

Ann Snyder: Okay. All right, what are we seeing in this example? And I think we have one more after this.

Speaker: Yeah, this is the other side of that same coin. The retention period seems high for fixed accounting records here, 21 years. It just seems a little weird, and come to find out, when you dig into the research, you find, oh, there's a legal requirement requiring Austria to have these records for life of asset plus 21 years. Well, if all the other countries that you're in have a much lower retention period, like, say, 11 years, maybe best to break that one out, so that the tail isn't wagging the dog for every other country, and have a jurisdictional exception for Austria.

Ann Snyder: So here you've seen, somebody already did a big bucket approach here and maybe oversimplified. So that's another side to be mindful of as you're reviewing your schedule, to see what has been done previously and whether that even makes sense. So, all right, let's move on to the last example here, 11: sub-jurisdiction considerations.

[Slide: Example #11: sub-jurisdiction consideration. Human Resources, Worker's Compensation (records of workers' compensation claims and filings): Final Resolution/Settlement + 18 years, driven by New York, NY CLS Work Comp 110 (1) [CR+18]. Revised: Final Resolution/Settlement + 7 years, EXCEPT Final Resolution/Settlement + 18 Years for New York.]

Speaker: Yeah, so I can walk through this. This isn't necessarily simplifying, but something to think about when you're going through your retention schedule, when you're doing the simplification, when you're refreshing. And this is kind of an example along the lines of privacy. We don't want the tail wagging the dog: the New York requirement, 18 years, for claims and workers' comp submissions, claim forms. Does it make sense to have your global retention period 18 years for these records? I mean, this is sensitive personal information across all jurisdictions, so absolutely not. See how you can normalize this.

And it used to be not really acceptable to create an exception for a sub-jurisdiction, but in this instance, maybe it should be. Maybe that's something to think about. So it's not really simplifying it, but it's an important consideration.

Ann Snyder: Okay. All right, I'm going to open it up now to questions. I don't know if any of the three of you have been watching the questions on the fly there and see some that you are keen to answer. But let's just work through some of these that I'm seeing. Some of them are out of context now. So, [audience question] does the Zasio tool have the capability to output, publish approved results to an intranet, possibly even on an internet in some cases, where staff can reference?

Warren Bean: Yeah, I can take that one, since it's on the technical side. Part of the solution for our tool is having an end-user view that is just a read-only view of the schedule that can be published internally, or in the cloud for that matter. It makes it really nice for people who just need to go in and do those searches and references without having any issue as far as messing up the schedule. But yeah, it's part of the tool.

Ann Snyder: Okay, so there's another question here: have you considered building in the ability to build a file plan into VR?

Warren Bean: In some ways, yes, because we often use Versatile Retention in conjunction with our records management tools, which do have file plans. And so oftentimes we'll link the two together so that one flows into the other. And that way you've got both the schedule view, as well as what we would often call the series or the file plan view. So we definitely do handle that as well.

Ann Snyder: Okay. All right. Sorry, I'm zipping through these. So, [audience question] would you recommend identifying those records on the records retention schedule that are digitally born, even though the retention is the same regardless of the media type it's housed in? In addition, identify those records that are scanned into the department's [inaudible] on the record schedule. So it's just, I think it's a question about adding additional types of information about the records.

Speaker: Yeah, we do recommend that. We've kind of shown just the basic components of the retention schedule here, but having other columns that list what database the records are in, where they're physically located, their security level, their personal information sensitivity, those types of things are all things that either exist for almost all clients on a background retention schedule, along with kind of the regulatory stuff, like the citations considered, the driving citations, and the operational needs. Some of those things get published to users, like location or something like that, but whether they want them to be hidden or just for the people managing the schedule is kind of a question that some clients decide.

Ann Snyder: Okay, I think we can dispose of this one pretty quickly: [audience question] I do not see the citations linked in the examples; including those would just add another column. The citations would be included in the tool. I think it was just a matter of an issue here of space. So, absolutely, a very important component. [audience question] Why are there no examples of the hazardous materials and the permanent retention? I think, again, I think that's just because it was an example. You certainly could have those. Anything to add on that one?

Speaker: Yep, yep. And you can list out individual chemicals, you can list out the different records associated with it.

Ann Snyder: Absolutely. Okay, [audience question] is there a separate view to set up the retention schedule for the IG team, and then another view for users once completed, or is this meant to be a shared experience as the schedule is developed, and for ongoing changes in real time, or all? Maybe that's a Warren question.

Warren Bean: Yeah, that kind of goes back to that idea of the fact that in our tool, we have the administrator view, which has more features and functions and robust capabilities, and then we have the end-user view, which is more geared toward just searching and finding things and reporting, and it's read-only, so that you are just kind of boiling it down to the basic needs of the end user.

Ann Snyder: Okay. This one, I don't know if we can answer without more information: [audience question] our organization operates under two retention schedules. When attempting to create a big bucket schedule, the triggers can vary widely, from one to 20 years, say for admin records. How can you deal with this issue without keeping the records too long as a default? I'm unclear as to how that's working and why.

Speaker: Yeah, I would expect to see different jurisdictional requirements driving those longer retention periods, and you deal with those with jurisdictional exceptions, like we had already discussed. If retention periods are vastly different for similar records for two businesses within the same jurisdiction, I think there's probably some operational needs at play that need to be kind of flushed out and figured out, because, legally, they would all be set at a similar period. If operationally they're different, I would ask the question why, and try to figure out how to get the inflated ones down, potentially.

Ann Snyder: So this is just another one related to the view, I think: [audience question] where are the citations located, and how do you consolidate and keep them tied to the actual document? So this is, I think, one of the advantages of doing this in a software platform, as opposed to just doing it in an Excel spreadsheet: you can update those things live. So it's just another part of the view. We didn't have it visible in the examples just because we needed some space to blow up the example so people would actually read them. Is that fair, Warren?

Warren Bean: It is, yeah. It would be another tab, like the countries tab. It's a listing of the citations. But one of the advantages, too, with the tools: you can have one instance of the citations and multiple links to those, whereas in the spreadsheet you're really copying and pasting the same reference over and over again to different schedule categories.

Ann Snyder: Okay, we are at three o'clock. I'm going to just see if we can blow through a couple more questions here, but I think we're definitely going to have to do a follow-up, if you guys are game for it. [audience question] Are there other best practices for executing on the retention schedule besides generalizing, simplifying retention periods, when you have many event-driven triggers? Auditors in regulated industries don't always allow for the retention period of regulated records to be simplified.

Speaker: Yeah, I think we've described several different ways to simplify, whether it be consolidating like items or globalizing. Those are just a few examples. But if auditors are rejecting trigger simplification, that's probably an indication that it's best not to simplify that specific trigger. Or maybe a discussion about how the trigger simplification is helping operationalize the disposition, which isn't occurring with the complex trigger, might help with that. And if you can modify the technical process to where you can get a feed of actual event trigger dates into the system that manages retention, then you can actually utilize those actual things, whether it's the end of a contract or closing of a case.

If that can be fed into your retention system so that you can actually calculate those retention dates when they occur, then you can still utilize the specific ones that the auditors want without compromising your retention schedule.

Ann Snyder: Okay. So, [audience question] how often do you see organizations keeping records longer than the legal minimums, based on business need?

Speaker: Yeah, I would absolutely say that's pretty common, actually. It's not uncommon to see that business operational needs will drive the retention period and the legal requirements will be shorter. So that is the case for a lot of different types of record series that we see. Yeah, they set the minimum, and the lawmakers aren't really in tune to what the operational needs are when they're doing it. They've got a different agenda when they're setting those laws.

But I mean, the most important reason to keep the records is for your operations and your operational need, and so if it extends past and it's reasonable, absolutely. Although privacy can drive it back down to that longest.

Ann Snyder: Okay. How about this one: [audience question] do you ever assign a number of years to permanent, such as 99 or 100, at least to set the scene for a review? Numbers can be needed in content systems. So this is just sort of working around a forced number entry. Do you see that?

Speaker: Yeah, we usually see that when the system just has a limitation where it requires a number, versus the ability to say that it's permanent. So it really is just system dependent.

Ann Snyder: And do you put in a default like that, like 99 years or something?

Speaker: We see that a lot. We'll usually convert that to the permanent category when we convert it over to our system, but we see that a lot.

Ann Snyder: Okay. All right, I'm going to wrap it there, because we're already a couple minutes over. So I think we will do a follow-up, if the Zasio team has game to do that. There are a bunch of unanswered questions here, sorry. I think that's a good sign. There's a lot of interest in this, so we will see about recording some responses to those. I want to thank all of our panelists for today's webinar and thank them for continuing to serve this community by sharing their knowledge. ARMA's next webinar will be announced very soon, so keep an eye on your email inbox. Before we close, I'd like to thank, just to remind you to become a professional member of ARMA International. Take time to invest in yourself. ARMA has an array of resources available for you, including white papers, training, articles in our magazine, webinars like this, and much, much more. On behalf of our speakers and the wonderful folks at Zasio, who give of their time and money to sponsor programming like this, and ARMA International, I want to thank you for joining us for today's webinar. I wish you the best in all your information endeavors. Stay safe and stay well. Thanks. [panelists: Thank you, Ann. Thank you.]

Questions answered in this webinar

Can the Zasio tool publish the approved retention schedule to an intranet, or even the internet, where staff can reference it?

Yes. Versatile Retention includes a read-only end-user view of the schedule that can be published internally or in the cloud, so people can search and reference it without any risk of changing the schedule. Answered by Warren Bean.

Should the retention schedule identify which records are born digital or scanned, even if the retention is the same regardless of media?

Yes, that is recommended. Columns for the database or physical location, security level and personal information sensitivity usually exist on a background schedule alongside citations and operational needs, and each client decides which of these to publish to users.

When building a big bucket schedule from two schedules whose retention periods for similar records range from one to twenty years, how do you avoid keeping records too long by default?

Differences driven by jurisdictional requirements are handled with jurisdictional exceptions. If similar records in the same jurisdiction have very different periods, operational needs are likely at play; ask why, and try to bring the inflated periods down.

What can you do when auditors in regulated industries will not allow event-driven triggers on regulated records to be simplified?

If auditors reject trigger simplification, it is probably best not to simplify that trigger, or to explain how simplification helps disposition actually happen. Another option is feeding actual event dates, such as a contract end or case closing, into the retention system so it can calculate retention from the real trigger.

How often do organizations keep records longer than the legal minimums because of business need?

It is pretty common. Legal requirements set the minimum, and operational needs often drive a longer retention period, which is reasonable, although privacy requirements can drive retention back down.

Do you ever assign a number of years, such as 99 or 100, to permanent records because a content system requires a number?

That is common when a system requires a number instead of allowing a permanent value, so it is system dependent. Zasio usually converts those entries to the permanent category when bringing a schedule into its own system.

We had so many great questions come in during the webinar, we added another session dedicated to addressing them!

Key takeaways: Breaking it Down: Best Practices for Simplifying Your Retention Schedule - Q&A Session

  • When consolidating records into a big bucket, use a record-specific jurisdictional exception for one long requirement so the rest of the bucket isn't over-retained.
  • Give each record series a unique alphanumeric code and number by fives, leaving room to add related categories next to the ones they belong with.
  • Keep paper versus electronic distinctions and system-of-record details out of the retention schedule itself, and track them in an inventory, file plan or data map.
  • Event triggers should be intuitive and clearly defined; vague triggers such as active or current leave too much interpretation to end users.
  • When a privacy maximum conflicts with a legal minimum, check which law controls and whether the privacy law has a carve-out for other legal requirements.
  • Simplifying a schedule improves adherence and makes maintenance cheaper, which matters because having a schedule and not following it is worse than having none.

Browse all Zasio webinars

Audio-described version
Transcript: Breaking it Down: Best Practices for Simplifying Your Retention Schedule - Q&A Session

Duration: 1:05:11

Speakers: Michelle Lynch, Marketing and Communication Specialist, Zasio (moderator); Warren Bean, Senior Sales Engineer, Zasio; Jennifer Chadband, Senior Analyst and Licensed Attorney, Zasio; Rick Surber, Senior Analyst and Licensed Attorney, Zasio

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

Michelle Lynch: Hello, everyone. We are back today to discuss some of the follow-up questions from the webinar "Breaking It Down: Best Practices for Simplifying Your Retention Schedule." I'm Michelle Lynch, the marketing and communication specialist at Zasio, and I will be your moderator for today's session.

[Slide: Panelists: Jenn Chadband Masingill, Senior Analyst, Licensed Attorney, CRM, IGP, Zasio Enterprises, Inc.; Rick Surber, Senior Analyst, Licensed Attorney, CRM, IGP, Zasio Enterprises, Inc.; Warren Bean, Senior Sales Engineer, CRM, Zasio Enterprises, Inc. (ARMA and Zasio logos).]

For today's Q&A session, we are joined again by subject matter experts Warren Bean, senior sales engineer at Zasio; Jennifer Chadband, senior analyst and licensed attorney at Zasio; and Rick Surber, who is also a senior analyst and licensed attorney at Zasio. Welcome back, everyone. [panelists] Good to be here. We've grouped the questions that came in during the original session into seven different sections to help keep things organized and easy to follow.

[Slide: Agenda: Section One: Breaking It Down – Record Retention Simplification Presentation Recap and Efforts to Optimize; Section Two: Records Retention Schedule Mechanics; Section Three: Triggers; Section Four: File Plans and Departments; Section Five: Executive Buy-In; Section Six: Versatile Retention; Section Seven: Risks and Privacy.]

With that, let's go ahead and jump right into the first section, "Breaking It Down: Record Retention Simplification Presentation Recap and Efforts to Optimize." I will go ahead and turn it over to our panelists.

Rick Surber: Thanks, Michelle. All of you should have watched the prior webinar, "Breaking It Down: Best Practices for Simplifying Your Retention Schedule," either live or maybe as a recording later. If not, Google that title and watch it on YouTube first, because this follow-up Q&A won't make any sense. For context, and to get us all back in the thought process, we broke it down as close to a workshop as we could using a webinar presentation to discuss our records retention schedule simplification techniques, some pain points, and a bunch of solutions. And there were nearly 100 questions asked during the presentation, and we were only able to touch on about a third of them live. So this is the follow-up to address the remaining questions. For some of those questions, we're going to be reading them as they were written in the Q&A box during the presentation. For many, we're just going to broadly describe the question, because maybe it was asked multiple times in multiple different ways, and so we'll summarize it. And we also grouped them all together to try to create a better flow. So, getting us started off, I thought one of the questions that really hit well and would be a good one to lead off on is the amount of effort it takes to optimize a records retention schedule. My answer is, that's all going to depend on what type of shape your records retention schedule is in and the goals for the desired state. And so, for example, if your records retention schedule has been reasonably well maintained, it's already a functional schedule, there's already been effort to reduce the number of categories to kind of follow a big bucket approach, we could be talking about a few weeks to optimize, and that's assuming a small number of jurisdictions to be researched and recommendations provided based on those legal requirements that are discovered. On the other side of that equation, for an outdated retention schedule that's departmentally organized, granular, we're talking probably months worth of work. We'll likely have to contact stakeholders to get more information about the records if things are stale, which adds time, and then adding research jurisdictions will add additional time to that. And also, the complexity of the industry that you're in is going to play a part as well. So a major RRS overhaul in a complex industry like financial services with an international research scope, that type of project could easily run nine months to a year, if not longer. And that's for us here at Zasio doing it. This is kind of our bread and butter, so we do it all the time. It might take longer if you're spearheading that effort with your RIM team.

For the next question, we got a question that kind of goes to the bucketing approach, and it's a good example, I think. It was, "For general accounting records, why not just group one category of records at seven years and all others in another category?" If that approach covers your operational needs and it covers the legal requirements in your jurisdictions, it might be feasible. And most clients do take an approach where you group most general accounting records in one place, with carve-outs from that based on laws and operational needs. So I think that thinking is in the right direction, but the retention period is going to depend on your jurisdiction. For example, many companies with a large footprint in Europe will harmonize to 11 years for accounting records to manage really broad accounting requirements in the EU jurisdictions. And so if the EU is just a subset or a footprint of your jurisdictions, maybe a regional retention at 11 and a lower retention for the rest of the world makes sense. But it's all going to depend on your operational needs. A big part of it is going to depend on your jurisdictions, and it needs to be optimized for your situation.

Jennifer Chadband: All right. I'll take on this next question we had. I loved actually seeing this question, because it indicated to me that people were really looking at our examples of consolidation in a very, I don't want to say critical, but people were definitely thinking of different ideas. How could I do this? How can you do that?

For this example, we talked about a workers' compensation claim record series set at 18 years. And it was really an example to illustrate how you are looking at a New York requirement of 18 years. And do you really want to set your entire global schedule for this record series that involves potentially sensitive information at 18 years? Does that make sense? So we talked about reducing that and maybe creating an exception for New York.

And the question was, "If it's active plus six for workers' comp, can it just go under litigation?" There's different approaches for that. And I really like, as I said, I like that this person thought about this, because it's a little bit like Tetris sometimes, looking at this and organizing and reorganizing and thinking of things in different ways. And I think certainly that is something that could go under litigation. We see it under litigation. Workers' comp also tends to be something that can fall under different functions for different reasons. Sometimes we see it in a risk function. Sometimes we see it under finance for some reason, and that's, I think, reflective of how that organization views that process and really where it falls under. We also see it under legal. And so, yeah, absolutely, I think there's options. And when you're looking at consolidating different record series, what might be the perfect idea for one organization may not be for another, but certainly looking at that big bucket option, because this involves essentially a claim. If you have a record series that says litigation, arbitration, claims, something along those lines, and an active plus six makes sense, absolutely, you can go ahead and do big bucket on that. So, yeah, that was a really great question.

Speaker: One thing to add to that, Jen: keep in mind, though, that if you do group it under litigation and you have a jurisdictional exception for New York, like we talked about, at 18, then you're getting into a situation where you might want to create a record-specific jurisdictional exception to that litigation category for workers' compensation, versus a jurisdictional exception for that whole litigation category, because you don't want to over-retain the rest of those litigation records for 18 years in line with New York's requirement. So it kind of demonstrates how consolidating and mixing the records together in these big buckets creates these situations for the exceptions, where at times record-specific exceptions may be necessary.

Jennifer Chadband: Yeah, absolutely. Record-specific exceptions, as we talked about in the example, creating an exception for New York: you can refine that and make sure it's only specific to workers' comp records. So it allows you some flexibility. It just depends: does that make sense? Do you find that retention period starts to get too complex? And then, under that analysis, go big bucket, or does it make more sense to keep it separate?

And then, going on to our next section, we have the RRS mechanics. And this is under section two of our categories of bucketed questions that we got. It says, "Explain the difference between the function column and the title column. Is the function/area responsible for the record?" I think it'd be helpful just to explain a little bit of why we title it function, and then what that represents versus the record series.

The function is supposed to represent the high-level business processes of the organization. And then the titles get more into representative processes, a brief description of a process that falls under that function. As to if the function/area is responsible for the record: yes, but I would say that a function doesn't necessarily designate who might be responsible for a record. I would say, to one of our prior examples, when we looked at the invoices, a function might be accounting and finance, but we also recognize that invoices come from many different business areas throughout the organization. So there's many different owners, and an owner of an invoice might be in sales and marketing, in relation to a sale of a product. Nonetheless, that record will fall under that higher-level functional area. So I would say there's a possibility that, yes, that happens to align, but because we're looking at a functional schedule, various business areas might have ownership over records under a particular function.

Warren Bean: Jen, I would even add to that that over the course of time, one of the drivers behind moving from departmental to functional has been due to the fact that there were constant reorganizations of departmental structures and who reports to who, which made it really difficult to keep track of the data owners. And so by going to a functional schedule, it really eliminates a lot of that constant shift and reassignment of those records.

Jennifer Chadband: Nice. Yeah, that's a good point, Warren. Absolutely. Another great question, I think, that we had, and I had to think about this, is: do you need a record code? I would say that industry best practice certainly is, for each records retention schedule series, to assign it a unique alphanumeric code. Alphanumeric is kind of the industry-standard best practice. That's what we recommend. And really what it provides is a unique identifier for each of those record series. And I think we see our clients really leverage and use those identifiers in different ways. It's a more concise way of tracking each of the record series. I know that for filing systems, aligning it with various systems, those alphanumeric codes can come in handy.

And it's really something that remains static for that record series because, this is a living document, of course, but when you have a record code that represents a series, that will not change. The title might get tweaked a little bit to some degree, or the examples might change, or the description, but you have something that's static that you can always use to keep track of that record series. And it provides flexibility too. Even though it's kind of static, you can always add new codes, a new alphanumeric code that fits within however you've titled those, and so there's some flexibility there. And I would add, I actually just want to ask Warren, with your experience with clients, what sort of unique significance on the software side do you see the records retention schedule codes carry?

Warren Bean: Yeah, I think, as you mentioned, Jen, it's a good way to just have a unique reference, although in the database itself, it's not required, because we have unique indexes that track the records themselves, the titles that can be unique as well. But really, it's just a good shorthand reference, especially if you have to reference maybe something that was deprecated at some point. And so if you want to say that this record code now references these two others, it's a lot easier to have a shorthand code for that than trying to spell out the entire title. So it's really just a way to quickly reference things, almost something like an icon on your desktop references a program, in a way.

Jennifer Chadband: Absolutely. I'd say, working with various client schedules, you gain such a deep familiarity with them that I can remember what a record series is. And when we talk about it, we actually talk about, "It's regulatory, it's REG 100, remember REG 100," so it's an easy way to memorize. And I think end users also absorb the record series in a more simplified way, because they start to recognize those record series that affect or relate to records that they have ownership over. And I think it's an easy way to remember and reference as well. We had one comment come in from an end user too. And I don't know if you wanted to talk about this too, Rick, but it goes to the mechanics and coding, and goes to how they have decided to organize their schedule.

Rick Surber: Yeah, I was just going to read it off. "This is exactly aligned with the broad functional classification system that I've developed over the years. Excellent. One thing I note is that it's helpful to have groups within the code, for example, ACF5 accounts payable, tax, accounts receivable, etc., which doesn't affect the retention, but is for organizing the files." And yeah, coding is a great way to group similar items within a function together that wouldn't normally fall together if they were just alphabetized. It'll keep them aligned and organized that way. For example, many clients organize their HR category to follow the recruitment, employment and termination cycle of employees. So for example, they could have a recruitment code at HUM15, an employment eligibility code at HUM20, and a personnel file at HUM25. And so I think it is useful to group these items together and make the schedule more intuitive the way that it's organized. And you noticed how in that example I counted by fives. We normally do this when we're creating retention schedules for clients, because that allows you to add related categories of records, if they come up, next to the ones that they go with. And so, yeah, we recommend using these codes for all the reasons listed, and counting by fives or leaving space between the two numbers to add new categories of records where it's needed.

Okay, so the next one discusses the mechanics as far as paper versus electronic goes: "How can you consolidate this scheme when you have one tier for physical records and a bucket retention for ECM?" And my comment here is: consider consolidating to remove the distinction between paper versus electronic records in the records retention schedule. I think that that's probably going to create some duplication and make your retention schedule longer than it needs to be. That type of record-specific distinction, I think, is better managed within an inventory or a file plan. And we'll talk a little bit more about inventories and file plans in a subsequent question.

Warren Bean: Hey, Rick, I would add to that that I don't see as much distinction now with regard to keeping one format longer than another, except maybe cases where there's a specific formatting requirement from a legal perspective. But I used to see that a lot more when people weren't sure if they could scan a record and keep it electronically and get rid of the paper. And I would say that the prevalence of that is much less now than we used to see.

Rick Surber: Yeah, there are still some jurisdictional requirements to keep different records in paper form. It's much more rare than it used to be. The trend is for laws that specify that an electronic version has the same weight as a paper version as long as certain conditions are met. So we do, within Versatile Retention, track format requirements. And we have a special way to indicate ones that are mandatory, that mandate a specific format. And so that's something that within Versatile Retention you can link to the category. And maybe you can have a special field within your retention schedule that notes that within a jurisdiction, certain types of records need to be kept in a certain format. And then the next one, it's related: "What's your take on indicating the format/platform of the records, how to pull it off in hybrid environments?" And like I just mentioned, a lot of people track that in a field, or a user-defined field within Versatile Retention is what we call it, that notes what formats the records have. Now, keep in mind that if you have a big bucket records retention schedule, it's just going to have to be a listing that covers all the records within a bucket. So a listing of either the platform or a listing of the format or something like that, or location. If granularity is needed to tie specific records to specific formats or specific platforms within a category, we recommend a records inventory or a file plan or even potentially a data map, things like that, to go more granular and really track that type of information, keeping the records retention schedule as simple, and as that kind of hardline policy that end users can follow.

Warren Bean: I agree. Looks like the next one is in my camp. So this one is about, in a similar way, how do you track the system of record for a given record category? And so that sort of ties again into format or storage or how you understand the details of the record. And for this, I'm going to share my screen and just show how we do that in the software, just to give the best example of that.

So here you should be seeing my screen showing the Versatile Retention application. So in this example, if I go into Schedules, we have the ability to do a lot with regard to additional metadata fields. And I'm going to just grab one of my existing items here. And we've got a number of ways to work with user-defined fields. But essentially, I'm just looking at General Accounting here. I've got a tab for user-defined fields where I can have things like what systems this record might be stored in and what examples it might have as far as document types.

[Slide: Versatile Retention demo, Schedules: ACF05 General Accounting (Corporate; Accounting, Finance, Payroll, and Tax; Creation Date + 7 Years; Approved), User Defined Fields tab showing Systems "SAP, Versatile Enterprise", Examples "Disbursement journals, Bank Recs, Balance Sheets", Security Classification "Internal, PII".]

So this is the type of thing where we can add as many of these types of fields as we need to. And in this case, things like that might be a pick list that you define and have users available to select whatever applicable systems might be used for the system of record. So a lot of flexibility there, and it just gives you an easy way to not only note that on the record type itself, but also, if you wanted to search by that, then you can search either with that name in that field using something like the all-field search, or you can search specifically on that in any of these user-defined fields and say, "Well, I'm looking for everything where we might have something in SAP," for example, and find all the records that are related to that. So it's a great way to be able to quickly locate records that might be in these different systems, as well as, when you're looking at a record type, know where you're going to find records of that sort. So that's just a good example of how we can use those. Michelle, I will give it back to you.

Jennifer Chadband: So, moving on to our next question we had: "What are the trends in discarding physical employee files if the original employee file has been scanned to electronic format?" This is a very common question that we get from clients, not even just specific to employee files, but their records in general, anything that they have scanned. And we do conduct a lot of research on this. Our database has a ton of different wet signature requirements, hard copy requirements versus electronic requirements, across the jurisdictions that we have, over 130. So this is something that we look into in detail for our clients. And so generally, I think, what our clients do, in considering all the research, is that electronic format is a permissible format, and it will carry a similar kind of evidentiary weight as a hard copy. Now, there are definitely carve-outs to that across the jurisdictions. We actually see jurisdictions, particularly in some of the Eastern European jurisdictions, Russia, where they're actually requiring a certain format for employee records, including electronic. And also, there's carve-outs for some jurisdictions with regard to employment contracts, that they want that in hard copy with the wet signature. And so typically, the approach for the employee records is that the electronic format generally is permissible; there's not a need to keep that physical copy. However, they're also looking to make sure we're considering all of the jurisdictions.

Is there anything, an outlier here, that we need to consider in that regard? So I would say that's typically the trend, and electronic tends to be pretty reliable and more common.

We have another question, and it was an example of a conflict between regulations. And I believe this was provided in the context of privacy: you might have a privacy requirement that would conflict with a law. We definitely see this. A lot of what we call the compelled privacy requirements require a shorter period of time for records, or a maximum period of time, whereas you might have a legal requirement that's saying, actually, you need to keep it this long, and there's a conflict. And it might even be a conflict within a relevant jurisdiction. I'll give you an example. Biometrics: really trending internationally, domestically, big deal; more and more jurisdictions are enacting laws. In fact, Illinois has a law, no longer than three years essentially, for employee fingerprints after the termination of employment. Texas also has one, no longer than one year. Now, this may conflict, in particular the Texas one, with regulatory requirements for certain industries where you need to keep employee fingerprints: FINRA, for broker-dealers, for example, you need to keep a record of those fingerprints for a certain amount of time. And so if you have a broker-dealer in Texas and you're keeping their fingerprints there, you've got two laws that conflict. Now, typically, these laws will allow for a carve-out for "unless there's another legal requirement" that requires something longer. So that's an example. Utah requires information collected about applicants to be kept no longer than two years after the decision is made about that applicant. Now, clients that we have that are government service contractors will say, "We have to keep those applicant records of non-hires for three years, pursuant to our very specific EEO obligations." And so there you've got a conflict, and we see our clients, where there's a conflict, end up retaining; the Utah law doesn't have a carve-out to keep longer. So I think that privacy analysis definitely, you do have to get into the weeds there and look through the laws and see which law will trump the other when you have conflicts, and whether there's a carve-out that allows for that. And then we have another question that feeds into this, and Rick, I think you were going to address this next one on a compendium.

Rick Surber: Yeah, the question is, "Is there a compendium where legislation that determines records retention can be referenced?" I am sorry to report that, to my knowledge, there's no free compendium of recordkeeping requirements. We're going to have a shameless plug here, however: Zasio's Versatile Retention software includes a database of recordkeeping requirements, along with robust search capabilities and an analysis of each legal requirement, breaking down who is regulated, what records are regulated, and the retention period. And it allows you to import your records retention schedule and link the requirements directly to your categories of records. So I think it's better than a compendium, and it's a great resource; that's a great deal if you can take the time to link the legal requirements to your records retention schedule and keep it maintained. And if you don't have time for that, our consulting team can help you out with that.

Warren Bean: Yep, that's a good point, Rick. That's kind of the reason we actually developed this system, because there are just so many sources and so many ways that you can go about trying to find that, none of which are exhaustive or conclusive. So hence the tool.

Rick Surber: Yep, I should have mentioned that there are over 130,000 citations in our database. That's US and domestic, and just domestic, there are over 60,000. So yeah, it's a lot. It's a lot. And I don't think that if you did find a compendium that's free, I don't think that they would keep it updated. And I don't know that it would be as reliable as Versatile Retention, nor as focused, because it would probably be a lot of different laws and regulations.

Warren Bean: Right. And speaking of citations, the next question deals with, "Where are the citations located, and how do you consolidate and keep them tied to the actual document?" So here again, I think showing is going to be the best way to work with this. So let me share my screen again, and I'll show you a couple of different examples of that. And there it is. So in terms of the location of the citations themselves, again, it's part of our tool, so it's in the database that the tool accesses. In this case, I'm showing you the software-as-a-service version, so the database itself is located in the cloud.

But just going into the Research tab, I wanted to take an example of how you can do that kind of searching through the tool. As an example, if you're looking for regulations in a specific jurisdiction, you might have those jurisdictions carved out per your retention schedule. I'm going to just use some general ones here and say, let's assume that we're looking for regulations in Australia, and we want to look for things related to common business activities, maybe accounting, something like that. And I could add keywords in there and so forth, if I wanted to, but we'll just keep it simple for today. So this would be a way to search on the jurisdiction and the topic, in this case accounting, and find, in this case, about 343 items related to that topic in that jurisdiction.

Each one of these items here has all the detail in terms of descriptions and requirements and details and text and so forth. So that's one way that I can search that. And then to tie that into how do you keep that associated or grouped with the specific document types, that's where I can take any of these items and select them and link them to my schedule. So by selecting the ones that I find that are relevant, I can then go to the Link option and choose where I want to link those. And I'm going to just do some sort of arbitrary ones here, because they're probably not really... I'm going to just say these are related to general finance and link those items to that finance record. Or, in this case, that one is already under change request, so I will link it to another one.

[Slide: Versatile Retention demo, Research: search on jurisdictions Australia (ACT Canberra, Australia Federal, Northern Territory and others) and business activity Accounting; selected citation: Australia Federal, Income Tax Assessment Act 1936, (262A)(1B), regulated party Foreign Banks.]

And so now those three items have been linked to a particular part of my schedule. And I can verify that by going to the schedule and see, yep, indeed, it is now linked to Accounting, Finance as far as the department, General Accounting as far as the schedule. And if I wanted to look at that detail, we're now switching over from the research side to the actual schedule. And so we're now on that General Accounting schedule, and we see, indeed, here are the items that are linked under my Citations tab. So this is how we can tie them to the specific record type. So we always have that as a reference to say, what are the legal requirements that we are saying are applicable to this category of records? And generally, taking the various references to retention periods here and coming up with a retention period that works within those legal boundaries, as well as those operational requirements.

So hopefully that demonstrates how that works and where those are stored.

Jennifer Chadband: All right. So I think we're going to transition into our next category. Should be section three, event triggers. So, a lot of chatter on the event triggers. And it's just interesting how controversial, or how many questions can come up surrounding "Is creation appropriate versus active?" Event triggers, I think, just to preface some of these questions and the conversation: they really should be as clear as possible. And even when they're as clear as possible, they also need to be defined very clearly. So event triggers, innately, they should be fairly intuitive. They should not leave too much discretion to the end users and how they interpret it. And they should also be part of training, helping people to understand, as part of the training, and making sure that they're clearly defined, and so they have those resources. When you get down to creation date, our first one says, "I've seen the trigger 'creation date' or 'date created' used in other schedules. Is there concern that those terms mean something different to an end user versus a records manager?" So that's a great question.

Absolutely, that could be the case. So the solution is that you need to be consistent in how you use that term, and it needs to be clearly defined. One thing that we recommend, and we see some of our clients might not even have an event trigger of creation. They might just have something that says five years, not creation plus five years. Or they could have something that says creation plus five years. Or it could be calendar year plus five years.

How are you going to define this? One thing I think that is helpful is to be all-encompassing here. So if you want to define creation, it could be that the retention period is triggered at the end of the calendar year in which the record is created or captured. So that definition encapsulates all these various items, which goes to another question we had: "Does creation mean when it's actually officially declared a record and captured? Or does it mean when it's actually created?" So how can you structure your definitions, event trigger titles, to be intuitive and provide really decisive direction for end users? "When do you use creation date plus number of years?" That goes to this definition that I just provided. Where can you be all-inclusive with your definition? Creation can mean this, but make sure you're including all the contingencies that fall within that. Whether you decide to do calendar year, whether you decide to use creation, or just list it as five years, for example, how are you going to define that within your definitions? Also, we had somebody comment, "I have used C as current year instead of an event trigger." So again, somebody is deciding to define it in their unique way, and that's fine, as long as you're consistent, as long as you have it defined, as long as it's decisive and it's inclusive for the different circumstances that might fall within that event trigger. Also, they mentioned, "I use E as an event trigger, for example, for contracts and agreements, which means E equals expiry of contract or agreement."

And so, absolutely. There's that distinction there, and as long as that is defined and available as part of your retention schedules to end users, there's definitely different ways to go. This question goes to the same topic: "What is the difference between current and creation plus?" That might be something that really is a very similar thing. We don't oftentimes see or recommend using the event trigger "current" in the retention schedules, because it tends to be something that can leave a little bit too much discretion and interpretation to end users and can be kind of ambiguous. So current and creation plus can very well be synonymous, but however you're defining it, again, just make sure it's consistent. "What is the difference between until superseded and current plus?" Kind of the same thing. If your end users are asking... if you're asking that question, your end users will be asking that question.

How can you potentially define it more clearly? Because superseded very well could be synonymous with current plus. So just make sure that everything aligns in a similar manner. We had another comment come up: "I suggest current year in place of creation." And they said, "Creation plus X years may be perceived as disposition is required at the time of inactivity or obsolescence, which would be difficult to keep in compliance.

Current year broadens the time period to manage disposition regardless of the day within the current year the document was produced." And so I think that is a good point. And I think this also sheds light again on how are you defining these event triggers? Is it tied to the current year? Is creation the creation or capture... of the year within which it was created or captured? So that's, I think, another example that really does go to: a definition can really help clarify this if end users are not sure.

Warren Bean: And Jen, if I can jump in there just to make an additional statement on that: within our records management software, we actually do have those distinctions, where even if you say it is creation plus, in the definition of creation date you can specify whether the retention should go to the day or if it just goes to the end of the year for whatever period of time is selected. So again, just underscoring the need for clarity and defining your rules as far as how they're applied.

Jennifer Chadband: Do you often see, Warren, that end users need to schedule to a specific day rather than calendar year, or is it more common to defer to a calendar-year type disposition process?

Warren Bean: More common to defer to the end of the fiscal or calendar year. Some people do destructions quarterly, some even monthly, but rarely are they monitoring that on a daily basis, just because of the work involved in approvals and execution of those.

Rick Surber: Sure. Yeah, I was going to say the same thing, Warren: even if you're doing a creation plus and scheduling to the day, without some kind of automated system notifying you when a schedule is due for disposition, logistically, most people do dispositions regularly at a quarterly interval or annually, but hopefully not as much annually, hopefully more quarterly.

Jennifer Chadband: We had another user comment, or, I'm sorry, a viewer comment: "Our company used the word 'active,' but the retention schedule was revised, for example, to now indicate current year plus seven." I think this is something we see more and more, and we try to stay away from using the term "active." Again, it's maybe even a little bit more difficult, I think, than "current." Active has a lot of... there's a lot of subjectivity that can go into that: what does active mean? For an end user, active could mean, "I want to keep this just in case."

That's an active reason for end users. So that can be a slippery slope, I think. And so, getting away from active: active could mean life of account, it can mean the life of asset, it can mean current year plus this. So if you can take active and really provide some event triggers where the nomenclature is more reflective of the life cycle of the records and provides just more direction, is a little bit more decisive... I think that this company's choice to move away from that was probably good. And that's what we are seeing more and more, and we definitely recommend. "And other triggers include after completion/closure, after audit, while active, expiration." Absolutely. I think these are all really good triggers. I think when you go through a retention schedule simplification, one of the goals is to reduce event triggers as much as possible and make sure they're clearly defined. And anytime you can do that, you provide some additional clarity and simplicity to the retention schedules, and the end users benefit from that. And so, like I see, after audit completion, after expiration, after completion/closure: these are event triggers that are reflective of the life cycle of the records and are, I think, important. "Do we ever see the use of life of company plus X years?" That's a question here. Yes, we do. And in fact, there are legal requirements that require this. And so, yes, we absolutely do. And typically, this is in relation to board of director records, shareholder meeting records, shareholder records. And oftentimes those regulations, or implementing this type of retention period, guarantees that if a subsidiary, or even the holding company, or the company itself, dissolves or is divested or whatnot, certain records are retained for a period of time thereafter, in case there's ongoing liabilities and/or pursuant to the legal requirements. So we do that. We also see clients that don't do that, and instead they have a different process where they address those ongoing recordkeeping requirements once the company is no longer active. And how do we apply [inaudible]...

Rick Surber: Yeah, sorry to interrupt. I was thinking maybe Warren's got a call at the top of the hour, so let's have him go next with some of his slides. And then we can extend past if we need to, or at least I can.

Warren Bean: Yeah, that's absolutely fine. Thanks, Rick. And a lot of mine don't necessarily require showing my screen, so we can save some time there as well. But some of the questions that we had dealt with some of the file plan situations, as well as just specifics around Versatile Retention. So with regard to file plans, this is in section four. One of the questions is about whether Versatile offers support for creation of file plans. And if we're talking about Versatile Retention, that's really outside the scope of that particular product. But it is something that we do in the records management tools, such as Versatile Enterprise, Versatile Professional, etc., where you're creating essentially a plan for how you will store the records, whether they are storing active files on a shelf or boxes in a record center. But a file plan typically deals with the record series and the structure of that, and is somewhat of a legacy concept now, because the idea behind file plans in the past was how do you best put your records into a physical space so that you can easily retrieve them and find them. That is now not as much of an issue when you can easily search for records by multiple criteria and be able to be told where those records exist. So yes, we can do that in other tools that we have, but it's not as much of an issue as it used to be in the past. Another question is about whether the system can export entire sets of records or schedules as structured data. And indeed it can. So, for example, in the Versatile Retention program, we have export buttons on just about every screen that you can export to CSV files, as well as any of the reporting system files or report templates can be exported to Excel spreadsheets. So you can take whatever columns and structure that you want and take the result of a search and export that to a spreadsheet as needed in order to get that out into a structured table to use in other forms. We can even do direct interactions with other databases if needed. So if that sort of ties into integrations, we definitely have some options there. And then, in terms of related questions to the software, this is dealing in section six with Versatile Retention itself. One of the questions was, "If the organization isn't ready to commit to a software solution such as Versatile, are there any homebrew solutions that you can recommend as a stopgap while working on buy-in to purchase a solution?"

And I would say probably the most common there is just a good old spreadsheet or Access database. That seems to be the database of default for any kind of a homegrown solution. Sometimes people will develop their own solutions, but it gets costly and ends up taking a lot of resources and time. So something simple like that is probably the best way to go. And that way, when it comes time to actually move that into a formal retention schedule management tool, it's much easier to import from a spreadsheet versus, say, from a Word document or a PDF, because of the structure that's there. So that's always a good plan.

In a similar kind of question, as far as the tool itself, one was about, "Is there need to do or implement an automated data scan and classification before I'm able to use this tool?" And I would say not necessarily. Doing a data inventory ahead of time can certainly help, especially if you are developing a retention schedule. It's a good first step to help you with understanding what records you have and how you're going to classify those, but definitely not a requirement, especially if you have maybe the start of a retention schedule that you want to put into the system and then manage it from that point forward. You can certainly do that.

And even if you do want to conduct a data inventory ahead of time, it doesn't necessarily have to be an automated scan. Those tools are great, but it depends on your budget and your needs as far as how you want to conduct an interview like that. Another question dealt with the citations themselves: "If I have Versatile Retention and we only do business in the US, would the global information be something I could use?" Well, it depends, first of all, on the subscription, because we do offer US-only or North America or international subscriptions. And you can certainly use the international subscription, even if you're only doing work in the US, if you need to see a reference to those other citations. Obviously, the cost is going to be higher, so you have to make sure that you can justify that cost, but you can certainly use that as another reference point if needed.

Rick Surber: On the other end of that, Warren, you can limit the jurisdictions that you see to only include your specific jurisdiction. So, for example, if you were in a handful of US states and you had a US subscription, there are ways to set up your company so that when you run searches, you select your company, and it only lists the requirements in your jurisdiction.

Warren Bean: Yeah, good point, Rick. Absolutely, because I don't think anyone, well, at least not very many companies, work in all 130 or so countries that we're dealing with, right? So the last one on my list of questions is about whether the program has a mechanism to set calendar reminders when documents are reaching their retention. "If so, can the reminder be broadcast to multiple individuals in the company?" So that's really more of a records management function, again, versus a records retention schedule function. Versatile Retention as a product is more about the policy, managing the rules and regulations and definitions, whereas records management is about implementing that policy on given records.

And so in that case, yes, if you used a tool like Versatile Professional or Versatile Enterprise, where it's tracking the individual records, indeed, we can have reminders that go out when records are due for destruction, and it can go to multiple people. That's all customizable. So that's certainly something we can do for you. So with that, it looks like it completes my list. So I will let you guys continue, and I'll drop off.

Thanks so much for letting me be a part of that panel. Great discussions. I was really loving all of the interaction that we had and all the questions. So I'm looking forward to getting additional responses to that. Take care, everyone.

Speaker: Thank you, Warren.

Jennifer Chadband: Okay. Why don't I just go ahead and circle back? There were just a few more points to talk about on triggers. And actually, both these last two are very similar. "How do you apply the retention rules to large policy manuals where different sections are updated at different times, but the overall policy needs to be managed in its entirety for regulatory compliance purposes?" So we do see this issue. The other comment was, "The policy retention is not clear for keeping old versions." So we see this issue. I think the question is...

Oftentimes they're grouped together, so we'll see expiration of policy or the life of the policy. And oftentimes those amendments, riders, or whatnot are kept alongside or as part of that policy. Now, because they relate to a prior version, there may be ongoing liabilities in relation to that prior policy version. So I think it goes to determining: do these need to be broken out? Can they be kept for a shorter period of time, rather than the life of the policy?

Maybe it is something like superseded/retired plus a certain amount of years. And can they be broken out and retained for a shorter period of time? If that is the case, then that's a possibility. Although typically we do see all of those records kept for the life of the policy. But if the records are super voluminous and you can keep them for a shorter period of time, of course, that's something you can consider, breaking those out.

Rick Surber: And that's me, right? Let's do... we had a couple of questions on archival records. First it was, we're still in triggers, Michelle, "How are archival records handled?" And I'll deal with that one first. So there are two things going on with that question that come to mind. For most retention periods, the trigger is going to be the period of time when the records are actively being used, and the number of years specified after the trigger is typically the archival period. Now, that's not always the case, but it works for a lot of clients and in a lot of industries. If you're in a situation where your triggers don't align with the records' active use, consider adding a separate field to your records retention schedule to inform what's active use versus what's the archival period.

Now, that's the records lifecycle management aspect of the archival records. The other aspect is you're going to have these historical records that are going to go into an archive and pretty much live on indefinitely. Many clients just bucketize those in one category of records and have a historical record for that, set it permanent. But this other question asked, "How do you implement when using a permanent retention?" When you do that, you don't have that trigger date/event to control the date the records should be transferred to the archives.

And so I think that's another one where having another field to specify the active versus archival period is going to be needed, especially where it's a big bucket of archival records, like historical records, where they may be actively used for different periods of time before they go into the archives. Another option, though, and we had a comment that talked about this during the presentation: if there is a trigger that aligns with the active use for a permanent category of archival records, you could have a trigger plus 99 years, with the policy that anything noted at a long-term retention of 99 years is in essence permanent. And that will allow you to have that active use and know when to transfer after the active use to the archive.

That's it for triggers. And so next, let's go into section four, which is file plans and departments. Warren already touched on this a little bit on the Versatile Retention side, with talking about creation of file plans and exports of legacy schedules. But here's another one that relates more to the consulting side of things: "Can you have a separate audit retention schedule for each department so they could be boxed together? We have audits for accounting every year, so this would be more of a logistics in both gathering the documents and information for the auditors." And so one option, again, and we've talked about this already before, is to tie categories together using a separate field within the retention schedule. So logistically, this could work by indicating which categories are relevant to a specific audit, so that you could generate a report by filtering by that particular audit. In Versatile Retention, you'd be able to generate a report based on that UDF, user-defined field. If more granularity is needed, which I assume is probably the case, because individual records are going to be relevant to this and not categories of records, I would track these items with an inventory that's mapped to the records retention schedule. That way, you can go to the record level and indicate which ones are relevant to an audit, filter by that, and be able to report on that. And as far as the storing of records in specific places, that's another place where a file plan, I think, is a great way to deal with and plan for how they're organized. And then the records retention schedule is going to feed the inventory the retention period. So Warren discussed that within the software side of things for Zasio, being a distinction between Versatile Retention, which is the records retention schedule rules manager, and then our other line of records management software, which helps you set up file plans, and you can create more granular listings of your records and inventories there.

And so next slide is five, executive buy-in and approvals. Yeah, so this was a great question: "We have to get approval for any changes to the retention schedule. If we consolidate, that means approval from multiple different directors, executives. Do you have suggestions or tips on how this might benefit them to help get buy-in?" And I can start on this one, but I welcome input, and I'm sorry that Warren left, because I would have liked to have heard his thoughts on this. But I think the way that optimizing your retention schedule is going to benefit the executives and the people that you're trying to get buy-in from is especially relevant where you have concerns that the retention schedule isn't being followed.

If you know that there's confusion, if you know that there's a problem with user adherence, that's one place where I think you're worse off... sorry, the only thing worse than not having a retention schedule is having one and not following it, because if you've got one and you're not following it, you know better. And so, yeah, I think if you have a retention schedule and you have concerns that it's not being followed because it's too complex or difficult to understand, the buy-in is that you're out of compliance with a policy, which could result in some bad things as far as if litigation happens or if regulators are looking for records that you can't provide, things like that. And so there's a compliance aspect to it. Another thing is that if there is user adherence, a larger retention schedule is difficult and potentially expensive to maintain. Laws are dynamic, so maintenance is a necessary thing to keep your records retention schedule up to date. Departments and structures of organizations are constantly changing, and so aligning the processes helps keep the retention schedule evergreen. And so optimizing your records retention schedule makes maintenance easier and less expensive. So those were the two buy-in points that I had to go to directors and executives with.

Speaker: Oh, you're muted, Jen.

Jennifer Chadband: I would add too, I think that simplification of a schedule in a way is a big change. It's kind of an overhaul of the schedule. And I think a lot of our clients, when they start these initiatives and we work with them, they're thinking, this is a chance for us to start fresh with our stakeholders, maybe new approaches. A lot of times our clients use this as an opportunity to get people away... Now that it's a functional schedule, people are sharing different areas, different record series; it's not necessarily end-user focused. The record series aren't necessarily just catered to the needs of one individual. It's really an opportunity for them to re-examine the retention periods of their schedule. And with privacy in mind, a lot of this is also, let's get the retention periods as tailored as possible to the legal requirements. Let's re-examine business operational needs, see if we really need to keep these records permanently. Can we get them to discuss this and re-examine?

And so I think, overall, in addition to the administrative ease that comes with it and the increased end-user adherence with the simplified schedule, it's an opportunity to re-examine those retention periods and see if there's areas for risk reduction in that regard as well, get rid of some of that over-retention. So there's, I think, a lot of different opportunities here. It's an opportunity to re-engage with end users and get them really on board and really involved in the records and information management program as well. So I think there's definitely a lot of different angles you can come at with this type of initiative.

Rick Surber: Yeah, privacy is a great one. And speaking of privacy, let's skip to section seven. We had a couple questions that touched on it, and they were great questions. I'm just going to read off these questions: "Apart from regulatory action or reputational damage, what is the actual risk posed to a data subject if we keep data for longer than is necessary? Can you give some examples of negative side effects on data subjects?" So that's a great question. And then another one that's along those same lines: "Can you share your thinking you mentioned about statutes and limitations regarding privacy?" And so the bad news is that privacy is its own beast, and talking through these questions would take an entire webinar in and of itself.

[Slide: For More Information Contact: Zasio, sales@zasio.com, 800-513-1000 opt. 1; ARMA International, education@armaintl.org, 913.444.9174.]

And so we don't have time today for that. We're already over by a few minutes. I can see... if keeping this under an hour. So the good news, though, is that we're going to talk about these questions and give you some other tips to optimize your records retention schedule, considering privacy, during our August 5th Virtual Coffee webinar, which will be at 9 a.m. Mountain Time, so 11 a.m. Eastern Time, on August 5th.

If you haven't joined us for a Virtual Coffee session yet, it's a casual forum to ask questions about pain points or questions trending on RIM topics. And for this one, we're going to submit that the topic is privacy. We've got these two questions already submitted that we'll be talking about. And you can also ask questions live, pre-submit questions, or just listen in. And there's no pressure to volunteer your name or company information. We can keep that stuff anonymous from other attendees if you do want to participate. So for more information on that, check out the News and Knowledge page on zasio.com. And that's it. I think we're through them all.

Michelle Lynch: Yeah, thanks, Rick and Jen. We hope you all found today's question and answer session to be a helpful resource and to complement our initial webinar. If you do have any follow-up questions for either organization, you can reach out to us using this contact information. And then, like Rick said, be sure to join us for Virtual Coffee. And then we'll also be sharing some information: we do have a new version of Versatile Retention coming out, so I think we will be offering a demo there. So we'll be sure to send that out in the follow-up email when we share the recording with you all. So have a great rest of your day. Thanks, everybody. See you next time.

Questions answered in this webinar

How much effort does it take to optimize a records retention schedule?

It depends on the schedule's current shape and the desired state. A reasonably maintained functional schedule with few jurisdictions might take a few weeks; an outdated, granular departmental schedule takes months, and a major overhaul in a complex industry with international research could run nine months to a year or longer. Answered by Rick Surber.

Do you need a record code for each record series?

Industry best practice is to give each record series a unique alphanumeric code. The code stays static even as titles, descriptions or examples change, gives a concise way to reference and track the series, and helps when aligning filing systems and other systems to the schedule. Answered by Jennifer Chadband.

Could a trigger like creation date mean something different to an end user than to a records manager?

Yes, so use the term consistently and define it clearly. An all-encompassing definition helps, for example that the retention period starts at the end of the calendar year in which the record is created or captured, which also settles whether creation means drafting or formal capture. Answered by Jennifer Chadband.

What are the trends in discarding physical employee files once they have been scanned to electronic format?

Generally clients treat electronic format as permissible and carrying similar evidentiary weight, so the physical copy isn't needed. There are carve-outs, though, such as jurisdictions requiring a specific format for employee records or wanting employment contracts kept in hard copy with a wet signature, so check every jurisdiction for outliers. Answered by Jennifer Chadband.

How do you handle archival records, especially when a category has permanent retention and no trigger to control transfer to the archive?

Typically the trigger covers active use and the years after it are the archival period. Where that doesn't fit, add a field showing active use versus archival period. Another option is trigger plus 99 years, with a policy treating 99 years as permanent, so you know when to transfer. Answered by Rick Surber.

Consolidating the schedule needs approval from several directors and executives; how can we show them the benefit to get buy-in?

If the current schedule is too complex to follow, you are out of compliance with your own policy, which creates risk in litigation or with regulators. A simpler schedule is also easier and less expensive to maintain, and the effort is a chance to re-examine retention periods and reduce over-retention. Answered by Rick Surber.

During this Q&A session, the Zasio team addresses questions about bucketing, records retention schedule mechanics, triggers, and more!