With All of This Data, What Must Be Retained as a Record?

Community Topic(s):

Keywords: retention, electronic, records management, records, record, data

Current Rating:
(0 ratings)

Most records managers will tell you that the retention of information content must be determined by the company’s retention schedule – and this a correct. However, as we know, the same or similar content is often stored on multiple media and in diverse formats - and not all data is equal or constitutes a record that must be saved beyond its business use.

Information content often exists in one or (usually) more of the following media and formats:

  • Electronic notes retained by use of an electronic device (e.g., on a  laptop).
  • Handwritten notes on hardcopy (e.g., paper)
  • Hard-copy documents (paper, fiche) as output by an electronic system or received from third parties
  • Hard-copy documents that have been annotated (electronically or manually) after creation
  • Electronic documents generated or received in electronic form and saved only in electronic form – e.g., as an electronic report, spreadsheets, MS Word docs.
  • Electronic documents that have been annotated
  • Data retained in spreadsheets and databases (i.e., source data used to generate routine or adhoc reports – or just for queries). These often have electronic templates associated with the reports that are generated. They also have or don’t have the ability to regenerate the output (e.g., report)
  • E-Mail that contains an attachment of an electronic document (above), with additional explanatory information included in the e-mail cover
  • Others

Additionally, electronic data (and records) may be unstructured (e.g., a document created through word-processing, a spreadsheet or a report) or structured (e.g., database tables) and the same or similar content may be in both forms. There are also often multiple versions and copies of the above documents, data and retained output.

Which of the above must be retained and for how long? What constitutes the “record?”

Here is my non-legal (but experienced Records Management) perspective:

The simple answer is that the final, complete or signed document that is evidence of a decision or transaction is the official record - and that is considered records management best practice. However, in our ever more complex electronic records world - it's simply not that simple. There are many complexities. And...as our electronic record-keeping systems mature....I believe that a more granular view is needed. Several of my technology friends who "get" records management - and with whom I've discussed this - have expressed the same opinion.

In short - we must take a look at the specific content to ascertain its value and the requirements surrounding it. Final assessment of requirements must be reviewed and approved by a firm’s Legal counsel.

Here are two use cases/"rules of thumb" for you to chew on: 

1. You have various versions/drafts of a document/report (hard-copy or electronic), the document/report in paper form, the electronic document, AND underlying data for the same content

Potential Decision: The electronic document can be declared the official record, and the other documents and underlying data can be considered duplicate data, as long as the following conditions exist:

  • The electronic document was captured and maintained in a manner that makes it “authoritative” per ISO 15489-1 (2001)
  • There are no unique regulatory, contractual or risk related requirements to keep the hard-copy
  • The underlying data is not needed to prove the reliability of the documentation (e.g., the IRS requires electronic data underlying tax returns to be maintained) or to recreate the output

Note: If a firm’s Legal Counsel has stipulated that a Preservation Hold requires that some or all of the shorter term documentation and data be kept, then these must be kept as well.   

2. You have underlying data, the template used to generate reports and the ability to regenerate the reports.

Potential Decision: A copy of the output (document) may not need to be kept because the ability to regenerate the record may suffice.  Legal and Compliance should make this determination.  Note: In some cases, a copy of the generated electronic or hard-copy report may need to be kept.

Regulatory requirements often state that records with specific content must be maintained. In other cases, the specific content is not dictated, except that records must be retained that provide evidence of certain activities. The latter is called a principle based requirement (very common in Canada). There also is often no stipulation that the final record (and not the source data) needs to be retained.

It is important to determine the records that must actually be created and maintained to satisfy regulatory as well as business requirements. Some source data may (depending upon a given firm’s interpretation) be considered no more valuable than as a means to generate the records. Other source data will be considered records to be maintained for the full required retention period for the “record.”

This is an emerging topic…We all have a long way to go in this arena...Your thoughts?

The opinions expressed here represent my own, and not those of Bank of America (BAC) or AIIM

Report

Rate Post

You need to log in to rate blog posts. Click here to login.

Add a Comment

You need to log in to post messages. Click here to login.

Comments

Bud Porter-Roth

Great Post and Thank You

Susan - really good information and I agree with your points. Could you also address how this information gets down to the office worker and will the typical office worker understand and actually complete all the actions needed to designate a record? It is my experience that the typical office worker still has problems understanding RM, and in some cases, does not think he/she is "responsible" for records management.
Report
Was this helpful? Yes No
Reply
Susan Goodman, CRM

Great Post and Thank you Author's Response

Thanks Bud! I agree with your comments. The office workers (and tech/application owners) request and reqiure good direction about what must be done with the data/records for which they are responsible. To the extent that critical decisions are made related to key sets of data (based on the retention schedule as well as an assessment of the value of the data that falls under specific content), the better.

The opinions expressed here represent my own, and not those of Bank of America (BAC) or AIIM
Report
Was this helpful? Yes No
Reply

Chris Walker

Declaration is Overrated

Figure out how long to retain stuff for, but make it transparent to the user.

No offense Bud, but the typical office worker has more stuff to think about than RM. Does the typical office worker think about other admin-type stuff, e.g.: HR, finance, purhasing.? Should they? Help no! We hire specialists for that stuff.

Leave RM to the RM specialists. Build your solutions properly and let folks get on with the jobs they were hire to do.

http://www.aiim.org/community/blogs/community/Records-Matter-Declaration-Doesnt
Report
Was this helpful? Yes No
Reply
Bud Porter-Roth

Office Worker and RM

Chris, No offense taken as I think we agree on where the office worker stands - reread my last sentence. And this, I think, is the real problem with RM, workers don't want to do RM but systems are not "intelligent" enough to do it for them. Let's not forget, however, that not all companies have the tools and resources to do RM automatically.
Report
Was this helpful? Yes No
Reply

John Phillips

It's the Reponsibility of Both Records Creators and Records Managers

Granted, no office worker should have to wrestle with retention rules. However, the only real authority on the content/value of information is the creator of information. And so they are critical to any Records Manager or RM process that is trying to establish appropriate retention.

They started the information life cycle process by creating the information and they need to help finish the process by associated content with some category that can be linked to a retention rule. This "declaration" can be manual filing or by autoclassification rules, but both need some input and participation by the records creators.

Otherwise, I suppose, RM and IT could get together and place a "one-day-retention-before-automatic-deletion" rule on information created by certain uncooperative records creators!
Report
Was this helpful? Yes No
Reply

Susan Goodman, CRM

Declaration is Overrated

Your comments support both Bud's comments and my reply above to Bud...

The opinions expressed here represent my own, and not those of Bank of America (BAC) or AIIM
Report
Was this helpful? Yes No
Reply

John Phillips

Yes, Records Need to Be Defined!

Yes! Insight into records content must be used to determine how long to retain information. This applies to all types of records objects - database files, Web pages, Office documents, e-blobs, etc. Remember why we keep records? Operational, regulatory, litigation, historical, and administrative reasons. Only one of these - operational - has any real ROI.

The others reasons we retain information is because someone besides the organization that is creating the records wants the organization to keep records - for their own particular purposes. Records Management practices were created to improve an organization’s “operational efficiencies and improve economies.” Not to keep information because we might get audited or sued and someone else might want it someday.

So, the only organizations that can ignore records value and associated retention rules are those organizations that are willing to fund the retention of vast quantities of mostly useless but potentially dangerous information – the proverbial e-discovery goldmine.


Report
Was this helpful? Yes No
Reply
Susan Goodman, CRM

Yes, Records Need to be Defined!

Good points John. I'd just argue that records maintained for reasons other than operational can have ROI - e.g., if identified as valuable for secondary purposes - such as public relations, marketing or developing a new product. I'd urge all to keep a look-out for the Sedona ROI guidance that will be out soon (and that I helped draft).

The opinions expressed here represent my own, and not those of Bank of America (BAC) or AIIM
Report
Was this helpful? Yes No
Reply
Susan Goodman, CRM

Yes, Records Need to be Defined Response with Sedona ROI Guidance Link

For "The Sedona Conference® Commentary on Finding the Hidden ROI in Information Assets," go to the Sedona Conference site,right hand side, recent publications. It http://www.thesedonaconference.org. I was a member of the drafting team. Good info on the ROI issue....Susan

The opinions expreseed here represent my own, and not those of Bank of America or AIIM.
Report
Was this helpful? Yes No
Reply

Alan Baldridge

Retention Scheduless and Methods

In many cases the Retention Schedules are set by authorities outside of the corporate structure. These particular records or documents are some of the most volatile from the impact they would have on a business if they were not retained long enough or possibly too long. Having worked with SOX and been involved with record retention for a several years I've seen the impact of both situations. I believe that companies sometimes get buried in record retention looking at all records and documents instead of focusing on the most important. Granted most records and documents have a degree of importance so there is some validity to reviewing all or most record and document types, but the primary focus has to be on the most important. Good systems design should always provide for a purge methodology to allow the company the ability to maintain it's databases as well as hard copy or electronic copy of documents. Years ago our society was not so crazy and looking for anything they could take a company or person to court over to make a gain for them selves, but today that has all changed, we have created a world where we have to keep our guard up at all times which overall impacts our business, profitability and even our personal lives. The true answer may not revolve around record retention but maybe morals, but until we can get the moral issues resolved focus on the critical records and don't stress out over every little tidbit of information.
This is my opinion only and not that of my employer.
Report
Was this helpful? Yes No
Reply
Susan Goodman, CRM

Response to Retention Schedules and Methods

Hi Alan - I agree with many of your points. There definately are regulatory requirements for records retention, which should be documented as part of retention schedule development. As you know, the longest retention (be it legal, business or other requirement) generally governs. I also agree that we can't worry about every little piece of data, and must prioritize our efforts on a risk based basis. However, I'm suggesting in my initial blog post that where a plethora of data exists with the same or similar content - decisions should be made about what needs to be maintained to satisfy record-keeping requirements. To the point of the other commentators, this should be communicated to users in a manner that will be easy to follow. As we all know, without guidance, users either inadvertently destroy data that should be kept - or (commonly) keep everything forever, at great cost. Regards, Susan


The opinions expressed are my own and not those of Bank of America or AIIM.
Report
Was this helpful? Yes No
Reply

Randy Moeller

End users need simple but they are pretty smart...

There is a lot of stuff that can go very quickly but the average end user will rarely go beyond 'how long do i keep a copy of a contract?' They ask the question too rare to remember the answer and you are thankful they know they have a copy.

Or should you be? I have found that folks are pretty good at knowing their work & role to whether they have a signed official contract or a copy (as an example). If you have a contract system, import to SAP or whatever folks have a pretty good idea their hard drive version is a copy.

Automated processes with the move to the e-world has made it a question I'm rarely asked. No one has said to me in many years that they have the original invoice. Is every pile of stuff managed as well as it could be? No, but folks do try. Systems without real records management functionality are just tough since it takes a hands on approach.
Report
Was this helpful? Yes No
Reply

Cathy Beil

"Documents" vs. "Data"

I've been thinking about these issues a lot too. In my organization we've got retention schedules that most staff understand as applying to "documents" and there's a lot of confusion and disagreement about whether they apply to "data." My inclination is to say that the information is the information, whether it is in an document image in our document management system or typed into a line-of-business application. However, some of our more long-term-research-oriented staff feel that we should keep the data (which originally came from the documents) so that they can use it for researching trends.

Setting aside the issue of laws and regulations that may apply and just looking at the "business need" aspect, does it make sense to say "we retain the document for x years and the data for x+ years," even if it's the same information? From a "traditional" RM perspective this makes me uneasy, but I can see why it might make sense in some cases. Thoughts?
Report
Was this helpful? Yes No
Reply
Alan Baldridge

Documents vs Data

In my opinion they are both the same and can both become an issue for a company if they or either kept to long or not long enough. Years ago the thought was keep everything forever, but now the concern is to keep it as long as required but then get rid of it as soon as possible after reaching the end of the retention period as defined by regulations or by company policy. I fight with the same issues but in the end we have to abide with Laws, Regulations, and with the company's Internal Audit and Legal departments.

The opinions expressed are my own and not those of my employer.
Report
Was this helpful? Yes No
Reply

This post and comment(s) reflect the personal perspectives of community members, and not necessarily those of their employers or of AIIM International