Student 2021/22 - Reason for ending instance
Student 2021/22Fields required from institutions in All fieldsReason for ending instance | return to field list | valid entries |
Type | field |
Short name | RSNEND |
Description |
This field is used to indicate for what reason the student left the student instance detailed in this return. |
Applicable to | England Northern Ireland Scotland Wales |
Coverage | All instances where Instance.ENDDATE is completed and where Instance.REDUCEDI = 00, 01, 04 or 08 |
Valid entries and labels | |
Notes |
Providers should only complete this field where they are closing a student instance. Guidance on when a new student instance is required is given in Instance.NUMHUS. Typically where a student progresses from one course directly onto another at the same level (e.g. HND to Degree, MPhil to PhD) a new student instance is not required and hence this field would not be completed although the QualificationsAwarded fields may be. If a student gains a qualification after completing a course, but not the qualification they were aiming for, then they should be coded 01 'Successful completion of course'. Code 02 'Academic failure/left in bad standing/not permitted to progress' is considered to be different from simply dropping out, code 07, which may be more closely related to personal reasons. Code 02 is intended to be for a fail at any stage. It is the code to be used for those students who fail assessment at, for example, the end of the first or second year of a three-year course and therefore leave the course, as well as for those students who have unsuccessfully completed their qualification aim and do not meet the definition to be returned as code 01. Code 08 'Written off after lapse of time': it is at the providers discretion whether to write-off an inactive student after a period of time. Code 09 'Exclusion' is the breaking of provider rules, either behavioural or financial. Code 12 'Transferred out as part of collaborative supervision arrangements' should only be used where a student is on a doctoral research training programme and the provider is passing reporting responsibility on to another provider. Code 12 must be used in combination with Instance.COLTOPROV and Instance.COLTODATE. The first provider can close down the instance for a student and interim awards can be made where required. If the award is delayed then the provider can keep returning the student as dormant until it is confirmed. Note: this may mean the first provider will not supply an Instance.ENDDATE when passing responsibilities for reporting over to a second provider as Instance.ENDDATE should reflect when the award for postgraduate research students is approved. Instead the existence of Instance.COLTOPROV / Instance.COLTODATE / code 12 in Instance.RSNEND should be used to identify these situations. Instance.ENDDATE and Instance.COLTODATE would not need to be the same, though it is expected in a number of cases that they would be. Code 98 'Completion of course - result unknown' implies that there will be further returns for the student to report results and reason for leaving. When providers are returning the student to provide the result, they should use the following guidance. For providers in England, Wales & Northern Ireland, when returning a student with an Instance.ENDDATE in the previous reporting year, the Instance.MODE should reflect the status of the student at the end of the reporting year in which they completed their activity. Please see Instance.MODE for further information. For providers in Scotland, the appropriate dormant code should be returned in Instance.MODE. In onwards analysis Statutory Customers and HESA may group codes 03, 04, 06, 07, 08, 09, 10 and 11 into a single category of 'Other'. An entry in this field means that an entry in Instance.ENDDATE will also be expected, except where code 12 is used. |
Quality rules |
Quality rules to follow
|
Reason required | To monitor transfer/progression/completion. Used in analysis of destinations of students. |
Part of | |
Field length | 2 |
Minimum occurrences | 0 |
Maximum occurrences | 1 |
Schema components |
Element: RSNEND
Data type: RSNENDCodeContentType |
Related fields | |
Owner | HESA |
Version | 1.1 |
Date modified | 2022-02-09 |
Change management notes | Additional guidance added to provide clarification on the use of valid entry 02. |
Contact Liaison by email or on +44 (0)1242 388 531.