Retention clocks that nobody owns
A retention schedule looks tidy until you ask who starts the clock when a customer closes, disputes, or migrates products. In sampling we often find clocks that never start, clocks that restart on every product add-on, and legal holds that never clear.
Name an owner per record class. Tie the clock to an event your systems already emit. Then sample ten closed files and see whether the archive matches the schedule — before a reviewer asks the same question.