5.1 Overview
Provision continues to develop in line with that stated in the 2018 year-end PUR and July 2020 update.
5.2 The Council Records Retention Schedule (retention schedule)
As stated in the RMP, the Retention Schedule is SCARRS. The review of those record types that are stored within SP is now substantively complete (evidence previously submitted and acknowledged). Over 2022-2024, the Records Manager will engage with the Business to expand this review to include document types not stored within SP.
Note: this Project was originally to be scheduled 2021-23 and would have formed part of the work programme in the proposed RMP covering that period.
This process will see the creation of a single unified Retention Schedule that will then be posted on the Council’s website. Currently, retention schedule outwith those record types stored within SP is a mix of SCARRS and stand-alone Retention Schedules generated since the adoption of SCARRS in 2014. This provision includes a number of updated Retention Schedules prepared as outlined in the update of July 2020. These projects are a mix of routine housekeeping and projects that seek to address specific issues not resolved by SCARRS.
Please see evidence document FCPUR21-14: HR Disciplinary records retention proposals paper. Please note that this report is under consideration at date of submission.
5.3 SharePoint retention
As outlined above (please see also 4.4- SP Project), the SP project is now substantively complete and the operation of SP is moving into BAU. Part of BAU will include both maintaining and developing retention provision within SP. The Records Manager will be involved in this at all times in their capacity as manager of the Retention Schedule.
One thing that is being done in this regard is to procure a stand-alone back-up platform for O365. This is being done in part for Information Security compliance reasons and also to assist in automated retention bedding-in as accepted and understood practice within the Council. The concern here is that business-based best practice retention periods may take a time to reach what they should be with documents initially cycling out of the system ahead of the end of the time of their legitimate business need.
Note: this provision is in live discussion at time of submission.
5.4 Retention in the wider Council MS Office365 (O365)
Within the wider O365, the Council has set retention to 2 years in both Teams and OneDrive. This has been suspended over the term of the Pandemic but is to be introduced over the coming time. The purpose of this is to ensure that these areas do not become log-term storage areas with no retention control. To ensure onward retention of documents, staff will simply move completed documents to the appropriate SP library. This practice has already been adopted by a number of work teams and individuals.
In addition, retention has been considered for other O365 apps. Of particular note here is the recording of video.
Please see evidence documents FCPUR21-15: recording meetings technical overview & overarching DPIA;
FCPUR21-16: staff guidance note on considerations when thinking about recording a meeting.
5.5 Technical Specification Document
This is a new development that has relevance across a number of PRSA elements. However, one of its primary benefits is in the area of records retention so it is included here.
The Technical Specification Document (tech spec) is an early-stage assessment tool for use in the purchase/ procurement of new technology solutions for the Council.
Its purpose is to map solution technical capability and compatibility with the Council network and, where there are issues, spark discussion and resolution of those issues and risks.
There has been a document of this type focussed on purely IT technical matters for a number of years. However, the revised document has both slimmed down the IT Technical asks and includes IG capabilities. From a PRSA pov, these include both retention (element 5) and destruction (element 6) as well as export to specified destination (element), IS and DP (elements 8 and 9) and audit trail (element 11).
The Records Manager is a member of the Working Group that has managed, and continues to manage, the development of the Tech Spec.
Please see evidence documents FCPUR21-18: tech spec form; FCPUR21-19: tech spec work instruction.