Ludendo

For school leaders · in development, not yet in useFor school leaders · in development

Deciding calmly.
With the reasons.

How the school is doing, what is waiting for your decision and who may do what. The report, leave and absence are ready with the rules. Without separate lists.

Walk through the day

Erik Mulder is the head of Het Voorbeeld College. Thijs Kramer is a team leader there. All screens show made-up data.

Phone screen of head of school Erik Mulder with made-up data: what is waiting for him. The leave request for Eva de Wit and the 4V2 report, with 10 of the 11 subjects ready. Below that: the administration still has 8 things open, and today 2 of the 412 lessons are cancelled.

· School leaders · Erik, between two meetings

How the school is doing.
On one screen.

Erik Mulder sees per department the teaching time, absence, passes and compulsory schooling side by side. What needs attention, you see straight away.

Clickable example: the overview is not in the app yet. Built, not yet in use: calculating the teaching time balance.

Skip the day
  1. The school in four numbers. 1,184 students, 4.1% absence and 82% passes in term 1. And one cohort has too few teaching hours.
  2. Per department. The first year, the lower school, havo 4 and 5 and vwo side by side. For havo the team leader is shown: Thijs Kramer.
  3. What falls short. Vwo 5 gets 68 hours too few lessons over the whole programme. Erik sees it now, and makes a plan to make up the hours.
Laptop screen of head of school Erik Mulder with made-up data: the overview of Het Voorbeeld College in term 1. 1,184 students, 4.1 percent absence, 82 percent passes and 1 cohort with too few hours. Per department: the first year with 214 students and 38 hours above the standard, the lower school with 398 students and 24 hours above, havo 4 and 5 of team leader Thijs Kramer with 268 students and 88 hours above, and vwo with 304 students, where vwo 5 is 68 hours below the standard. Per cohort: vwo 5, started in 2022, has 5,632 hours planned, the standard is 5,700. Erik taps Make a catch-up plan.

· School leaders · Erik, on his laptop

Deciding on leave.
With what the law says.

Last night Mark de Wit requested two days of leave for Eva in the app, for a wedding in the family. The request reaches Erik straight away, with the rules.

Built, not yet in use. Deciding on leave, with the reasons the parent reads.

  1. The request. Eva de Wit, 3H3: Thursday 19 and Friday 20 November. Requested by her father, who has parental authority.
  2. What the law says. Up to and including ten school days the head of school decides, above that the attendance officer. A wedding in the family is an important circumstance. And it is her first leave this school year.
  3. Granting, with one sentence of explanation. Mark reads the same words in the app. Even with a no, he knows why. The leave shows up in Eva’s absences straight away.
Laptop screen of Erik Mulder with made-up data: the leave requests of this school year. At the top, the request for Eva de Wit, 3H3, is waiting: Thursday 19 and Friday 20 November, 2 school days, for a wedding in the family, submitted by her father Mark de Wit on Thursday 8 October at 20:14. What the law says: ten school days or fewer, so the head of school decides; a reason the law recognises; the first leave this school year. Erik grants it with the reason: a wedding in the family is an important circumstance. Mark gets a message.

· School leaders · Erik, on his laptop

Finalising the report.
Only when everything is ready.

Term 1 ran up to and including today. Erik sees per subject whether the tests are ready, and who the report meeting needs to discuss. Nobody has to ask around.

: Built, not yet in use ready for the report per subject, Built, not yet in use and finalising and releasing with the promotion rules.

  1. Ready for the report? In 4V2, 10 of the 11 subjects are ready. In chemistry, Sem Jansen still has to sit the test Acids and bases.
  2. The rules, with a zone for discussion. 19 students pass everything. 4 will be discussed at the report meeting. For Sem, one grade is still missing.
  3. Finalise, then release. After finalising no teacher can enter grades any more. That is why Erik waits for Sem. You release after the meeting, and that cannot be undone.
Laptop screen of Erik Mulder with made-up data: the term 1 report of 4V2, 24 students. Ready for the report: 10 of 11 subjects. Only chemistry is waiting: Sem Jansen is catching up on the test Acids and bases. The progression rules: 19 students pass everything, 4 to discuss (Daan Smit, Jesse Bouma, Milan Kok and Lotte de Wit) and 1 not complete yet. What happens next: finalise, the report meeting on Tuesday 27 October, and release, which cannot be undone. The Finalise button only works once chemistry is ready.

· School leaders · Erik, on his laptop

Keeping an overview of absence.
Who is nearing the limit, you see in time.

If a student misses 16 hours or more without a valid reason in four school weeks, the school reports it to DUO. Erik sees per department who is over it and who is getting close. The work stays with the administration.

: Built, not yet in use absence per class and compulsory schooling, Built, not yet in use and looking along with the administration.

  1. Per department. Absence over the last four school weeks, as a percentage of the lesson hours. Sick, doctor and leave do not count for compulsory schooling.
  2. Around the limit. Ravi Peeters (3H2) was at 17 hours. The administration reported it at 11:40. Jesse Bouma (4V2) is at 13 of the 16 hours: his mentor is talking to him.
  3. Looking along, without buttons. Erik sees the same list as Sanne Vos from the administration: 8 things still open. That way he knows whether it is busy.
Laptop screen of Erik Mulder with made-up data: absence over the last four school weeks per department, from 3.2 percent in the first year to 5.4 percent in havo 4 and 5. Around the limit of 16 hours without a valid reason: Ravi Peeters from 3H2 with 17 hours, reported to DUO by the administration at 11:40; Jesse Bouma from 4V2 with 13 hours; Bas Meijer from 4H1 with 12 hours. Then Erik looks along with the administration, read only: 8 things still open. 2 from earlier days, 1 absent without a reason today, 1 about compulsory schooling, 2 requests from teachers and 2 applications.

· School leaders · Erik, on his laptop

Who may do what, per role.
What is not switched on, nobody may do.

Every screen in the app checks who may do what: everything, only for their own students, only in their own department, or nothing. Erik sees it in one overview.

: Built, not yet in use giving the right to manage absence codes, Built, not yet in use and more roles in one account. Permissions in one overview: still a Clickable example.

  1. All permissions in a row. For each permission you see which role has it. A parent only sees their own child, a teacher only their own classes.
  2. One extra permission. Erik gives the administration the right to manage absence codes. Everyone with that role gets it straight away, including Sanne Vos. His name goes into the log.
  3. Two roles, one account. Thijs Kramer teaches maths and is team leader of havo 4 and 5. He signs in once and sees both.
Laptop screen of Erik Mulder with made-up data: an overview of permissions against the roles student, parent, teacher, mentor, administration and team leader. A parent sees their own child’s grades, a teacher those of their own classes, the administration those of all students, the team leader those of his department. Erik switches on the permission Manage absence codes for the administration; at the bottom is the notice with Undo. Only the school leaders may change permissions. Then Thijs Kramer’s account, with two roles: maths teacher for 3H3 and 4V2, and team leader of havo 4 and 5.

· Team leader · Thijs Kramer, after his last lesson

Teaching and leading a department.
In one app.

Thijs Kramer teaches maths, to Lotte too. And he is team leader of havo 4 and 5. After his last lesson he reads along with the 5H1 report, before the report meeting.

: Built, not yet in use teacher and team leader in one account, Built, not yet in use and reading along with the report. The overview of the department is a Clickable example.

  1. First his lessons. Maths in 4V2 and 3H3 are done. Below that, after a line, what he does as team leader.
  2. Reading along with the 5H1 report. 24 of the 27 students are ready. He will discuss Thomas van Dam and Sven de Lange at the meeting. Finalising is done by the school leaders.
  3. His department. Havo 4 and 5 with 268 students: absence, passes and who is nearing the limit. This overview is still a clickable example.
Phone screen of team leader Thijs Kramer with made-up data. At the top his maths lessons: 4V2 at 09:20 and 3H3 at 12:40 are done; in 3H3 Eva de Wit was reported sick. Below that, as team leader of havo 4 and 5: the 5H1 report to read along with, and the administration with 8 things still open, only to view. The 5H1 report: 27 students, 24 ready, 2 to discuss (Thomas van Dam failing 3 subjects, Sven de Lange with English from 7.1 to 5.6) and 1 not complete yet: Nina Kuipers is missing economics. Finalising is done by the school leaders. Then his department: 268 students, 5.4 percent absence, 78 percent passes and 88 hours above the standard. Bas Meijer from 4H1 is nearing the limit with 12 of 16 hours.

What else it can do

Everything for school leaders.
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. What the team leader can do is here too.

Built, not yet in use15
  • 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
  • Decide on leave, with the reasons the parent readsBuilt, not yet in use
  • Absence per class, who is over the limit, and compulsory schoolingBuilt, not yet in use
  • Setting the school’s absence rules and thresholdsBuilt, not yet in use
  • Absence codes per school, and giving that right to the administrationBuilt, not yet in use
  • Looking along with what the administration still has open, without buttonsBuilt, not yet in use
  • More roles in one account, such as teacher and team leaderBuilt, not yet in use
  • Calculating the teaching time balance (the calculation rule; the screen is still an example)Built, not yet in use
  • Set up programmes, student numbers, leaving reasons and the resit ruleBuilt, not yet in use
  • Export everything: one file with all the school’s dataBuilt, not yet in use
  • The log: who signed in, who opened which file and who changed what, in plain sentencesBuilt, not yet in use
  • Team leader: teacher and team leader in one accountBuilt, not yet in use
  • Team leader: reading along with a class reportBuilt, not yet in use
  • Team leader: looking along with what the administration still has openBuilt, not yet in use
Clickable example9
  • Overview of the school with key figures, per departmentClickable example
  • Teaching time per cohort against the hours standardClickable example
  • All permissions in one overview and adjust them yourselfClickable example
  • Switch on what your school uses; off is really offClickable example
  • School absence per week, term or reasonClickable example
  • Results per year group and classClickable example
  • Annual calendarClickable example
  • ComplaintsClickable example
  • Team leader: your department with classes, results, absence and cancellationsClickable example
Idea1
  • Setting the promotion rules with the school’s own numbers (for now the app uses one fixed rule)Idea

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

You decide.
The work stays where it belongs.

Administration

Sanne Vos handles what is open: messages to parents, compulsory schooling, applications. You look along, without buttons.

The team leader

Thijs Kramer reads along with the reports of his classes and sees his department. You finalise and release.

The parent

Mark de Wit requests leave in the app and reads your reasons. Nobody has to call to ask why.

The data belongs to the school: with one button you export everything in one file. Anyone who opens or changes something goes into the log. Back to the day of the whole school

Would you like this at your school?

Let’s
get to know each other.

We are looking for schools that want to try it together with us. Do not send any information about students.

Email us How far along we are