Published for 2024-25
2. Approval of New Taught Programmes | 2.3 Outline Approval |
2.1 Timelines for the Approval of Taught Programmes | 2.4 Final Approval |
2.2 Initial Programme Planning and Development |
2. Approval of New Taught Programmes
1. | New taught programmes are approved by the UCL Education Committee under powers delegated from the UCL Academic Board. The Education Committee is advised by the Programme and Module Approval Panels (PMAP), a sub-panel of Quality and Standards Committee. |
2. | Programme planning is the first phase with new proposals considered through the Student Numbers Planning process with the mandate for further development granted by Financial Performance and Planning Committee (FPPC). Programme development is the second phase and then submission for review and recommendation from PMAP for final programme approval is the third and final phase. |
3. | Faculties and Departments may adopt local practices in addition to those outlined below, such as the involvement of additional committees or the Vice-Dean(s) Education. However, PMAP will continue to require sign-off from the named individuals and groups listed in the Programme Proposal form. |
2.1 Timelines for the Approval of Taught Programmes
1. | For marketing of programmes to be given the best opportunity to attract the highest quality students, for programmes to be included in the prospectus, and for UCL to uphold its responsibilities with respect to consumer protection legislation, the following deadlines are essential: |
a) | For undergraduate programmes: Final Approval should be achieved not later than November of the calendar year two years prior to the intended start of a programme (22 months in advance of a September start). | |
b) | For postgraduate programmes: Final Approval should be achieved not later than the end of June in the year prior to the intended start of a programme (15 months in advance of a September start). |
2. | Where it has not been possible to meet the deadlines outlined above, final approval must be achieved not later than the end of September in the year prior to the intended start of a programme (12 months in advance of a September start). |
3. | While these are the very latest deadlines, programme initiators should be encouraged to begin work on programme development much earlier to give sufficient time for: effective competition/market appraisal (both within and outside of UCL); development and approval of the business case; obtaining Faculty approval. Programme initiators should aspire to the timelines outlined in Annex 7.1.1: Detailed timelines for Programme Approval and Amendment. |
4. | Prior to embarking on the process towards PMAP approval, the business case for new programme proposals including the additional student numbers must be considered as part of the Student Numbers Planning (SNP) process and approved by the Financial Performance and Planning Committee (FPPC). The FPPC meets regularly throughout the year. The specific date for FPPC consideration of a programme proposal will be agreed with the Strategy Delivery Account Managers in the Office for the Vice-President (Strategy). |
5. | Programme initiators should note that FPPC approval is required prior to the consideration of approval at a PMAP meeting. New programme proposals must be submitted no less than 10 working days in advance of a PMAP meeting. Submissions received later than 10 working days in advance of a meeting will be considered at a subsequent meeting of the Panel. A comprehensive list of the dates on which PMAP will meet in 2024-25, as well as the corresponding paper deadlines, can be found in Annex 7.1.2: PMAP 2024-25: Meeting Dates and Paper Deadlines. |
2.2 Initial Programme Planning and Development
1. | The intention to develop a new programme should be reflected in the relevant department’s strategic planning and should be captured in the Faculty’s student number planning. This ensures that any projected increases in student numbers can also be represented in the budget and funding for staffing and learning resources can be anticipated. |
2. | In addition, new programmes and their planned student numbers should be included in the student numbers planning submission as part of the annual Student Numbers Planning exercise. In year changes to student intake plans can be made using the Change Request process. |
3. | Programme initiators must consider how their programme contributes to the achievement of UCL’s strategic aims and objectives as detailed in the UCL Strategic Plan 2022-27. They should also consider how the programme will embed equality, diversity and inclusion. |
4. | A programme proposal is usually initiated and developed at department level, in close consultation with relevant members of staff in the Faculty (usually the Faculty Tutor). Programme initiators should consult with the following relevant parties or documents when developing their programme proposal: |
|
2.2.1 Programme Structure
1. | Information on the level, structure and components of a programme of study, as well as a list of the approved qualifications, and their threshold requirements, can be found in Chapter 7, Part A: Qualifications and Credit Framework. |
2. | Information on programme length and modes of attendance can be found in Chapter 3, Registration Framework for Taught programmes. |
3. | Assessment, progression, award and classification should follow the regulations set out in Chapter 4, Assessment Framework for Taught Programmes. |
4. | Where a programme is made up of multiple routes or pathways leading to different named qualifications, the programme diet and statements of aims and learning outcomes must be clear for each. |
5. | Interim qualifications are available for all UCL programmes. It is possible to offer these interim qualifications as programmes of study, either connected to a larger award or as standalone programmes. In such cases, a programme summary must be maintained for each programme. |
2.2.2 Material Programme Information
1. | During the development stage, programme initiators should be mindful of the need to provide clear, accessible and accurate information to prospective and current students on the purpose, structure and aims of their programme. |
2. | Additionally, UCL is obliged, under the QAA Quality Code, the OfS Conditions of Registration and under consumer protection legislation, to provide clear and accurate information to prospective students and offer holders. Therefore, programme initiators must identify the following when designing a new programme: |
a) | the level of the programme within the Framework for Higher Education Qualifications; | |
b) | the intended qualification and any interim qualifications; | |
c) | the programme title; | |
d) | the overall credit value; | |
e) | the programme’s aims, objectives and learning outcomes (with reference to relevant subject benchmark statements); | |
f) | the entry requirements (both academic and non-academic); | |
g) | the programme’s structure, including the number and type of contact hours, any compulsory modules, an indication of likely optional modules and the expected workload; | |
h) | the overall methods of assessment (both formative and summative); | |
i) | the duration of the programme and its modes of study; | |
j) | the location(s) of study, including where relevant, any distance learning; | |
k) | whether the programme could be accredited by a PSRB; | |
l) | whether the programme will be offered in partnership with others; | |
m) | whether the programme will have a period in placement or study abroad; | |
n) | an initial assessment of the tuition fees to be charged (in consultation with the Dean or nominee); | |
o) | any additional costs to students (such as field trips or material costs); | |
p) | any barriers to accessibility and how these could be mitigated. |
3. | The required documents for programme proposals provide space for the programme initiator to record this information. |
2.2.3 Financial Performance and Planning Committee (FPPC) approval for development
1. | As detailed in 2.2 Initial Programme Planning and Development Section 3, all programme proposals require approval by the Faculty and the Financial Performance and Planning Committee (FPPC) prior to development and Approval by the Department, the Faculty and PMAP and prior to completion of the detailed programme proposal. Documents required by FPPC and as part of the Student Number Planning (SNP) process can be found on the Office for the Vice-President (Strategy) website and include: |
a) | The New Programme Impact Assessment, including consideration of potential programme overlap or duplication, the implications for the student experience and information on the likely impact on central UCL resources including teaching space, support other administrative costs. | |
b) | Evidence of market research, including the programme rationale, evidence of demand and competition, and graduate outcomes. | |
c) | The Financial business case, detailing the anticipated student numbers, the expected income and any additional staffing, learning resources or other additional costs that may be incurred by the Faculty. |
2. | Template documentations will be released annually and is available on the Office for the Vice-President (Strategy) website. |
3. | Programme proposals must complete the business case documents (as above), including market research prior to developing the programme. Programmes that cannot demonstrate full business case viability and marketability will not be approved for development. |
2.2.4 Programme Development with the UCL Institute of Higher Education, Development and Support (HEDS)
1. | Programme initiators for all taught programmes should contact the UCL Institute of Higher Education, Development and Support (HEDS) to discuss their programme proposal, in accordance with the timelines provided in Annex 7.1.1. |
2. | Initiators are strongly encouraged to attend a programme development workshop through UCL Institute of Higher Education, Development and Support (HEDS). This workshop, developed with input from Marketing and Communications and Careers, will support programme initiators in the preparation of programme approval documentation. |
3. | Programme initiators should not enrol on the workshop until the Business case and market research have been signed off. |
4. | Programme initiators can find further information at Annex 7.2.1 and should take account of the resources available which can be found at the Education Planning pages of the UCL Teaching and Learning portal. |
2.3 Outline Approval
1. | Programme approval is confirmed at Department and Faculty level prior to consideration at PMAP and requires sign off from the Head of Department; DEC Chair; Dean of Faculty and FEC Chair. In order to confirm approval, departmental and faculty reviewers must satisfy themselves that: |
a) | The proposal is included in and/or is in line with department and faculty level strategic operating plans, and student numbers plans; | |
b) | The business case is appropriate, is backed by reliable market research and has accounted for all associated costs; | |
c) | The proposed programme will not directly compete with other programmes of study operating in the Faculty or elsewhere in UCL; | |
d) | The programme initiator(s) have sought or are in the process of seeking advice and guidance from relevant professional services teams or academic colleagues; | |
e) | That the proposed curriculum is current, appropriate for the level of study and is in line with the relevant subject benchmark statements; | |
f) | The constituent modules are suitable for the programme, the assessment is appropriately balanced across the modules and any new modules have been reviewed by an external scrutineer; | |
g) | The proposed programme of study is in line with relevant strategies, in particular the UCL Strategic Plan 2022-27 and its sub-strategies; | |
h) | If the proposed programme constitutes additional growth in student numbers, there is sufficient space, staffing and resource to accommodate this and that comments from UCL Estates have been taken into account; | |
i) | Proposals to make use of modules from other programmes of study, departments or faculties have been discussed and agreed with the relevant Head(s) of Departments and Faculty Tutor(s); | |
j) | Programme proposers for taught programme proposals have discussed the proposal with the UCL Institute of Higher Education, Development and Support (HEDS) and, where advised, attended a workshop through the Institute of Higher Education, Development and Support (HEDS) on programme development. |
2. | In addition, departmental and faculty reviewers must not approve proposals until all paperwork has been correctly completed. This includes ensuring that: |
a) | All documents have been signed in the appropriate place by the named role holder or approved delegate. This is crucial for audit purposes; | |
b) | All document fields have been completed with the appropriate information, including where relevant, an indication that the field is not applicable; | |
c) | The documents contain no errors or typographical errors; | |
d) | All information is presented in a clear and accessible format. This is particularly important when describing the programme structure or the assessment format. |
3. | Once satisfied, departmental and faculty reviewers should provide feedback to the programme initiator on further developments that could be made to the proposal, in preparation for the submission of the programme proposal for consideration by PMAP. |
4. | Submission to PMAP for approval is contingent on the sign off and approval of the programme business case by FPPC. Programmes that do not get full business case viability and marketability approval will not be considered by PMAP. |
2.3.1 Information and Documentation Required
1. | Approval by PMAP will focus on academic and quality assurance aspects. A summary of the other minimum information and corresponding documentary evidence required for programme approval by PMAP, is provided below: For all programmes:
Where there is internal module sharing or shared teaching arrangements:
Where there is an Academic Partnership:
(For further information, refer to Chapter 8 of the 2024-25 UCL Academic Manual) Where there is a year abroad or in industry, or a placement:
(For further information, refer to Chapter 8 of the 2024-25 UCL Academic Manual) Where there is a Level 7 / Masters Apprenticeship programme / qualification:
Where there is a Professional, Statutory or Regulatory Body (PSRB) accreditation or approval of the programme:
|
2.3.2 PMAP Approval Process
1. | Once approved by the Faculty, programme proposals must be submitted to the PMAP Secretary by the Faculty Tutor. These proposals are circulated to members of the Education Committee and relevant professional services teams and are considered at the next PMAP meeting. |
2. | 2. PMAP formally considers the programme proposal at this stage and will either:
|
3. | Once granted, PMAPprogramme approval status is valid for 24 months. If the conditions of approval are not met within this 24 month period, a new programme proposal must be submitted to FPPC, the DEC, the FEC and PMAP. |
4. | Once conditional approval is determined at a PMAP meeting, programmes may be advertised on departmental websites in the following format: |
a) | Programme title and intended qualification; | |
b) | Aniticipated start date; | |
c) | A brief description of the programme content and structure omitting references to particular modules or credit values; | |
d) | The following disclaimer: Please note that this programme is still subject to final approval. As such, the content and structure of the programme is subject to change and may differ from the outline given here. As soon as the programme has been approved it will be advertised in its finalised form and applications will be taken on this basis. If you’d like to be notified when this programme has been approved and applications are open, please email [relevant departmental contact]. |
2.4 Final Approval
1. | Final approval is confirmed by Education Committee and requires sign off from the Head of Department; DEC Chair; Dean of Faculty; FEC Chair and PMAP. To confirm final approval, reviewers at Faculty level must satisfy themselves that the criteria required for approval are still met. In addition, PMAP must satisfy itself that: |
a) | The programme initiator(s) have consulted widely with colleagues from cognate departments to identify possibilities for module or resource sharing and that there is evidence of any agreements made; | |
b) | The programme initiator(s) have responded to the feedback provided by PMAP and made developments or amendments where appropriate; | |
c) | The proposed programme of study is in line with UCL’s regulations, particularly the Qualifications and Credit Framework, the Assessment Framework for Taught Programmes and the Registration Framework for Taught Programmes; | |
d) | The proposed programme of study is in line with relevant external benchmarks, such as the Framework for Higher Education Qualifications; | |
e) | That the material programme information (as required by Consumer Protection Legislation) is clear and easy to understand; | |
f | The programme initiator(s) have discussed the proposal with current or prospective students and acted on their feedback; | |
g) | The proposal has been reviewed by an appropriately qualified external scrutineer; | |
h) | Agreements are in place for any proposed external partnerships. |
2. | Once approved by PMAP, a programme will normally begin admitting students. As such, PMAP must assure itself that the programme will not pose a risk to standards, the student experience or UCL’s reputation. |
2.4.1 Information and Documentation Required
1. | A ‘Response to PMAP’ document will need to be completed and submitted with the final submission to PMAP, detailing how and where in the documentation previous issues raised by the Panel have been addressed. This document is issued to the initiator(s), by the Secretary to PMAP, once the programme proposal has been considered by PMAP. |
2. | A summary of the minimum information and corresponding documentary evidence, required for final programme approval is provided below: For all programmes:
Where there is internal module sharing or shared teaching arrangements:
Where there is an Academic Partnership:
Where there is a year abroad or in industry, or a placement:
(For further information, refer to Chapter 8 of the 2024-25 UCL Academic Manual) Where there is a Level 7 / Masters Apprenticeship programme / qualification:
Where there is a Professional, Statutory or Regulatory Body (PSRB) accreditation or approval of the programme:
|
2.4.2 Final Approval process
1. | Once approved, the relevant team in Education Services will finalise the set up of the programme in the student record system and confirm with the department, faculty and relevant professional services teams when this has been done. They will then carry out the relevant tasks in their respective areas. |
2. | Once the programme has been set up, it will usually open for applications at the earlierst opportunity. There may be occassions where this has to be delayed, for example, to await a signed memorandum of agreement. |
2.4.3 Probationary Review Following Final Approval
1. | New taught programmes will be reviewed for the first three years that the programme runs, as part of the Student Numbers Planning exercise. If the programme is not on course to meet targets after two admission cycles, the programme team should consider action that might need to be taken in respect of programme design or marketing. After three admission cycles, the Office of the Vice-President (Strategy) will review the programme against the business case to ensure that it is viable and will advise on next steps. |