HESA Student Record 2013/14 - Expected length of study
HESA Student Record 2013/14
Fields required from institutions in Scotland
Expected length of study
return to field list
This field is used to indicate the normal elapsed time in the units indicated by Instance.UNITLGTH from the commencement of study, (the first learning/teaching week) to completion of the instance. This will normally include time for examinations. It does not purport to indicate the amount of study time, learning time or contact time.
|Applicable to||England Northern Ireland Scotland Wales|
All instances where Instance.REDUCEDI = 00, 01 or 09
This should be the length applicable to the instance as a whole and includes holiday time.
Where there are both part-time and full-time students following a programme of study, the expected length of study should be the normal length applicable for the mode of study of the student.
Cases where there is not a defined normal length for the programme of study, or where the programme of study is self-paced with an indefinite length, should have an empty element returned with the ReasonForNull attribute set to 9 (not applicable), i.e:
Validation will ensure that if this field is an empty string then Instance.UNITLGTH must be coded 9.
For postgraduate research students, any extra writing-up period must be ignored. For example, a full-time PhD would typically be coded 3 years.
It is not expected that the length of study be adjusted for individual students. However, where there are different options that students can take, for example, foundation years and sandwich placements, it is expected that the length reflects the options taken.
Where a student elects to take an integrated foundation year this should be reflected in the length of study. For example, where a student undertakes an integrated foundation year it is normally expected that the length be recorded as one year longer than if the student had just taken a stand-alone degree. Integrated foundation years are returned with Instance.YEARPRG = 0. It is important that the Instance.SPLENGTH and Instance.YEARPRG are coded correctly to ensure that the student is included in the NSS population at the correct time. For example, a student studies Science with an integrated foundation year. The duration of the course is 4 years in total.
The NSS population algorithm takes account of the foundation year through the YEARADJ calculation and the student will be surveyed in their final year of study. Further guidance on the NSS population specification can be found in 'Understanding the NSS reports'.
Where the option of a sandwich course is available but it is not taken up by a student then Instance.SPLENGTH should be revised at the point where the student makes a decision not to take-up the sandwich option, normally by the end of their second year, to reflect the expected length excluding the sandwich year. For example students coded 4 in Instance.SPLENGTH and 1 in Instance.UNITLGTH in the first year should be recoded 3 in Instance.SPLENGTH at the end of the second year if they are not expected to take the sandwich option. This re-coding is required to ensure that the correct cohort of student is identified in the National Student Survey (NSS) target list.
The length of study for courses that include an intercalation should reflect the length of the individual course aim in each year rather than the length of the instance in total. For example, a student enrols on a 5 year Masters in Medicine course. In the third year they intercalate to the third year of a Bachelor in Biotechnology before returning to complete the remaining years of the Masters programme.
In the Student record they would be returned as follows:
* The coding of Instance.SPLENGTH in the intercalating year will depend on how the institution treats intercalated years. If they are viewed as one year courses the expected length would be one year but if they are considered direct entrants to the third year of a three year course then the expected length would be recorded as three years.
The length of this field is 2 characters and the move to XML enables data to be returned with or without leading zeros, e.g. 03 or 3.
An instance lasting for two and a half years would be coded 30 months.
Quality rules relating to this field are displayed here.
To monitor the expected length of programmesand to determine whether a non-standard academic year student is counted or not in a given year.Used to determine the National Student Survey target list, price groups for students, funding calculations, and to monitor changing course lengths in the sector.
Data type: PositiveIntegerWithNullStructure2
|Change management notes||Notes section revised to improve the guidance given for this field.|
Contact Liaison by email or on +44 (0)1242 388 531.