Proposal forms Cross-functional flow chart

Program Development & Approval Overview

Every academic program will go through the program development and approval process – at the point of its introduction and subsequently if it is revised or deleted.

While all program developments require consideration and approval at the Faculty level, some developments also require consideration and approval by University committees, as described in the following table.

Type of Program Development	Consideration/Approval Required
Minor revisions to existing programs(*)	Faculty Proponents must submit proposals to their own Faculty and/or School for approval.
Addition of new programs Major revisions to existing programs(*)	University Following endorsement of proposal by Faculty and/or School, proponents must submit Concept Proposal to the Academic Program Advisory Group (APAG) and full proposal to the Program Approval Committee (PAC) who will recommend proposals to Academic Board.
Change of program name Deletion of existing programs	University Following endorsement of proposals by Faculty and/or School, proponents must submit full proposal to the PAC who will recommend proposals to Academic Board.

(*) To help determine whether a program development is a major or minor revision, please refer to the table of revision categories.

Note:  While Academic Board will consider recommendations from the PAC, it is the Vice-Chancellor and President who has the delegated authority to give final approval to all program developments, except minor revisions.

Program Development and Approval – Simplified Flowchart

A cross-functional flow chart outlines the process for development and approval of new programs and major revisions to existing programs.  This indicates the interaction between Faculty processes, central University processes and subsequent publication/system outcomes.