KiddieDesk

Every task in a nursery’s day touches the same child. Who dropped her off this morning, what did he eat at lunch, was the medicine given, who collected her in the evening, has this month’s fee been paid. When those records live in separate notebooks, chat groups and spreadsheets, a change in one never reaches the others. KiddieDesk is the management platform VenusSoft builds for nurseries and preschools, and enrolment, daily care, parent communication, safe pick-up, health, the kitchen and finance all work on the same child and family record.

The product has three surfaces. The school web panel is the shared door for the principal, the teachers and the parents; there is no separate parent portal, and a person’s role decides what they see. The iOS and Android app is in the pocket of parents and teachers: parents follow their child’s day, menu and health notices, and teachers keep attendance and daily logs from inside the classroom. The back office for the team that runs the platform ships as a separate bundle, so none of its code ever reaches a parent’s browser.

The most sensitive moment of the day is pick-up, and the system records it as an event of its own. A parent can say in the app who will collect the child and roughly when, but the people they can choose from are limited to the school’s approved pick-up list. Someone who is not on it, even if they are authorised for another child, cannot be chosen. If a person’s authorisation is withdrawn before the hand-over is confirmed, staff cannot confirm it and the child stays inside. Tapping a card at the door does not count as a hand-over either: the card read, the attendance record and the hand-over are separate records. A hand-over is complete when the person collecting the child and the staff member releasing them are matched on the same record.

Health gets the same caution. A parent opens a medicine request with the dose, the time window and the instructions, but the request is not an order: it reaches the teacher’s daily list only after the school accepts it. Every dose given, not given or refused is recorded with its reason, the person who gave it and the actual time, and the parent is notified. The same dose cannot be marked twice, and a request sent again because the connection dropped does not create a second request.

In the kitchen, the menu is checked against each child’s allergies, intolerances and diet. An allergy match blocks, an intolerance warns, and a preference is only shown as information. An ingredient with no declared allergen information is not treated as safe. The software warns, but the final check stays with the person in the kitchen.

The thing most easily missed in school software is that a permission is not the same as a data scope. In KiddieDesk the same read permission narrows to a parent’s own child and to a teacher’s own class. When someone asks for a record outside their scope, the system does not say “access denied”; it behaves as if the record does not exist, so not even another child’s existence is given away. Gallery sharing depends on parental consent child by child. Each school’s data is kept apart at the database level, and one person can belong to several schools in different roles: a parent at one, a teacher at another.

No two schools arrive with the same needs. Modules can be switched on and off per school, and those that depend on each other are managed together; a nursery without a school bus never sees the bus screens. On the finance side, contracts, charges, collections and parent statements are kept to the cent, and payment, e-invoice and accounting providers are designed to connect through a separate adapter layer.

Automation and AI are there to lighten the work, not to make the decisions. Before an automation rule goes live, the school can preview whom it would affect that day. Drafts prepared by the AI are not applied until an authorised person approves them.