- SOLUTIONS & SERVICES
I have been involved in a lot of ECM implementations and guess how many have included a File Plan?
I contend that this is not an uncommon scenario. Typically the Client is focused on the electronic storage of the documents, being able to find them again with little effort, and then automating the business processes for those documents. The focus is on productivity.
The focus is not on compliance issues and how a File Plan and Records Management can benefit the organization. The ECM implementation team is not asking any of the primary RM questions such as:
How long do we need to keep these documents (retention)?
Here are 4 reasons why a File Plan must be part of your ECM implementation, or if it is not, it needs to be Phase II.
An ECM system bears many risks if a File Plan is not created and implemented. A previous post discussed the differences between a Taxonomy and a File Plan. The reality is that they should complement each other, one without the other does not address the full scope of managing your content. If you have implemented an ECM solution, then you have probably improved your productivity, but without the File Plan, you have not addressed your compliance risks. Both of these practices together will benefit and protect your organization.