Ludendo

For IT and systems · in development, not yet in useFor IT and systems · in development

Calm management.
Everything in one place.

Integrations with their status. Signing in with the school account. First see what changes, only then import. Who may do what is in one register, and the log says in plain sentences who did what.

Walk through the day

Ilse de Groot is the IT coordinator of Het Voorbeeld College. All screens show made-up data.

Laptop screen of IT coordinator Ilse de Groot with made-up data: the integrations with their status (signing in with the school account via a simulated Entree works, the timetable was updated at 07:12, DUO is not on yet) and what happened today: 6 changes imported, an extra role for Mr Kramer and everything exported.

· IT · Ilse, before the first bell

Every integration,
and whether it works.

On one screen you see what Ludendo gets from other programs, and what not yet. The timetable comes from the timetabling program. At 07:12 two changes came in; at 07:40 Lotte sees them on her phone.

Built, not yet in use, tested with a mock integration. DUO is still a Clickable example: until it is there, you report to DUO yourself.

Skip the day
  1. What works. Signing in with the school account and the timetable from the timetabling program. Every integration with its status in words.
  2. Today’s timetable. At 07:12 two changes: English in A112, history is cancelled. If the timetabling program drops out for a moment, the timetable simply stays.
  3. What is not on yet. DUO, transfer files and learning materials without a second sign-in. You see that too, honestly.
Laptop screen of Ilse de Groot with made-up data: the integrations. Signing in with the school account (students and staff, via a simulated Entree) works. The timetable from the timetabling program works and was updated at 07:12: 4V2’s English at 10:30 is in A112 instead of B108, history at 11:20 is cancelled. At 06:30 there was no connection for a moment; the timetable stayed and at 06:31 everything was updated again. DUO, transfer files (OSO) and learning materials without a second sign-in (ECK iD) are not on yet.

· Parent · Mark de Wit, at the kitchen table

Signing in with the school account.
Parents always with a code.

What Ilse set up, you see with others. Students and staff sign in with their school account via Entree. Parents have their own account and always enter a code from an app. That is how Mark signs in, one minute before he reports Eva sick.

: Built, not yet in use signing in, tested with a simulated Entree, Built, not yet in use and the code for parents. A real connection to Entree is not there yet.

  1. Two ways. Students and staff with their school account. Parents with their email address. Mark taps Parent.
  2. Always a code. After his password Mark enters the code from the app on his phone. Without a code nobody gets in.
  3. In, and out again by itself. He sees Lotte and Eva. After 8 hours, or after an hour of doing nothing, he is signed out by himself.
Phone screen of Mark de Wit with made-up data. The sign-in screen of Het Voorbeeld College has two ways: students and staff with their school account via Entree, parents with their email address. Mark picks Parent, enters the code from the app on his phone after his password and is in at 07:50. He sees Lotte (4V2), with English in A112, and Eva (3H3), with a new grade for maths. He stays signed in for at most 8 hours.

· IT · Ilse, on her laptop

First see what changes.
Only then import.

Three students are joining, with five parents. Ilse picks two files from the student administration system. Ludendo recognises the columns and shows per line what is new, what changes and what is wrong. Then everything goes in, or nothing.

Built, not yet in use. Rolling back is not possible yet. Inviting parents from this screen is a Clickable example.

  1. Two files. The students and the parents, as CSV, also the way Excel saves them. Ludendo recognises the columns itself.
  2. The check first. 3 new, 3 changed, 1,176 unchanged, no errors. Two students are no longer in the file: Ludendo does not deregister them by itself.
  3. All or nothing. One tap and the six changes are in. The five new parents get an invitation for their account.
Laptop screen of Ilse de Groot at 10:05, with made-up data. She picks two files: students-9-october.csv with 1,182 lines and parents-9-october.csv. Ludendo recognises the columns. The check: 3 new (students, with 5 parents), 3 changed (two addresses and a class), 1,176 unchanged and 0 errors. 2 students are no longer in the file; Ludendo does not deregister them by itself. She taps Import 6 changes: all or nothing. Then an invitation is ready for the 5 new parents. The school now has 1,184 students.

· IT · Ilse, on her laptop

Who may do what, in one register.
What is not in it, nobody may do.

Mr Kramer teaches maths and this school year is also team leader of havo 4 and 5. That is not a second account: he has an extra role. At 11:40 Ilse checks what that role may do. At every page and button Ludendo first asks: may this person do this, for this student?

: Built, not yet in use the permissions, also in the database itself, Built, not yet in use and more roles in one account. The overview for adjusting permissions yourself is a Clickable example. IT is not yet a role of its own in the app: here Ilse has the school leaders role as well.

  1. One account, two roles. Maths teacher and team leader of havo 4 and 5. The permissions of both add up.
  2. What a team leader may do. Publish grades and view the file, only in their own department. Medical information is only seen by those who need it: the care coordinator, the administration and the parent of their own child.
  3. Refused, and recorded. At 11:52 Mr Kramer tries to open Sem Jansen’s medical details. That is not allowed, and it is in the log.
Laptop screen of Ilse de Groot at 11:40, with made-up data. Thijs Kramer’s account has two roles: maths teacher and team leader of havo 4 and 5. What a team leader may do: publish grades, record attendance and view the full file, only in their own department. Not view medical details: medical information is only seen by those who need it: the care coordinator, the administration and the parent of their own child; not change roles and permissions, only the school leaders may do that. At 11:52 Mr Kramer tried to open the medical details of Sem Jansen (4V2); that was refused and is in the log.

· IT · Ilse, after the bell

Who looked at Lotte’s file?
The log says it in plain sentences.

Who signed in, who opened which file and who changed what. Also what was refused. Nobody can change or delete a line, not even Ilse. If a parent asks who looked at their child’s data, you look it up in one place.

Built, not yet in use. Viewing the log is a right of the school leaders. There is no retention period yet: for now the log only grows.

  1. The day in sentences. From the sick report at 07:51 to Erik Mulder, who looked up everything about Lotte at 15:45. With who, what and when.
  2. Everything about one student. Ilse searches for Lotte de Wit. Only Mr Bakker opened her data, as her mentor. That was allowed. At 15:45 Erik Mulder had already looked this up for her father.
  3. Exporting. The lines go along as a CSV file, so the school leaders can answer the parent. That search is in the log too.
Laptop screen of Ilse de Groot at 16:00, with made-up data: today’s log, in sentences. 15:45: Erik Mulder looked up everything about Lotte de Wit. 15:31: Mr Bakker opened Lotte de Wit’s profile, as mentor. 14:30: Erik Mulder granted leave for Eva de Wit. 13:40: Mr Bakker showed the grades for test Acids and bases. 11:52: Mr Kramer tried to open Sem Jansen’s medical details; refused. 11:40: Ilse viewed Mr Kramer’s permissions. 10:19: Sanne Vos sent 3 messages to parents. 10:05: Ilse imported 6 changes. 07:51: Mark de Wit reported Eva sick. On the right Ilse searches for Lotte de Wit: at 15:45 Erik Mulder had already looked this up; only Mr Bakker opened her data, as her mentor, and her grade became visible. She exports these lines as a CSV file.

· IT · Ilse, before she goes home

The data belongs to the school.
Everything goes along in one file.

With one button you fetch everything: students, parents, staff, classes, timetable, grades, absences, messages and the log. With a description of how it is built up, so another program can read it. That way the school can always leave.

Built, not yet in use. Exporting everything is a right of the school leaders. The log only goes along if you may view it too.

  1. What is in it. Nine tables, from 1,184 students to 51,306 lines of log.
  2. One button. Every table gets a tick. Done: one file of 38 MB to download.
  3. This is in the log too. Who exported everything when, you can look back on. Earlier exports stay in the list.
Laptop screen of Ilse de Groot at 16:05, with made-up data: all data of Het Voorbeeld College in one file. In it: 1,184 students, 1,912 parents, 142 staff, 186 classes and groups, 38,120 lessons, 48,210 grades, 21,904 lines of absence, 9,877 conversations and 51,306 lines of log. She taps Export everything: every table gets a tick and the file voorbeeldcollege-2026-10-09.zip of 38 MB is ready. Under Earlier exports, today 16:06 is now at the top, above 30 September and 9 July. Every export is in the log.

· IT · Ilse, a week before the first school day

Setting up the school year.
Right once, then it is right everywhere.

The school year, the lesson times and the locations. The rules for absence and resits. And which parts the school uses. What Ilse sets here, students, parents and teachers will see everywhere.

: Built, not yet in use locations with BRIN and location number, Built, not yet in use and the rules for absence and resits. Choosing parts is a Clickable example.

  1. The school year. From 24 August up to and including 9 July, in four terms. Lessons of 50 minutes. Two locations, each with the number DUO uses too.
  2. The school’s rules. When absence becomes a report, and how resits work. Mentors and students see exactly these rules.
  3. Which parts are on. Basic, Recommended or Everything, and per role. Switching off does not delete any data.
Laptop screen of Ilse de Groot on Monday 17 August, with made-up data. School year 2026/27: from Monday 24 August up to and including Friday 9 July, in 4 terms, lessons of 50 minutes and the 1st period at 08:30. Locations under BRIN 99XA: Main building 99XA00 for years 2 to 6, and Paviljoen Noord 99XA01 for the first-year classes. The school’s rules: a report at 16 hours of absence without a valid reason in four school weeks, and resits: one test per subject per term, the highest grade counts. Under Sections, Recommended is chosen: timetable, homework and grades are on, the parents’ evening comes later. Switching off does not delete any data.

What else it can do

Everything for IT and systems.
Honest about how far along it is.

Built means: in the real app, tested with made-up data. Not yet in use at any school.

Built, not yet in use
15
Clickable example
6
Planned
2
Idea
2
Built, not yet in use15
  • Board, schools and locations with BRIN and location numberBuilt, not yet in use
  • Settings: the thresholds for absence and the rule for resitsBuilt, not yet in use
  • Integrations on one screen, with their status (tested with a mock integration)Built, not yet in use
  • Fetching the timetable from the timetabling program; if it drops out, the timetable staysBuilt, not yet in use
  • Signing in with the school account for students and staff (tested with a simulated Entree)Built, not yet in use
  • Parents always sign in with a code from an appBuilt, not yet in use
  • After 8 hours, or after an hour of doing nothing, you are signed out. Sign out of your school account and you are signed out everywhere.Built, not yet in use
  • Import with a check first: what is new, what changes, the error per line; then all or nothingBuilt, not yet in use
  • Several roles in one accountBuilt, not yet in use
  • Every page and button first checks whether you may, also in the database itselfBuilt, not yet in use
  • Separated per school board, in the database itselfBuilt, not yet in use
  • The citizen service number stored encrypted, only shown with a separate permissionBuilt, not yet in use
  • The log: who signed in, who opened which file and who changed what, with export (no retention period yet)Built, not yet in use
  • Technical logs without personal dataBuilt, not yet in use
  • Export everything in one file with a description of its structureBuilt, not yet in use
Planned2
  • Data with one host in the EU; which host has not been chosen yetPlanned
  • Backups in a second place; how often and how fast recovery works has not been decided yetPlanned
Clickable example6
  • Choose the parts: Basic, Recommended or Everything, and per roleClickable example
  • Manage accounts: reset two-step sign-in, invite parentsClickable example
  • All permissions in one overview and adjust them yourselfClickable example
  • Pass data to DUO, with the response that comes backClickable example
  • Receive transfer files via OSOClickable example
  • Digital learning materials without a second sign-in (ECK iD)Clickable example
Idea2
  • A home screen and menu of its own for ITIdea
  • Sign in with a passkey for parentsIdea

Clickable example: a worked-out design with made-up data, not yet in the real app. How far along we are in total

What is not really connected yet.
So you know where you stand.

Entree
Signing in works the way Entree asks, but has been tested with a simulated Entree. A real connection is not there yet.
Timetabling program
Tested with a mock integration, not yet with a school’s real timetabling program.
DUO, OSO and ECK iD
A technical design and a clickable example. Until DUO is connected, you report to DUO yourself.
Where it runs
Only on our own computers, with made-up data. A host in the EU has not been chosen yet.
Outside check
Every change goes through automatic checks and tests. A penetration test and a review by an outside developer have not happened yet.
Retention
How long the log is kept, and how often there is a backup, has not been decided yet.

Who does what in management?
Only those who need it.

Administration

Imports students and parents, and enrols and deregisters. Only sees the citizen service number with a separate permission.

School leaders

Manage the integrations, change roles and permissions, look in the log and export everything.

The care coordinator

Sees a student’s medical details. Medical information is only seen by those who need it: the care coordinator, the administration and the parent of their own child. Not IT and not the school leaders.

IT is not yet a role of its own in the app. On this page Ilse has the school leaders role as well; several roles in one account is already possible. Anyone who views or changes something goes into the log. Back to the day of the whole school

Questions about signing in, integrations or security?

Request a
technical conversation.

We tell you honestly what already works and what does not yet. Do not send any information about students.

Email us For schools