Welcome to the University Policy Library.
If you are unable to find what you are looking for please use the 'search' function below.
Delegations of Authority Policy is the key document for who is responsible to exercise a delegation – Note: Policies and procedure documents may not reflect the current delegations. Please refer to the Delegations of Authority Policy to identify who the delegate is.

Either type in a key word(s) in the search bar (e.g. scholarship) or select ‘Exact Search’ to search for a specific phrase (e.g. Commonwealth Supported Places)
Policy Framework Procedure
1. Purpose:
This procedure supports the Policy Framework Policy by stating requirements for developing and reviewing Policies and Procedures, implementing their requirements and monitoring their Effectiveness. Some points also apply to Guidelines and Local Instructions, and specify this.
2. Scope:
This procedure has the same scope as the Policy Framework Policy.
3. Procedure:
  1. Types of policy framework texts and their relationship with one another
    1. The Policy Framework Policy:
      1. defines the types of text in the policy framework (Policy, Procedure, Guideline and Local Instruction) and the sort of content they will contain, and
      2. states the hierarchy of texts that can state requirements, and what must be done if there is inconsistency between a text lower in the hierarchy and a higher text.
  2. Interpretation of texts
    1. Where a Policy, Procedure or Local Instruction uses the verbs ‘will’, ‘must’, ‘cannot’, ‘must not’ or the phrase ‘only [specified position or committee] can’, it states a requirement.
    2. Where a Policy, Procedure or Local Instruction uses the words ‘include’ or ‘including’, or the phrases ‘for example’ or ‘such as’, the inclusions or examples are not exhaustive.
    3. Where a Policy, Procedure or Local Instruction uses the singular, it also means the plural, and vice versa.
  3. Effect of policy requirements
    1. The Charter of Conduct and Values includes compliance with Rules, Policies, Procedures and Local Instructions as a conduct expectation for staff. Failure to comply may be a performance issue or, in cases of serious non-compliance, may lead to disciplinary action under the University's Enterprise Agreement.
    2. Students accept that they are subject to the University’s Rules, Policies, Procedures and Local Instructions as a condition of enrolment. The University of Canberra (Student Conduct) Rules 2017 state that non-compliance with Rules, Policies, and Procedures is a type of non-academic misconduct, which may be subject to action under those rules.
  4. Approval of policy framework texts
    1. The Delegations of Authority Schedule under the Delegations of Authority Policy states which committees or officers of the University may approve, for each category of activity (governance, academic or management):
      1. Rules, Policies and Procedures, and substantive changes to these
      2. administrative changes to Rules, Policies and Procedures, and
      3. definitions of terms that apply to all texts in the University’s Policy Suite.
    2. The Policy Sponsor of a Policy may approve a Guideline that supports the Policy, or changes to such a Guideline.
    3. The executive dean of a faculty or head of a division may approve a Local Instruction.
  5. Roles in relation to Policies
    1. For each Policy, staff (and in some cases students) will be nominated to perform the following roles:
      1. the Policy Sponsor, who will be a member of the Vice-Chancellor’s executive or the Chief People Officer
      2. the Policy Custodian, who will be nominated by the Policy Sponsor: typically this will be the chief officer, director, deputy director, associate director or pro vice-chancellor of the central division with the greatest responsibility for the area of activity covered by the Policy
      3. the Procedure Custodian, who will normally be the same as the Policy Custodian; however, a Procedure for one of the activities covered by a Policy may need a different custodian from the central division with the greatest knowledge of that activity
      4. Core Stakeholders, one of whom will be nominated by the executive dean of each stakeholder faculty and the head of each stakeholder division.
      5. The roles and responsibilities section below states the responsibilities of these roles.
    2. A Policy Custodian may delegate leadership of consultation activities, benchmarking research and drafting of the Policy, its supporting Procedures and (if any) Guidelines to a staff member or consultant (a Policy Developer).
    3. Policies on some areas of activity may have additional specialised Core Stakeholders, as follows:
      1. The Pro Vice-Chancellor, Indigenous will nominate one or more Core Stakeholders for Policies for which they consider development and review need to be informed by knowledge of the needs of Australian First Nations staff and students.
      2. The Chief People Officer will nominate a member of the Equity and Diversity team as a Core Stakeholder for Policies for which they consider development and review need to be informed by expertise in inclusive practices. This Core Stakeholder may involve, as subject matter experts in consultation, groups who have expertise in aspects of inclusive practice.
      3. For student-facing  Policies, the Student Representative Council may be invited to nominate a Core Stakeholder.
      4. For Policies with academic quality aspects, Academic Board may be invited to nominate a Core Stakeholder.
      5. For staff-facing Policies, the staff union may be invited to nominate a Core Stakeholder.
  6. Policy development and review process
    1. Development or review of a Policy will include development or review of its supporting Procedures and Guidelines, if any.
    2. Development or review of a Policy will include the following activities:
      1. where a new Policy is proposed, consultation between the proposed Policy Custodian and the Office of the General Counsel and University Secretary to consider whether a new Policy is essential, or (preferably) the requirements can be added to an existing Policy/Procedure and/or as a new Procedure
      2. initial research, including benchmarking research to identify leading practice in similar Policies in the university sector (it may also include review of professional literature)
      3. consultation with Core Stakeholders to identify issues and consider how to resolve them, and plan implementation of proposed changes, before drafting begins (further benchmarking research may be needed during consultation to inform the choice of solution to an issue)
      4. development of an implementation and communication plan listing the tasks that will be needed to ensure users of the Policy will be aware of changes to requirements, will know how to follow the new requirements and will have the resources and systems to do so. (The implementation plan will allocate each task to a manager responsible for carrying it out, and state the expected time frame for the task. Where the implementation plan allocates tasks to a manager who is not in a stakeholder faculty or unit, the Policy Custodian will consult that manager about whether the task and the time frame for it are feasible.)
      5. posting of drafts for comment by members of the University community, and
      6. review of drafts by the Office of the General Counsel and University Secretary before they are submitted for approval, to ensure the drafts are in plain English and use inclusive language.
    3. The Policy Custodian will:
      1. keep a record of issues raised during consultation and how these were handled
      2. keep a record of comments by members of the University community when the drafts were posted for comment, and responses to the comments
      3. provide these records to the Office of the General Counsel and University Secretary as a precondition for the Policy being submitted for approval, and
      4. circulate these records to, as relevant, Core Stakeholders or those who commented on the drafts, so they can see how their issues or comments were handled.
  7. Requirements specific to review
    1. A Policy will be reviewed within five years of the Policy’s original approval or its approval following its previous review.
    2. The General Counsel and University Secretary will maintain a schedule for reviews of the University’s Policies, and will remind each Policy Custodian of any review they are due to complete, one year before the scheduled review completion date.
    3. In addition to the initial steps in clauses 3.6.2.2 and 3.6.2.3 above, review of a Policy will consider:
      1. the log of issues raised in relation to the Policy and its supporting Procedures since their original approval or previous review
      2. the record of monitoring of the Effectiveness of the Policy and its Procedures, and any changes to supporting Procedures and (if any) Guidelines since the last review, and
      3. risks in relation to the activity governed by the Policy, the level of the risks and whether they are well enough mitigated by the  Procedure requirements.
    4. Where the Policy Custodian and Core Stakeholders agree, following consultation, research, benchmarking and risk analysis, that no changes to the Policy and its supporting Procedures and Guidelines (if any) are needed at this time, the Policy Sponsor can submit a recommendation to the approving authority that the Policy be regarded as reviewed and re-approved without changes to requirements. In this case
      1. the remaining steps of the review process (implementation planning, redrafting, etc.) will not be needed, and
      2. if the approving authority accepts the recommendation, the Policy can be regarded as reviewed.
    5. A Policy or a Procedure may be changed at any time to resolve issues identified by a post-implementation review or by ongoing Effectiveness monitoring, or changes to legislative requirements. Such changes
      1. must involve a workshop to consult Core Stakeholders of the Policy on the proposed changes
      2. must involve posting of the changes for comment from the University community
      3. do not constitute review of the relevant Policy, and do not change the date by which the Policy must be reviewed.
    6. Where, however, there is exceptional urgency to make changes to a Policy or Procedure, the chair of the Legislation Committee of Council may waive some or all of the requirements in clause 3.7.5, provided that:
      1. The exception and the reasons for it are communicated to the Core Stakeholders, and are reported to the next meeting of the Legislation Committee.
      2. As far as possible, consultation with Core Stakeholders on the proposed changes and how to implement them takes place before they are submitted for approval.
      3. Where the time-frame does not permit consultation with Core Stakeholders on the proposed changes and how to implement them before they are approved, the consultation takes place as soon as is practicable.
    7. A review of a Policy is complete when either:
      1. the new versions of the Policy, their supporting Procedures and (if any) Guidelines have been approved by the relevant approval authorities, or
      2. the relevant approval authority has accepted the report of the Policy Sponsor that the Policy has been reviewed by the process required in this procedure and no changes are needed.
    8. Where the review of a Policy is not complete by the scheduled review date, the Policy Sponsor or the General Counsel and University Secretary will ask the approval authority whether:
      1. it is willing to extend the deadline for the review, or
      2. the Policy should be removed from the website or Policy Library until it has been reviewed.
  8. Drafting texts
    1. Policy developers will draft Policies, Procedures and Guidelines in accordance with the Policy Writing Guideline.
    2. Policies will as far as possible state measurable objectives, to facilitate monitoring of their Effectiveness.
    3. The Office of the General Counsel and University Secretary will review draft Policies, Procedures and Guidelines before they are submitted for approval, and may edit them for plain English in collaboration with the Policy Custodian.
  9. Consequential changes
    1. Development of a Policy or Procedure, or changes to such a text, may require a change to another related text (a consequential change).
    2. Where a consequential change is needed, the Policy Custodian will identify and draft the consequential change as part of the approval submission, then either:
      1. if the approver of the Policy or Procedure has authority to approve the consequential change, ask them to approve it at the same time as they approve the Policy or Procedure, or
      2. if the approver of the Policy or Procedure does not have authority to approve the consequential change, ask them to endorse it at the same time as they approve the Policy or Procedure, and forward the consequential change to the appropriate approver, for approval.
  10. Publishing texts
    1. Only the Office of the General Counsel and University Secretary may publish Statutes, Rules, Policies, Procedures, Guidelines or changes to these.
    2. New or reviewed Policies, Procedures and Guidelines will be published in the University’s web policy repository, and the Office of the General Counsel and University Secretary will announce their publication to the University community.
    3. Local Instructions will be published on a web page of Local Instructions maintained by the faculty or division to which the instructions apply. The web page must be accessible to all staff, and to students if the Local Instructions apply to students.
    4. Rules, Policies, Procedures and Local Instructions take effect when they are published, unless the publication states a later take-effect date for some or all of the text’s provisions.
  11. Implementation
    1. The Policy Custodian will coordinate implementation of changes to requirements and processes arising from development or review of a Policy and its Procedures, in collaboration with Core Stakeholders and (where relevant) Procedure Custodians.
    2. Core Stakeholders will coordinate implementation in their faculty or division, and will inform the Policy Custodian of whether implementation is proceeding smoothly and of any implementation issues that arise.
    3. Where the implementation and communication plan for a new or reviewed Policy allocates tasks to other managers, these managers will carry them out.
  12. Administrative changes
    1. The Delegations of Authority Schedule under the Delegations of Authority Policy authorises the University Secretary to approve an administrative change to a Policy, Procedure or Guideline.
    2. An administrative change is a change that does not change the substance of the text, such as:
      1. correcting a stylistic error such as incorrect spelling or punctuation, an obviously omitted word, an obviously redundant word or an obviously mistaken order of words, or
      2. updating a position’s title, the title of an organisational unit or the name of a system, form or template.
  13. Post-implementation review
    1. Where a new Policy or Procedure, or a review of a Policy and its Procedures, introduces changes to requirements for staff or students, the Policy Custodian will within one year from the date the new requirements took effect
      1. hold a post-implementation review meeting with the Core Stakeholders of the Policy, and
      2. provide a report to the authority that approved the Policy, on whether the post-implementation review meeting considered the implementation successful or identified issues with the Policy and, if so, how these are to be resolved.
  14. Effectiveness monitoring
    1. The Policy Custodian of a Policy and its Core Stakeholders will collaborate to monitor the Effectiveness of the Policy and its Procedures on an ongoing basis. This monitoring will involve, at a minimum:
      1. Core Stakeholders raising issues with Effectiveness of the Policy and its Procedures with the Policy Custodian as the issues arise
      2. the Policy Custodian maintaining a log of issues with the Policy and its Procedures that are raised by Core Stakeholders, users of the Policy or identified in other ways (such as through complaints, appeals or analysis of data), and
      3. occasional meetings of the Policy Custodian and Core Stakeholders to consider whether the Policy is achieving its objectives, the issues log and whether changes to the Policy or its Procedures are needed.
4. Roles and Responsibilities:
Who Responsibilities
Deputy University Secretary
  • Procedure Custodian of this procedure.
  • Contact with whom to raise issues and seek advice on this procedure.
Core Stakeholders
  • In development/review of Policies, lead consultation and implementation in their faculty or division.
  • Involve subject matter experts in their faculty or division in consultation and implementation planning as needed.
  • Keep their executive dean or head of division informed of progress with consultation and implementation.
  • Monitor Effectiveness of the Policy and its supporting Procedures, raising any issues with the Policy Custodian.
General Counsel and University Secretary
  • Coordinate Policy development/review activities in the University.
  • Approve administrative changes to Policies, Procedures and Guidelines.
Office of the General Counsel and University Secretary
  • Advise Policy Sponsors and Policy Custodians on whether a suggested new Policy is needed or whether new requirements can be added to the Policy Suite as changes to existing texts and/or as a new Procedure.
  • Publish Rules, Policies, Procedures and Guidelines on the website or in the Policy Library.
  • Convene the University’s community of Policy practice.
  • Support Policy Custodians and Policy Developers to draft texts concisely in plain English and in inclusive language; where necessary, edit drafts in collaboration with Policy Custodians.
  • Collaborate with the Pro Vice-Chancellor, Indigenous to ensure that the policy framework meets the needs of Australian First Nations staff and students and supports their cultural safety.
Policy Custodians
  • Lead development/review of the Policy and its supporting Procedures and (if any) Guidelines, in collaboration with Core Stakeholders.
  • Monitor Effectiveness of the Policy and its supporting Procedures and (if any) Guidelines, in collaboration with Core Stakeholders.
  • Maintain a log of issues noticed or raised with the Policy and its supporting Procedures and (if any) Guidelines.
  • Initiate changes to Procedures as needed to resolve issues.
  • Participate in the University’s community of Policy practice.
  • As needed, nominate a Policy Developer(s) to carry out these responsibilities on their behalf, and support the Policy Developer(s) in this work.
Policy Developers
  • Carry out responsibilities of the Policy Custodian (see above), on behalf of the Policy Custodian.
  • Participate in the University’s community of Policy practice.
Policy Sponsors
  • Have overall responsibility for the Effectiveness of the Policies they sponsor.
  • Submit new/reviewed Policies and Procedures to approval authorities for approval.
  • Nominate and support the Policy Custodian.
Procedure Custodians
  • Lead development/review of the Procedure and its supporting Guidelines (if any), in collaboration with the Policy Custodian and Core Stakeholders.
  • Monitor Effectiveness of the Procedure and its supporting Guidelines (if any) in collaboration with Core Stakeholders.
  • Participate in the University’s community of Policy practice.
Pro Vice-Chancellor (Indigenous)
  • Identify which Policies need one or more Australian First Nations Core Stakeholders, to advise how they can meet the needs of Australian First Nations staff and students and support their cultural safety.
  • Collaborate with the Office of the General Counsel and University Secretary to ensure that the Policy Suite as a whole meets the needs of Australian First Nations staff and students and supports their cultural safety.
5. Implementation and Reporting:
  1. The General Counsel and University Secretary will report annually to
    1. the Legislation Committee of Council on progress with the University’s schedule of Policy review projects, and
    2. Academic Board on progress with the schedule of academic Policy review projects
6. Governing Policy and Legislation:
  1. This procedure supports the Policy Framework Policy.
  2. Other Policy and legislation related to this procedure are:
    1. the University of Canberra Act 1989 (ACT), especially Part 4
    2. the Council Governance Charter
    3. the Charter of Conduct and Values
    4. the Delegations of Authority Schedule under the Delegations of Authority Policy (authorities to approve Policies, Procedures and Guidelines)
    5. the University of Canberra (Student Conduct) Statute 2015, and
    6. the University of Canberra (Student Conduct) Rules 2017.
7. Supporting Information:
The Policy Writing Guideline supports this procedure.
8. Definitions:
Terms Definitions
Administrative Change As defined in clause 3.12.2
Core Stakeholder As defined in clauses 3.5.1.4 and 3.5.3
Policy Custodian As defined in clause 3.5.1.2
Policy Developer As defined in clause 3.5.2
Policy Library The Unversity's online repository of Policies, Procedures and Guidelines.
Procedure Custodian As defined in clause 3.5.1.3.
Policy Sponsor As defined in clause 3.5.1.1.
University  The University of Canberra (ABN 81 633 873 422).