What can Rondus not do yet?
Rondus cannot do everything today. The Capacity module is still in development, and full operating theatre planning is outside Rondus. Links with payroll or HR administration are not set up as standard, but they are possible together with your care organisation.
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.
We are self-employed. Does Rondus work for us too?
Yes. For self-employed specialists the agreements of your rostering group apply; you set those up as an own profile.
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, in Dutch; 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 proposed shift says why that person was up: the count, the dienst-fte, the share of a full shift package each person carries, and how many colleagues could work the shift within the rules. 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. For a small rostering group too, we make a fitting proposal.
Is the Capacity module needed?
No. You can make the whole roster without it: Rondus then plans on the staffing you set for each shift code. The Capacity module is optional and in development.
Where does our data sit?
With Supabase in the eu-central-1 region (Frankfurt), inside the European Union. For the roster data, transfer outside the EU is not part of the design. Two caveats we add ourselves: static files of the application are delivered over a global network, and Vercel's session check runs in the region nearest the user, also outside the EU. The roster data itself is stored in Frankfurt.
How long does implementation take?
Full implementation takes about a quarter of a year, once procurement and the privacy review have approved. After that we stay available for help, including by sitting next to you. We want to give you the best experience and let you get to know the system well.
What if our cao differs?
Cao Ziekenhuizen and Cao UMC are in there as profiles. If your local agreement differs you duplicate a profile and adjust the values. The collective agreement (cao) is the floor; an own profile can be set stricter, never looser. Outside the hospital, Rondus has no built-in collective agreement profile; we will discuss with you which rules apply.
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 have a personal app in which they see their roster day by day and pass on their requests. They can also put the roster 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 collective agreement profiles (cao), 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 organisation. 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.
Does Rondus take over the scheduler's work?
No. Rondus does the arithmetic: sharing out shifts, checking rules and finding bottlenecks. The scheduler keeps the decisions. You can adjust shifts within the legal limits, and every proposed shift shows why Rondus proposes it that way. That leaves the scheduler time to weigh things up, talk them through and look ahead.
If your question is not here, half an hour is quicker than an email.