Is a free shift scheduling app enough for a 12-person care team?

One of the first documents they look at during a care audit is the shift roster. If you use a free app that doesn't flag violations of the daily 11-hour uninterrupted rest period, inspectors will write up management directly.

We tried a free tool back when it had a 10-person limit. The day our 11th nurse started, the app locked the entire team out of the calendar and wouldn't display any rosters until we paid 4.50 Euro per person per month. We had no choice and ended up paying 54 Euro that month.

Stop sharing patient addresses and staff shift info in messaging group chats immediately. If someone files a complaint, penalties for healthcare data privacy violations are extremely severe.

When monthly salaries and vehicle expenses for a 12-person care team easily run into tens of thousands of Euros, pinching pennies over a 50 Euro/month shift scheduling software—the absolute backbone of your operation—makes zero sense to me.

When choosing software for a care service, verify these 3 things: 1) Servers are in Germany or within the EU and an AVV can be signed, 2) The system warns you about statutory rest period violations, 3) Phone support is available for emergencies.

push notifications are usually delayed on free tools. when a morning shift was changed and the notification didn't go through we had staff showing up late for their shifts.

Are all 12 people on the team full-time, or do you have part-timers or minijob workers? Some paid systems offer discounts by counting part-timers as half a license.

If your budget doesn't allow for it right now, stick to the Excel sheet on the board, but add basic formulas to track rest hours. That's the safest middle ground until you can budget for proper business software.

I agree. Just because everyone does it doesn't mean it's right.

This is my opinion, I'm not claiming it's absolute truth.

we need to take it step by step. code without setup documentation isnt yours even if you have it.

i'm also curious if anyone does it differently.

I'm writing this so you don't make the same mistake. The answer varies greatly by industry; there is no one-size-fits-all rule.

If code ownership isn't in the contract, you have no bargaining power when leaving. This is my opinion, I'm not claiming it's absolute truth.

There's a trap here let me mention it. The biggest time-waster for us was not knowing who had the final say.

Just because everyone does it doesn't mean it's right. If you post the result here, it will help others too.

We need to take it step by step. Don't hesitate to ask; those who don't ask always pay more.

Weekly written progress reports are much more useful than asking for dates.

My perspective changed after experiencing that. In legacy systems, the most expensive thing is unknown dependencies.

This is my opinion, I'm not claiming it's absolute truth.

My question might sound amateurish, sorry about that. When we decide without measuring, we always end up in the same place.

I was thinking the same thing. Solutions that work at a small scale collapse when you grow; I learned this late.

Good luck with that.

There's also a measurement aspect to this. I mean the system lives on after delivery; maintenance is a separate line item.

Good luck with that.

Yes that's exactly how it is with free shift scheduling app... honestly the real issue isn't the number, but what it's based on.

If you don't write this down from the start, it leads to arguments later... tbh good luck with that.