WF-07 — Admission, Enrolment and Registration
| Workflow ID | WF-07 |
| Pack owner | IoL Academic Affairs (decision of 2 September 2026; see Architecture/04_Ownership_Model.md) |
| Family | B — Learner lifecycle, teaching and assessment |
| Channel | C1 accredited programmes |
| Primary OBEF KPIs | 2.2 Retention year 1 to year 2 (5.0%), denominator |
| Contributes to | 1.1 Employment rate (20.0%) · 1.2 Employment in relevant jobs (5.0%) · 4.4 Student research participation (5.0%) · 5.3 Dual or joint degree (2.0%) · 2.6 Student satisfaction (2.5%), through contact data |
| Programme-level yield | 5.0% primary; sets or conditions a further 34.5% |
| Workflow owner | ______________ |
| Data steward | ______________ |
| Version | 0.1 draft |
| Effective | |
| Next review |
This workflow sets denominators, and denominators are irreversible. Almost nothing here scores directly. What it does instead is decide, at the moment a learner is registered, which population every later KPI is measured against, whether the Ministry can reach that learner to survey them, and whether the programme's field of study is coded in a way that lets KPI 1.2 recognise a relevant job. A field left blank at registration is not a gap that can be filled later; it is a KPI that will be computed on the wrong population.
1. Purpose
To ensure that every learner admitted to an IoL programme is registered once, in the correct academic period, against the correct Program Code and CIP classification, with complete and durable personal contact data and a correctly recorded employment position, so that the learner can be counted, surveyed, tracked and progressed for the whole of their relationship with MBRU and for the twelve months after graduation on which a quarter of the OBEF framework depends.
2. Scope
Scope statement. This process manages learner entry from receipt of an application, through admission decision and offer, to a confirmed registration record in the student information system carrying every attribute the OBEF framework and the CHEDS submission require.
Applies to. All applicants and admitted learners on PGDipHPE and MScHPE, in every intake, including learners admitted with advanced standing, learners transferring in from another MBRU programme, and learners registering on a part-time or distance mode of study.
Does not apply to. Registration on non-credit CPD
and CME activity (WF-21), micro-credential registration where it is not
embedded in an accredited programme (WF-22), or visiting and observing
participants who hold no MBRU student record. These populations must
never appear in Students - Enrollment.xlsx rows used for
programme-level KPIs, because they inflate denominators for retention,
student research participation and mobility without ever appearing in
the numerators.
Applicable requirements. OBEF guide v11.5, KPI 2.2,
KPI 1.1 and 1.2, KPI 5.3, Appendix B evidence requirements for
stakeholder contact data, Appendix C sampling thresholds; CAA admission
standards for postgraduate entry; MBRU admissions policy; the CHEDS
Master API specification of 18 February 2026 for
Students - Enrollment.xlsx and
Applicants - Basic Details.xlsx; UAE data protection
obligations covering learner personal and employment data.
The definition that governs everything below. KPI 2.2's denominator is not an annual headcount. It is first-year students enrolled in the autumn or fall semester of the previous academic year. A learner admitted in a spring intake is not in that denominator at all. Whether that is favourable or unfavourable depends on who those learners are, but it is not optional and it cannot be adjusted after the fact.
3. Trigger, boundary and endpoint
| Trigger | An application is received for an IoL programme, or an internal transfer request is raised |
| First activity | Application receipt and eligibility screening |
| Last activity | Registration record confirmed and validated against the CHEDS field set |
| Endpoint | A complete, validated enrolment record exists for the learner for
the academic period, with Enroll_1st_Academic_Period set
once and never overwritten, and the applicant funnel counts closed for
the cycle |
| Upstream workflows | WF-01 programme design (Program Code, CIP code, study plan, mobility option) · WF-05 accreditation and eligibility status |
| Downstream workflows | WF-09 assessment · WF-10 progression and graduation clearance · WF-12 simulation and learning resources · WF-13 placement · WF-16 student research · WF-25 alumni outcomes · WF-26 OBEF data assembly |
4. SIPOC
| Element | Content |
|---|---|
| Suppliers | Applicants; MBRU central admissions; programme academic reviewers; Dubai Health employing entities as sponsors or referees; registry; WF-01 for programme reference data |
| Inputs | Application and supporting qualifications; equivalency evidence;
language evidence; programme entry criteria; approved Program Code,
Major CIP Code and study plan; academic period calendar;
sponsorship or employer nomination where applicable |
| Process | Receive application → screen eligibility → academic review and decision → issue offer → accept and confirm → collect and verify enrolment attributes → assign Program Code, level, CIP and mode → register for the academic period → validate the record against the CHEDS field set → close the applicant funnel counts |
| Outputs | Confirmed enrolment record; applicant funnel counts; learner contact set; employment status and sector; first academic period stamp; dual and outbound mobility indicators; cohort definition for KPI 2.2 |
| Customers | Learner; programme director; WF-10 and WF-25; the Ministry's Student Experience Survey and Graduate Destination Survey; WF-26 and the OBEF submission |
| Success criteria | Every registered learner has a complete CHEDS-valid enrolment row;
Enroll_1st_Academic_Period is correct and stable; contact
data is personal and reachable; CIP coding matches the approved
programme record; no non-award participant appears in the enrolment
file |
5. Accountability
Process owner. IoL Director of Programmes, or the role able to change admission criteria, agree intake timing with central admissions and resolve conflicts between programme requirements and central registry rules.
| Step | Programme Director | Admissions Officer | Registry | Data Steward | Learner | Quality and IQA |
|---|---|---|---|---|---|---|
| Screen eligibility | C | A/R | I | I | R | I |
| Academic review and admission decision | A/R | R | I | I | I | C |
| Issue and record offer | C | A/R | I | R | I | I |
| Confirm acceptance | I | A | R | I | R | I |
| Collect and verify contact data | I | R | A | R | R | I |
| Record employment status, sector and position | C | R | A | R | R | I |
| Assign Program Code, level, CIP and mode of study | A/R | C | R | C | I | C |
Set Enroll_1st_Academic_Period |
I | C | A/R | C | I | I |
| Set dual and outbound mobility indicators | C | I | R | A/R | I | C |
| Register for the academic period | I | C | A/R | I | R | I |
| Validate the record against the CHEDS field set | I | I | C | A/R | I | C |
| Close applicant funnel counts for the cycle | C | A/R | C | R | I | I |
Escalation.
| Condition | Escalates to | Within |
|---|---|---|
| Learner registered without a personal email or mobile | Registry to Data Steward, then Programme Director | 5 working days of registration |
Enroll_Major_CIP absent or inconsistent with the
approved programme record |
Data Steward to Programme Director, then WF-01 | Before the period census |
Enroll_1st_Academic_Period overwritten on an existing
learner |
Data Steward to Registry management | Immediately, treated as a data incident |
| Non-award participant found in the enrolment file | Data Steward to Registry | Before submission, always |
| Intake falls outside the autumn period and the KPI 2.2 treatment is unclear | Programme Director to Quality and IQA | Before the admissions cycle opens |
6. Process steps
Receive and log the application. Record the application against the intake and Program Code. [CAPTURE] applicant count for the cycle. Serves the
Applicants - Basic Details.xlsxfunnel (Number of Applicants), which is not itself an OBEF KPI but is the reference population every selectivity question is answered from.Screen eligibility against published entry criteria. Record the criteria version applied. This record has a second life: KPI 2.2 at programme level treats a transfer out as attrition unless the destination programme has comparable admission criteria, and that comparison is only possible if the criteria applied are recorded and dated.
Academic review and admission decision. [CAPTURE] offer count. Serves
Number of Admissions Offered.Issue the offer and record acceptance. [CAPTURE] new-enrolment count. Serves
Number of New Enrollments. The three funnel numbers must reconcile: applicants at least offers, offers at least new enrolments.Collect and verify contact data. Capture a personal email address and mobile number, not only an employer address. [CAPTURE]
Enroll_Student_Email_Address,Enroll_Student_Mobile_Number. Serves 2.6 through the Ministry's Student Experience Survey distribution list, and serves 1.1 and 1.2 later throughGrad_Student_Email_AddressandGrad_Student_Mobile_Number. This is the most consequential five minutes in the workflow. IoL learners are employed clinicians. An employer email address stops working the moment a learner changes post, which is exactly the twelve-month window in which the Graduate Destination Survey tries to reach them. Twenty percentage points of the framework sit behind KPI 1.1, and its only failure mode that IoL controls is unreachability.Record employment status, sector and position. [CAPTURE]
Enroll_Employment_Status,Enroll_Employment_Sector,Enroll_Employment_Position. Serves 1.1, 1.2 and 3.1 as context, and serves the Category 2 substitute-data case described in section 9. IoL learners are overwhelmingly already employed, most of them inside Dubai Health entities. That fact is educationally central and it is also the reason IoL can plausibly report a near-census of employment outcomes later. It is only usable if it is recorded at entry rather than asserted at submission.Assign Program Code, student level, mode of study, CIP and specialisation. [CAPTURE]
Enroll_Program_Code,Enroll_Student_Level,Enroll_Mode_of_Study,Enroll_Major_CIP,Enroll_Area_of_Specialization,Enroll_Student_Type. Serves 1.2, 2.2 and 4.4. Decision point.Enroll_Major_CIPmust equal theMajor CIP Codeheld for the programme inInstitute - Academic Programs.xlsx. If they differ, stop and route to WF-01. Do not correct one to match the other locally, because the CIP code drives the ISCED mapping that the Ministry's relevance matrix uses to decide whether a graduate's job counts for KPI 1.2, and a locally invented value stays invisible until five points have already been lost.Set the first academic period. [CAPTURE]
Enroll_1st_Academic_Period. Serves 2.2. Set once, on first registration, and never overwritten by a later re-registration, programme transfer or return from deferral. The KPI 2.2 denominator is built by selecting learners whoseEnroll_1st_Academic_Periodequals the autumn period of the previous academic year, so an overwritten value silently removes a learner from a cohort that has already been reported.Set the dual, joint and mobility indicators. [CAPTURE]
Enroll_dual,Enroll_Outgoing_Exchange_Indicator,Enroll_Exchange_University_Code, and separatelyEnroll_Incoming_Exchange_Indicator. Serves 5.3. Decision point. A learner may only be flagged outbound where a CAA pre-approved agreement is on file and the mobility is worth at least four weeks or the equivalent of a three-credit-hour course, counted within the programme's credit hours. Otherwise the flag is left unset and WF-01 is told the programme has no qualifying option, so the redistribution rule can be applied honestly.Register for the academic period and confirm the census position. [CAPTURE]
Enroll_Academic_Period,Enroll_Total_Credits_Registered. Serves the 2.2 and 4.4 denominators and the 2.6 two-semester eligibility filter.Validate the record against the CHEDS field set. Run the checks in section 13 at registration rather than at submission. A record that will fail in March fails today, at a cost of one email to the learner rather than a reconstruction exercise.
Close the applicant funnel for the cycle. Reconcile applications, offers and enrolments; archive the criteria version used.
7. OBEF data generated
| KPI | Data element | Capture point | Captured by | Destination | Level |
|---|---|---|---|---|---|
| 2.2 | First-year autumn cohort (denominator) | Steps 8 and 10 | Registry | Students - Enrollment.xlsx:
Enroll_Student_ID, Enroll_Academic_Period,
Enroll_1st_Academic_Period,
Enroll_Student_Level, Enroll_Program_Code,
Enroll_Student_Type |
Both |
| 2.2 | Continuation into year two (numerator, computed in WF-10) | Next-year registration | Registry | Same template, next academic year, joined on
Enroll_Student_ID |
Both |
| 1.1, 1.2 | Learner contact data, carried forward to the graduate record | Step 5 | Registry | Enroll_Student_Email_Address,
Enroll_Student_Mobile_Number |
Both |
| 1.2 | Field-of-study classification | Step 7 | Programme Director | Enroll_Major_CIP,
Enroll_Area_of_Specialization |
Both |
| 1.1, 3.1 | Employment status, sector and position at entry | Step 6 | Registry | Enroll_Employment_Status,
Enroll_Employment_Sector,
Enroll_Employment_Position |
Both |
| 5.3 | Dual or joint degree enrolment | Step 9 | Data Steward | Enroll_dual |
Both |
| 5.3 | Outbound mobility participation | Step 9 | Data Steward | Enroll_Outgoing_Exchange_Indicator,
Enroll_Exchange_University_Code |
Both |
| 5.3 | Inbound mobility, recorded and excluded | Step 9 | Data Steward | Enroll_Incoming_Exchange_Indicator |
Both |
| 4.4 | Total enrolled students (denominator) | Step 10 | Data Steward | Enroll_Student_ID, Enroll_Academic_Period,
Enroll_Program_Code |
Both |
| 2.6 | Student Experience Survey distribution list and the two-semester eligibility filter | Steps 5 and 10 | Data Steward | Enroll_Student_Email_Address,
Enroll_1st_Academic_Period,
Enroll_Total_Credits_Registered |
Institution |
| n/a | Applicant funnel | Steps 1, 3, 4 | Admissions Officer | Applicants - Basic Details.xlsx:
Number of Applicants,
Number of Admissions Offered,
Number of New Enrollments |
Institution |
Capture rule. Four things must be recorded at the time and cannot be reconstructed afterwards: the personal contact set as it stood at entry, the employment status, sector and position at entry, the first academic period, and the eligibility criteria version applied at admission. Everything else in this table can be recovered from the registry. These four degrade the moment the learner moves job, changes programme or graduates.
Reproducibility test. A second analyst can reproduce
the KPI 2.2 denominator from Students - Enrollment.xlsx
alone by selecting rows where Enroll_1st_Academic_Period
equals the autumn period of the previous academic year and
Enroll_Student_Level indicates first year, provided two
conditions hold: the first-period stamp has never been overwritten, and
the meaning of "first year" for a postgraduate-entry programme has been
decided and written down. The second condition is not met
anywhere in the IoL document set today, and it is a genuine defect
rather than a formality. The OBEF guide does not state whether
"first year" means the first year of the programme or the first year at
the institution, and for a postgraduate programme admitting learners who
already hold an MBRU qualification the two populations differ.
8. Max-score design
| KPI | Top anchor (scores 100) | Start of High (scores 75) | IoL achievable target | Reasoning |
|---|---|---|---|---|
| 2.2 (programme) | 100% | 80% | 90 to 100% | The programme-level anchors are the more forgiving pair. With small, employed, motivated cohorts the realistic loss is one or two learners a year, and the number is made in WF-10, not here. This workflow only has to get the denominator right. |
| 2.2 (institution) | 100% | 90% | Contributes | Institution-level anchors are harder and transfers are treated differently. IoL contributes a correct cohort, nothing more. |
| 1.1 | 100% | 90% | 100%, subject to reachability | Learners are already employed. The only things that stop this scoring are an unreachable graduate and a cohort too small to survey. |
| 1.2 | 100% | 90% | 85 to 95% | Depends entirely on the CIP code being right, because the relevance matrix is derived from it and MBRU does not control the matrix. |
| 5.3 (programme) | Yes, binary, on one actively enrolled student | binary, no intermediate band | 100 if WF-01 creates the option, otherwise redistribute | One registered student under one CAA-approved agreement scores 100. This workflow supplies the registration; it cannot supply the agreement. |
| 4.4 | 15% of students | 12% | 100% | An MSc with a dissertation clears the top anchor outright. This workflow supplies the denominator only. |
What this workflow must do to reach the target.
- Stamp
Enroll_1st_Academic_Periodonce and protect it. Make it non-editable after the first census without a data-incident record. Owner: Registry. - Make personal email and mobile mandatory and non-bypassable at registration, and re-confirm both at every re-registration. Owner: Registry, with the Data Steward monitoring completeness.
- Reconcile
Enroll_Major_CIPto the programme record before every census. Owner: Data Steward. - Record employment status, sector and position for every learner, without exception, since IoL's whole substitute-data case rests on knowing its learners' working lives. Owner: Registry.
- Exclude every non-award participant from the enrolment file. Owner: Data Steward.
- Record the admission criteria version applied, so WF-10 can later apply the comparable-criteria test to any programme-level transfer. Owner: Admissions Officer.
[REDESIGN] actions.
| # | Change | Unlocks | Approver | Lead time |
|---|---|---|---|---|
| R1 | Designate a single principal autumn intake for both programmes, or, if multiple intakes are retained, formally document how non-autumn entrants are treated in the KPI 2.2 denominator and hold that treatment constant across the three-year rolling average | Makes KPI 2.2, 5.0 points, computable and defensible. Without it the three-year series rests on a shifting population and cannot survive review | Curriculum governance with central admissions | One admissions cycle |
| R2 | Make personal email and mobile mandatory non-bypassable fields, separate from any employer-issued address, with annual re-confirmation | Protects KPI 1.1, 20.0 points, and KPI 1.2, 5.0 points, whose only IoL-controllable failure mode is an unreachable graduate. Also feeds the 2.6 survey list | IoL operational, with Registry | Immediate |
| R3 | Add employment status, sector, position and normalised employer name as mandatory attributes at registration, using the same controlled organisation list WF-13 uses for placement sites | Enables the Category 2 substitute-data case across 1.1, 1.2, 2.4, 2.6 and 3.1, a combined 32.5 points, and makes the KPI 3.1 employer match possible | IoL operational, with Registry and Data Steward | One month |
| R4 | Lock Enroll_Major_CIP to the approved programme
record, with a dated annual sign-off by the Programme Director
and Quality and IQA |
Protects KPI 1.2, 5.0 points, which is decided by a matrix MBRU cannot see or appeal | Programme Director with Quality and IQA | One month |
| R5 | Add a registration step for a CAA-approved mobility or dual option, ready to use the moment WF-01 and WF-24 create one, with the outbound indicator, partner code and credit value captured at registration | KPI 5.3, 2.0 points, binary on a single registered student | Curriculum governance and CAA for the option; IoL operational for the registration step | Registration step immediate; the option itself two to three cycles |
| R6 | Build a transfer-equivalence table recording, for each pair of MBRU programmes, whether admission criteria are comparable | Protects the KPI 2.2 programme-level numerator from counting a lateral transfer as attrition | Quality and IQA | Two months |
Sequencing note. R2 and R3 cost nothing and can start this week. R1 is the one with a governance cost and a long shadow: because KPI 2.2 is a three-year rolling average over three distinct cohorts, an intake structure settled in year one is worth more than a better structure settled in year three.
9. Indirect strategy where data cannot be collected
Category 4 is the dominant case here, and Category 2 is conditioned by what this workflow captures.
Category 4, activity exists but is invisible. Everything this workflow governs already happens. IoL admits learners, knows where they work, knows what they were doing before they enrolled, and stays in contact with them. None of it counts unless it is recorded in the fields the Ministry reads. The response is capture, at steps 5, 6, 7 and 9, and it is not a tactic. It is the difference between a department that knows its learners and a submission that can demonstrate it.
Category 2, population too small, is set up here even though it is exercised elsewhere. IoL cohorts will fall below the Appendix C thresholds, most likely below 70, which puts them into the small-sample guidance rather than the 30% response-rate rule. Two sanctioned routes follow, and both depend on data this workflow captures. Appendix C grouping of PGDipHPE and MScHPE is defensible on the stated principles of similar content area and similar employment fields, and the grouping must be decided and documented before any survey runs. Substitute data, under the guide's explicit invitation for KPIs 1.1, 1.2, 2.4, 2.6, 3.1 and 4.1, is only available to a department that holds complete, dated, personal contact data and knows each learner's employment circumstances. That is captured at steps 5 and 6, or it is not available at all.
A note on Category 3 and KPI 5.3. If IoL offers no CAA-approved dual, joint or mobility option, the programme-level weight is redistributed and no points are lost. That is the framework working as designed. What loses points is offering something informal, recording it as mobility, and failing the evidence test. The classification must be made honestly in WF-01 and reflected here by leaving the indicator unset.
A caution about the template itself. In the supplied
Students - Enrollment.xlsx, the header cell for
Enroll_dual carries trailing whitespace, and several
neighbouring headers do the same. Any local extract that matches column
names by exact string will silently return nothing. Match on trimmed
names, and record that you have done so.
Boundary check. This workflow must never:
- set
Enroll_Outgoing_Exchange_Indicatorfor any activity that lacks a CAA pre-approved agreement, a credit value counted within the programme, and a duration of at least four weeks or a three-credit-hour equivalent; - count an inbound exchange learner toward KPI 5.3, which counts outbound participation only, however natural it feels to treat inbound and outbound mobility as one activity;
- include CPD attendees, observers, visiting participants or
micro-credential-only registrants in
Students - Enrollment.xlsxrows used for programme-level KPIs; - overwrite
Enroll_1st_Academic_Periodon re-registration, transfer or return from deferral; - adjust
Enroll_Major_CIPlocally in order to obtain a more favourable KPI 1.2 relevance match; - move a learner's recorded intake period in order to place them inside or outside a KPI 2.2 cohort;
- record an employer-issued email address as the learner's only contact point.
10. Service standards
| Service | Standard |
|---|---|
| Application acknowledged | 3 working days |
| Admission decision communicated | 15 working days of a complete application |
| Offer acceptance recorded | 3 working days of receipt |
| Enrolment record created after acceptance | 5 working days |
| Personal email and mobile present at registration | 100%, non-bypassable |
| Employment status, sector and position present | 100% |
Enroll_Major_CIP reconciled to the programme
record |
Before every period census |
| CHEDS field-set validation run | At registration and again before each census |
| Contact data re-confirmed | At every re-registration, and again at graduation clearance in WF-10 |
| Applicant funnel reconciled | Within 10 working days of the intake closing |
11. Records and evidence
| Record | Retention | Owner | Appendix B exposure |
|---|---|---|---|
| Application, decision and criteria version applied | 7 years | Admissions Officer | Indirect: supports the comparable-criteria judgement behind KPI 2.2 |
| Enrolment record for each academic period | Permanent | Registry | Yes. Registration records demonstrating continuation are the named evidence for KPI 2.2 |
| Learner contact set with the date it was confirmed | Per data protection policy, and at least the period the Ministry may request | Registry | Yes. Appendix B names participant contact data for surveys the university runs, and for substitute data under 1.1, 1.2, 2.4, 2.6 and 3.1 |
| Employment status, sector and position at entry | 7 years | Registry | Indirect: supports substitute-data methodology |
| Dual, joint and mobility registration with the partner agreement reference | Life of agreement plus 7 years | Data Steward | Yes. Appendix B names contact data for students enrolled in dual, joint or mobility programmes, and the formal agreement documents |
| First-academic-period audit trail | Permanent | Registry | Indirect, but decisive if a cohort is queried |
| Applicant funnel counts | 7 years | Admissions Officer | No |
Appendix B readiness. Today, IoL could most likely produce enrolment records and admission decisions within 15 working days, because they live in the registry system of record. It could not reliably produce a dated, complete personal contact set for a past cohort, because contact data is typically overwritten rather than versioned, and it could not produce evidence for a mobility claim because no qualifying option currently exists to claim. The first gap is closed by R2; the second is a WF-01 decision.
12. Risks and controls
| # | Risk | Consequence | Control | Owner |
|---|---|---|---|---|
| 1 | Enroll_1st_Academic_Period overwritten |
A learner silently leaves a cohort already reported; the three-year series stops reconciling | Field locked after first census; changes raised as data incidents | Registry |
| 2 | Denominator built from an annual headcount rather than the autumn period | KPI 2.2 computed on the wrong population, in a direction nobody can predict | Validation check 1 in section 13, run at census and not at submission | Data Steward |
| 3 | Only an employer email captured | Graduate unreachable at 12 months; KPI 1.1 and 1.2 lost through non-response | Personal email and mobile mandatory, re-confirmed annually | Registry |
| 4 | Enroll_Major_CIP inconsistent with the programme
record |
KPI 1.2 relevance matrix returns a false negative that MBRU cannot see | Annual reconciliation with dated sign-off | Data Steward |
| 5 | Non-award participants in the enrolment file | Denominators inflated for 2.2, 4.4 and 5.3 | Registration route separated from CPD and micro-credential registration | Registry |
| 6 | Inbound exchange counted as mobility | Overstatement on KPI 5.3 that fails on evidence | Separate fields, separate validation assertion | Data Steward |
| 7 | Intake structure changes mid-series | Incoherent three-year rolling average for KPI 2.2 | Intake treatment documented in the mechanism field and held constant | WF-26 |
| 8 | Employment data collected without a clear lawful basis or purpose statement | Data protection exposure on a field IoL genuinely needs | Purpose stated at collection; retention and access defined | Data Steward |
| 9 | "First year" left undefined for postgraduate entry | Two analysts produce two defensible and different denominators | Definition decided, written down and referenced from WF-26 | Quality and IQA |
13. Performance measures
| Dimension | Measure | Target |
|---|---|---|
| Capture completeness | Enrolment rows passing full CHEDS field-set validation at registration | 100% |
| Capture completeness | Learners with a personal email and mobile present and dated | 100% |
| Capture completeness | Learners with employment status, sector and position recorded | 100% |
| Capture completeness | Learners whose Enroll_Major_CIP matches the approved
programme record |
100%, zero exceptions |
| Accuracy | Enroll_1st_Academic_Period changes after first
census |
Zero |
| Accuracy | Applicant, offer and enrolment counts reconcile | 100% |
| Accuracy | Inbound exchange rows appearing in any KPI 5.3 numerator | Zero |
| Timeliness | Enrolment record created within 5 working days of acceptance | 95% |
| Service | Admission decision within 15 working days of a complete application | 90% |
| Reproducibility | KPI 2.2 denominator reproducible by a second analyst from records alone | Yes |
The four capture-completeness measures are the ones to watch. Admissions service quality matters for its own reasons, but no admissions service level has ever moved an OBEF score, and a blank contact field has.
14. Change control
| Date | Version | Change | Reason | Approved by |
|---|---|---|---|---|
| 2026-09-02 | 0.1 | Initial draft | IoL OBEF pilot | draft, unapproved |