- What is SharePoint 2010? Vision and Reality
7
comments
- Installing SharePoint 2010 on Windows 7
12
comments
- Web CMS Market Predicted to Hit $1 Billion in 2010
3
comments
- 2010 Web CMS Trends from Industry Analysts
- Overview: SharePoint 2010 Metadata and Taxonomy Management
8
comments
- A Week in Google: Gmail Rings Telephones, Chromium 7 Hits the Mainstream
1
comment
- Cisco Moves to Acquire Skype for US$ 5 Billion
1
comment
6 Ways Document Management and Records Management Differ
With the growing importance of compliance and eDiscovery issues for many companies, it might be time to consider deploying a records management system. Chances are that your company already uses some kind of document management system. The question is, will your document management system also support records management?
At the core of this question is what is the differences between document management and records management. Let's examine six differences.
1. Documents v Records
What are documents?
Documents consist of information or data that can be structured or unstructured and accessed by people in an organization.
What are records?
Records provide evidence of the activities of a given organization’s functioning and policies. Records often have strict compliance requirements regarding their retention, access and destruction, and generally have to be kept unchanged. There are often very stiff penalties for not doing so.
By some estimates, and depending on the company, 90% or more of all documents are records (meaning a portion of them are not!). Conversely, all records are documents.
2. DMS v RMS
Document Management Software (DMS)
Document management software was developed to make it easier for users with a shared purpose, usually within an enterprise, to access and manage documents. Another important ability is that it also allows them collaborate on those documents.
Common access to the documents is enabled by existence of a library and/or a repository within the system.
Records Management Software (RMS)
RMS software is more concerned with identifying, storing, maintaining and managing data that is used to describe events in an organization’s work cycle that are related to statutory, regulatory, fiscal or operational activities within the organization.
Unlike document management systems, record management repositories are generally focused on keeping only what is necessary for a specified length of time.
3. Storage
One of the critical differences between document and records management relates to the reason and approach each takes to storing documents.
Document Management And Storage
The principal reason for storing the documents in a document management system is so users who need to access the information stored in those documents can do so quickly and easily.
In general, these generalized electronic document repositories provide for the checking-in and out of documents that can be revised and unlocked for future revision, with version tracking and histories.
Records Management And Storage
Records management requires that records be kept in their original format in case they are needed for compliance or legal reasons.
Good records management needs to place records in their proper context so that generally they are kept in series, or in indexes determined not by internal, enterprise-dictated rules, but by external rules.
In fact, record keeping has become such an issue that in addition to on-site records storage, many organizations operate an off-site records center too.
4. Automated processes
While all companies in the regulatory or compliance zone have to spend a lot of time ensuring that their records and document management do exactly what they’re supposed to do, many of the processes involved are now automated.
Document Management
Automated processes are one of the elements that make document management attractive to companies whether that means the mass capture of documents and placement of that information in the repository, or its placement in a records management system.
In fact, automated process are a core function of these systems controlling the document’s life cycle, security access controls and other key features like version control and short-term storage.
These processes automate workflows so that the right actions are carried out on the right documents by the right people at the right time.
Records Management
Records management uses automated processes to manage records in a consistent manner no matter what format those records happen to be in.
Electronic record keeping systems must be able to preserve not only the content of those records, but also the context and structure they came from and often for long period of times. The final records should be auditable in their original form long after they have been put in the records repository.
5. Security
There is no getting away from the security and integrity of documents in either system. The difference between the two, though, is that with document management software security is desirable, with records management essential.
Document Management
With document management, security has to be placed in the context of document accessibility for users. Authorized users have to have quick access to information with comprehensive document management security controlling access to the repository.
While all systems will have means of tracking who has been using a document, when it was checked it out and when they put it back in the repository, and any changes that were made to the document — including new versions — the security standards are not necessarily as stringent as those required for keeping records.
Records Management
At the moment, the standard to which records security and records security within records management software is judged is the US Department of Defense 5015.2 regulations.
If a system is compliant with the DoD 5015.2 standard or equivalent it sets the standard for management of records that will be eventually transferred to the U.S. National Archives and Records Administration (NARA).
These include government personnel records, manuals, standards, directives and documents that are scheduled for declassification or redacted items. In Europe, MoReq 2 is the standard applied across the entire EU as a standard.
6. Disposal
Document Management
The disposal of documents in a document management system occurs when the life cycle of the document has been complete and is no longer needed in the business process. While this can mean destruction it can also means turning them into records.
The decision to turn a document into a record depends on the need of the company and whether there are legal requirements to hold onto the documents.
Records Management
The destruction of records is generally regulated by law with strict procedures so that the information contained in them will not be disclosed. Records management software plays a significant role in this by implementing retention and destruction schedules that are compliant with regulations.
However, with public bodies, the records will not be physically destroyed, but converted into a format that is acceptable to U.S. National Archives and Records Administration (NARA), or National Archives of the country you reside in.
Final Thoughts
Document management software was created to make it easier to use store, manage and collaborate on electronic information. Records management software was designed to manage the life cycle of records so that organizations can easily comply with regulations and support the eDiscovery process.
It's very likely that you require both document and records management capabilities within your organization. Depending on your needs, a document management system may be able to support most of your requirements. Understanding the difference between document and records management and the software that supports each, should help you decide your next steps.
6 Reader Comments
Leave a Response
Job Openings View all
| Post a job
|
RSS
- Content Manager at Expedia
- Business Development Manager at Saba
- Graphic Designer at USTREAM
- Enterprise Business Representative at Salesforce.com
- Copy Editor/Proofreader at Business Wire
- Technical Program Manager at Animoto
- Interactive Project Manager at RealTime Media
- Digital PR Strategist at Mekanism
Featured Events View all
| Add event
|
RSS
- Sep 19, 2010 – Oracle OpenWorld 2010
- Oct 7, 2010 – HartmanEVENT 2010 - Social Media & Mobile Usability
- Oct 13, 2010 – Day Ignite - Chicago 2010
- Nov 2, 2010 – Day Ignite - Berlin 2010


Get the Newsletter
Email It
Buzz it
Tag It
Stumble It
Add RSS
Processing...


Nice introduction to Records Management. I'd also be interested to see the potential or RM in the cloud - I know this may be long way away because of trust/security concerns but we have the capability to do this on our cloud collaborative content management platform SambaJAM (we can plugin DoD 5015.2 certified RM because we're built on top of Alfresco) but not sure of the potential in the market for this yet! Is RM essential to smaller businesses which can't afford on-premise RM applications or only the highly regulated industries who can?
Really useful explanation. I recognize that companies need both record and document management functionality in a single system. Otherwise, it's going to be a hassle if you first try to find a document in a DMS and then, if you failed, in a RMS. Anyway, a “unified” system should be able treat the stored unit properly depending on whether it's a record or a document. Or, if you wouldn't mind, depending on the document life cycle stage.
Thanks for this helpful delineation.
So many content managers consider records management a subset of their field, akin to workflow, character recognition, forms processing, hierarchical storage management, etc!
I tell them, “Content management is a toolbelt of technologies; records management is a professional discipline.” That said, I maintain that the two fields really do need each other.
I am curious to learn what drives the decision to make an investment in a document management software package in today's business environment. What is considered an average investment in a package and is it typically something that is being factored into IT budgets in today's business environment in light of the economic uncertaintity that exists?
The article has a many errors.
1. Any document that has an evidential value is record or is useful for the business is a record, not a document.
2. Documents don't become records at the end of their useful life as stated at point 6, but when they become uneditable and unchangeable. The difference between a document and record is that the document can be edited and versioned but the record cannot. That fact that records cannot be edited preserve their authenticity and evidential value.
3 It is alo wrong to state that records are never detroyed. Many of them are destroyed through a controlled and auditable process.Only a small number of public records goes to the National Archives.
Hi Lucia
Thanks for your thoughtful response. I accept that any document that has evidential value is a record and covered that in the first difference where I stated that “Records provide evidence of the activities of a given organization?s functioning and policies.”
However, this does not mean that all documents emanating from a company constitute a record. A document is only a record, as you state, once it has become immutable.
Emails, for example, between system users regarding possible changes to business processes would be considered documents, but as they are not an exchange of evidential information about enterprise processes they cannot be considered records.
If it can be changed/edited it is not a final record and as such is still a document.
Documents provide information for enterprise activities rather than a legal record of those activities. Subtle difference but important nonetheless.
Finally, there was no suggestion that records are never destroyed: “The destruction of records is generally regulated by law with strict procedures so that the information contained in them will not be disclosed. Records management software plays a significant role in this by implementing retention and destruction schedules that are compliant with regulations.”
While all documents in public bodies do not necessarily go to the National Archives, they must be in a format that enables their sending and registration as archives, if required. Whether they are or not depends on a given agency's protocols.
According to the National Archives Under 44 U.S.C. 3101 “…the head of each Federal agency must make and preserve records containing adequate and proper documentation of the organization, functions, policies, decisions, procedures, and essential transactions of the agency.
“These records must be designed to furnish the information necessary to protect the legal and financial rights of the Government and of persons directly affected by the agency's activities.”
best regards,
David