The University's Program Development and Approval process applies to the development of new academic programs, and to major revisions or deletions of existing programs.
A revised program approval process was approved by the Academic Board at Meeting 1/18.
Program development and approval processes ensure academic programs meet quality assurance.
For advice on entry requirements, refer to the program structure and entry requirements.
Further information regarding the APEAC process is available on our FAQs page.
When planning proposals, proponents must allow for:
1. Prior to developing a Concept Proposal
Prior to developing a Concept Proposal for a new program in a new disciplines it should be discussed at the DVCA Faculty Group meeting (DVCA(A)FG). Contact Stephanie Rogers. Faculties will be notified of the outcome following the DVC(A)FG consideration.
2. All Concept Proposals
3. PPC delegate reviews proposal
4. Strategic proposals
Strategic proposals will be scheduled for discussion at the PPC meeting and if approved for development will be recommended for further Commercial Assessment/Development Business Case or the regular 90 day process to develop full APEAC documentation. (see point 5. Operational proposals for an overview of the 90 day process)
5. Operational proposals
Operational proposals commence the regular 90 day process:
For new programs and major revisions the regular 90 day process consists of a Faculty Working Group that develops the Program Proposal Plan.
The group will normally include:
- the Deputy Dean Learning and Teaching as convenor,
- the program proponent(s),
- a Learning & Quality Support Officer allocated to the program and,
- in the case of multi/cross disciplinary programs, representatives from other faculties
- faculty office staff relevant to curriculum development are also included
- other internal and external stakeholders will also be consulted during the development of the program plan.
The first meeting of the working group must occur no later than one week following the advice from the PPC meeting. The faculty will arrange meetings of the working group.
The purpose of these meetings is to ensure that the program plan is developed with academic and pedagogical rigour and that it aligns with all relevant internal and external frameworks (e.g. University policies, AQF, ESOS, HESF, accreditation requirements).
Learning & Quality Support will provide advice on the relevant stakeholders to be consulted to ensure that the program plan is sufficiently formed to facilitate the program’s implementation (eg CRICOS registration, configuration within University student and learning systems, etc).
For changes to entry requirements, a memo providing all required information (e.g., rationale, current entry requirements, proposed entry requirements, effective date, impact on current and future students, impact on pathway programs) should be provided.
6. The Program proposal plan
At the completion of the working group’s deliberations, the Program Proposal Plan is endorsed by the DDLT and the Executive Dean. It is then submitted to the APEAC Executive Officer (as per APEAC submission deadlines) for consideration at the next scheduled APEAC meeting.
APEAC will consider the recommendations based on the program plan’s merits and decide whether a recommendation for approval is to be made to the Academic Board.
APEAC submits a report of its recommendations to the Academic Board on new, revised and deleted programs 1.5 weeks prior to the Academic Board meeting.
7. If APEAC endorse the Program Proposal Plan
If APEAC endorse the Program Proposal Plan they recommend:
- new programs, major revisions and deletion for approval to Academic Board (AB)
- entry requirements for approval to the DVC(A). Once approved by the DVC(A), entry requirements are then noted only by AB.
APEAC recommendation to AB is noted by PPC.
New programs, major revisions and deletions endorsed by AB are recommended for approval by the Vice-Chancellor.
8. Notification of outcome
Please contact the APEAC Executive Officer if additional information is required on the Program Development and Approval process.