In the course of doing some work for one of our partners – we were asked to take a look at the existing workload for their ECM team. This particular ECM team has done a great job maintaining and integrating ECM components from a variety of vendors. As typical in such an environment – we found that everyone on the team had primary support duties for at least one component, and was involved in customer support issues or updating /enhancing one or more of the company’s ECM products on pretty much a daily basis. Continue reading
If there’s one message I consistently hear from customers today, it’s how big of a deal public disclosure is for the government and how we need better solutions around it. That being said, you would not believe how many of these organizations don’t feel that they have a good handle on their content.
In Washington State, public disclosure refers to the release of all documents and content to the person making the request. These documents at minimum need to be available for the requestor to view. There are some exemptions to this, such as sealed case files.
Good public disclosure practices really start with one thing: good record-keeping (and destruction). We hear time and time again from customers that they’ve never thrown anything away for fear that the document may be needed at a later date. While they may be thinking that this is the best way to avoid throwing anything away that should be kept, it also means keeping records that should have been destroyed.
Some aren’t aware of the fact that when a public disclosure request comes in, organizations are required by law to turn over any documentation pertaining to the request (as long as it is subject to disclosure). That means that if documents haven’t been destroyed and fall under the specific request, those documents need to be turned over as well, even though they are past the retention period. This poses a huge risk in regards to potential litigations.
Getting your records in order may seem like an overwhelming task, but here are some steps you can take to move toward better practices related to retention and disposition of records.
- Understand YOUR Organization’s Requirements for Record Retention and Disposition
Every organization is different. Certain records have to be kept longer than others, some records might need to be sealed, others may need redaction before they can be turned over, etc. Each organization, each department, even each business process may have different requirements around records. Determine and document what the requirements are so that when you start to do an inventory of content, you have a definitive plan regarding what needs to be kept and for how long. Click here for a link to the Washington State Records Retention Schedules.
- Where are my Records?
Identify where records are kept. Are they stored on a network share? In a file cabinet? In a content management system? Somewhere else? Are they in paper form? Electronic? Are there video files? Regardless of where the documents are kept, the regulations are around how you get the content organized, not the file format or how hard the collection process is. This will help ensure that there are not duplicate documents, and if there are, that only the pertinent copies are kept so as not to be a factor in a potential litigation.
- Perform an Analysis and Inventory of Your Records
Some organizations choose to do this internally, some hire a contractor, and some take a hybrid approach. Regardless of which path you choose, determine what content you have, what needs to be kept, and what can be disposed of before evaluating any technology. This will keep you from bringing content into a solution that will need to be immediately disposed of after the initial analysis.
- Choose a Solution that is Flexible and Easy
95% of organizations I work with are looking for a solution that is easy-to-use yet flexible enough to change with requirements. They want something that can easily set up to work with current retention and disposition schedules, yet can be updated without too much effort if laws or regulations change.
- Trust the System
If you’ve done the prep work correctly, then what you need to do is trust what you’ve put in place is going to work. Choose a good partner with a track record of success to help you.
These are just a few ideas to get you thinking about what can be accomplished around public disclosure, records retention and your content. ImageSource has been assisting customer partners with these types of solutions for the last 20 years. We have done everything from initial consulting through implementation and support. Below is a short list of some of offerings:
- Expert consulting to determine your “as is” state and develop a plan to get you to your “desired” state using industry best practices
- Assessment of your current technology and how it can be leveraged
- Solution evaluation to perfectly match technology with your requirements
- Solution deployment, configuration, training and rollout
- Document collection, conversion, scanning, taxonomy definition and automated classification and metadata extraction
- Data Migration
- Ongoing partnership for system/process tuning, growth and support
- Managed applications services
The ILINX platform can assist any organization with getting a handle on their content.
In ILINX Capture, the most basic unit is a batch profile. A batch profile is a container that includes batch fields, one or more document types and a workflow. It is unique, self-contained and completely independent from each other. In general, you would want to create a batch profile for each unique workflow process in the system.
If you have multiple doc types that mostly follow the same process, you should think about creating a single batch profile to hold all the doc types. With this setup, you can then use permissions to give users access to their specific doc types. Furthermore, within the workflow designer you want to break your workflow logic into common processes, shared by all doc types and specific doc type sub-flows. If you find that you need to create too many sub-flows, re-evaluate the relationship between a batch and doc types and see if you can fix the problem.
The goal is to create unique workflow processes so that system maintenance is easy; and one way to deal with that is to avoid duplicating batch profiles that are performing the same tasks.