Bulletin Board - 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 receive 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, take a note of where you up to and return later to make a further submission.
-
DO NOT exit from the interface until you have completed all three stages of the submission process.
-
If you would like a copy of the comments you made via the Bulletin Board, please email policy@rmit.edu.au and specify which document you provided feedback on and a copy of your submission will be emailed to you.
(1) This Instruction provides details on how to develop or review policies at RMIT. (2) Authority for this document is established by the Policy Governance Policy. (3) This Instruction applies to all staff who are developing or reviewing (4) The steps for developing a new policy or reviewing an existing policy are almost identical. Where variations exist, they are described below. (5) Where procedures are developed separately, the development or review process should follow all the steps outlined below, except for those concerning creating a policy advisory group and consulting with the approval authority midway through the process. (6) It is at the discretion of the person developing or reviewing an instruction or guideline as to how much of the process below they would like to conduct. As the purpose of instructions and guidelines is to enable policy implementation, these lower-level documents are subject to the principles in the overarching policy and therefore informed by the research contributing to the policy’s development. (7) Where RMIT legislation (regulations or statute) exists in relation to a policy suite, it must be included in the scope of the cyclical review of a policy suite. (8) After a proposal for a new policy has been endorsed by the University Policy Manager, the project lead nominated in the proposal form can commence work on the policy development. (9) Central Policy reminds policy owners of their requirement to conduct a major policy review approximately 9-12 months prior to the ‘review by’ date published on the Policy Register. (10) Where a cyclical review is being undertaken for an existing policy, the project lead nominated by the policy owner should commence the review at least nine months prior to the ‘review by’ date published on the Policy Register. This allows time for extensive engagement and consultation, and for processing the revised documents through the relevant committees and approval authority. (11) It is recommended that project leads establish a small working party of subject matter experts from across the (12) The policy advisory group meets as often as is necessary to support the policy lead, and this will vary depending on the size or complexity of the policy suite. For a small policy suite, this may only be three or four times over the development period, for reasons including: (13) For planning purposes, project leads must notify Central Policy that they are commencing policy development or review. Central Policy may initiate a meeting with the project lead to provide advice on the development or review process, the resources and assistance available, and the expectations of approval authorities. (14) Policy owners and authors must provide direction to the project lead at the commencement of the development or review process and outline the issues they wish the policy to address. (15) Project leads must consider engaging with the Sustainability team and utilising the Sustainability and Equity Evaluation Tool. The tool provides insights into how the policy subject matter intersects with RMIT’s commitment to supporting the United Nations Sustainable Development Goals, the policy’s impact on Aboriginal and Torres Strait Islander staff, students and community, and gender equality. (16) After completing the Sustainability and Equity Evaluation, project leads must reach out to the Indigenous Education, Research and Engagement team to determine whether the policy suite requires input from Aboriginal and Torres Strait Islander staff, students or community. This must be done early in the process as policies that may impact on place and community will require time for Aboriginal and Torres Strait Islander staff to consult with Elders and community members. (17) Heads of each of the controlled entities must be contacted early in the process to determine if the new or revised policy will have significant implications for local operations. If so, a local subject matter expert should be sought for the policy advisory group. (18) Early guidance and ongoing engagement on new or revised academic and governance policies should be sought from the Education Regulation, Compliance Assurance team for insight into regulatory compliance requirements to be addressed in the policy. (19) Desktop research must be conducted for both policy development or review and findings reported to the approval authority with the policy submission. Desktop research includes: (20) After completing desktop research and developing ideas for the new or revised policy suite, project leads should engage with key stakeholders about the proposed changes to a policy suite, or proposed content for a new policy suite. Refer to the resource on Effectively Engaging with Policy Stakeholders on the staff Policy Hub for ideas and guidance on engagement and consultation. (21) All aspects of the desktop research and stakeholder engagement should be documented as the approval authority may seek evidence of this work. (22) Prior to drafting the policy suite, the policy owner must submit a brief report (the ‘midway check’) to either the Vice-Chancellor's Executive Meeting (for governance and operational policies) or Academic Board to: (23) This step does not apply to procedures or lower level documents developed as single documents separately from the development or review of a policy suite. (24) Drafting the policy suite is an iterative process that involves seeking feedback from the policy advisory group, policy author, policy owner, and others as required. Refer to the guidance notes for writing policy documents on the staff Policy Hub. (25) When the policy owner endorses the documents for official consultation, the policy documents are sent to Central Policy. Central Policy checks the documents for clarity, compliance with the Policy Governance Policy and Procedures, any overlap with other policies, and enters the final draft documents into the database underpinning the Policy Register. The documents may be returned to the project lead with questions or for amendment. (26) It is compulsory to conduct two rounds of consultation on the Policy Register Bulletin Board. (27) Changes to policy documents between the rounds of consultation must be sent to Central Policy to add to the versions in the policy database, including after the RMIT Group-wide round on the Bulletin Board. This is to enable Central Policy to provide the policy author with PDFs of the final versions of the policy documents to submit to the approval authority. (28) Refer to the Policy Governance Procedure for preparing a submission for policy suite approval, and to the relevant Secretariat for submission content and timeline advice.Policy Governance Instruction - Developing and Reviewing Policies
Section 1 - Purpose
Section 2 - Authority
Section 3 - Scope
Section 4 - Instruction
Commencing
Early engagement with stakeholders
Desktop research
Engaging midway with the approval authority
Quality and compliance checks
Formal consultation
Preparing documents for the approval authority