Now, rather than attending a live class, you can absorb all the information in one sitting or break it down to fit your timeline (it’s only an hour long, though). You can go back and cover topics multiple times if necessary, and you’ll have the information at your fingertips.
That is the biggest difference between the previous training and this new option; this one is recorded and available immediately upon purchase. Students can replay it at a later time which is totally convenient to them.
As a little refresher for what will be covered:
What even is it? Well, it’s basically a way to track how long you should keep your files. In many organizations, they have different time periods grouped together and don’t understand how to translate that information into the iManage Records Manager (IRM) settings.
In this Self-Paced IRM Retention Policy Basics Training class, you get access to a one-hour training where I go over how you create what they call a Retention Schedule in IRM and how to create Retention Events that go into that schedule. Those are the two building blocks of how to put together those rules in the software.
While 10 retention basics will be covered, here are a couple of other more detailed examples on how to:
You have your rules in place. However, if there’s any sort of pending lawsuit against your company or your client or your firm, you will need to make sure any relevant files are not destroyed. That’s what the Hold is for. You need to understand how to put that hold into the system so that it stops files from being destroyed.
Now, there are some pros and cons to that. I will teach you what the hold will and won’t do in iManage during the class. It’s very important to understand that from a legal standpoint for your business.
The Disposition Eligibility Report is the native report in the iManage Records Manager software. You will use this report to share a list of possible files to be destroyed with the responsible attorney or executive. They can then make the decision of whether or not those files can be destroyed. And if not destroyed, which ones should be kept? You take that feedback and update your software accordingly.
How does it get done? How can you automate and simplify that process?
Once you have your retention schedules and assign them to a file, you are then ready to use a retention policy. I will show you how to update what’s called a Record Status on the file. When files are originally created or born, they’re listed as “Active” in the system. The retention policy allows you to go through and update the status of a file. Say the status of the file is now “Missing,” you want to list that on the file. You can now do that by having all your rules in place. Or if you want to destroy a file, you can do that as well and update its status to simply say “Destroyed.”
All of these basics (and more!) will be covered in this one-hour, self-paced class: IRM Retention Policy Basics (Self-Paced) Training.