Document Feedback - Review and Comment
Step 1 of 4: Comment on Document
How to make a comment?
1. Use this to open a comment box for your chosen Section, Part, Heading or clause.
2. Type your feedback into the comments box and then click "save comment" button located in the lower-right of the comment box.
3. Do not open more than one comment box at the same time.
4. When you have finished making comments proceed to the next stage by clicking on the "Continue to Step 2" button at the very bottom of this page.
Important Information
During the comment process you are connected to a database. Like internet banking, the session that connects you to the database may time-out due to inactivity. If you do not have JavaScript running you will recieve a message to advise you of the length of time before the time-out. If you have JavaScript enabled, the time-out is lengthy and should not cause difficulty, however you should note the following tips to avoid losing your comments or corrupting your entries:
-
DO NOT jump between web pages/applications while logging comments.
-
DO NOT log comments for more than one document at a time. Complete and submit all comments for one document before commenting on another.
-
DO NOT leave your submission half way through. If you need to take a break, submit your current set of comments. The system will email you a copy of your comments so you can identify where you were up to and add to them later.
-
DO NOT exit from the interface until you have completed all three stages of the submission process.
(1) This procedure provides requirements to ensure Information is destroyed pursuant to obligations in the Public Records Act 1973. (2) Authority for this document is established by the Information Governance Policy. (3) This procedure applies to RMIT Group staff, students, temporary employees, contractors, visitors and third parties who create, use, manage, handle or process data and information defined by Part A (Institutional Data) or Part B (Research Data) of the Data and Information Lifecycle Management Procedure. (4) In addition to this procedure, destruction of Research Data must follow requirements in the Research Data Management Plan. (5) Data and Information defined in Part C (Unofficial Information) of the Data and Information Lifecycle Management Procedure is not in the scope of this procedure and authority for its destruction sits with the Chief Information Officer (CIO). (6) This procedure should be read in conjunction with the Retention and Disposal Standard. (7) Destruction of RMIT Records is conducted lawfully from either of the following: (8) Records which have a retention period specified in the RMIT RDA may be destroyed when the records meet all conditions below: (9) Destruction of RMIT records must be planned and integrated into the University’s business processes and programs, including information governance. (10) Records designated for destruction must no longer be required by the responsible work unit, school or college, or for any other justifiable business or operational purpose. (11) Destruction actions and retention periods for information must be justified. (12) Destruction actions must be based on an informed decision-making process. (13) Destruction of RMIT records must be authorised. (14) Internal authorisation must be sought prior to destruction. (15) The University must be able to evidence that implementation of destruction decisions was authorised and lawful. Documentation must include: (16) Once authorised, records must be disposed of or destroyed in a timely manner. (17) Destruction should be undertaken with a level of security commensurate to the Information Classification of the record. (18) Records destruction must be monitored to ensure it has been undertaken accurately. (19) Destruction of records must be secure and irreversible such that records be inadvertently released or lost. (20) Records which can be destroyed via Normal Administrative Practice (NAP) principles are not subject to the retention requirements in the RDA, are pre-authorised for destruction and do not require documentation. (21) NAP allows for the destruction of: (22) Requirements for the Destruction of Information must be met and documented this via the RMIT Destruction of Information Data Template. (23) All decisions relating to the destruction of information must be approved and overseen by RMIT employees with the appropriate delegations, as defined in the Public Records Act 1973 and outlined below. (24) The Chief Data and Analytics Officer oversees information governance at RMIT University, which includes the destruction of data and information. (25) Any staff member who has custody and responsibility over certain bodies of information at RMIT can propose information for destruction and is responsible for: (26) Information Trustees (as defined in the Information Governance Policy) are accountable for reviewing and approving information destruction. For the purposes of this procedure:Destruction of Information Procedure
Section 1 - Context
Section 2 - Authority
Section 3 - Scope
Section 4 - Procedure
Requirements for the Destruction of Information
Legal Requirements
Business Requirements
Authorisation
Documentation
Timeliness
Security and Irreversibility
Destruction of records under Normal Administrative Practice (NAP)
Destruction of records under a Retention and Disposal Authority (RDA)
Responsibilities
Top of PageSection 5 - Definitions
Record
Disposal
1. the retention, destruction or deletion of records in or from recordkeeping systems
2. the migration or transmission of records between recordkeeping systems
3. the transfer of ownership or the transfer of custody of records (for example, to PROV)
The lawful disposal of records is an essential and critical component of any records management program.
Destruction
The process of eliminating or deleting records, beyond any possible reconstruction.