Hi everyone
I have a question regarding implementation of the big bucket approach to retention scheduling, and jurisdictional regulatory requirements.
I work in a multinational company. HR would like to split its record series into as many jurisdictions that it works in, citing a specific regulatory retention requirement in each jurisdiction. The HR records schedule has about 10 records series, and this will create 130 series.
I think that this would become problematic when implementing in O365, not to mention the maintenance and update of the retention schedule, and am trying to persuade them to go for setting an overall retention period per record series, aligned to the longest regulatory retention requirement.
Admittedly there are a couple of unusually long retention requirements out there that would justify separating out, and this can be done, but on the whole they are generally only a year or two apart.
HR is extremely concerned about any over-retention of personal info. Apart from HR there are other functions that have split their records series too, whenever they encounter a different retention requirement, rather than integrating it into an overall retention rule, they want to create a different rule.
Would like to hear from others who may have encountered a similar issue, and hopefully resolved it!
Many thanks,
Paula McClure
AMIRMS, MLIS
To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK
To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK
For any technical queries re JISC please email [log in to unmask]
For any content based queries, please email [log in to unmask]
|