Home · Education · Student tracking system app
Industry · Education & EdTech

Custom student tracking system app.

A custom student tracking app that fits your teaching model: progress registration, test results, observations, student records and a parent portal in one seamless flow. Built vendor-independent, integrated with ParnasSys, Magister, SOMtoday, Eduarte or Osiris, with GDPR, ECK iD and AI Act compliance from sprint one.

SectorPrimary & secondary education
SectorVocational education (MBO)
SectorHigher education (HBO & WO)
SectorHealthcare competency register

The student tracking landscape in numbers.

~7.700
Primary and secondary schools using a student tracking system
~60
Vocational institutions (MBO) typically work with Eduarte or Eduarte equivalents
~80%
Of higher education uses OSIRIS or Studielink in the chain
5
Standards we integrate with as a matter of course: UWLR, OSO, ECK iD, Edu-iX, Entree

Source: Kennisnet, SURF, DUO and our own count among education clients.

A student tracking package covers the basics, not your didactic reality.

The Dutch education market for student tracking systems has consolidated. ParnasSys runs in most primary schools, Magister and SOMtoday dominate secondary education, Eduarte is the de facto choice in vocational education (MBO), and Osiris and Studielink handle the central flows of HBO and WO. These packages do what they were built for: they record grades, register attendance, deliver reports on time and export neatly to DUO. They work as administration. They rarely work as a didactic tool.

The problem starts when your institution needs something more distinctive than the package offers. A special-education school that wants to track a detailed development perspective plan (OPP) for each pupil, with goals, evaluations and adjustments. A vocational programme that wants to store observations in its own rubric structure, with photo evidence and voice recordings. A university of applied sciences that wants to link inclusive education to career guidance and internship performance in a single student profile. A healthcare programme that keeps a competency register alongside progress: which procedures may this student already perform, who signed them off, when does the authorisation expire? Flows like these don't fit into a field the package vendor once designed for the whole of the Netherlands.

On top of that, the packages set their own pace. A wish your care coordinator considers urgent this year only reaches the roadmap two releases from now, if it fits at all. There have historically been two answers to that problem: either you live with it, or you build a specialist app that works alongside the package, with integrations via a custom LMS approach or on top of the existing SIS, and that is what this page is about. We explain a thorough comparison of package versus custom in our guide to custom LMS versus package.

We have spent years building this custom student tracking system (SVS) layer together with educational institutions and healthcare training programmes. It doesn't replace what already works; it adds a layer of your own that captures the specific flows of your institution: individual development plan (OPP) management for special education, an observation app for teachers in vocational education (MBO), drop-out monitoring for study career counsellors in higher professional education (HBO), a competency register for a teaching hospital. One view of each student, your own data, your own source code, and integrations you don't have to rebuild with every package update. For the broader education overview, see our education app development page, and for the service layer around a single programme, see building a programme app.

Your own SVS flow for every level of education.

A student tracking system for a special education school is something very different from one for a higher professional education programme or a teaching hospital. Below, for each level, you'll find what we typically build, with which integrations and which compliance requirements.

Primary & secondary: inclusive education and the development perspective plan

In primary and secondary education, internal support coordinators, mentors and care coordinators work with a view of the student that a packaged SVS only covers for the basic flows. For pupils who need extra support, ParnasSys's standard OPP rarely suffices: it lacks structure for goals per subject area, evaluation moments, parental signatures on the OPP, and the link with the educational psychologist who sits outside the school.

We build a specialist app alongside it: an OPP module with a clear goals tree, evaluations that trigger scheduled moments, a parent portal with digital signatures, and a file that can be exported as a summary to the Samenwerkingsverband Passend Onderwijs (regional inclusive education partnership). For test results and observations, we build a teacher app in which the class teacher can record an observation with photo, audio and rubric in thirty seconds, on the move, in the classroom, without four tabs open. Data syncs with ParnasSys via UWLR, with BSN pseudonymisation and ECK iD exchange.

For secondary education, we build on top of Magister or SOMtoday. There we typically build a mentor dashboard with attendance, grade trends, subject progress and care indicators on a single screen, with a click-through per student to a file that only authorised mentors and care coordinators may see. Mentor conversations are recorded in a structured way, and dropout-risk signals come from clear rules rather than an opaque algorithm.

  • OPP moduleGoals per learning area, evaluations, parental signatures and a summary export for the regional partnership.
  • UWLR + OSOStandard integration with ParnasSys, Magister and SOMtoday for student data and transfers between schools.
  • Observation app for teachersQuickly record an observation with photo, audio and rubric, made for the classroom, not for behind the desk.
  • Parent portalAccess to reports, the OPP and attendance, with digital parental signatures and logic for separated parents.

MBO, HBO/university and the competency register.

MBO (secondary vocational education): Eduarte has become the dominant player in MBO, with SOMtoday as the main alternative. For basic administration these keep working; for the practical learning context we almost always build a custom layer. An MBO programme in healthcare or technology wants to see performance at the work placement as clearly as the grades from a written test, and that data is never fully in the package. We build a practice portfolio with rubrics, a feedback loop between workplace supervisor and teacher, photo or video evidence, and sign-off moments that follow your institution's examination regulations. For internships and BPV (work placements), we build a three-party flow between student, workplace supervisor and BPV coordinator. Everything with audit logs that comply with the SaaS-Toets-Convenant and with ECK iD as a pseudonymous identifier, so citizen service numbers (BSNs) don't unnecessarily cross supplier boundaries.

HBO & university: Here everything runs centrally via Studielink, OSIRIS and local variants of them. The packaged student information system covers enrolment, exam administration and grade registration. The pain lies in everything that touches on student guidance: study career counselling (SLB), tutor meetings, thesis projects, placement supervision, alumni monitoring. We build an SLB app in which tutor, student and study adviser share the same timeline, with meeting notes, goals and, where desired, a dropout-risk indicator that comes transparently from clearly defined rules (and not from a black-box model). For services such as AI support for drop-out prediction, we build the layer on top with explicit AI Act care: bias tests, human review, transparency reporting, opt-out.

Competency registers in healthcare — Healthcare institutions that provide training (teaching hospitals, mental health organisations, elderly care providers) must keep track, for every employee or student, of which reserved procedures they are authorised to perform, which learning objectives they are still being assessed on, when an authorisation expires and which annual reassessment is required. The combination of the Wet BIG, the Kwaliteitskader Verpleegzorg and NEN 7510 makes this a distinct branch of student tracking systems. We build competency registers that link procedures to learning objectives, training dates, supervision hours and sign-off moments — with a dashboard for the practice educator and automatic alerts when an authorisation is about to expire or a reassessment is due. Integrations with Workday, AFAS HRM and Nedap Ons are standard.

Specialist variants — Besides these four main groups, we also build portfolio apps for educational publishers that track teachers and pupils across multiple teaching methods, dyslexia tracking systems for educational care providers, Dutch as a second language (NT2) tracking systems for integration courses and sports performance tracking systems for elite sports academies. The same principles always apply: vendor-independent, integrations via open standards, and code ownership with the institution.

Compliance is not an afterthought in a student tracking system.

A student tracking system (SVS) collects extremely sensitive data: pupil progress, care indicators and sometimes medical context in special needs education or healthcare programmes. From sprint one we work within the GDPR for education (AVG-O), the Privacyconvenant Onderwijs 4.0, NEN 7510 for healthcare variants and the AI Act for anything involving prediction.

GDPR for education (AVG-O) and Privacyconvenant Onderwijs 4.0

The stricter education-specific GDPR layer

In addition to the general GDPR, the education sector has its own sector-specific framework: the Privacyconvenant Onderwijs (current version 4.0) and the associated assessment by SIVON and SURF. Among other things, it includes additional safeguards for processing pupil data, a standardised data processing agreement with education suppliers, and clear rules on which data may and may not be shared with third-party suppliers. We follow this convention by design and, as standard, deliver the corresponding data processing agreement and sub-processor registers.

BSN, ECK iD and pseudonymisation

Identity without the BSN wherever possible

The education sector uses the BSN (citizen service number) as the statutory unique identifier towards DUO and for funding. For everything outside that — exchanges with suppliers, integrations between schools, the parent portal — we work with ECK iD by default: a pseudonymous identifier issued by Kennisnet that keeps the BSN out of the chain. Pseudonymisation is not an option but the default; the BSN is only used where the law requires it.

UWLR, OSO and Edu-iX

Open standards for data exchange

For exchanging pupil data between schools we work with OSO (Overstapservice Onderwijs); for exchange with suppliers and teaching methods with UWLR (Uniforme Webservice voor Leerresultaten); and for central identity exchange with Edu-iX and — in higher education — with SURFconext via Entree. All three standards run through a single abstraction layer, so switching supplier later does not require a complete recode and your institution can replace suppliers independently in the future.

EU AI Act — high-risk (Annex III)

Predictions and assessments under responsible AI

The EU AI Act explicitly names education and exam admission as high-risk contexts in Annex III. This means that drop-out prediction, automatic grouping by level and AI-based admission assessments fall under a stricter regime: governance documentation, bias tests across gender, background and disadvantage criteria, human review before any decision on leaving a programme, and transparency reporting to the supervisory authority. We build this layer with explicit AI Act care and advise against building in autonomous decisions about pupil progression, even if the technology could do it.

SaaS-Toets-Convenant

Assessment software in line with the Education Sector Covenant

Assessment results that end up in the student tracking system (SVS) fall under the SaaS Assessment Covenant for Education. It sets requirements for audit logs, identity verification and secure storage, and for the institution's ability to build in a second-opinion flow in case of doubt or objection. We follow that covenant and deliver the corresponding audit trail as standard.

WCAG 2.2 / EAA

Accessibility for students, parents and teachers

Since the European Accessibility Act of 2025, WCAG 2.2 AA is mandatory for public education apps and for the parent portal. We test with JAWS, NVDA and VoiceOver, build full keyboard navigation, and deliver an accessibility statement that can be accepted by Stichting Drempelvrij or a comparable audit body.

NEN 7510 (healthcare variant)

Information security for competence registers

For competence registers in healthcare, NEN 7510 applies as the security standard, and the Kwaliteitskader Wijkverpleging (district nursing quality framework) or the Kwaliteitskader Verpleegzorg (nursing care quality framework) affects the processes to be followed. We build access management that aligns with these standards, with fine-grained role setup for practice educators, supervisors and students, and with audit logs that can be shown during an inspection visit.

Seamlessly connected to your existing student tracking ecosystem.

We rarely replace your SIS/SVS package. We build alongside it and integrate via the open education standards. Below are the vendors we work with as standard.

ParnasSys
SVS · Primary education
Magister
SVS · Secondary education
SOMtoday
SVS · Secondary & vocational education
Eduarte
SVS · Vocational education
OSIRIS
SIS · Higher professional & university education
Studielink
Central application system for higher professional & university education
Kennisnet (Entree)
Identity federation
SURFconext
SSO · Higher education & research

Standard integrations, with your own specialist app on top.

We have standardised the integrations mentioned above across multiple education projects. On a new project, we set up the integration with the same abstraction layer, which means fewer integration bugs, a working flow within just a few sprints, and functional management that can maintain it independently once we step out. If your institution later switches package vendor (for example from Magister to SOMtoday), the specialist app simply keeps working — only the connector is adapted.

For institution-specific software — custom middleware, decades-old Java or Oracle extensions on the SIS, custom OSIRIS modules, in-house reporting tools built sometime in 2003 — we integrate case by case. That takes extra work in the planning phase but prevents integration debt later. For publishers and EdTech start-ups that want to record method-specific progress, we look at a custom LMS in which the SVS part is a first-class component rather than an add-on.

For exchanges with government bodies and quality frameworks, we integrate as standard with DUO (BRON), Dutch Inspectorate of Education reports, Vensters PO/VO, NVAO audits in higher education and Samenwerkingsverbanden Passend Onderwijs (regional inclusive education partnerships). For healthcare competence registers, we integrate with AFAS HRM, Workday, Nedap Ons and the relevant quality registers of the professional associations. For a broader view of our approach to education, see the general education app page.

How a student tracking system project runs.

An SVS project for an educational institution has its own rhythm. Five phases that will be familiar to every client, although each phase scales with the complexity of your educational context.

01 · Audit

Didactics & data mapping

A day with a mentor, an internal coordinator or care coordinator, and a functional administrator of the package. Result: current student data mapped, bottlenecks flagged, didactic starting points documented.

02 · Design

Scope & integrations

Which SVS flow goes into the app for each target group, which integrations take priority (ParnasSys/Magister/SOMtoday/Eduarte/Osiris), and which flows only fit in a later release.

03 · Build

Short sprints

One working SVS flow delivered every sprint. Teachers, mentors and, where relevant, students or parents test it straight away. The first working flow is live within a few sprints.

04 · Cutover

Pilot & rollout

One class, one programme or one department first, then the next. At each rollout: teacher training, material for the helpdesk, hand-over to functional management and updates to the existing package integrations.

05 · Maintenance

Ongoing

We adapt with every GDPR-O change, new version of Magister or SOMtoday, or update of the Privacyconvenant Onderwijs (Dutch education privacy covenant). Fixed monthly price, first-line support within the same working day.

Working in a sector that relies heavily on standards.

Kennisnet · Monitor Digitale Leermiddelen

"Schools increasingly opt for a specialist app alongside their existing SVS, for special educational needs, observations or communication with parents, rather than a complete replacement of the package."

SURF · Trendrapport Onderwijs & ICT

"The greatest added value of custom software in higher education lies in the guidance layer: study career guidance, thesis tracks and placement monitoring that SIS packages barely cover, if at all."

Privacyconvenant Onderwijs (SIVON)

"Educational institutions remain the data controller for student data. Code ownership and clearly defined data processing agreements are almost always a condition of public funding."

Fabian van Dijk Business developer · Education & EdTech at Appfront
fabian.vandijk@appfront.nl

Answers for institutions looking to strengthen their SVS.

The questions we hear most from board members, ICT managers, student support coordinators and programme coordinators.

Do you replace ParnasSys, Magister, SOMtoday or Eduarte?
In most projects, no. The package SVS contains core administrative processes (enrolment, funding, exam administration, BRON reporting) that no institution replaces lightly. We usually build a specialist SVS layer alongside the package, for special educational needs, OPP management, observation flows, drop-out monitoring or competence registration, and integrate via UWLR, OSO, ECK iD and Edu-iX. For some niche institutions (a small private academy, an international school, a specific care training provider) a fully custom SVS can be the right route; we find that out during the audit phase.
How do you handle privacy and GDPR-O for student data?
From the first sprint we work within GDPR-O and the Privacyconvenant Onderwijs 4.0. That means data minimisation to what is didactically necessary, retention periods per data object, a data register, a DPIA on delivery and a data processing agreement in line with the covenant. We work with ECK iD and pseudonymisation as standard; the BSN (citizen service number) is only used where legally required. For institutions with a Data Protection Officer, we coordinate directly with that person.
What about drop-out prediction and the AI Act?
Drop-out risk prediction, automatic placement in level groups and AI-based admission assessments fall under the high-risk category of Annex III of the EU AI Act in education. We document governance, run bias tests across gender, background and disadvantage criteria, build in human review before any decision that affects a student's progress, and publish a transparency report. We don't build autonomous drop-out decisions, not because the technology can't do it, but because the AI Act risk, the didactic risk and the reputational risk are too great. See also our page on AI development for our broader approach to AI.
Will we get the source code and the data under our own control?
Yes. Code ownership is laid down contractually; the institution owns the source code, schemas and data. For publicly funded education this is almost always a requirement (and, more broadly, a good safeguard against vendor lock-in). We deliver a runbook, hand over knowledge to functional management and structure the codebase so that another team can take it over after us.
Do you work with UWLR, OSO and ECK iD?
Yes. UWLR for exchanging learning results with learning methods and suppliers, OSO for transferring pupil records between schools, and ECK iD as a pseudonymous identifier instead of the BSN (citizen service number) where possible. For higher education, we work with SURFconext and the Edu-iX chain. All three or four standards run through a single abstraction layer, so switching suppliers later doesn't require a complete recode.
What is the difference between your SIS app and a custom LMS?
An LMS focuses on delivering and working through learning material: courses, modules, assignments, tests. An SVS (student tracking system) focuses on following the student as a person: progress over the years, individual development plans (OPP), care indicators, records, parent communication. In practice there is a grey area: we often build an SVS component on top of an existing LMS, or an LMS component alongside an existing SVS. For the choice between package and custom in an LMS context, we wrote a separate guide: custom LMS vs off-the-shelf LMS.
Can you build an SIS for a teaching hospital or healthcare organisation (competency register)?
Yes, this is one of our strongest use cases. Alongside the usual progress tracking, a healthcare competency register tracks procedures, supervision hours, NEN 7510-compliant audit logs and authorisation expiry dates. We build it with fine-grained roles for practice educator, supervisor and student, with automatic alerts when authorisations are about to expire, and with integrations to AFAS HRM, Workday or Nedap Ons. The Nursing Care Quality Framework (Kwaliteitskader Verpleegzorg) and the Wet BIG (Dutch Healthcare Professions Act) guide the design.
Can you build a multi-tenant SIS for a school board or a group of vocational colleges?
Yes. For school boards with multiple schools, vocational college groups (ROC) with multiple colleges, or healthcare organisations with multiple training departments, we build multi-tenant from the start. Each entity gets its own branding, its own role setup, its own integrations and its own data isolation within a single codebase. That keeps maintenance manageable while letting each entity operate independently, including its own data processing agreements where needed.
How does this relate to your broader education app service and your training app service?
This page is specifically about student information systems. For a broader view of our education team, see education app development, which also covers student portals, teacher apps, e-learning, language-learning apps and proctoring. For a single, clearly defined course focused on sharing study material and scheduling, building a training app is the right service page. Clients often start on a service page, read this one for the SIS-specific context, and then move on to a project.

Talk to us about your student information system.

A half-hour introduction with our education team. We listen to your educational context and look at how your existing package fits and which specialist layer adds value. No obligation.

Edit content