Skip to main content

Student record 2013/14

Back to C13051

Check documentation guide

Version 1.1 Produced 2014-08-14

This is a guide to the C13051 check documentation. This documentation should be used in conjunction with the C13051 coding manual and the Check documentation definitions and notes document.

Contents: Introduction | What to do if you find issues with your check documentation | Checkdoc_1 | Checkdoc_2 | DLHE | REF2014 | Fees | Collaborative_Franchise | FE_Students | PI sheet | ITT_EnglishHEIs | CCANALYSIS | UCAS_Data_for_HESA | Query sheet | Exception Report | HIN

Introduction to check documentation Back to top

A successful TEST_COMMIT/COMMIT transaction will generate several reports containing management information that institutions will need to review to assess data quality. The check documentation is the most substantial of these reports. A template of the check documentation workbook for C13051 can be downloaded from C13051.

white_cd.gifCheck documentation takes the form of an Excel workbook containing a series of tables which present much of the returned data to enable institutions to ensure that their submission represents their institution as expected. In part, check documentation provides a preview of some of the onward uses of the data. Therefore, review of the check documentation should be undertaken by institutions to verify the submitted data.

CD_Compare.pngCheckdoc Compare facility. The data collection system will provide a second version of the check documentation for every RE-COMMIT/TEST_COMMIT processed by an institution. This version of the check documentation presents a colour shaded version of the Excel spreadsheet with variances being highlighted.

Within the check documentation is an 'Institutional_information' tab. The items held within this tab are provided for institutional purposes and highlight useful internal planning/data management areas. Alongside this, the tabs for Campus, PI, UCAS data for HESA and ITT English HEIs are designed solely for institutional checking. These sections of the check documentation are not analysed by HESA.

All other tabs within the Excel workbook are intended to be checked by both institutions and HESA. However, colleagues are reminded that primary responsibility for data quality rests with them. Colleagues within institutions are in an excellent position to recognise more detailed anomalies within their data, using local knowledge of the intricacies of their own institutions, and are strongly encouraged to closely scrutinise the check documentation reports. The check documentation is also used by HESA to conduct data analysis and quality assurance of a data submission. Queries raised on these items form the basis of any data quality queries fed back to institutions through the Minerva data quality database.

This guide details each of the items in turn, providing details of the populations and fields used in their creation along with guidance on interpreting the item and tips detailing common issues. Note that this guide is not exhaustive and institutions are advised to extensively review the check documentation for their own purposes.

DDFS.gifData Supply: This report available after a successful TEST_COMMIT/COMMIT provides back the submitted data in flat file and xml formats. This can then be used to analysis the submitted data locally and recreate the populations used by HESA in the check documentation. The derived fields are also included within the Data supply file. These fields are identifiable as those that begin with 'X'. Details of the derived fields used in the C13051 record can be downloaded from Derived field specifications.

Item priorities:

Each check documentation item covered in this guide has been allocated a priority based on the data concerned (including minimum data quality standards acceptable to HESA's Statutory Customers), the knock-on effects, and common issues. However, the assigned priorities should be treated with caution as these are general estimates. Depending on the submitted data the actual severities assigned to data quality queries raised in Minerva may differ for individual institutions. For example, Item 4 is classified as Minor, however, if the difference between ERASMUS numbers reported by the institution and the ERASMUS UK office are significant this would inevitably increase the severity of the query raised.These priorities will be denoted in Minerva through the following icons.

Priority Minerva icon
Critical minerva_red_critical.png
Major - high priority minerva-majorhigh-triangle.png
Major - low priority minerva-majorlow-triangle.png
Minor n/a

What to do if you find issues within your check documentationBack to top

Where anomalies are found you should record them on any relevant Minerva queries raised by HESA and set the queries to be fixed on resubmission. The institution should then contact [email protected] to request that the data is decommitted in order that the necessary amendments can be made and the data resubmitted.

Check_document_1 Back to top

Those items contained within Check_Document_1 are deemed to be critical by HESA. These items details the number of students and qualifiers at the institution in the reporting year. Any issues found within these tables should be treated as a priority.

Item 1 - Student instance numbers by mode, level and domicile

PRIORITY: CRITICAL

This item displays an institution's student numbers. Student numbers are used extensively, including in HESA's Statistical Release of Student Enrolments and Qualifications obtained, Students in Higher Education Institutions publication and in data enquiries handled by the HESA Information Services team.

POPULATION: Standard registration population (XPSR01) and population as as 1st December of the reporting year (XPDEC01)
FIELDS USED: EntryProfile.DOMICILE,EntryProfile.FEEELIG, EntryProfile.POSTCODE, Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, Instance.COMDATE
DERIVED FIELDS USED: XMODE01, XDOMGR01, XFYRS01, XFYEAR01, XLEV501

DESCRIPTION: This item details student instance numbers by mode, level and domicile. Figures are provided for both the current and previous reporting year to provide a comparison along with percentage and total number differences between 2012/13 and 2013/14.

NEW for 2013/14 is the introduction of the proportion difference table added for C13051. This will show year-on-year differences in proportion for domicile and level of study within mode. The final two columns show domicile and mode within the total population.

WHAT TO LOOK OUT FOR: Check that the numbers are as expected. All variations of greater than 10% and 50 students should be checked. Large differences in student instance numbers will impact on other items within the Check Documentation. All differences of this magnitude should be addressed and/or explained as necessary in Minerva.

Check for similiar spread of domicile codes compared to previous years. Significant shifts may indicate possible mis-coding of EntryProfile.DOMICILE as will previously used codes that are no longer valid.

TIPS:

  • Small student number changes can shift percentages significantly.
  • Correct coding of PGR students who have been reported as writing-up will affect student numbers in the PGR category as such students do not appear in the XPSR01 population.
  • Check for similar spread of domicile codes compared to previous year. Significant shifts may indicate possible miscoding of EntryProfile.DOMICILE.
  • Those QualificationAwarded.QUAL codes classified as ITT are H11, I11, I71, H71 and M71.

Item 2 - Qualifications awarded to students

PRIORITY: CRITICAL

This item displays an institution's qualifier number. Qualifier numbers are used extensively, including in HESA's Statistical Release of Student Enrolments and Qualifications obtained, Students in Higher Education Institutions publication and in data enquiries handled by the HESA Information Services team.

POPULATIONS: Qualifications obtained population (XPQUAL01)
FIELDS USED: QualificationsAwarded.QUAL, Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, Course.TTCID, Instance.ITTPHSC
DERIVED FIELDS USED: XQMODE01, XQLEV1003, XQOBTN01, XPQUAL01

DESCRIPTION: This item displays qualifications awarded by mode, level of study and qualifications obtained. Figures are provided for both the current and previous reporting year to provide a comparison. Year-on-year percentage and total number differences are also provided to assist analysis.

WHAT TO LOOK OUT FOR: Check that the qualifications the students are awarded (in rows) are, for the majority of students, those which they were aiming for (in columns). Increases/decreases in student numbers (displayed in Item1) could affect the numbers of qualifications awarded.

TIPS:

  • If the number of qualifications reported are lower than last year it may be due to qualifications not yet confirmed. This can be checked by looking at the Frequency Counts to see the number of instances have been returned with Instance.RSNEND completed as '98 Completion of course - result unknown'. Email Liaison if late awards are not yet available to indicate when they will be included within the return.
  • Cells in which we would not expect to see qualifications will be shaded.

NEW FOR 2013/14: Item 2 ITT - ITT qualifications awarded to students (2013/14 and 2012/13

PRIORITY: CRITICAL

POPULATIONS:
Qualifications obtained population (XPQUAL01)
FIELDS USED:
QualificationsAwarded.QUAL, Course.TTCID, Instance.ITTPHSC
DERIVED FIELDS USED:
XQLEV1003, XLEV501, XQOBTN01, XPQUAL01

DESCRIPTION: This item shows the number of students gaining QTS for BEd Primary and Secondary courses and Postgraduate Primary and Secondary courses. For more information about ITT qualifications.

WHAT TO LOOK OUT FOR: If the number of qualifications reported are lower than last year it may be due to qualifications not yet confirmed. This can be checked by looking at the Frequency Counts to see the number of instances have been returned with Instance.RSNEND completed as '98 Completion of course - result unknown'.

TIPS:

  • There is an Exception Warning that works in tandem with this check documentation item.
  • It is expected that QTS should be achieved by at least 80% of ITT leavers.

Item 2a - Qualifications obtained by students on HE course by level of qualification obtained and mode of study

PRIORITY: CRITICAL

POPULATIONS:
XPQUAL01 = 1
FIELDS USED:
Instance.MODE, QualificationsAwarded.QUAL
DERIVED FIELDS USED:
XQMODE01, XQLEV501, XQLEV1003

DESCRIPTION: This item displays qualifications obtained by mode and level of study. Figures are provided for both current and previous reporting years to provide comparison. Year-on-year percentage and total number differences are also provided to assist analysis.

WHAT TO LOOK OUT FOR: It is not expected that differences between years will be greater than 10% and/or 300 students. All differences of this magnitude should be addressed and/or explained as necessary. The Difference (numbers) columns are shaded where difference is greater than 300 and the Difference (%) columns where the difference is greater than 10%.

TIPS:

  • Compare figures with item 1 - increases or decreases in overall student numbers should be reflected in qualifications awarded.

Item 2ai - Proportion of qualifications obtained by students on HE course by level of qualification obtained and mode of study (2013/14 and 2012/13)

PRIORITY: CRITICAL

POPULATIONS: XPQUAL01
FIELDS USED: QualificationsAwarded.QUAL, Instance.MODE
DERIVED FIELS USED: XQMODE01, XQLEV501, XQLEV1003

This table is wholly derived from Item 2a.

DESCRIPTION: This item displays a proportion of the Item 2a qualifications obtained by mode and level of study compared to the total for that mode. Figures are provided for both the current and previous report year to provide a comparison.

WHAT TO LOOK OUT FOR: It is not expected that the year-on-year difference will vary radically for mode as a proportion of the qualifications obtained. To highlight high levels of change, differences between years of greater than 5 will be shaded light grey and differences of greater than 10 will be shaded dark grey.

Item 2b - REF doctoral degrees awarded

PRIORITY: MAJOR-HIGH

POPULATIONS: XQOBTN01 in (D00, D01) XLEV501 = '1' XMODE01 in (1, 2, 3, 4, 6) and RSNEND in (01, 05)
FIELDS USED: QualificationsAwarded.QUAL, Instance.MODE, Instance.RSNEND
DERIVED FIELDS USED: XLEV501, XQOBTN01, XMODE01

DESCRIPTION: This item displays a count of research qualifications awarded that are included/not included in the REF, split between Doctorates (D00) and New Route PhD (D01). The data submitted in the C13051 Student record is compared against the REF dataset. The REF dataset includes all doctorate/PhD qualifications awarded that meet the REF criteria since 2007.

WHAT TO LOOK OUT FOR: It is not expected that any/many doctoral degrees will fall into any of the categories of item 2b. Where instances are counted here the data should be examined and corrected as necessary. If the data is genuine the reason will need to be provided to HESA via Minerva.

TIPS:

  • For an instance to be included in the REF it cannot have previously been recorded as having received the award.

Item 2c - Doctoral degrees awarded that do not match REF criteria

PRIORITY: CRITICAL

POPULATION: Criteria for level of study + PGR: PGR: XQBTN01 in (D00, D01) XLEV501 = '1' XMODE01 in (1, 2, 3, 4, 6) and RSNEND not in (01, 05) or RSNEND is null. RSNEND not coded 01, 05 is either 02, 03, 04, 06, 07, 08, 09, 10, 11, 98 or 99
FIELDS USED: QualificationsAwarded.QUAL, Instance.RSNEND, Instance.MODE
DERIVED FIELDS USED: XLEV501, XQOBTN01, XMODE01

DESCRIPTION: This item displays the number of doctorates/PhDs that have been returned where either RSNEND has not been completed, where RSNEND is other than 01 Successful completion of course or 05 Death, or where the level of study for the instance is below PGR. This item is intended to check that PhDs are being awarded correctly. It would not be expected that a PhD would be awarded where the instance was unsuccessful, uncompleted or below PGR level.

WHAT TO LOOK OUT FOR: It is not expected that any/many dotoral degrees will fall into any of the categories of item 2c. Where instances are counted here the data should be examined and corrected as necessary. If the data is genuine the reason will need to be provided to HESA via Minerva. There a series of Exception Warnings that work in tandem with these check documentation items.

New for 2013/14 SSN Item - Students with an SSN who started / left within 2 weeks

PRIORITY: CRITICAL

POPULATIONS:
Standard registration population (XPSR01)
FIELDS USED:
Instance.SSN, Instance.COMDATE, Instance.MODE,
DERIVED FIELDS USED:
XLEV501, XMODE01

DESCRIPTION: This item is new for C13051 and reports on students who started and left within 2 weeks.

WHAT TO LOOK OUT FOR: If students relevant to the revised coverage of the student record have been left out of your return, please take action to include them. For further information about the reporting of students who leave shortly after registering please see the coverage statement.

Check_Document_2Back to top

Item 3 - Student instance apportionment by mode, level and subject area

PRIORITY: MAJOR-HIGH

POPULATION: Standard registration population (XPSR01)
FIELDS USED: CourseSubject.SBJCA, Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH
DERIVED FIELDS USED: XMODE01, XLEV501, XJACSA01, XFPE01

DESCRIPTION: This item details the spread of students across subject areas. It acts as a useful reference to check that the spread of students across subject areas matches the situation at the institution. This item is useful in checking data that will be passed to UNISTATS.

WHAT TO LOOK OUT FOR: Ensure the spread of students to subject areas is as expected. Coding of courses as 'Y000 Combined' is not expected. The percentage change in each area is calculated to assist in reviewing the table.

TIPS:

  • Check subjects are coded correctly, e.g. nurses may be incorrectly coded to 'Medicine and Dentistry' rather than 'Subjects allied to medicine'. Institutional knowledge means that it is easier for the institution to notice inaccuracies with the reported apportionment than it is for HESA.
  • This table may split a student's Subject of Course across more than one Subject Area, as per HESA's Subject Area Apportionment method - outlined in the Student Circular 02/03 'Subject Areas and Related Issues'. The apportionment specification is detailed in the definitions document, under the heading 'Subject Area' (2011/12 & 2012/13)
  • The column headed 'Difference' shows shifts in apportionment between years. This column becomes column is shaded where there is a difference between years of >50.
  • The total % change column is shaded where there is a difference between years > 10%

Item 4 - Outgoing ERASMUS student numbers

PRIORITY: MINOR

POPULATION: N/A
FIELDS USED: Mobility.MOBSCHEME = 03 - ERASMUS
DERIVED FIELDS USED: None

DESCRIPTION: This item shows students identified as being on an exchange programme by the HEI compared with those identified to HESA by the ERASMUS UK office.

WHAT TO LOOK OUT FOR: Where students are identified by the ERASMUS UK office, it is expected that these student instances will be identified in the HESA Student record. Where there is a count of students provided by the ERASMUS UK office to HESA but zero students identified by the institution, or where the difference between the figures is greater than 20%, institutions are required to check and verify this data. The percentage difference displayed will be shaded grey where the difference is greater than 20%.

TIPS:

  • The count provided by the ERASMUS UK office this year is based on number of mobility instances, the HESA count is also based on the number of instances. However the figures returned from ERASMUS UK office only contains outgoing ERASMUS instances whereas HESA count is calculated using Mobility.MOBSCHEME = 03 - ERASMUS. Code 03 includes Erasmus Mundus, Comenius, Tempus and Erasmus for All.

New for 2013/14 Item 4a Mobility Instances

PRIORITY:

POPULATION: N/A
FIELDS USED: Mobility.MOBSCHEME, Mobility.MOBTYPE
DERIVED FIELDS USED: N/A

DESCRIPTION: This item is new for C13051 and reports a count of all mobility instances with a split by Mobility.MOBTYPE and Mobility.MOBSCHEME.

WHAT TO LOOK OUT FOR: For the majority of institutions. it is unlikely that there will be no mobility instances.

Item 5 - Course length profiles

PRIORITY: MAJOR - LOW to MAJOR - HIGH

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH
DERIVED FIELDS USED: XMODE01, XLEV501, XELSP01

DESCRIPTION: This item maps course lengths for Doctorate PhD, and Other postgraduate research (PGR), postgraduate taught (PGT), first degrees, and other undergraduates (OUG) split by full-time and sandwich, and part-time.

WHAT TO LOOK OUT FOR: Expected lengths for full time courses are often:PhD 2-4 years,Other PGR >1<3 years, PGT 1-2 years, OUG varies, First Degree 3-4 years, unless students are enrolled on medical, dentistry or veterinary courses. Engineering courses that include a sandwich year will also extend to 5 years. Part time courses are generally expected to be at least twice the length of full time courses.

TIPS:

  • Some PGR courses are 1 year in length: these are often Master of Philosophy (MPhil) courses.
  • It is not expected that many students will be on courses with an undefined length. Those students coded as undefined can include OUG.
  • Cells within the emboldened outline highlight where the majority of data is expected to sit.

Item 6a-d - Student cohort analysis full-time and sandwich

This Item is split into 4 separate tables. They detail student cohort analysis split by full-time and sandwich (item 6a), standard instance years (item 6b), part-time (item 6c) and non-standard instance years (item 6d). The split tables will allow for clearer analysis of Instance.YEARSTU and Instance.YEARPRG data. Instances where there are more than 10 students in total who have Year of Student 1 and Year of Course more than 1 will be queried.

PRIORITY: MAJOR - HIGH

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Instance.YEARSTU, Instance.YEARPRG, Instance.COMDATE, Instance.MODE
DERVIED FIELDS USED: None

DESCRIPTION: This item has been split into 4 separate sections. Tables 6a and 6c show the year of the course compared against the year of the student. Tables 6b and 6d show the academic year of the start of the instance against the year of student.

WHAT TO LOOK OUT FOR:

Item 6a & 6c: It is expected that for the majority of instances the year of course and year of student will correlate. For example, third year students should be on the third year of their course in 2013/14 and should have started in 2011/12. It is anticipated that data will follow the emboldened diagonal cell line within the tables.

Item 6c: Please note that where students study full-time courses on a part-time basis the year of course should still increment every year. For example, if a student is studying a degree normally taken full-time over 3 years, over 6 years part-time, the year of course should start at 1 and increase each reporting year to 6.

TIPS:

  • For both FT and PT students YEARSTU and YEARPRG should be incremented for each academic year of the course.
  • Students with year of student not required are those on reduced returns where YEARSTU is not a required field.
  • Year of course 'Not applicable' includes students on low credit bearing courses. If there are more than 5% of the total number of instances appearing in this column, it should be checked whether these are all low credit instances.
  • Where YEARSTU is greater than YEARPRG this can be due to re-sit students.
  • Where YEARPRG is greater than YEARSTU this can be due to direct entrants to later years of a course.
  • There a series of Exception Warnings that work in tandem with these check documentation items.

Item 6b: It is expected that the majority of standard instances will be populated in the emboldened cells within this item.

Item 6d: It is expected that for the majority of non-standard instances YEARSTU will correlate to two YEARPRGs.


TIPS:

  • Instances that have had a period of dormancy in a prior year may appear outside of the expected pattern.

Item 7a & 7b - Highest qualification on entry for first years

PRIORITY: MAJOR - HIGH

This item is useful for all institutions, but particularly so for those in England and Northern Ireland to monitor Equivalent and Lower Qualifications (ELQ).

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, EntryProfile.QUALENT3, Instance.COMDATE
DERIVED FIELDS USED: XMODE01, XLEV501, XQUALENT01

DESCRIPTION: This Item is now split into 2 separate tables.

Table 7a: details qualifications on entry returned for first years, split by mode (full-time and sandwich, and part-time) and level (PGR, PGT, first degree and OUG). There is a subtotals row for Postgraduate/PGCE/First Degree and another for Level 2 and below/Other qual/No formal qualifications.

Table 7b: This table is wholly derived from Item 7a. The table displays as a proportion the Highest qualification on entry for first year of Item 7a qualifications on entry by mode and level of study, compared to the total for that mode.

WHAT TO LOOK OUT FOR: It is generally expected that the majority of first degree students will have a level 3 qualification (including A levels, Highers & equivalent) as their highest qualification on entry. The total of not known qualifications for both UCAS and non-UCAS entrants should not exceed 5% of the total.

TIPS:

  • It is not expected that many students will enter a course with a qualification at a level higher than this new course of study.
  • Access courses are classified as 'Other qualification'.
  • Where Not knowns exceed 5% these values will be shaded in the table.

Item 8 - Comparison of full-time first degree entrants 2013/14 and 2012/13 by entry qualifications

PRIORITY: CRITICAL

Three columns have been added to this Item to show data as a proportion in percentage terms of UK domiciles for 2013/14 and 2012/13 with a Difference value.

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, EntryProfile.QUALENT3
DERIVED FIELDS USED: XTARIFF, XHOOS01

DESCRIPTION: This item provides a comparison of full-time degree entrants 2013/14 and 2012/13 by entry qualifications. Entry qualifications are displayed by tariff score and based on HESA-calculated tariff scores using the derived field XTARIFF.

WHAT TO LOOK OUT FOR: It is generally expected that the tariff point profile will remain relatively consistent from year to year and any large variances will be queried. High levels of unknown tariff points will be queried as they may impact the Performance Indicators. HESA will only be checking UK entry qualifications.

TIPS:

  • Small student number changes can shift percentages significantly.

Item 9

Not used.

Item 10 - Classification of first degree qualifications obtained

PRIORITY: MAJOR - HIGH

POPULATION: Qualifications obtained population (XPQUAL01)
FIELDS USED: QualificationsAwarded.QUAL, QualificationsAwarded.CLASS
DERIVED FIELDS USED: XCLASS01

DESCRIPTION: This item provides a breakdown of the classification of first degree obtained by students in the 2013/14 reporting period. Figures are provided for both the current and previous reporting year to provide a comparison.

WHAT TO LOOK OUT FOR: Check that there is a spread across all classifications and that these are similar to those returned in 2012/13.

TIPS:

  • Veterinary, dentistry and medical graduates and integrated masters coded as 12, 13 or 14 will be coded as unclassified.
  • Institutions in Scotland will often have a larger number of unclassified degrees.
  • A % change of classifications of +/-3% between years will be shaded grey.

Item 11 - Unknown values

PRIORITY: MAJOR - HIGH

POPULATIONS:
Standard registration population (XPSR01)
FIELDS USED:
Percentage of default/unknown codes used in population relevant to field
DERIVED FIELDS USED:
None

DESCRIPTION: This item details the level of unknown values returned in key Student and Entry profile entity fields. Unknown values impact onwards analysis of the data.

WHAT TO LOOK OUT FOR: Column N '% of unknown values' will shade when tolerance levels as outlined below are exceeded. For the majority of unknown values the cells in column N will shade when they are greater than the sector average plus 1%.

Additionally, some fields have had lower tolerance thresholds applied and they are as follows:

  • Student.BIRTHDTE Unknowns should not exceed 1%
  • Student.ETHNIC should not exceed 2%
  • EntryProfile.DOMICILE, Instance.DISALL and EntryProfile.PGCECLSS unknowns should not exceed 5%.

The associated cell will shade if:

  • Instance.YEARPRG unknown levels exceed 9%
  • EntryProfile.RELIGION and EntryProfile.PARED 10%
  • EntryProfile.SOC2000 and EntryProfile.SEC 20%.

High levels of unknown values in the Instance.DISALL, and EntryProfile.SOC2000 fields will affect the institution's Performance Indicators (PIs). A high number of unknowns in EntryProfile.POSTCODE and Instance.DISALL can affect Widening Participation funding. Institutions in England should be aware that unknown values in EntryProfile.QUALENT3 are regarded as ELQ students.

TIPS:

  • Key fields to investigate as a priority are denoted with the symbol (#1) and include Instance.DISALL, EntryProfile.QUALENT3, Student.TTACCOM, EntryProfile.POSTCODE and Student.TTPCODE.
  • A refined version of this item listing unknown values for FE students is available as Item 13 within the Institutional_Information sheet.
  • The populations used in this item varies between fields.
  • Please check that information refused for fields Ethnicity and SOC2000 are genuine refusals.

Item 12ai - Average instance FTE (%) Standard instance year

PRIORITY: MAJOR - HIGH

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, Instance.STULOAD , Instance.TYPEYR , Instance.NOTACT, Instance.RSNEND
DERIVED FIELDS USED: XMODE01, XLEV501

DESCRIPTION: This item displays the average FTE for instances split by level and mode of study. This item has been split in 3 ways to display New starters in the reporting period (Instance.COMDATE and Instance.ENDDATE in the year), Leavers in the reporting period (Instance.ENDDATE in the year) and Others.

New for 2013/14

For 2013/14 the withdrawn (Instance.RSNEND codes 02, 03, 04, 05, 06, 07, 08, 09, 10, 11 or 99) and suspended (Instance.NOTACT codes 1 and 2) have been split out.

Starters
The instances that fall into this category are new starters in the current reporting period i.e. commenced on or after the 1st August of the reporting year. This also includes those that started and ended their study in the current reporting period i.e. End date (Instance.ENDDATE) = on or after the 1st August.

Leavers
The instances that fall into this category are those that started in a previous reporting period and are concluding their period of study in the current reporting period i.e. Start date (Instance.COMDATE) before 1st August and end date (Instance.ENDDATE) on or after the 1st August.

Others
The instances that fall into this category are continuing students who have not completed their programme of study i.e. Start date (Instance.COMDATE) before the 1st August and end date (Instance.ENDDATE) does not exist.

WHAT TO LOOK OUT FOR:

The following tolerances apply to the Total (excluding withdrawn or suspended) column.

For full-time and sandwich PGR students the average FTE for institutions in England is expected to be greater than 90%. For institutions in Scotland and Wales the FTE is expected to be greater than 80%.

For full-time and sandwich PGT students the average FTE for institutions in England is expected to be greater than 80%. For institutions in Scotland and Wales it is expected to be greater than 70%.

For full-time and sandwich FD students the average FTE is expected to be greater than 95% for institutions in England and 80% for institutions in Scotland and Wales.

For full-time and sandwich OUG students the average FTE is expected to be greater than 80% for institutions in England and 70% for institutions in Scotland and Wales.

The average FTE for part-time students in English institutions is expected to be in the range of 20-60%. For institutions in Scotland and Wales average FTE is expected to be in the range of 10-60%.

The following tolerances apply to the Withdrawn and Suspended column.

For full-time and sandwich PGR, PGT, FD and OUG for all institutions the average FTE is expected to be greater than 10%.

For part-time PGR, PGT, FD and OUG for all institutions the average FTE is expected to be in the range of 5% to 60%.

TIPS:

Item 12aii - Average instance FTE (%) Non-standard instance year

PRIORITY: MAJOR - HIGH

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, Instance.STULOAD, Instance.TYPEYR, Instance.NOTACT, Instance.RSNEND
DERIVED FIELDS USED: XMODE01, XLEV501

DESCRIPTION: This item displays the average FTE for instances split by level and mode of study. This Item is split in 3 ways to display New starters in the reporting period (Instance.COMDATE and Instance.ENDDATE in the year), Leavers in the reporting period (Instance.ENDDATE in the year) and Others.

New for 2013/14

For 2013/14 the withdrawn (Instance.RSNEND codes 02, 03, 04, 05, 06, 07, 08, 09, 10, 11 or 99) and suspended (Instance.NOTACT codes 1 and 2) have been split out.

Starters
The instances that fall into this category are new starters in the current reporting period i.e. commenced on or after the 1st August of the reporting year. This also includes those that started and ended their study in the current reporting period i.e. End date (Instance.ENDDATE) = on or after the 1st August.

Leavers
The instances that fall into this category are those that started in a previous reporting period and are concluding their period of study in the current reporting period i.e. Start date (Instance.COMDATE) before 1st August and end date (Instance.ENDDATE) on or after the 1st August.

Others
The instances that fall into this category are continuing students who have not completed their programme of study i.e. Start date (Instance.COMDATE) before the 1st August and end date (Instance.ENDDATE) does not exist.

WHAT TO LOOK OUT FOR:

The following tolerances apply to the Total (excluding withdrawn or suspended) column.

For full-time and sandwich PGR students the average FTE is expected to be greater than 80%.

For full-time PGT students the average FTE for institutions in England is expected to be greater than 70%. For institutions in Scotland and Wales it is expected to be within the range of 70-75%.

For full-time FD students in institutions in England the average FTE is 95%. For institutions in Scotland and Wales the average FTE is expected to be within the range of 75-85%.

The average FTE for part-time students in English institutions is expected to be in the range of 20-55%.

The following tolerances apply to the Withdrawn and Suspended column.

For full-time and sandwich PGR, PGT, FD and OUG for all institutions the average FTE is expected to be in the range of 5% to 95%.

For part-time PGR, PGT, FD and OUG for all institutions the average FTE is expected to be in the range of 5% to 55%.

TIPS:

Item 13 - Expected length of study by year of curse for FT UGs

PRIORITY: MINOR

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Instance.YEARPRG, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH
DERIVED FIELDS USED: XELSP01

DESCRIPTION: This item tracks the progression of students on courses compared to the expected length of the study instance as returned in the Instance.SPLENGTH and Instance.UNITLGTH fields.

WHAT TO LOOK OUT FOR: It is not expected that many students will be studying on undefined course lengths. The majority of such students are anticipated to be reduced records as Instance.SPLENGTH is not required.

TIPS:

  • Students counted as undertaking year 0 will be on a foundation year.
  • If students are studying of a course expected to last for 4 years then it is expected that there will be a spread of students across years 1-4 (and will be contained within the shaded area).
  • Cells within the emboldened outline show where the majority of instances are recorded.

Item 14 - Module status and outcomes

PRIORITY: MINOR

This item allows for analysis of StudentOnModule data and can be used to assist in quality assuring Instance.FUNDCOMP derivations.

POPULATION: n/a
FIELDS USED: Instance.MODE, StudentOnModoule.MODSTAT, StudentOnModule.MODOUT
DERIVED FIELDS USED: n/a

DESCRIPTION: This item splits out module outcome by mode and module status.This will be queried for Welsh HEIs only.

WHAT TO LOOK OUT FOR: It is expected that the majority of modules coded as StudentOnModule.MODSTAT 1, 2 or 4 will not have StudentOnModule.MODOUT coded as 6 or 7.

TIPS:

  • This item works in tandem with a series of exception warnings that check combinations of MODSTAT and MODOUT.

Item 15 - FE student instances by mode, domicile and fundability

PRIORITY: MINOR

Where FE student instances were previously returned in 2012/13 they will appear on the institution's FE HIN target list for 2013/14. If these continuing students are not returned in 2012/13 they will cause HIN errors. If there is an unexpected fall in FE numbers institutions are advised to check their FE HIN reports to obtain details of those students who have not been reported, and to subsequently resubmit to resolve these HIN errors.

POPULATION: Standard registration population (XPSR01)
FIELDS USED: Course.COURSEAIM, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH, EntryProfile.DOMICILE, EntryProfile.POSTCODE, Instance.FUNDCODE
DERIVED FIELDS USED: XQMODE01, XDOMGR01

DESCRIPTION: This item details FE student instance numbers by mode, level and domicile. Figures are provided for both the current and previous reporting year to provide a comparison.

WHAT TO LOOK OUT FOR: Ensure that the number and spread of FE student instances reflects the institution's provision in 2013/14.

TIPS:

  • This item will only be populated for those institutions returning FE student data to HESA. From C13051 it includes instances where Instance.MODE = 65 (FE continuous study) and Instance.MODE = 99 (FE in England)
  • Small student number changes can shift percentages significantly.
  • This item should be used in conjunction with the 'FE_Students' sheet.

NEW FOR 2013/14: Item 16 - Financial Support

PRIORITY: CRITICAL

POPULATION: Standard Registration Population (XPSR01) where the following additional criteria are met:
  • XINSTC01 = E
  • Course.COURSEAIM begins with H, I, J, C or is M22, M26, M28, M71 or M88 (excluding H50, H60, H61, H62, H78, H81, I60, I61 or I81)
  • Instance.EXCHANGE = N or Y or is NULL
  • Instance.FUNDCODE = 1 or 7
  • Instance.FEEELIG = 1
  • Instance.REDUCEDI = 00 or 01.
FIELDS USED: Course.COURSEAIM, FinancialSupport.FINTYPE, FinancialSupport.FINAMOUNT, Instance.EXCHANGE, Instance.FEEELIG, Instance.FUNDCODE, Instance.MODE, Instance.SPLENGTH, Instance.UNITLGTH,
DERIVED FIELDS USED: XMODE01

DESCRIPTION: This new item for C13051 provides a summary of Financial Support that the HEI provides. It is split by FinancialSupport.FINTYPE, mode (XMODE01) and reports on several things. It has a count of the number of awards given, a total of amount distributed, an average amount, the lowest amount and the highest amount given all by FINTYPE.

WHAT TO LOOK FOR: It is not expected that the financial support awarded to part time students would be greater than that awarded to students studying full time. Where data has been returned in FINTYPE 04 'Other' HESA will be asking if it includes the loan of equipment.

DLHEBack to top

Item 1 - Student numbers in the DLHE target population (POPDLHE) by mode, level and domicile

PRIORITY: MAJOR - HIGH

These students will later be surveyed as the HESA C13018 Destinations of Leavers in Higher Education (DLHE) population.The DLHE population is compiled from the HESA Student record. It is important to ensure this population contains the expected number of leavers as this population cannot be amended once the 2013/14 Student record has closed.

POPULATION: DLHE population (XPDLHE02)
FIELDS USED: EntryProfile.DOMICILE, QualificationsAwarded.QUAL, Instance.MODE
DERIVED FIELDS USED: XQMODE01, XQLEV301, XHOOS01, XDLEV301, XPDLHE02

DESCRIPTION: This item provides details of the number of students expected to be surveyed as part of the DLHE return for 2013/14. Figures are provided for both the current and previous reporting year to provide a comparison.

WHAT TO LOOK OUT FOR: The number is expected to be fairly consistent year-on-year. The spread of leaver numbers between Full-time and Part-time, and between UK and Other EU should also be similar to last year.

TIPS

  • It is advised to cross-compare this item with Check_document_1 Item 2 in order to confirm correlation. This comparison can highlight areas where the levels of qualifications awarded have altered which subsequently has affected the POPDLHE calculations.
  • A large decrease in the POPDLHE cohort may suggest that not all qualifications have been returned in the dataset. Check whether there are late awards which have not yet been included in the HESA extract.
  • Liaise with colleagues responsible for completing the DLHE return to ensure they are content with the population. HESA DLHE contacts are provided with read-only access to the Student record in order to view and download the POPDLHE file. Following the Student record being set to credible, it is advisable to notify DLHE colleagues that the POPDLHE file is now stable and finalised in order that they download the latest version to use for the survey.
  • Cells will shade where year-on year-comparison data fluctuates by more than 10%.

Popdlhe.gif

The POPDLHE icon included within the TEST_COMMIT/COMMIT reports provides further breakdowns of the DLHE population. It is from this icon that the population can be downloaded.

Item 2 - DLHE undergraduate population broken down by JACS level 2

PRIORITY: MAJOR - HIGH

POPULATION: XPDLHE02
FIELDS USED: QualificationsAwarded.QUAL, Instance.MODE
DERIVED FIELDS USED: XDOMHM01, XDLEV301, XPDLHE02, XJACSLEV201, XQMODE01, XFPE01

DESCRIPTION: This item provides a breakdown of the undergraduate DLHE population by JACS level 2 split by Full-time and Part-time. This will provide a preview for the KIS record.

WHAT TO LOOK OUT FOR: Ensure that the breakdown of subjects is representative of the profile of your institution.

TIPS:

  • DLHE data will be used in the KIS record to provide information on employment profiles.
  • Only full time DLHE data will be used in the KIS, unless the course is only offered on a part time basis.
  • The same instance can appear more than once in this table if it is associated with a course that has multiple course subjects that map to more than one JACS level 2 code.

REF2014Back to top

Changes relating to the Research Excellence Framework

REF.UOA2014 has replaced RAEData.UOA2008 to reflect recent changes to the Research Excellence Framework (previously RAE). To ensure consistency in the data returned we encourage contacts to liaise with their colleagues responsible for the REF as well those undertaking their institution's Staff return. Cross checks between the Staff and Student records will be carried out by HESA to ensure that the REF units of assessment are consistent.

Student.REFData.UOA2014: The first two characters are the Unit of Assessment (UOA) assigned to the student's supervisor in the 2014 REF. The final character is the letter denoting the multiple submission the member of staff was associated with or 'Z' where a multiple submission was not made. Institutions should refer to the guidance on the REF Unit of Assessment located in the field and detail list on the coding manual.

TIPS:

  • We would not normally expect there to be students assigned to a unit of assessment where there are no staff.
  • We would normally expect there to be Staff on a Unit of Assessment (Person.REFUOA2014) where there are students.
  • It is recommended that colleagues responsible for the Student record liaise with those responsible for the Staff record to ensure that REF data is comparable.

FeesBack to top

Items 1a, 1b, 2a, 2b Net fees for Undergraduate and Postgraduate Full-time and Sandwich students both Fundable and Non-fundable

PRIORITY: MAJOR - HIGH

POPULATION: (FEEREGIME = 20 and Instance.SSN is blank) or (FEEREGIME = 30, FUNDABLE = 1, 5 & 7, NON-FUNDABLE = 2, 3 & blank)
FIELDS USED: Instance.FUNDCODE, Instance.NETFEE, Course.COURSEAIM, CourseSubject.SBJCA, Instance.MODE, Instance.FEEREGIME
DERIVED FIELDS USED: XJACSA01, XMODE01, XPSR01, XFPE01, XLEV301

DESCRIPTION: This Item is split into 4 separate tables. Items 1a and 2a display Instance.NETFEE information for undergraduate and postgraduate full-time and sandwich student instance numbers by subject area split between fundable and non-fundable. Items 1b and 2b display fee information for undergraduate and postgraduate part-time student instance numbers by subject area split between fundable and non-fundable (item 1b and 2b). The items use different fee bandings depending on whether the course is fundable and on the level of study.

WHAT TO LOOK FOR: In both fundable and non-fundable sections, it is not expected that many courses will be returned with zero fees. For full-time and fundable instances fees are not generally expected to be less than £6,000 or more than £9,000. It not expected that all full-time fundable fees are reported at £9,000; the expectation would be that some fees are lower than this due to the application of fee waivers. For part-time undergraduate and sandwich students the likelihood is that fees may be less than £6000. Where Instance.SSN has been returned and the institution has not opted to return Instance.GROSSFEE and Insatnce.NETFEE these instances will be shown in the 'Blank' column.

HESA will not be checking this item but we encourage institutions ensure that the spread of fees accurately reflects the fees charged at your institution.

TIPS:

  • The items include all undergraduate/postgraduate provision; be mindful of varying fee levels for different types of provision.
  • Zero fees will be flagged in two commit warnings; Instance.NETFEE.Exception.1 and Instance.NETFEE.Exception.2. You are advised to review these warnings for details of those instances returned with a zero fee.
  • Where the fees are paid for by the NHS or other body as a lump sum Instance.NETFEE will be recorded as zero.
  • Medicine & Dentistry and Subjects allied to medicine full-time undergraduate fees could fall under the £9,000+ column where Instance.FUNDCODE = 5.
  • These items use the full person equivalent (FPE) population XFPE01. Consequently, instances that link to multiple subject areas will be displayed in each of the applicable rows as the full NETFEE for the instance. This duplication should be taken into account when analysing these items.
  • Low fees may be attributable to non-annualised fees having been returned in error. If a student leaves the HEI part the way through the instance year, the annualised amount the student would have been charged should be returned in Instance.NETFEE.

Collaborative_Franchise sheetBack to top

PRIORITY: MAJOR - HIGH

Note that the Funding Councils require full reporting of collaborative/franchise arrangements.

DESCRIPTION: This sheet lists a count of student instances by mode and level where teaching is being conducted at a collaborative/franchise institution. Figures are provided for both the current and previous reporting year to provide a comparison.

WHAT TO LOOK OUT FOR: Ensure that all expected collaborative/franchise institutions are listed and that the number of instances attributed to them are correct.

TIPS:

  • Use of generic codes such as 4001 'Other UK institution', will be monitored to see whether they can be further defined using the valid entries in Module.TINST.
  • Where a UK institution is not listed in the Module.TINST valid entries but the institution has a UKPRN, please notify [email protected] to request that this institution be added to the valid entries. Code 4001 'Other UK institution' is not valid for English institutions but where permissable should only be used where a UKPRN has not been assigned.

FE Students (Institutions in England and Wales with FE students only)Back to top

PRIORITY: MINOR

DESCRIPTION: This sheet provides a general headcount of FE student instances by course aim and FE general qualification aim (Course.FEQAIMC).

WHAT TO LOOK OUT FOR: Ensure the spread between Course.COURSEAIM and Course.FEQAIMC is representive the level of FE provision at the institution. Institutions in Wales should check how many students have been coded with an FEQAIMC of unknown '66666666'. HESA would not expect the number of unknowns to be higher than 10%.

TIPS:

PI sheetBack to top

PRIORITY: CRITICAL

These tables depict key groupings that will be used to create the Performance Indicators (PIs) for your institution. These will not be checked by HESA but are for institutional use. It is important that the information in these tables is reviewed internally.

POPULATION: See check documentation 'Definitions' sheet for full details.

Table 1a

DESCRIPTION: This table details the number of young full-time undergraduate entrants that are from state schools split by first degree, all undergraduate entrants and other undergraduate entrants. Figures for 2012/13 are also provided for comparison.

Table 1b

DESCRIPTION: This table details the number of young full-time undergraduate entrants that are from NS-SEC classes 4, 5, 6, 7 split by first degree, all undergraduate entrants and other undergraduate entrants. Figures for 2012/13 are also provided for comparison.

Table 1c

DESCRIPTION: This table details the number of young full-time undergraduate entrants that are from low participation neighbourhoods (POLAR2) split by first degree, all undergraduate entrants and other undergraduate entrants. Figures for 2012/13 are also provided for comparison.

WHAT TO LOOK OUT FOR IN TABLES 1a, 1b, 1c:

For all three tables 1a-1c it is expected that levels will be similar to last year. Any change greater than 2% where the percentage is fewer than 10%, and greater than 3% where the percentage is over 10% should be checked and verified.

Note that low participation data is not produced for institutions in Scotland; static data for 2012/13 will show as zero for these institutions.

TIPS:

  • Differences can be affected by the level of unknown values in EntryProfile.PREVINST, EntryProfile.SEC and EntryProfile.POSTCODE. These levels can be checked in Item 11.
  • NS_SEC is collected directly by UCAS. Institutions are encouraged to code non-UCAS entrants. Consequently institutions with non-UCAS entrants which do not opt to collect SEC information locally can result in a blank table 1b.

Table 7 - Receipt of disabled students allowance (DSA)

DESCRIPTION: This table details the number of students in receipt of the disabled students allowance (DSA). Figures for 2012/13 are also provided for comparison.

WHAT TO LOOK OUT FOR: Ensure that the data accurately displays the institution's profile.

TIPS:

  • The values displayed for 2012/13 for comparison may not exactly match those returned on the C12051 Student record. This is due to duplicates being removed prior to the publication of PIs.

ITT (Institutions in England only)Back to top

PRIORITY: CRITICAL

DESCRIPTION: Tables 1a, 1b, 2a and 2b on this sheet detail the number of students gaining teaching qualifications and QTS for BEd (Primary courses), BEd (Secondary courses), Postgraduate (Primary) and Postgraduate (Secondary) respectively. This item is useful for previewing the potential TA performance profiles.

WHAT TO LOOK OUT FOR: Check that the number of degrees and percentage being awarded QTS is as expected. HESA does not check this sheet as data on the number of QTS awards will be reviewed as part of Item 2. This sheet is provided for the benefit of institutions and to assist in local checks.

TIPS:

  • It is expected that QTS should be achieved by at least 80% of ITT leavers.

CCAnalysisBack to top

PRIORITY: CRITICAL

DESCRIPTION: This sheet provides comparative analysis between the Student Record, Staff Record and Finance Statistics Return data for 2012/13 against the 2013/14 Student Record cost centre data.

New for 2013/14 there is a new column which will identify whether or not the cost centre was returned in the Institution Profile return (C13041) for the same reporting period.

WHAT TO LOOK OUT FOR: It is a standard data quality check that for costs centres where student FTE is returned, there will also be staff FTE and expenditure attributed to this cost centre.

Cost centre 999 'Cost centre not assignable' should only be used in cases where it is not possible to allocate the activity to an academic cost centre. Use of this cost centre will be queried by HESA in Minerva. For institutions in England, HEFCE make use of cost centres in their funding allocations. HEFCE have stated that provision returned under cost centre 999 will be allocated to the lowest price group for funding.

TIPS:

  • The Institution profile record provides metadata for use with the HESA Finance, Staff and Student records. The academic cost centres submitted in this collection will be used to validate the data being returned in the Student record.
  • It is recommended that the Staff, Student and FSR record contacts liaise ahead of the data submission period to ensure all three returns will be completed consistently. This liaison should ideally be undertaken ahead of the submission of the Institution profile record.
  • Where there is a small amount of Staff FTE and/or expenditure attributed to cost centre 136 Continuing Education, this may be to support non-credit bearing student activity which is excluded from the coverage of the Student record.
  • Where there is zero student FTE returned to a cost centre with activity last year this may be due to the closure of a department. Conversely, student FTE in a cost centre previously returned as zero may signal new courses at the institution. If this is the case you will need to ensure the Staff and FSR returns will be completed on the same basis to return staff FTE and expenditure in the same cost centre.
  • Following the review of cost centres, from 2012/13 it will not be possible to do a detailed comparison of the use of cost centres, however, checks should be conducted to ensure that use of new cost centres has occurred where expected.
  • A further breakdown of cost centre analysis by level of study and Instance.FUNDCODE is provided in item 14 on the 'Institutional_information' sheet within the check documentation.

UCAS_Data_for_HESABack to top

The majority of UCAS member institutions have agreed for their UCAS data for HESA (*J) transaction data to be shared with HESA in order for any inconsistencies between the data captured by UCAS in Apply and the data sent to HESA by the institution to be highlighted. It is through this check documentation tab that this is carried out.

DESCRIPTION: The item details;

  • the number of records with the same value in the UCAS and HESA data
  • the number of records with unknown/null data in UCAS, but for which data has been captured for HESA
  • the number of records with known data in UCAS, but for which unknown/null has been returned to HESA.

WHAT TO LOOK OUT FOR: It is expected that the majority of records will either match the data returned by UCAS, or be an improvement to the data held by UCAS, i.e. a known value has been returned rather than an unknown/null held by UCAS.

TIPS:

  • Matches are carried out between the UCAS data for HESA (*J) transaction and the HESA Student record based on matches to the UCAS scheme code (returned in the EntryProfile.UCASAPPID field) and Student.UCASPERID.
  • This data item is restricted to full time undergraduates that entered the institution via UCAS.
  • The UCAS data for HESA (*J) transaction is provided to institutions by UCAS. Further details of the transaction can be found at UCAS Data for HESA.

Query Sheet (New for 2013/14)Back to top

The Query sheet has been added to the check documentation from 2013/14 and is designed primarily as an aid for the Data Quality Assurance team at HESA to use during the quality checking period. The sheet has been made available to providers as it may be a useful aid in identifying potential data quality issues. The queries listed in the Query sheet are generic queries based on the shading within the relevant check documentation item. Please note that the Query sheet is indicative only and will not necessarily reflect the content of any data quality queries raised by HESA during the quality assurance process.

Exception Report Back to top

Exception.gif Institutions are advised to review any warnings listed within the Exception Report following a successful TEST_COMMIT/COMMIT transaction. Any data items listed should be examined and amended and/or explained as necessary through Minerva.

Full details of the commit-stage exception rules for this collection can be found at COMMIT-stage validation.

Exception Report compare facility

To assist comparison of commit transactions the Exception reports will be retained on the system for all commit transactions. The reports will feature the number and details of records failing a rule along with a percentage change column to enable quicker recognition of changes between submissions.

HIN Back to top

HINRED.gifHIN is the linking mechanism used by HESA to track continuing student instances of study between HESA reporting years. The HIN reports detail potential discrepancies with student instance linking within the committed data file. To pass the HIN validation institutions will need to resolve/explain all errors and/or warnings generated within the HIN reports. View Understanding the HIN Reports for assistance with these reports.

Contact Liaison by email or on 01242 211144.