BKR calculation and staffing in childcare
The GGD (the Dutch health authority that carries out inspections) uses the same calculation tool as you do during an inspection, so working out the ratio is not the problem. The question is whether you can show that the ratio was correct for the whole session, including around breaks, when a child was collected early, and within the three hours in which you may deviate.
Why a snapshot is not enough
The staff-to-child ratio sets the minimum number of qualified staff that must be present with a group. In daycare, that is one to three for children under one, one to five for ages one to two, and one to eight for ages two to four. In out-of-school care, it is one to ten for ages four to seven and one to twelve above that. The ministry provides a calculation tool, and the GGD uses that same tool during inspections.
So the ratio itself is clear-cut. What makes it difficult is that it applies at every moment, and every variable keeps changing. Children are dropped off and collected at different times, swap days, and move to a different age category on their birthday. Staff take breaks, call in sick and sometimes work at two locations. Each of those events changes the outcome.
There is also the three-hour rule: you may deviate from the ratio for a maximum of three hours a day, provided your policy sets out when. That is not a free pass but an agreement, and during an inspection you will be asked whether reality matches what your policy says. Without recording each moment, that cannot be reconstructed afterwards. The calculation tool and its guidance can be found at 1ratio.nl.
How we build this
The starting point is the day as it actually unfolds, not the planning. The planning is almost always right; the day deviates from it, and it is precisely that difference the system needs to capture.
Which groups, which age mix, which opening hours and which break structure. With vertical or combined groups the calculation gets complicated straight away, and that shapes the set-up.
At which times you deviate, and why. Those periods come from your own pedagogical policy, and we adopt them as a rule so the system can check whether practice matches.
Every sprint ends with something you can check yourself, and we start with recording drop-offs and pick-ups. Without those moments, every ratio calculation is just an assumption about the planning.
We have the system recalculate a past week and compare the result with what you expected. That usually turns up a moment nobody had noticed.
What the software actually does
The ratio per moment is the core; recording drop-offs and pick-ups is what feeds it. The rest makes it usable on the group floor.
Ratio at every moment of the day
Not one result per session but a continuous line, because staffing changes with every child who arrives or leaves. That way you see where the day gets tight, instead of hearing about it afterwards.
Recording drop-offs and pick-ups
On the group, in seconds, by the childcare worker or by the parent themselves. If this is filled in at the end of the day, it contains times nobody actually observed and the reconstruction will not be accurate.
The three-hour rule monitored
The system counts how much deviation time you have used that day and checks whether the moments fall within your own policy. A deviation outside the recorded periods is something different from a deviation within the three hours.
A warning before it goes wrong
A break that starts while there are too few staff on the group is a signal in the moment, not in a monthly report. That is the difference between steering and merely noting.
Qualifications and registration taken into account
A staff member only counts if she is qualified and listed in the Personenregister Kinderopvang (the national childcare staff register). A trainee counts differently. Those rules belong in the calculation, not in the location manager's head.
File for the GGD inspection
You can read back how staffing went for each day and each group, with the deviations and their justification. Preparing for an inspection then becomes a check rather than a reconstruction from rosters and attendance lists.
Who we build for
The number of locations and whether you work with mixed-age groups determine the complexity. Four situations.
Day nurseries
Here the ratios are at their strictest and children move between categories on their birthday. With mixed-age groups, the required staffing changes as a result, without anything having been altered in the planning. If a quality file also runs alongside this, see HKZ quality manual.
Out-of-school care
Looser ratios but far more variable: short afternoons, training days, holiday weeks with different opening hours. The challenge is that staffing differs by type of day and the planning does not follow suit.
Organisations with multiple locations
Staff who cover at another site, plus the question of which location is running short. With dozens of locations, that overview is the real reason to build this. With multiple locations, this touches on staff scheduling.
Childminder agencies and networks
Different rules and different administration, but the same problem: proving that it was correct at every moment. Establish which standards apply to your form of childcare before you build anything.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Registration happens in the group room, with a staff member holding a child, so one-handed operation is a design requirement. In addition, the calculation rules change, so they should be configurable and stored per period.
If you want to compare your locations against the National Childcare Register (Landelijk Register Kinderopvang) and see every difference, read more about our LRK integration.
If you want annual statements for all parents in one go, checked against the invoices, take a look at our software for contracts, invoices and hours statements.
For healthcare, where staffing follows from clients' care intensity, there is our software for scheduling by care intensity.
For hours per child per month and the statement for the childcare benefit, there is our app for the hours statement for childcare benefit.
Why Appfront
The GGD uses the same calculation tool
Calculating is not your problem; proving it is. That is why we do not build yet another calculation tool, but the registration underneath it, which substantiates the outcome for each moment.
Steering rather than noting
A ratio that turned out to be wrong after the fact can no longer be put right. The alert should come at a moment when someone can still be brought in.
The three hours are an agreement, not a margin
In an inspection, what matters is whether practice matches your own policy. We test against that, and not just against the total number of hours.
Honest about our role
We are not a pedagogical adviser and not a regulator. Which standards apply to your form of childcare and what your policy says is for you to decide; we build the system that carries it out and records it.
Security and privacy
This concerns children, and that makes every consideration stricter. A child's attendance data says something about the family: who drops off and picks up, on which days a child is there, and sometimes how a contact arrangement works. That last point is particularly sensitive with separated parents. We separate the operational registration from everything related to the family situation and set up access to it separately.
Something similar applies on the staff side. Qualifications and registration status are needed for the calculation, but the reason someone doesn't count doesn't need to be visible to everyone on the group. The daily record is also immutable: a correction shows up as a correction and doesn't overwrite the original, because in an inspection or an incident, what counts is what was recorded at the time. A system in which times can be smoothed over after the fact works against you. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the BKR
In daycare, one qualified childcare worker for every three children under one, one for every five children aged one to two, and one for every eight children aged two to four. In out-of-school care, one for every ten children aged four to seven and one for every twelve above that. For mixed-age groups, the ministry's calculation tool is used. Check the current standards, as they have changed in recent years.
Because the calculation tool gives a snapshot, while an inspection covers the whole day. The GGD (the regional health authority that inspects childcare) uses that same tool, so it won't set you apart. What's missing is the record underneath it: at what moment there were how many children of which age, and how many qualified staff. That is what you need to be able to demonstrate.
It keeps track of how much deviation time you have used that day and checks whether those moments fall within the time slots you've set out in your policy. That distinction matters: deviating for three hours at times that aren't in your policy is different from deviating for three hours as agreed. In an inspection, it's the second that is looked at.
The child moves into a different age category and the required staffing changes, without anything having changed in the schedule. The system processes this automatically and flags it in advance so the planner can take it into account. In mixed-age groups, this is one of the most commonly missed causes of a shortfall.
That depends on their qualification and on the rules that apply to your type of childcare; staff in training have their own conditions. We implement those rules as a setting rather than hard-coding them, so a change doesn't turn into a rebuild. What exactly applies is something you determine with your own adviser.
Often it can, and that is the intention: your planning system remains the source for contracts, placements and rosters. We pull from it who is scheduled, and record alongside it who was actually there. It is precisely the difference between those two that matters. Which integration is possible depends on your package; we map that out beforehand. That goes through integrations.
Only if it can be done with one hand and in seconds. A childcare worker often has a child on their arm and no time for a form. We build it as a single action on arrival and departure, optionally done by the parent themselves on a tablet at the door. If it's filled in at the end of the day, the record is worthless.
That depends on the number of locations and groups, whether the three-hour rule is included and whether it needs to integrate with your child planning system. The daily registration with the ratio per moment is usually quick to put to use and delivers the most; the integrations cost more. We give a well-founded estimate after the discovery phase.
Building BKR software?
Take any day from last month and try to demonstrate that the ratio was right at quarter past two. What you would need for that is exactly what this system records. We build this as a standalone app and as part of a broader custom software project.