Custom absence registration and truancy reporting app development
Appfront builds apps for schools and school boards that record and follow up on absence: absence per lesson logged from the classroom, authorised or unauthorised with the reason noted, a count per pupil showing when the statutory reporting threshold is approaching, and reporting to DUO's Verzuimloket with the file the truancy officer requests. So the attendance coordinator no longer has to search through lists and no report goes out late or without justification.
What is an app for absence registration and truancy reporting?
Every school records absence, usually in its pupil administration system. Following it up often happens somewhere else: in the attendance coordinator's spreadsheet, in emails with the mentor, in notes from conversations with parents. An app for absence registration and truancy reporting brings this together: what has been recorded, what has been done about it, and whether a pupil is approaching the reporting threshold.
The Compulsory Education Act requires schools to report unauthorised absence, including when a pupil is absent without permission for sixteen hours or more within a period of four consecutive school weeks. Counting this by hand means reports go out late or too often, and a report without supporting detail comes back from the attendance officer with questions the school could already have answered. The real work lies between those steps: the conversation with the pupil, contact with parents, and the pastoral team.
We build custom software because the app has to fit your pupil administration system and your absence protocol: which system you use and what it makes available, how lateness and removal are counted, who takes action after how many hours, and how you work with your municipality's school attendance officer. A standard administration system records; your school's protocol is rarely part of it.
Counting against the reporting threshold
For each pupil, unauthorised absence across the current period of school weeks, with a signal well before the statutory threshold is reached and a report becomes mandatory.
Follow-up in line with protocol
For each step in your absence protocol, a task for the form tutor, head of year or attendance coordinator, with what was discussed and what was agreed.
Reporting with a case file
The report to the Verzuimloket prepared with the data DUO requires, and a case file for the attendance officer with dates, conversations and contact with parents.
How we build your app for attendance registration and compulsory education reporting
We start with your absence protocol: who does what after how many hours, how counting is currently done, and how often a report was late or lacked supporting detail.
Your absence protocol, the pupil administration system and what it makes available, the roles within the school, and the agreements with the attendance officer.
Absence per lesson taken from the administration into the app, the rules for authorised and unauthorised absence, and the count per pupil against the reporting threshold.
Tasks for each step in the protocol, conversation notes, messages to parents, and an overview per form group and per team.
Preparing the report to DUO, the case file for the attendance officer, reporting for the leadership team and the inspectorate, and ongoing management and expansion afterwards.
What an app for attendance registration and compulsory education reporting actually does
The components below come up at almost every school. Which ones you need depends on your type of education and on how your protocol is organised.
Absence per lesson
Absence, lateness and removal from lessons per lesson period, taken from the administration or recorded directly in the classroom, with the reason and the status authorised or unauthorised.
Threshold monitoring
Unauthorised absence per pupil across the current period, with a signal before the threshold and a list of pupils for whom a report should be ready.
Protocol tasks
Once a set trigger is reached, a task for the form tutor, head of year or attendance coordinator, with a deadline and a record of what was done.
Contact with parents
Messages and conversations with parents recorded against the pupil, with the date and who was in contact.
Reporting case file
The details needed for the report to the Verzuimloket and a case file for the attendance officer with the progression, conversations and agreements.
Reporting
Absence by class, team and period, the number of reports, follow-up at each step, and the pupils with prolonged or recurring absence.
Who we build an app for attendance registration and compulsory education reporting for
The app is intended for schools where absence is recorded, but follow-up and reporting still happen through separate lists and emails.
Secondary education
Many lesson periods, many teachers, and absence recorded per lesson. The count against the reporting threshold and the tasks for form tutors are the core.
Secondary vocational education
Students who are partly subject and partly not subject to compulsory education or qualification requirements. The separation by age and the reporting case file matter most.
Primary education
Fewer hours, more contact with parents and no more lost time around holidays. Contact with parents and leave requests are what matter most.
School boards
Multiple schools, one protocol. Cross-school reporting and a shared way of working with the municipalities are at the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
This page is about the school that records and reports absence. For the municipality that receives and processes the report, see our page on school attendance and RMC software; for attendance in general, our page on attendance registration software; and for the school-wide system, our page on education ERP. Read about our process at building software.
Why choose Appfront for your absence registration and compulsory education reporting app?
Absence is often the first sign that something is wrong with a pupil. That is what we build on: registering is the start, follow-up is the work, and reporting happens on time and with supporting evidence.
Reported on time
The count runs alongside every lesson. The absence coordinator sees which pupil is approaching the threshold before the report is overdue.
Follow-up made visible
Every step in the protocol has an owner and a status update. The head of department sees where things stall, and the inspectorate can see that the protocol is being followed.
A report that holds up
The file is ready when the report is made. The compulsory education officer receives the full course of events, not just a number of hours.
Security and privacy for an absence registration and compulsory education reporting app
The app holds data on underage pupils, absence, conversation notes and contact with parents. Access is set by role: the form tutor sees their class, the head of department their team, and the absence coordinator the school. Sensitive notes are separately protected, and every view is logged with name and time.
The app runs in a European data centre, with encrypted storage and daily back-ups. We work under a data processing agreement that fits the arrangements in education, and we do not keep data longer than your policy prescribes.
Frequently asked questions about an absence registration and compulsory education reporting app
Questions schools ask before getting started.
It takes absence per lesson from your student administration or records it in the classroom, counts unauthorised absence per pupil against the reporting threshold, creates tasks according to your absence protocol, records contact with parents and conversations, and prepares the report to DUO's Absence Desk with a file for the compulsory education officer.
The Compulsory Education Act requires schools, among other things, to report when a pupil is absent without permission for sixteen hours or more within a period of four consecutive teaching weeks. Other forms of absence may also require a report, and many schools make additional arrangements with their municipality. The app counts against the statutory threshold and against your own protocol.
No. Registration stays where it is now; the app reads absence from the administration system and adds the follow-up, the count and the report. If your system does not support lesson-by-lesson registration well, the app can also do that registration itself.
The app prepares the report with the data the DUO Absence Desk requires, and the absence coordinator submits it. Whether that happens via an integration or through the portal depends on what DUO makes possible for your situation; we'll examine that in the first step.
In line with your protocol. Many schools count lateness separately and trigger a step after a certain number of occurrences; being sent home can be counted as absence or as a separate signal. We'll record those rules in the app.
Yes, if you wish. Parents submit a leave request, the headteacher decides according to the rules on exemption and leave, and the decision is recorded against the pupil. Unauthorised absence around holidays is then immediately recognisable as such.
Check that first. Some systems have absence reports and a reporting function, and that is sufficient if your protocol is straightforward. Custom development makes sense if follow-up currently happens outside the system, if several schools want one way of working, or if collaboration with the education welfare service and pastoral care team needs to be documented.
No more reports of lateness or absence without a record?
Tell us which pupil administration system you use, what your absence protocol looks like and how reporting currently works. We'll show you what the counting, follow-up and reporting record look like.