n-iManage RecordsManager Tracks Retention Deadlines. We Make Sure Someone Acts on Them.
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.
What RecordsManager tracks on its own
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.
Where the tracking stops and the waiting starts
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.
Where this shows up in practice
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.
A hold gets logged somewhere besides iManage
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.
What's still manual around your records retention process?
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.
Running RecordsManager but still tracking disposition dates by hand?
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