Following on from our previous blog – Expanding the GRDS – we’re asking if it would be easier for your business if we did away with functions and only had activities that could be used under any function?
In the feedback you’ve given us so far, we’ve received opinions for and against this idea.
For the against camp, ‘Remove all functions from the GRDS – We are not fond of this option as you are losing context as you will not know which function the activity relates to unless there is an indication of which functions the retention relates to.’
For the yes camp, ‘The concept of a list of records types as per Western Australia is probably the most user friendly to non-records personnel, and assuming adequate cross referencing to cater for differences in terminology this is potentially the most user friendly to all employees in an organisation.’
What do you think? Are you a traditionalist and like the structure of function/activity/record class, or can we be innovative and have a GRDS that is more user-friendly and could be adapted to your organisation’s needs?
For all you traditionalists out there, how about if we keep the same structure of function/activity/record class but elevate the common activities of planning, policy, agreements etc to a ‘Common Activities’ section. As we mention in the GRDS Renewal Discussion Paper^, the Northern Territory Records Disposal Schedule of Administrative Functions has 16 common activities which can be used across any of the functions.
So far the feedback has been nothing but positive for this concept:
The idea of a common activities and common functions as per the Northern Territory Archives Services is appealing as it would enable: a more comprehensive coverage of various record types, and reduce duplication or omission where we currently have some record types that are covered under one function and not the other.
One function for multiple activities – Prefer this option as it would remove a lot of ambiguity.
Raising some common activities that are relevant to multiple functions, to a function level so that the record class or subject index is able to be utilised without having to repeat them across functions is very appealing.
Advantages of this approach include a smaller GRDS to implement, reduced duplication of activities and consistency of retention periods across functions.
If we go ahead with this concept, would we also need to provide you with implementation advice?
On a slightly different note, we have received some feedback about the use of ‘Major’ and ‘Minor’ and ‘Significant’ and ‘Other’ to differentiate which records should be kept permanently. You have told us that these record classes can be confusing because either they are not being consistently used in the schedule or there is disagreement within an agency on what is considered major or minor, etc. How would you like to see these terms being used if at all? Do we need to have information at the beginning of the schedule about what ‘significant’ means? See the WA General Disposal Authority for State Government Information as an example.
Before the discussion paper closes for comment on 27 February 2015, we are having a drop-in session at Café Cue on the ground level of 80a George Street in Brisbane on Wednesday 25 February from 8am to 1pm. This is an opportunity for agencies to provide feedback in person and there is no set agenda or time slots or presentations. Just drop in for a chat and a coffee. We haven’t forgotten our regional friends, so keep an eye out for an event coming soon.
^Please note: the GRDS Renewal project has finished. The new version of the GRDSwas released on 1 September 2016.