Module instance (ModuleInstance)

Navigation: Index / Data Dictionary / Module instance



Module instance
Short Name
The Module instance records a student's specific engagement with a Module and the Module outcome.
Uniquely Identified By
Applicable To
England Northern Ireland Scotland Wales

An entity is required for each interaction a student has with a Module at providers in Northern Ireland, Scotland and Wales and Approved (fee cap) providers in England where Qualification.QUALCAT starts with E, M, H, I, J or C except where Engagement.INCOMINGEXCHANGE exists or (SessionStatus.STATUSCHANGEDTO = 02 for the entire reference period) or (Leaver.ENGENDDATE - Engagement.ENGSTARTDATE <= 14 days and RSNENGEND = 03, 05, 11, 12).

Optional for each interaction a student has with a Module at Approved providers in England.

Optional where Engagement.INCOMINGEXCHANGE exists.

Optional where Qualification.QUALCAT starts with D or L.


Providers in England that are registered with the Office for Students in the 'Approved' category are not required to return Module data but can do so optionally.

Providers in England that are registered with the Office for Students in the 'Approved (fee cap)' category must return Module data. 

Further information regarding the OfS register can be found here

Module data is optional to return for postgraduate research students and incoming exchange students.

This entity associates a StudentCourseSession with a Module that a student is engaging with as part of that StudentCourseSession, including the module outcome.

ModuleInstances should be submitted against the StudentCourseSession, not just the reference period in which they occurred. Therefore all of the ModuleInstance associated with the StudentCourseSession will be returned for the reference period in which the StudentCourseSession finishes.

The ‘retake’ of a module could take two forms, either the retake of a final exam (no taught elements of module repeated) or the complete retake of the module including taught elements and final assessment. 

If a student retakes a module in the same StudentCourseSession, the module would be returned as below: 

  1. if the student was retaking an exam then record this information under the same Module Instance
  2. if the student was redoing the whole module then 2 module instances (with the same MODID) and the provider will need to request a tolerance override

Modules spanning StudentCourseSessions

One Module instance can only be associated with one StudentCourseSession and therefore cannot span StudentCourseSessions. If a student's engagement with a Module spans two or more StudentCourseSessions, then multiple Module instances are required, one associated with each StudentCourseSession. The first would have an associated module outcome where ModuIeInstance.MODULEOUTCOME= 06 'Will complete Module in a subsequent StudentCourseSession'. Both ModuleInstances returned would be linked to the same Module.

If at the end of the StudentCourseSession the student has completed activity but the result is not yet known, a ModuleInstance.MODULEOUTCOME = 05 ‘Module result not yet known’ can be returned for students where module result information is required to indicate this

Where a student is resitting a module in a subsequent StudentCourseSession (whether resitting teaching or just exams), the ModuleInstance.CONTINUING field would not be returned as they are resitting rather than continuing the module. If returning fees on a modular basis, any fees associated with this resit would be returned in ModuleInstance.MIFEEAMOUNT. If returning fees on a StudentCourseSession basis, any fees associated with this resit would be returned in StudentCourseSession.SCSFEEAMOUNT.

In some cases a ModuleInstance may be returned to record the outcome of a module only, this may be because the student is resitting exams, or the outcome was not confirmed at the end of the previous StudentCourseSession. In these cases, the ModuleInstance.INACTIVEMOD field would be returned to indicate that there was no activity associated with the ModuleInstance. The start and end dates for the ModuleInstance would align with the start date for the associated StudentCourseSession.

Providers in England and Northern Ireland

Whilst providers may recognise prior learning and allow students to take APEL modules, APEL modules should not be returned in the student record by providers in England and Northern Ireland. This is to prevent confusion over those modules taken through APEL and those not undertaken through APEL, to avoid FTE being allocated incorrectly.

Quality Rules
Quality rules to follow
Reason Required
To record the Modules that Students engage with, to record module outcomes.
Minimum Occurrences0
Maximum Occurrences
Child Fields
Revision History
Coding Manual VersionElement VersionNotes updated to match legacy Student and Student Alternative return - change to exclude 2 week SLC rule and dormant students. updated to match legacy Student and Student Alternative returns - Change to exclude 2 week SLC rule and where RSNENGEND = 03, 05, 11, 12.