Custom education ERP development
Appfront builds custom back-office software for educational institutions: from enrolment and placement to timetable logistics, results recording and the data you use to justify your funding. It connects to the national chains and to the systems you already use, rather than being a package your organisation has to bend to. Get in touch.
What is an education ERP?
An education ERP is the administrative backbone of an institution: who is enrolled, in which programme and group, which curriculum that person follows, which results have been achieved, and which data goes to the national registrations that funding depends on. It is the place where student, programme, teacher, room and money come together.
It differs from a general ERP system because the core entity is not an order or a product but a learner with an educational pathway, with its own concepts such as cohort, learning route, absenteeism and graduation — and with a chain of national data exchanges that simply have to be right.
Appfront builds this as custom software. In practice, we rarely replace a complete core registration system; more often we build the layer around it that the standard package does not cover and connect it, for example through a Eduarte integration.
The learner at the core
One record covering enrolment, programme, group, results, absenteeism and support, instead of data scattered across five systems.
Logistics that add up
Education programmes, groups, teachers and rooms in context, so that a change to the programme visibly carries through to the timetable and staffing.
Funding backed by evidence
The data that determines your funding in one place, with alerts when an enrolment or result is incomplete before a reference date.
Education ERP or general ERP? Where the line falls
Appfront builds both. The difference lies in what the system registers at its core.
The educational pathway
Learners, programmes, cohorts, results, absenteeism, graduation and the national data exchanges. Timetabling and teacher deployment are part of it because they follow from the education programme.
Orders, stock and production
If it is about business processes around purchasing, stock, production or projects, see custom ERP systems. For the learning environment itself, an e-learning platform is the right starting point.
Our development process for your education back office
Education administration is full of exceptions that only become visible once you write them down. We spend the first phase on exactly that.
We map out your programme structure, enrolment routes, results rules and absenteeism handling, plus which national data exchanges apply to you and which systems currently handle them. Often part of this is already covered and the issue is the gaps in between.
We design the learner model, the programme structure, the integrations and the roles — student, teacher, administration, programme manager — each of which needs a different view of the same record.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing maintenance, monitoring and further development as your education offering or regulations change.
What custom education software delivers in practice
What you need varies greatly by sector and institution. These are the components that come up most often.
Enrolment and placement
Application, intake, admission and placement in a group or learning route, with the status transitions and checks that fit your sector.
Education programme and groups
Programmes, cohorts, course units and groups in context, so that changes to the programme carry through without manual rework.
Timetabling and teacher deployment
Deployment of teachers and rooms derived from the programme, with visibility of bottlenecks before the timetable is published.
Results and progress
Recording of results and progress using the rules that apply to each programme, and alerts for learners who are falling behind or at risk of dropping out.
Absenteeism and support
Registration and follow-up of absenteeism using the mandatory reporting routes, linked to the support around the learner. See also compulsory education and RMC software.
National data exchange and funding
Submission to the registers your funding depends on, with completeness checks before the reference date instead of repair work afterwards.
Typical use cases in practice
Regulations differ greatly between education sectors, and so does what there is to build.
Secondary vocational education (mbo) institutions
Institutions with learning routes, work placement agreements and work placement registration, where administration around employers and support is a separate flow alongside regular education.
Private training providers
Providers of courses and vocational training who have their own enrolment and payment flows and do not fit into an institutional package.
Universities of applied sciences and universities
Institutions that need their own layer alongside the core system for placement, specific programmes or partnerships.
Partnerships and corporate training
Organisations that provide education for multiple parties at once and need to be able to account for what was delivered per client.
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 →Technology we use
The integration with existing education systems often determines what is possible. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, without dependence on per-user licences.
Why Appfront for your education back office?
Appfront builds custom software for a wide range of organisations in the Netherlands. In education, we start by asking which part you really need to build yourself. Replacing a core registration system is rarely wise; the layer around it that nobody covers often is.
If Osiris needs to exchange data with the rest of your systems, there's our Osiris integration.
If you want to schedule shifts and invigilation for support staff, take a look at our software for support staff shift scheduling.
If you want assessment results from Woots in your own dashboards, take a look at our page on a Woots integration.
If you want to exchange messages securely with partners in the education chain, take a look at our page on Edukoppeling.
For recording lessons delivered, absences and substitutions per group, there is our app for teaching time and cancelled lessons.
We design from the perspective of the administration team that works in it every day. Education administration is full of exceptions, and a system that cannot handle them leads to shadow administration in spreadsheets — exactly what you wanted to solve.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also take a look at our broader services around custom software, custom ERP and e-learning platforms. Not sure about the approach? Get in touch.
Security and privacy in your education software
Student data is personal data, and some of it is sensitive: pastoral support, reasons for absence and sometimes health information. Appfront builds in line with the OWASP ASVS and with the GDPR as its starting point, using role-based access so that a teacher only sees what belongs to their role.
In education, sector agreements on data exchange and processor relationships also apply. We document the data flows per integration and set up retention periods per type of data, so that student records are not kept indefinitely.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- Retention periods per type of data in the participant record
Frequently asked questions about building education ERP
Answers to the questions we get asked most often.
The administrative backbone of an educational institution: enrolment and placement, curriculum and groups, timetabling and teacher allocation, results and absence, and the data exchange on which funding depends. Everything revolves around the student and their educational journey rather than around an order or a product.
Usually not, and we rarely recommend it. Replacing a core registration system is a heavy and risky undertaking, especially with national data exchanges attached to it. What we more often do is build the layer around it that your package does not cover and integrate it — that usually solves the real bottleneck faster.
Yes, that is usually the core of the work. We regularly build integrations with student information systems and with learning environments. What is technically possible depends on what the supplier allows; we investigate that up front, including whether there are contractual objections to an integration.
By treating the submission as a verification process rather than an export. Before the reference date, the system flags which enrolments or results are incomplete, so you can correct them rather than fix them afterwards. The exact rules differ per sector, and we define them together with your administration team.
Yes, and this is often where the question is sharpest, because institutional packages don't fit your own enrolment and payment flows. For private training providers we usually build a more compact solution: enrolment, scheduling, results and invoicing, without the heavy chain obligations of publicly funded education.
Education data is personal data, and parts of it are sensitive: guidance, absenteeism, sometimes health information. We work with role-based access so a teacher sees what they need and no more, and with retention periods per type of data. This is also a requirement under the standard agreements in the education sector.
Yes. A student portal for enrolment, timetables, results and requests, and a teacher portal for groups, entering results and reporting absence. This self-service takes most of the pressure off the administration, provided data entry stays simple enough to be used in practice.
For publicly funded education, the standard packages are usually the wisest starting point, precisely because of the chain obligations. Custom development pays off for the layer around them, for private training providers who don't fit, and for institutions with an offering the standard model doesn't cover. We'll tell you honestly when a package is a better fit.
Ready to build your education back office?
Tell us which systems you use now, where the administration gets stuck and which chain obligations apply to you — we'll gladly help think through scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom development pays off in your situation.
If you want to explore this topic more broadly, applatenmaken.com has a page on building education ERP software.