NOMARQUE 9.5Eight capabilities. One connected student record.Explore NOMARQUE 9.5
Student operations and compliance platform

One student record.Every college workflow.Compliance built in.

NOMARQUE brings admissions, registry, teaching, assessment, finance and student support together in one platform for UK higher and further education.

Keep student records accurate, connect everyday college operations, and produce HESA, ILR and funding returns from the same trusted data.

Your statutory year, in one place2026/27
HESA Student returnBuilt from the live record, codes checked to the year
Ready
ILR returnChecked against all 843 DfE validation rules
Checked
Student Loans CompanyPayment report matched to student fees
Matched
GLA Adult Skills FundFunding worked out from the learner record
Calculated
OfS B3 continuationContinuation tracked from course start dates
Monitored

Built to the published specifications of

  • HESA
  • Office for Students
  • Department for Education
  • Student Loans Company
  • Greater London Authority
See it working

One change. Every team kept in step.

Follow three everyday situations through NOMARQUE and see what happens across the college when one person records one thing.

The problem

Disconnected systems create work, and risk.

In most colleges, student records, finance, attendance and statutory returns live in separate systems and spreadsheets. Every handover is a chance for the data to disagree.

  1. 01Duplicate records create avoidable work

    Admissions, registry and finance each hold their own copy of a student, and reconcile them by hand.

  2. 02Compliance becomes a deadline-driven exercise

    HESA and ILR files are pieced together at the last minute from exports that are already out of date.

  3. 03Student risks remain hidden between teams

    Attendance, marks, fees and support sit with different teams, so no one sees the full picture in time.

The solution

The student record is the centre of everything.

Teams work from one shared student record, reducing duplicate entry and keeping operational and compliance data aligned.

Your teams

AdmissionsApplications and offers
RegistryEnrolment and status
Teaching staffRegisters and marks
FinanceFees and payments
Student supportCases and plans

One student record

Every change kept with its date. Nothing already recorded is overwritten.

  • Course and statusFull history
  • AttendanceEvery register
  • Marks and awardsBoards and resits
  • Fees and fundingInvoices, SLC, GLA
  • Support and casesAccess controlled

What it produces

HESA Student returnHigher education
ILR returnFurther education
SLC confirmationsRegistration and attendance
GLA fundingAdult Skills Fund
Management reportsBuild your own
The platform

Every college workflow, connected.

Eight connected areas cover the full student lifecycle, from the first application to the final award.

NOMARQUE 9.5

Eight capabilities. One connected student record.

NOMARQUE 9.5 brings more of your college's operations into one platform, connecting more of the work your teams do every day.

Explore NOMARQUE 9.5
  1. Finance
  2. Student Loans Company
  3. Exams and moderation
  4. Student support
  5. Reports and automation
  6. Moodle
  7. GLA Adult Skills Fund
  8. Security and data protection
The difference

Compliance built into the daily work.

Returns and funding come from the records your teams already keep. NOMARQUE builds and checks them; your college submits them as it does today.

Higher education

HESA and the OfS

The Student return, built from the live record each time it is opened.

How it works
  1. Every coded field is checked against HESA's valid entries for that year's collection, and every field against its length limit.
  2. Records needing a decision, such as leavers and breaks, are listed to review before the final return.
  3. Each version is saved as a snapshot that can't be changed, compared side by side, and tracked to submission.
Collection
C26056, the 2026/27 Student return
Also covers
B3 continuation, IMD, TUNDRA, POLAR4, ABCS
Submission
By your college, to HESA
Further education

ILR and DfE

The Individualised Learner Record, built, checked and compared before it reaches DfE.

How it works
  1. Enrolled learners are brought into the return with the learning aim their course gives.
  2. The file is checked against DfE's validation rules and DfE's own reference data: learning aims, postcodes and employers.
  3. Each problem points to the learner it belongs to. Files from your current system can be read in and compared.
Specification
ILR 2026/27
Rules
843 DfE validation rules, version 5 (22 Oct 2026)
Submission
By your college, to DfE
Funding and finance

Student Loans Company and GLA

The weekly SLC routine and adult funding, handled inside the student record.

How it works
  1. SSNs are checked for the right format and check letter as they are typed, and can be uploaded in bulk.
  2. Registration, attendance and changes of circumstances are prepared in bulk; a person confirms each withdrawal fee before it is sent.
  3. SLC's weekly payment report is read in and matched to each student's fees. GLA funding is worked out month by month.
SLC files
Layouts confirmed with your own SLC exports during set-up
GLA
Adult Skills Fund, built to GLA's published 2026/27 rules
Security and data protection

Records you can stand behind at an audit.

Security, access control and accountability built into every student record, for providers who hold special category data and safeguarding records.

London region

The application and its database run in Google Cloud's London region. Google encrypts data in transit and at rest.

Two-step sign-in

Covers every staff login, including external examiners. Access can be set to end on a date.

A sealed audit trail

Each night, new audit entries are sealed with a chained SHA-256 fingerprint. A check then shows any entry changed, removed or added afterwards. Seals can be kept outside the database, so even a database administrator cannot alter the trail unnoticed.

Safeguarding kept apart

Concerns, referrals and outcomes are visible only to named staff, and are left out of reports and data requests.

Data protection built in

Subject access exports, erasure and anonymisation, and keeping periods for each kind of record.

Each college kept apart

Access rules are enforced by the database itself, not only by the screens.

Backups and restores

Daily backups are kept for seven days. Every release's checks restore a backup and confirm the copy matches the original.

Alerts if it goes down

The system is checked continuously, and an alert is sent if it stops responding.

Every role has the access it needs. Nothing more.

Start from ready-made roles, then add or remove single rights for any person. Open the table to see what each role can do.

See what each role can do
Default roles shown. Any right can be given to, or taken from, one person.Safeguarding is given to named staff by the super admin.
Evidence

Tested end to end before every release.

What we measure, and what NOMARQUE does with a realistic college's data.

4,900+automated checks pass before a release ships
0.3sto save a register, with 40 people using the system at once
39sto check an 8,000-learner ILR against every DfE rule
843DfE validation rules, each built and tested one by one
ILR check · demonstration college47 learners, 0 errors

Further education learners checked against DfE's full reference data. The only finding was the demonstration college's invented provider number.

0 errors, 0 warnings on learners
Upgrade · 9.3.1 to 9.5Existing data kept

A college already on the previous version was upgraded with all its data in place. Running the upgrade again changed nothing.

Upgrade repeatable
Pre-release review · 9.517 findings, all fixed

Money handling and security were each reviewed before release. Every finding was fixed and given its own check, and each original test case is now refused.

Every finding re-tested

How these were measured. Release checks cover the database, the server and every screen in a real browser. The register figure is the typical time to save one register with 40 simulated users working at the same time, on a two-processor test server. The ILR figure is a generated college of 8,000 learners checked against the ILR 2026/27 rules (DfE version 5) on the same server.

The demonstration college, Linden Row, holds invented data only.

Implementation

Moving to NOMARQUE, step by step.

You keep your current system running until NOMARQUE has produced the same returns from the same data.

Set up your college

Courses, campuses, intakes and fee rules, with the college set up for higher education, further education or both.

Bring your records in

Student records uploaded in bulk. Existing ILR files read in and checked exactly as they arrive.

Give each team its access

Ready-made roles for registry, admissions, finance and teaching staff, with two-step sign-in switched on.

Compare, then switch

Build your returns in NOMARQUE and compare them with your current files before you go live.

Why NOMARQUE
Built by someone who understands college operations, for the people who sign off the returns.

NOMARQUE was shaped by the real responsibilities of registry work: keeping student records accurate, managing complex academic decisions and preparing statutory returns.

Fee status has three owners

Admissions assesses, finance approves, and registry enrols only after both.

Withdrawals keep their reason

Withdrawn for attendance and withdrawn for finance are separate statuses, as registries need them.

A final-year fail stays open

The record stays open until the case closes: termination, unit award or completion.

Resits follow the rules

A passed resit is capped at the pass mark, and the assessment board decides what happens next.

Questions

What registrars ask us first.

Do you support higher and further education?

Yes. Each college is set up as higher education, further education or both, and staff switch between them from the menu. The menu then shows the HESA return, the ILR return, or both.

How do we move from our current system?

Student records are uploaded in bulk and existing ILR files are read in and checked. You then build your returns in NOMARQUE and compare them with your current files before switching over.

Does NOMARQUE submit our returns for us?

No. NOMARQUE builds and checks the HESA and ILR files from your records. Your college submits them to HESA and DfE through their own systems, as it does today.

Does NOMARQUE check SSNs with the Student Loans Company?

NOMARQUE checks that each SSN is in the right format with a valid check letter as it is typed. It does not look the number up with SLC.

Does it work with Moodle?

Yes. Assignments, resources, feedback and grades are kept in step between NOMARQUE and your Moodle site, hourly or on demand.

Do updates affect our data?

No. Every release is tested by upgrading an existing college's data to the new version, and running the upgrade a second time changes nothing.

Book a demo

See how NOMARQUE could work within your college's existing processes.

Personalised walkthroughNo obligationHigher or further education

What we'll cover

  • Your HESA or ILR reporting workflow
  • Admissions, attendance, assessment and finance
  • Roles, permissions and data security
  • Data migration and implementation

What happens next

  1. We contact you to agree a time.
  2. We confirm which returns and processes matter most to you.
  3. We show NOMARQUE working through them.

Book your personalised demo

ILMOVEAI LTD will use these details only to arrange your demo and follow up with you. See our privacy policy.

Back to NOMARQUE Release notes

NOMARQUE 9.5

Eight capabilities, built and tested together, bringing more of your college's operations into one connected student record.

Released 2 November 2026Upgrades from 9.3.1 with all data keptFor higher and further education
Quality

How 9.5 was checked

  • Every database, server and screen check passes on a fresh build.
  • Money handling and security were each reviewed before release. All 17 findings were fixed, each with its own check.
  • An existing 9.3.1 college upgraded to 9.5 with its data kept, and a second upgrade changed nothing.
  • The Moodle link was tested against a real Moodle installation.