What can Rondus not do yet?
Rondus cannot do everything today. Training a whole rostering group falls outside our guidance, though we are glad to sit beside the scheduler for the first roster. A link with payroll or HR administration is not set up as standard, although it can be arranged in consultation with your local system administrator. And of course: your data is safe with us, with the care that belongs to it.
Who is the controller?
Your institution or rostering group, the group of specialists who share one rota. Rondus works on instruction and is the processor. For this website and for demo requests Rondus is the controller itself.
What if our cao differs?
Cao Ziekenhuizen, Cao UMC and the AMS, the terms for medical specialists, are in there as profiles. If your local agreement differs you duplicate a profile and adjust the values. One direction is fixed: an own profile can raise a statutory minimum, never lower it.
What happens to our data if we cancel?
At the end of the agreement you get the data back in a common format, or we delete it. That is your choice. Backups follow Supabase's retention periods.
Does it work on mobile?
Yes. Staff see their own roster day by day on their phone and can put it in their own calendar through a revocable link, for Outlook, Google or Apple Calendar.
What does it cost us in our own time?
We do the setting up: the shift codes, the cao profiles, the rest periods and the agreements the rostering group already has. From you that asks checking and filling in gaps, not data entry. After that you build one roster period in Rondus alongside your current roster; that is the bulk of the work and it lands with the scheduler. The rest of the rostering group notices nothing until publication.
We are not the first rostering group in our hospital. Does that matter?
Not for the monthly amount: that is per rostering group and follows the size of your own rostering group. For the setup it does, because the environment is already in place and that comes off the one-off fee. You do not have to do anything for it; we see it and it is in the proposal. We agree the planning together.
Where does our data sit?
With Supabase in the eu-central-1 region (Frankfurt), inside the European Union. Transfer outside the EU is not part of the design. The one caveat we add ourselves: static files of the application are delivered over a global network, the roster data stays in Frankfurt.
How long does implementation take?
About eight weeks from first conversation to a published roster: a week to meet, two weeks setting up together, four weeks running in parallel with your current roster and a week to go live. If your shift codes are already settled it can be shorter.
Can we enter our own rules?
Yes. Shift codes, phases, staffing requirements, the consequences of a shift and agreements per person are data, not code. You set them yourself, without us and without a new release.
Is there a data processing agreement?
Yes. A read-only version is on this site; you can print it or save it as a PDF. A signable copy is available on request.
What if part of the rostering group does not want to move?
Every shift says who was up and why: the count, the dienst-fte, the share of a full shift package each person carries, and the rules that applied. Someone who disagrees is not disagreeing with the roster but with an agreement, and that is something you can change together. Beyond that, the scheduler keeps deciding: Rondus proposes, you adopt what is right and discard what is not, and you may override a warning with an argument.
How many staff do we need at least?
There is no minimum. A small rostering group simply falls into the lowest rate.
If your question is not here, half an hour is quicker than an email.