Announcing general availability of Records Management

IrinaWins I agree with you, it's cumbersome to have to do this manually. On the other hand, you may be able to 'architect' the environment so that:

• The majority of records (and other ROT content) are subject to auto-deletion retention policies
• A specific and much smaller set of document libraries map to label-based retention policies. I know there can be variations, but we found that most of our business areas had no more than 10 active libraries in a smaller set of 'records sites' (as opposed to Group-based or other sites with lower-grade retention requirements).
• An even smaller subset of document libraries that were used to store records that would be transferred to an archival institution at some point. These will never come up for disposition review. 

While the disposition review process throws up individual documents, these can be filtered by document library; if there is only a smaller subset of libraries (in point 2 above), this may be less onerous. However, the organisation needs a process to ensure that (a) the person doing the review of the library can access all the content and (b) they have somewhere to save the metadata (we used an 'Archives' SPO site for this purpose, also used to manage paper records).  

I had another related question last week. Some organisations may want to keep what they call a record 'stub' when a record is deleted (or certain other actions such as migrated) from the library; so the library shows the record USED TO exist but was deleted at a given time, on the authority of someone. I don't think this is possible in SPO unless you export the metadata to a list instead.