Why RotaGrid exists
A small, bootstrapped team in Brussels and Barcelona. This page is what we would want to know about a company before handing it our own team's schedule: where the product came from, what we are here for, and what happens to your data.
It started with one rota
The team leader of a hospital laboratory in Brussels was building the lab's schedule by hand, month after month, and losing days to it. Days spent on a rota that still left people unhappy about who got which weekend.
The first version of RotaGrid was built to give those days back. Almost everything since has come from the same place: a real team, a real month, and a constraint that would not fit in a spreadsheet. That is still how we decide what to build next.
What we are here for
RotaGrid exists to give every team leader the scheduling capability of a workforce-planning department. The tools that balance hours, hold coverage and keep a roster inside its own rules have existed for decades, in large employers with a department to run them. A team of fourteen has the same problem and none of the department.
Every row is somebody's week
The point of automating a rota is not that it saves you an afternoon. It is that your team gets hours they can plan a life around, published early enough to be worth planning around.
Where your data lives
Hosted in Germany
The application and its backups both run on EU infrastructure in Germany, and the backups are encrypted. Our privacy policy lists every sub-processor that sees anything, and says what each one is for.
Talk to us
One address, and a person reads it. About the product, about your data, or about anything on this page.