Skip to main content

Student 2019/20 - Module status

Back to C19051

Student 2019/20

Fields required from institutions in All fields

Module status

return to field list

valid entries
Short nameMODSTAT

This field records detail of whether modules span HESA reporting years.

Applicable toEngland Northern Ireland Scotland Wales

All student on module records

Valid entries and labels
1Continuing from previous reporting year
2Contained within reporting year
3Continuing into next reporting year
4Taken in a previous reporting year (outcome only)
5Not coded
6Continuing from previous reporting year and into next reporting year

For providers in England, Wales and Northern Ireland where Instance.ENDDATE is in the previous reporting year and all modules for the instance are returned with MODSTAT 4 ‘Taken in a previous reporting year (outcome only)’, Instance.MODE should not be updated. For providers in Scotland, the appropriate dormant code should be returned in Instance.MODE.

Code 5 'Not coded' is an acceptable default code for use in this field unless otherwise indicated by the provider's funding council. Providers in Wales must not use code 5. Providers in England are encouraged to complete module information on the Student Record, to enable Office for Students to take this information into account in the future distribution of funding.

Code 6 should normally only be used where students have modules which genuinely span 3 reporting years. This is likely to be relatively rare, and will most likely be relevant to Postgraduate research students where a single module is being used to represent a programme of study.

For Welsh HEPs, the status of an APEL module (coded as StudentOnModule.APEL = 1, 2) can either be as for the same module not taken through APEL if the assessment is taken at the same time as other enrolments on that module, or, if the assessment takes place in a particular period it can reflect whether that period of time is contained within a reporting year or spans reporting years, as appropriate.

Quality rules
Quality rules to follow
Reason required Collection of this data will allow more accurate allocation of modules to reporting years for monitoring of completion and achievement, and of funding. Used in the calculation of module completion rates.
Part of
Field length1
Minimum occurrences1
Maximum occurrences1
Schema components
Element: MODSTAT
Related fields
Date modified2020-07-27
Change management notesAdditional guidance added to provide clarification when modules for the instance are returned with MODSTAT 4.

Contact Liaison by email or on 01242 211144.