Higher education Student administration ECTS and diplomas

Custom student information system for higher education

In higher education, the student information system is the register where four things come together that are managed separately elsewhere in the institution: who is enrolled, which programme that student is following, which credits have been earned and which degree certificate results from them. Everything around it relies on it. The learning environment pulls groups from it, timetabling pulls enrolments in course units from it, the finance department derives tuition fees from it, and the national registers expect a periodic data submission from it. If there is an error in the register, that error travels on to the diploma supplement and to the funding data. Appfront builds custom software around that core: additional registration where the package does not bend, integrations with Studielink and DUO, portals for students and lecturers, and the calculation rules that turn individual results into a graduation decision. For universities of applied sciences, universities, non-funded providers in higher education and partnerships that offer programmes across institutions.

The core register of a university of applied sciences or university

A student information system, usually abbreviated to SIS in the sector, is the administrative core of a higher education institution. It keeps track of the person, the enrolment in a programme, the course units that belong to that programme, the credits earned and the final degree certificate. That sounds like four registrations, but it is really one: a result only has meaning within a course unit, a course unit only within a programme of a particular cohort, and a programme only within an enrolment that was valid at the time the exam was taken. That chain is exactly what a spreadsheet or a standalone assessment application cannot hold on to.

What sets higher education apart from other education sectors is that students direct their own programme. They choose elective modules, take a minor in another faculty, spend a semester abroad, apply for an exemption, switch to a related programme and take the credits they have earned with them. Each of those steps changes the set of requirements they must meet to graduate, while the requirements themselves are laid down per cohort and per academic year in the teaching and examination regulations. A student information system (SIS) that does not model this as data shifts the calculations onto the study adviser and the risk onto the examination board.

The second characteristic is that the administration has to reach beyond the institution. In the Netherlands, applications and enrolments run through Studielink, programmes exist only once they appear in the national register of accredited programmes, enrolments and diplomas are reported to the DUO register, and that reporting underpins funding. A system that is internally consistent but does not keep up with the chain is not finished.

You only notice what this means in practice when something goes wrong. A student enrolled on the wrong variant is not in the right group in the learning environment and is missing from the exam attendance list. A course unit with the wrong number of credits produces a grade list that does not match the diploma supplement. An enrolment that was wrong on the reference date resurfaces in the check on funding data. They all come down to the same thing: there is one register that the rest of the institution relies on, and that register has to be explainable, not just populated.

Are you in the right place? This page is about universities of applied sciences and research universities, and about student administration as the core register. If you are looking for a system to track the development of individual pupils, with observations, support agreements and parent communication in primary and secondary education, you want a student tracking system. If you are looking at an institution's wider operations, including timetabling logistics, staff, procurement and the data behind funding, then education ERP is the broader starting point. There, the SIS is one register in a larger landscape; here, it is the subject.

One person, multiple enrolments

The same student can be enrolled in a bachelor's, a pre-master's and a contract course at the same time. The file follows the person; the entitlements follow the enrolment.

The programme differs per cohort

The 2023 requirements apply to the 2023 cohort. A curriculum change must not silently alter the programme of students who are already studying.

A diploma is a decision, not a document

The examination board determines the result. The system must support that decision and keep it traceable, even years later.

Enrolment and admission, where the file begins

Applying for a bachelor's or master's in Dutch higher education runs through Studielink. Students submit their enrolment request there, and the institution receives that request in its own system, enriches it and sends statuses back. That sounds like an integration, but in practice it is a process: an application is not a snapshot but a file that stays in motion for a long time. The student changes their choice of programme, withdraws their request and applies again, submits their previous education details later, chooses a different start date or turns out, on closer inspection, not to be eligible. Each of these events arrives as a message, in an order that is not guaranteed and sometimes with retroactive effect.

That is why the first design question is not which fields you store, but how you handle that stream of messages. A system that overwrites an application with its latest state loses the reason a status changed. A system that records every event and derives the current state from those events can later explain why this student counted on 1 October and that other one did not. That difference is not theoretical: the data that underpins funding is audited every year, and for each enrolment you must then be able to show which conditions were met at which point in time. Recording that a payment was received is not enough; you must be able to demonstrate that it was on time and which tuition fee category applied.

There is a second requirement on the identity side. An institution registers the student under a personal number, usually the citizen service number (BSN), and otherwise an education number for those who do not have one. That number enables data exchange with national registers and is at the same time the most sensitive field in the entire record: it may only be used where the law permits, it does not belong as a search key in an internal portal, and it has no place in an export file sent to a dashboard supplier. Alongside that number sits the institution's own student number, and the two must be kept strictly separate in their function.

The tuition fee then attaches to the enrolment, and it is not an amount you enter but the outcome of rules. Which category of tuition fee someone owes follows from criteria relating to nationality and residence status, and to whether they have previously obtained a degree of the same type. A reduction also applies to certain first-year students. This means the system must derive the category, record the criteria used, and be able to recalculate when personal data changes, because a nationality that is corrected later changes the basis retroactively. In addition, enrolment in higher education is per academic year: re-enrolment is required, and anyone who deregisters mid-year loses the right to sit exams as of the end date. That too is data that goes outside the institution, because deregistration affects the student's student finance.

Admission is a decision that carries a burden of proof

You can only enrol a student once admissibility has been established, and how that is established differs per entry route. For a student progressing from secondary education, it comes down to diploma type, profile and sometimes additional subject requirements set per programme; a missing subject is then a deficiency that must be made up before the start. For the lateral entrant with a foreign diploma, it involves an evaluation of that diploma and a language test. For those who lack the required prior education and are twenty-one or older, there is the admission examination route. For the master's applicant, the question is whether their bachelor's degree grants access, with or without a pre-master's programme and under which conditions. For programmes with a limited number of places, a selection procedure is added, with rankings, placement rounds and the filling of places that become available when someone withdraws.

These are not variations of the same form. They are different decisions with different supporting documents, different decision-makers and different deadlines. What custom software adds here is that the decision itself becomes an object: which requirement was assessed, on the basis of which document, by whom, with what outcome and under which condition. Without that record, the admission decision lives in a mailbox and the student administration has to reconstruct what was agreed every time there is an objection. With it, applicants can see in their own portal what is still expected of them, which is exactly the question that causes most phone calls.

Study programme and curriculum as a data model

This is the hardest part of a student information system, and in practice the part most often left half-solved. A programme is not a single list of courses. It is an accredited programme with a mode of study, full-time, part-time or dual, possibly with specialisations, with a curriculum that differs per cohort, and with requirements laid down in the teaching and examination regulations for that academic year. Beneath that sit course units with a study load, an assessment form and sometimes partial assessments that together form a single result. Alongside that is free elective space that the student fills in themselves, with a minor at another faculty or with courses at another institution.

Model it as a flat list of courses and you get three predictable problems. A curriculum change affects students who started under the old regulations. A course that is withdrawn makes credits already earned worthless unless someone records what replaced it. And the question of whether someone can graduate can no longer be answered without manual work, because the requirements sit in a PDF and the results in a database. The programme regulations for each year should therefore exist as data, not just as a document, with a validity period and a reference to the adopted text.

That same structure is also what the rest of the landscape needs. The digital learning environment wants groups and participants per course, timetabling needs to know how many students have enrolled, and the examinations office needs to know who is eligible for each assessment. They should all draw on the core register, not on their own copy that drifts out of sync unnoticed.

Beneath the curriculum sits a process of its own: enrolling students on courses and assessments. This involves capacity limits, priority rules for students for whom the course is compulsory, enrolment periods that open and close, and the question of what happens if someone withdraws too late. The same applies to assessments: who is eligible, how many attempts has someone already used, and is there a condition that must be met first? This is exactly where administration and teaching meet, and where a system that only records what has already happened lets the organisation down.

Programme, variant and cohort

The accredited programme with its mode of study and specialisations, and beneath it, per intake year, the curriculum that applies to that cohort.

EC

Course and study load

Credits, assessment format and partial assessments that together lead to a single result, with the weighting by which that result is determined.

Elective space and minors

Free space that the student fills, including with courses from another faculty or institution, and which is still checked against the requirements.

Entry requirements and assessment conditions

Conditions for taking part in a course or an assessment, checked at enrolment rather than after the fact.

Transitional arrangements

When the curriculum changes, recording which old course is replaced by which new one, so that credits already earned still count.

Learning outcomes and microcredentials

Flexible part-time education describes courses as learning outcomes, and shorter modules lead to a recognised certificate alongside the degree.

ECTS and results registration

The European credit system gives higher education a common unit of account: a full academic year is worth sixty credits, and under Dutch law one credit equals twenty-eight hours of study load. A university of applied sciences bachelor's covers 240 credits, a research university bachelor's 180, and a master's sixty or more. That unit makes study load comparable between institutions and between countries, which is precisely why it must not be free input in the administration. Credits are awarded not for effort but for a completed course, so the question is not how many credits someone has, but on the basis of which result.

That is where the real work begins. A result for a course unit often comes from partial assessments with a weighting, sometimes with a minimum requirement per component that the weighting must not compensate for. The rounding rule differs per programme: to the nearest half, to the nearest whole number, or no rounding below a certain threshold. For a resit, the regulations determine whether the highest or the most recent result counts. An exemption is not a grade but is still a reason to award credits, so it counts towards credit totals and not towards the average. Results can have a period of validity, and an expired result must visibly show as expired rather than quietly disappear. Each of these rules is set per programme, and every rule that is not in the system ends up being applied by a staff member with a calculator.

The weighted average is the underestimated component. It is used for admission to a master's programme, for a distinction (judicium) and for selection within the institution, and almost every programme calculates it slightly differently: weighted by credits or not, with exemptions included or not, with the failed attempt of a resit included or not. As long as that average is calculated in a spreadsheet, it is a decision with no traceability. In the register it should be a calculated value with a readable explanation: which results were included, with which weighting, and which rule was applied.

Data entry calls for its own rigour. Grades often arrive in bulk from a learning environment or from a testing and examination platform, and that is fine as long as the core register remains the established source of truth. Who may enter a result, who may publish it and who may still change it after publication are three different authorisations. A change after publication should have a reason, a decision-maker and a timestamp, because that is the trail a student, an examination board or an auditor will fall back on years later. Registration of fraud or an irregularity belongs in a separate, restricted-access part of the file, kept apart from the regular grade list.

The same data feeds study progress, which is a second application with its own requirements. First-year students receive advice on whether to continue their studies based on the credits they have earned at a given moment, and that advice is a decision with consequences. It should therefore be calculated reproducibly, with a fixed reference date, with the warnings that preceded it and with room to take personal circumstances into account. In addition, the study adviser needs a picture that goes beyond a credit total: which components are missing, what agreements have been made and which adjustments apply. And students themselves want to see in their own portal how they are doing relative to their programme, not relative to an average.

That is precisely where the file becomes sensitive. A request for an accommodation due to a disability, a conversation with the student counsellor, a payment arrears case or a fraud file are not data that belong on the general student screen. They belong behind a separate authorisation, with a record of who has viewed them. Authorisation in a student information system is therefore rarely a simple role: an examiner sees their own course units, a study adviser their own programme, an administrative staff member a faculty, and a decentralised administrator may configure but not view. Retention periods also differ per type of data, which means that clean-up is a built-in function and not an annual manual task. The same rule applies to test and acceptance environments: they should not contain real student data.

  • Weighting of partial assessments with a minimum requirement per component
  • Rounding rules per programme, in the system and not in someone's head
  • Highest or latest attempt, according to that year's regulations
  • Exemptions as a reason for credits, with their own code
  • Validity period of results is visible, not discarded
  • Weighted average as a calculated value with an explanation
  • Entering, publishing and amending as separate permissions
  • Every change after publication recorded with reason, decision-maker and time
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

From results to a degree certificate

In higher education, a degree certificate is not a file that comes out of a printer, but the outcome of a decision. The examination board establishes that the examination has been completed, and at that moment a result date, a degree, possibly a specialisation and possibly a distinction come into being. That decision rests on a check that is far more laborious than it looks: does the set of results achieved meet the programme requirements as they applied to this cohort, including the free electives, the requirements for the final project and the transitional arrangements from mid-programme curriculum changes?

Why the graduation check so often remains manual work

Because the requirements live in a document and the results live in a system. The regulations may state, for example, that the free electives must form a coherent whole, that a proportion of the credits must be achieved at a certain level, that a minor may not overlap with the compulsory components, and that the final project may only begin once a number of components have been completed. As long as nobody captures those conditions as rules, a staff member checks them student by student with the grade list alongside. That works with a few dozen graduates and breaks down with hundreds, precisely in the period when everything has to happen at once.

What custom development delivers here is a check that gives the student and the board the same picture: for each requirement, whether it has been met, with which result, and what is still missing. The outcome is advice, not an automatic decision, because the board retains its own authority and can deviate on the basis of an exemption or a hardship clause. That is exactly why a deviation should also be recorded as a deviation, with who made the decision and on what grounds. A student who disagrees with a decision of the examination board can appeal to the board of appeal for examinations, and the question is then not what the system calculated but what was decided and why.

The degree certificate itself comes with a second set of requirements. A higher education degree comes with a diploma supplement that explains the programme, the level, the study load in credits and the grading system, so that an employer or a foreign institution can place the document. Anyone who leaves the programme without a degree is entitled to a statement listing the components they did complete. A certificate is, as a rule, issued only once, and anyone who loses their copy does not get a duplicate but a digital extract from the national diploma register. That means that delivery to that register is part of the graduation process and not an administrative afterthought.

Retention is the final piece, and the part most often forgotten in self-built systems. Degree data must still be findable and verifiable decades later, even if the system that produced it no longer exists. That calls for a readable export format, for signatures that remain verifiable, and for an agreement on which data may, in fact, be deleted. For shorter modules there is also the digital variant: a signed certificate that the holder can share themselves and that a recipient can verify without calling the institution.

Graduation check as a rule set Result date and degree Distinction Diploma supplement Statement of completed components Digital signing Delivery to the diploma register Certificates for short modules Long-term archiving

Exchange with national registers and chain partners

A student administration in higher education never stands alone. At the front end, applications arrive from Studielink and statuses flow back to it. An enrolment can only exist for a programme listed in the national register of accredited programmes, with the code that belongs to it, and that recognition depends on the programme's accreditation. At the back end, enrolments and diplomas go to the DUO register, where they underpin funding and where the student's financial support depends on them. An enrolment that is recorded incorrectly there is not a cosmetic administrative error: it affects the institution's money and the student's money.

These deliveries are not one-way traffic. You submit, you receive feedback, and that feedback includes rejections you have to fix. Corrections arrive with retroactive effect, sometimes across a reference date, and then a data item changes for which a file has already been sent. The part that is most often underestimated when building in-house is exactly this: not the sending, but keeping track of what you sent and when, what was accepted, what was rejected and what has changed since. Without that administration of the administration, every discrepancy turns into a search through log files.

Within your own landscape, data exchange works best through an open standard rather than through one integration per application. The sector has a shared specification for education data for this purpose, which lets a learning environment, a timetabling application, a student app or a dashboard retrieve the same data in the same way. The same applies to logging in: federated authentication and an institution-independent identity make it possible for a student to take courses at another institution without a second account. Anyone offering education across institutions needs this, because an enrolment on a unit must then come back elsewhere as a result in the student's own record. For the learning environment itself, a targeted integration is often the fastest route, for example an itslearning integration.

International mobility has its own chain. For exchange students there are European agreements to exchange learning agreements and nominations digitally, and to retrieve results achieved elsewhere in a standardised format rather than from a scanned piece of paper. That saves more than typing: it makes the origin of a result verifiable at the moment the examination board bases an exemption or an inclusion in the programme on it.

When an off-the-shelf package is the better choice

The Dutch market for student information systems in universities of applied sciences and research universities is not a blank spot. A small number of mature packages serve the vast majority of institutions, and these packages already have the Studielink integration and the DUO delivery in place, including keeping up with changes in legislation and national standards. For an institution that follows the usual pattern, meaning cohorts, a regulation per academic year, exams and graduation per programme, that is the wiser route. Your effort then shifts from building to configuring, and with a core register that is more honest work than it sounds.

Custom development pays off in fewer situations than vendors suggest, but in clearly identifiable ones. The first is an education model that doesn't fit cohort thinking: flexible part-time education where students join per learning outcome and set their own route, or a non-funded provider that works with continuous intake rather than academic years. The second is an institution that wants to keep the package as its register but gets stuck on everything around it: the application portal, the study adviser's guidance, graduation checks, reporting to the programme director. Building that layer on the data from the package is often the shortest route to a difference people actually notice. The third is collaboration between institutions, where none of the existing systems owns the process.

The downside is part of the picture too. With a custom build, keeping up with changing regulations and national standards falls to your own organisation, and in this sector that is no small item. That is why the middle route is often the best answer: the package remains the source for person, enrolment and result, and the custom work goes into the processes, portals and rules that set you apart. How we make that trade-off, and what does and doesn't belong in the custom work, is something we would rather discuss before a quote process begins.

If your institution uses Osiris and your own systems need to connect to it, take a look at our Osiris integration.

  • Message exchange with Studielink, including withdrawals
  • Programme codes from the national programme register
  • Delivery of enrolments and diplomas to DUO
  • Feedback, rejections and recovery as a process of their own
  • Retroactive corrections across a reference date
  • Open standard for education data within the landscape
  • Federated login and an institution-independent identity
  • European exchange for mobility and results achieved

Frequently asked questions about a student information system

The student information system is the register: person, enrolment, programme, result and diploma. The digital learning environment is where the teaching itself takes place, with materials, assignments and feedback. Grades often originate in that learning environment or in an assessment platform, but only take on meaning once they have been confirmed and published in the core register. The learning environment pulls groups and participants from the register; the register does not pull truth from the learning environment. Reverse that division of roles and you end up with two sources with different grades and no rule to decide which one applies.

A student tracking system follows the development of individual pupils, with observations, support agreements and communication with parents, and is mainly suited to primary and secondary education. An education ERP covers an institution's broad business operations, including timetabling logistics, staff, procurement and the data underlying funding. A student information system for higher education sits in between as the core register: enrolment, curriculum, credits and diplomas, with the exchange to Studielink and DUO. In a broader landscape, that register is the source the other systems build on.

Anyone offering publicly funded higher education in the Netherlands receives applications and enrolments via Studielink and delivers enrolments and diplomas to the register at DUO. That exchange is not a one-off import but an ongoing process with messages, statuses, feedback and rejections that have to be corrected. The hardest part is not sending, but keeping track of what you delivered when, what was accepted and what has changed since. When corrections apply retroactively across a reference date, you must be able to explain that later.

A full academic year is worth sixty credits, and under Dutch law one credit equals twenty-eight hours of study load. Credits therefore belong to a passed course unit, not to a student as a loose number. The model must handle partial assessments with a weighting, rounding rules per programme, the choice between the highest and the latest attempt, exemptions as a separate result type, and a validity period that can cause a result to expire. The weighted average should also be a calculated value, with an explanation of which results were included and with what weighting.

Entering, publishing and changing after publication are three different authorisations, and a system should treat them that way. For the examiner, entering and publishing are routine work; a change afterwards affects an established result and therefore needs a reason, a decision-maker and a timestamp. The examination board remains authorised to determine the outcome and to make exceptions, for example on the basis of an exemption. That trail is what a student, an examination board or an auditor falls back on years later.

Often yes, and for many institutions that is the wiser route. A small number of mature packages serve most of higher professional and university education, with messaging to Studielink and delivery to DUO already built in. If your education follows the usual pattern of cohorts, a regulation per academic year and graduation per programme, you buy that off the shelf. Custom development becomes interesting for flexible education with learning outcomes, for continuous intake without academic years, or when the package works fine as a register and the processes around it are the problem.

Related services

Student tracking system

If it is about tracking individual pupils, with observations, support agreements and parent communication in primary and secondary education, you belong with a custom student tracking system.

Education ERP

If the question goes beyond the student administration, to timetabling logistics, staff, procurement and the data underlying funding, then building an education ERP is the broader starting point.

Examination software

If the bottleneck is in the assessment itself, with a question bank, administration, marking and cut-off scores, then building examination software is the right page. The result then lands in the core register.

A closer look at your student administration

Tell us three things: how an application moves through your organisation today, where the graduation check is still done by hand, and what happens when DUO rejects a delivery. Those three answers usually show whether the bottleneck lies in the register itself, in the processes around it, or in the integrations between them. Even if the outcome is that you are better off staying with a package, that conversation gives you a sharper picture of what you should and should not build.

Edit content