Type of instance year
return to field list
This field identifies which of the basic types academic year is applicable to the instance.
|Applicable to||England Northern Ireland Scotland Wales|
All instances where Instance.REDUCEDI = 00 or 01
|Base data type||TYPEYRCodeType|
To show the relationship between the instance academic year and the HESA reporting year, to support population definitions and to ensure single-counting.
A student completes a foundation degree in June 2008 and then undertakes a bridging course from July to September and then joins the final year of a degree which they complete in June 2009.
The HESA reporting year runs from the 1 August - 31 July.
Instance academic years that are contained within the HESA reporting year should be coded 1.
Instance academic years which overlap HESA reporting years should be sequentially coded 3, (4), 5 in consecutive HESA returns, or may be coded 2.
Postgraduate research students would usually be coded as being on non-standard years.
Institutions in Scotland and Wales can only use codes 1 or 2.
Code 3 implies commencing an instance without having done another year of the instance in the same HESA reporting period.
Code 5 implies finishing one instance academic year and not starting a further year of the instance in the same HESA reporting year.
Information is required at instance level. It is not expected that adjustments should be made for individual students whose pattern may be slightly different e.g. a student who starts a course late.
Where a student’s studies include, within the same instance, a foundation degree to degree bridging course this bridging course element will be shown by code 1 ‘Foundation degree to degree bridging course’ in Instance.BRIDGE and an increased FTE in Instance.STULOAD. Where the bridging course spans HESA reporting years the FTE should all be returned in the second HESA reporting year, this may differ from the method used for other non-standard instance academic years. Institutions should also indicate in Instance.BRIDGE that the student has studied a foundation degree to degree bridging course only in the year in which the FTE is increased. It may be that the inclusion of a foundation degree to degree bridging course means that the year of instance becomes non-standard ie. no longer contained within the HESA reporting year. However, where the year would otherwise have been recorded as a standard academic year the year should still be recorded as such in this field.
Large numbers of students have Instance.TYPEYR recorded incorrectly, or are changing from non-standard to standard academic years between HESA reporting periods. Institutions are reminded that any student on a full-year course will be on a non-standard academic year, and therefore it is expected that most masters and doctoral students will be returned with a Instance.TYPEYR other than 1. In general, students should not change between non-standard and standard academic years; the only exception being where the course includes a partial year that starts and completes within one HESA reporting period. An example of such a case would be a student on an 18 month masters programme starting in October, that would be recorded as Instance.TYPEYR=2 in the first HESA return and Instance.TYPEYR=1 in the second.
|Change management notes||New final paragraph added to clarify correct coding of this field|
Data type: TYPEYRCodeContentType
|Valid entries and labels|