For schools · in development, not yet in use at any schoolFor schools · in development
One app, not five.
For the whole school.
Do you decide on your school’s system? Ludendo aims to bring together the student administration, the app for parents and students, the learning environment, messages and absence. Calm to use, with the rules of education built in. And you can always leave again.
For school leaders, school boards and procurement. All screens show made-up data from Het Voorbeeld College.
What it replaces
One sign-in, one register.
What works well, stays.
Today a school often works with five separate systems. Ludendo aims to replace them with one app. The timetable and the learning materials stay where they are: Ludendo connects to them.
Aims to replace
- The student administrationApplications, placing and deregistering are built. The rest, with the connection to DUO, comes later.
- The app for parents and studentsTimetable, homework, grades with an explanation, reporting sick and leave.
- The learning environmentStudy guide, learning materials and handing in, right at the lesson.
- Messages and lettersOne inbox for school, teachers, mentor and parents.
- Absence and compulsory schoolingSick report, teacher and front desk come together by themselves in one register.
Stays where it is
- Your timetabling programThe school makes the timetable where it does now. Ludendo fetches it.
- Learning materials from publishersThat stays with the publishers. Opening it without a second sign-in is a clickable example.
· IT · Ilse de Groot, on her laptop
Connecting to what your school already has.
Nothing kept twice.
Ilse de Groot is the IT coordinator. Everyone signs in with the school’s account. The timetable comes from the program the school already uses for timetabling. Ludendo does not make its own timetable.
Built, not yet in use. Tested with mock integrations; nothing is really connected yet.
Skip the day- Signing in. Students and staff with the school account, via Entree. Parents with their own account, and always with a code from an app.
- The timetable. It comes from the timetabling program. At 07:12 two changes for today came in: English in A112 and history is cancelled. Lotte sees it at 07:40.
- What is still to come. DUO, the transfer file (OSO) and textbooks without a second sign-in only exist as a clickable example for now. Until then the school reports to DUO itself.
· IT · Ilse de Groot, on her laptop
In with a check.
Out with one file.
Switching over has to be possible, and leaving too. You import students, parents, classes and teachers from a file. Only after a check does everything go over in one go. And the school always takes everything with it.
Built, not yet in use. Importing with a check first. Rolling back is not possible yet.
- A check first. Ilse picks a file from the current student administration system. 1,182 lines, the columns have been recognised. Nothing has been saved yet.
- All or nothing. 3 new students with 5 parents, 3 changes and 0 errors. With one button the 6 changes go over in one go.
- Being able to leave again. All the school’s data in one file, with a description of how it is built up. The school does not have to ask us for that.
· School leaders · Erik Mulder, on his laptop
The rules are built in.
Whoever decides, stays a person.
Ludendo knows the rules of education: leave, the promotion rules and teaching time. It does the counting and gets the work ready. Erik Mulder is the head of school. He decides.
Built, not yet in use. Deciding on leave and finalising the report. The screen for teaching time: Clickable example.
- Leave, with the law alongside. Mark de Wit requests two days of leave for Eva, for a wedding. Up to ten school days the head of school decides. What Erik writes, Mark reads in the app.
- The rules do the counting. In 4V2, 19 students pass everything and 4 are to be discussed. The report meeting decides about them, not the app.
- Teaching time per cohort. The app counts the planned hours over the whole programme. Vwo 5 comes out 68 hours below the standard. You see that now, not only at the end.
Why it stays simple
Little explanation needed.
Not for new colleagues either.
One blue button
Every screen has one main button: what you do there most often. The rest stays calm.
Undo
You undo a mistake straight away, on every screen. Built, not yet in use
Red only when needed
Colour only warns when something needs doing, and always with the word next to it. With an average, the sum is shown. Built, not yet in use
For school boards and procurement
Separated per board.
In the database itself.
A board can have several schools and locations, each with a BRIN number and a location number. What belongs to one board, the other does not see. That is guarded by the place where the data is stored, not only by the app.
Separated per board
Tested, not yet checked from outside. Built, not yet in use
Schools and locations
With BRIN and location number, as DUO knows them. Built, not yet in use
A list of requirements?
Taking part in a tender? We are happy to fill in your list of requirements. Email it to [email protected].
How far along, and becoming a pilot school
To be honest:
we are on our way.
Ludendo is in development and not yet in use at any school. We are looking for schools that think along and try the app early. With one of them we later want to be the first to work with real data. The order is fixed, the dates are not yet.
Possible now
An introduction.
A talk about your school: what works, what rubs, what you need.
Possible now
A demo.
The app with made-up data. After that we agree together on the form, the scope and the duration, and what happens when it stops.
Next
A test environment.
A first version online, with one company in the EU, with backups in a second place. Still with made-up data. Your school tries it out.
After that
Review and contract.
An outside developer reviews the code, a separate firm tests the security, and we sign a data processing agreement.
Then
The first pilot.
Only then does real data go in. When that will be, we do not know yet.
113of the 189 features built
A feature is something you can do or see in the app, such as reporting sick or deciding on leave. Built means: in the real app, tested with made-up data.
- Built, not yet in use113Built in the real app. Not online anywhere yet.
- Planned17Decided, and it is in the build plan.
- Clickable example51A worked-out design with made-up data. Not yet in the real app.
- Idea8This is how it could work. Not decided yet.
Every school that thinks along helps decide what we build first, has one fixed contact person and keeps its data. Please do not send us any information about students or staff yet.
What else it can do
For the whole school.
Honest about how far along it is.
What a decision-maker asks first: switching over, integrations, the rules and the administration. The screens for care, careers guidance, exams and timetabling are here too; they are still a clickable example. Built means: in the real app, tested with made-up data. Not yet in use at any school. Open a group for the list.
Built, not yet in use26
- Importing with a check first: what is new, what changes and the error per line, then all or nothingBuilt, not yet in use
- Export everything in one file, with a description of the structureBuilt, not yet in use
- Signing in with the school account for students and staff, tested with a simulated EntreeBuilt, not yet in use
- Parents always sign in with a code from an appBuilt, not yet in use
- Fetching the timetable from the timetabling program, tested with a mock integrationBuilt, not yet in use
- All integrations on one screen, with their statusBuilt, not yet in use
- Separated per school board, in the database itselfBuilt, not yet in use
- Board, schools and locations with BRIN and location numberBuilt, not yet in use
- The log: who signed in, who opened which file and who changed what, in plain sentencesBuilt, not yet in use
- Decide on leave, with the reasons the parent readsBuilt, not yet in use
- Request leave: first the rules, then the form and the decision with reasonsBuilt, not yet in use
- Ready for the report: per subject, see which tests are not ready yetBuilt, not yet in use
- Finalising and releasing the report, with the rules and a zone for discussionBuilt, not yet in use
- Calculate the balance of teaching timeBuilt, not yet in use
- One register: sick reports, teachers and the front desk come together automaticallyBuilt, not yet in use
- What is still open at the administration, with one button per lineBuilt, not yet in use
- Absent without a reason: the message to the parent is ready, instead of a round of phone callsBuilt, not yet in use
- The compulsory schooling report is ready, with the days you have leftBuilt, not yet in use
- Applications, admission and placing in a classBuilt, not yet in use
- Deregister with last school day and reasonBuilt, not yet in use
- The study guide per class at the lessons, instead of a separate PDFBuilt, not yet in use
- Grades with the weighting in words, the average and the sumBuilt, not yet in use
- Undo after an actionBuilt, not yet in use
- Export everything, also for school leaders: one file with all the school’s dataBuilt, not yet in use
- Works on phone and laptopBuilt, not yet in use
- Light and dark, following your device settingBuilt, not yet in use
Planned5
- The data with one company in the EUPlanned
- Backups in a second placePlanned
- The student card: everything about one student in one placePlanned
- Online applications and importing applicationsPlanned
- Record a suspensionPlanned
Clickable example20
- Pass data to DUO, with the response that comes backClickable example
- Sending enrolments to DUOClickable example
- Receive transfer files via OSOClickable example
- Request and pass on the transfer fileClickable example
- Opening publishers’ textbooks without a second sign-in (ECK iD)Clickable example
- Manage accounts: reset two-step sign-in, invite parentsClickable example
- The year transition: everyone moves up a classClickable example
- Teaching time per cohort against the hours standardClickable example
- Searching the whole appClickable example
- Care: the students who receive supportClickable example
- Care: who looks along, only with the parent’s consentClickable example
- Care: the development perspective with its deadlinesClickable example
- Careers guidance: subject profile choice per classClickable example
- Careers guidance: does a subject package fit in the timetable?Clickable example
- Careers guidance: careers and further educationClickable example
- Exams: the exam filesClickable example
- Exams: test week and central examClickable example
- Timetable: cancellations and coverClickable example
- Timetable: the test week timetableClickable example
- Timetable: keeping track of teaching timeClickable example
Idea2
- Import grades and history from a previous schoolIdea
- The promotion rules with the school’s own numbersIdea
Clickable example: a worked-out design with made-up data, not yet in the real app. How far along we are in total
Questions
What decision-makers often ask.
Honest answers.
Does any school use it yet?
No. Ludendo is in development and not yet in use at any school. Everything on this site was made with made-up data.
Does a pilot run alongside our current system?
That has not been chosen yet: alongside the current system, or only once Ludendo can handle the whole student administration. We also agree on the scope and duration together. The export of all data has already been built; how and when you get it if the pilot stops, we will set down together.
Where is the data stored?
Nowhere yet: Ludendo is not online yet and there is no real data in it. It has been decided that the data will be with one company in the European Union, with backups in a second place. Which company it will be is still open.
Has it been tested by someone from outside?
Not yet. There has been no review by an outside developer yet and no penetration test (a trial attack by an expert). That happens before any real data goes in.
What about the sector’s agreements?
Signing in via Entree has been built and tested with a simulated Entree; the real connection has not been requested yet. OSO, ECK iD and the connection to DUO are a clickable example. We have not yet joined the Dutch education privacy covenant. An addendum to the data processing agreement, a privacy information sheet, building blocks for the DPIA and the procedure for a data breach are in draft, not yet reviewed by a lawyer. You can request them.
Which schools is it for?
For Dutch secondary education: vmbo, havo and vwo. Whether it also fits practical education, the international transition class and secondary special education, we are still finding out.
What does it cost?
That has not been decided yet: not whether a pilot costs anything, and not what Ludendo costs after that. We will only say once we know for sure.
When can a pilot start?
There is no date or year for that yet. First come the test environment and the outside review. Which school will be the first to work with real data, we choose together with the schools that think along.
Do you decide on your school’s system?
Come and get
to know us.
We show the app with made-up data, tell you honestly what already works and mostly listen. Or become a pilot school and help decide what we build first. Do not send any information about students.
Your email reaches Thomas and Geert, the makers of Ludendo. Nothing has been fixed about a pilot yet.