Bring your data in
Lyceum Data reads an extract from your records system, a secure file transfer or a spreadsheet export. Access is read-only. Each extract is kept as a fixed copy, so any run can be repeated and explained later.
The product
Everything between your records system and a submittable return.
Lyceum Data sits alongside your student record system. It reads your data, puts it in HESA’s shape, checks it and gives your team one list of what needs attention.
Works with SITS, Banner and systems built in-house
How it works
Five steps, run as often as you need.
Run the whole return overnight, or re-check a single faculty in minutes after a fix.
Map it once
Your fields are mapped to the HESA data model in rules your team can read, review and approve. Complicated derivations, such as the main source of tuition fees, become visible logic instead of a spreadsheet only one person understands. Every change creates a new version, and you can preview its effect before it goes live.
Check against every rule
All of HESA’s quality rules run against your data, including the ones that depend on more than one field, such as a postcode that is only required when the student’s domicile is in the UK. You can focus a run on one faculty, one cohort, the forty students you just corrected or only the rules that failed last time.
Resolve what’s found
Every finding becomes an exception your team can assign, discuss and close. Results are compared run by run, so you can see what is new, what is fixed and what has come back.
Generate and submit
Lyceum Data builds the HESA XML against the published schema and brings the results of HESA’s own validation kit into the same exception list. An evidence pack records the data, mapping and rules behind each result for internal sign-off.
Exceptions and verdicts
One list of issues, with the reason and the regulator for each.
Each exception names the rule that raised it, explains the problem in plain English and shows the value in your records next to the value sent to HESA. That tells you straight away whether to fix the data or the mapping.
- A verdict for each regulator: would reject, or warn
- Assign to a colleague, add notes, track the fix
- Suppress or accept a risk, always with a reason and the right approval
- Issues that return after being fixed reopen automatically
- Export to Excel for sign-off meetings, or feed into your own systems
Exception detail
Engagement · MSTUFEE
Main source of tuition fees is blank. This student has a sponsor record, so a fee source is expected.
- Value in your records
blank- Value sent to HESA
blank- Expected
- A valid fee source code
- First seen
- Run 198
OfS · warnMedr · would reject
Corrections
Fix it in Lyceum Data when you can’t fix it at source yet.
Some corrections take weeks to make in the records system. Lyceum Data lets authorised staff apply approved corrections to the return without changing your source data.
Approved corrections, no code
Build a correction from conditions and actions, such as setting a value when a field is blank for a given course. Preview exactly which records change, then approve it.
Source data never changes
Corrections apply only to Lyceum Data’s working copy. The original value, the corrected value, who approved it and why are all recorded.
Only what changed is re-checked
After a correction, only the affected records and rules are checked again, so you see the result quickly.
Records that don’t fit yet
Records that can’t be matched to HESA’s model, such as a student without a linked course, are kept in a separate list from rule failures, because they need a different fix.
Code lists you can trust
HESA code lists and your own local translations are managed and versioned, and each run records exactly which versions it used.
Talk to us about your next return
Tell us how your return is prepared today. We’ll show you what Lyceum Data would do with your own data.
Talk to us or email askus@lyceumdata.com