Upcoming dispositions land on someone's actual task list
A matter approaching its disposition date shows up as a task for the person who needs to approve or extend it, instead of waiting inside RecordsManager until someone happens to check.
iManage RecordsManager is the records retention and disposition add-on inside iManage: it tracks how long a matter's records need to be kept, flags legal holds, and schedules when something becomes eligible for disposition. We don't administer RecordsManager or set its retention policies. We build the automation that turns an upcoming disposition date or a hold into something a real person actually sees and acts on.
RecordsManager applies retention schedules to matters and documents inside iManage, tracks legal holds that should block disposition, and flags records once they become eligible for review or destruction under a firm's own policy.
That's real compliance infrastructure, and it does the tracking correctly as long as someone is watching the right screen inside iManage at the right time.
A disposition date flagged inside iManage doesn't notify anyone outside it. Someone on the records or compliance team has to open RecordsManager on a schedule, check what's coming up, and chase down approvals before anything actually gets disposed of or extended.
That manual check is exactly where disposition deadlines slip, not because the schedule was wrong, but because nobody looked at the right moment.
A matter approaching its disposition date shows up as a task for the person who needs to approve or extend it, instead of waiting inside RecordsManager until someone happens to check.
A legal hold placed in RecordsManager creates a record in your firm's own compliance tracking or case management system, so it's not the only place that knows the hold exists.
A disposition review that depends on someone's calendar reminder, a hold nobody logs anywhere else: tell us what it is and we'll look at what's actually possible to automate.
Tell us what's not connected, a disposition deadline nobody catches until it's close, a hold that only exists in one person's memory. We'll look at what's realistic to build around RecordsManager's own schedule data. And if records retention isn't actually where the risk sits in your firm, that's fine too; the same question applies to anything else running on a manual check.
Let's talk →An add-on inside iManage that tracks records retention schedules, legal holds, and disposition eligibility for matters and documents, built for firms that need to show they're following a formal retention policy.
Not on its own in most setups. It flags records as eligible for disposition according to the firm's schedule, but actually destroying or extending them typically still needs a person to review and approve it.
It's a separate module inside the iManage product family, not something every iManage Work license includes by default, so firms that need formal records retention typically add it on.
Within RecordsManager itself, exactly what notification options exist depends on the version and configuration a firm runs. It's not something we administer, but it's exactly the kind of gap we build automation around when the built-in options fall short.