reference document for document for Prospective like for it to be more prospective and current current students. Possibly and current students programme centric. students in mind (i.e. push a different document for (Confirmed that it is table on front page to end these latter two definitely a formal of document with stakeholders? requirement of QAA and marketing blurb upfront)? sections are However, difficult to get prescriptive). DoS to write this. Any other suggestions? Programmes should Programme The University needs to Programme supply unit outlines in one Specification template have a content Specifications are not document to show (and the majority of management system. useful documents students what the templates across the programme might look Code of Practice) are Version control is an like (with a caveat to say designed and badly issue. that this may change) formatted, making the time spent filling them HSS tend to deal with in frustrating (i.e. Prog and Prog Annual Quality report, Descriptions separately QA4 form 1 etc). but put them in one document for publishing The University should on the web. The have a content programme description management system for should ideally be linked to this type of information. unit catalogue as this is the most up-to-date Do we need to have a information student support section? QAA says Could LTEO provide What do sessions for ‘normally’. peers do? Cardiff- Yes, administrators around Exeter Yes, Bristol - No Easter on the potential – changes to QA44, Handbooks and Programme Specs?
reference document for current students. Possibly a different document for these latter two stakeholders? document for Prospective and current students like for it to be more programme centric. (Confirmed that it is definitely a formal requirement of QAA and sections are prescriptive). prospective and current students in mind (i.e. push table on front page to end of document with marketing blurb upfront)? However, difficult to get DoS to write this. Any other suggestions? Programmes should supply unit outlines in one document to show students what the programme might look like (with a caveat to say that this may change) Programme Specification template (and the majority of templates across the Code of Practice) are designed and badly formatted, making the time spent filling them in frustrating (i.e. Annual Quality report, QA4 form 1 etc). The University should have a content management system for this type of information. Do we need to have a student support section? QAA says ‘normally’. What do peers do? Cardiff- Yes, Exeter – Yes, Bristol - No The University needs to have a content management system. Version control is an issue. HSS tend to deal with Prog and Prog Descriptions separately but put them in one document for publishing on the web. The programme description should ideally be linked to unit catalogue as this is the most up-to-date information Could LTEO provide sessions for administrators around Easter on the potential changes to QA44, Handbooks and Programme Specs? Programme Specifications are not useful documents
APPENDIX_2_-_Review_of_QA44_-_Report_for_PI_Sub-Committee_xMarch_2013x_FINAL.docx