01What a rota is made of
Take the software away and a rota is four inputs and one output. The inputs are when each person can work, how many people each shift needs, who is allowed to do what (opening, closing, handling the till) and the fixed rules you apply every week. The output is one schedule that everyone reads in the same place. Automation does not decide any of those inputs. It collects them in a fixed format, applies your rules and publishes the result. If the rules live only in the manager's head, the first job is writing them down, and that job is the same whether you use a spreadsheet, an app or something we build.
- Availability: each person's days and hours, collected the same way every time
- Demand: how many people each shift needs, per weekday
- Skills: who can open, close or work alone
- Your rules: for example no more than five days in a row, or one weekend off a month, set by you
02Why five people is a different problem
Large rota software exists to solve optimisation: hundreds of people, dozens of constraints, a solver that hunts for the cheapest valid schedule. With five people you do not have that problem. You have an exceptions problem. Someone is ill, someone has an exam, two people want the same Saturday. A person can still build the week in ten minutes, so the gain is not a cleverer schedule. It is that availability arrives on time, the published rota is the only version, and nobody goes hunting for a screenshot in a chat thread. We have not measured how much time a five-person team saves, so we quote no number.
- Collect availability on a fixed day each week, in one form, not across separate chats
- Keep one published rota; old versions get replaced, not forwarded
- Let the manager build the week if it takes ten minutes. Automate the collecting and the telling
- Count the real cost first: how many minutes the rota takes you today
03Swaps and reminders are where a rota breaks
Building the week is the easy part. The trouble starts after it is published: a swap agreed in a chat the manager never saw, a reminder nobody sent, a shift each of two people thinks the other one has. Automate this part first. A swap works as a short chain. One person asks, only colleagues who are free and allowed to do that shift can accept, the manager approves, and the rota updates and tells everyone affected. A reminder is a timed message the evening before. Approval stays with a person. The automation carries the request, it does not decide it.
- A swap request goes only to colleagues who are free and allowed to do that shift
- The manager approves; the rota changes only after that yes
- A reminder the evening before, plus a note to the manager on who is working tomorrow
- Email is the channel we can name plainly; WhatsApp or text reminders would be a custom build, priced on request
04Check the tools you already have first
Before paying anyone, try a shared calendar with one entry per shift and a form or sheet for availability. Many scheduling apps exist and some are cheap. We did not open any app's pricing page for this post, so we quote no prices and recommend none. A tool is enough when your rules are simple and your people will actually use it. A custom build starts to make sense when the rota has to talk to something else: the calendar your clients book into, payroll hours, a CRM, or a channel the tools do not support. Booking clients is a different job, and our posts on scheduling for medical offices and on appointment booking automation cover it.
- Start with a shared calendar and an availability form, and run it for a month
- A tool is enough when the rules are simple and everyone uses it
- Custom makes sense when the rota must feed bookings, payroll hours or a CRM
- Client appointments are a separate job with its own posts
05What PROOF48 would build
PROOF48's AUTOMATE plan costs 2,997 EUR a month. Its list names an AI website chatbot that qualifies and books, AI DM and email auto-responders, booking automation with a CRM, and two custom automations a month. Staff scheduling is not a line on that list, and no other plan names it. A rota with availability collection, swaps and reminders would be a custom automation, scoped from a real description of your team. Whether it fits inside the two a month is a scoping question. Without the monthly plan, a single build is scoped and priced on request through the start page. Our post on what two custom automations a month means explains the allowance.
- AUTOMATE: 2,997 EUR a month, with two custom automations included
- Staff scheduling: not a listed feature, so it is scoped as a custom build
- A single build without the plan: priced on request at the start page
- WhatsApp and phone: outside AUTOMATE
06Where PROOF48 is the wrong choice
We are the wrong choice in three cases. If a shared calendar already works, keep it: automation would add a system to maintain for a problem you do not have. If your rules change every week, automation will run the confusion faster, which is why we map the process before we build. And if you want the system to settle a question about working time, it cannot. Rest periods and overtime are rules you define in writing with your accountant or a labour-law professional, and a person stays accountable for them. We did not research Romanian working-time law for this post, so we state none of it.
- A shared calendar already works: keep it
- Rules that change weekly: agree them first, automate after
- Working-time law questions: a professional's call, not a tool's
- A pattern that never changes: print it and pin it up
A team that reads its work on a phone
ATP Spedition runs courier, moving and freight from one transport management system PROOF48 built: a web dispatch console for the office and driver apps on iOS and Android that keep working offline. That is a dispatch system. The case study does not describe shift rosters or staff availability, so we claim neither. What carries over to a five-person team is the shape: decide in one place, and let people read the result on their phone. The office should never have to ask whether everyone is looking at the same version.
See the build: ATP SpeditionQuestions, answered
Does a team of five need scheduling software?
Often not. A shared calendar with one entry per shift and a weekly availability form covers most small teams. Software earns its place when swaps, reminders or a second location create more messages than you can track by hand. Count the minutes your rota takes today before deciding.
Can staff swap shifts without calling the manager?
They can ask without calling. The request goes only to colleagues who are free and allowed to cover, and the manager approves before the rota changes. The decision stays with a person.
Does PROOF48 sell a scheduling tool?
No. No PROOF48 plan lists staff scheduling. A rota would be a custom automation, scoped from a description of your team and priced on request at the start page, or discussed as one of the two custom automations a month in AUTOMATE.
Can the rota enforce working-time rules?
It can apply rules you give it, for example a maximum number of days in a row. It does not know the law and it is not legal advice. Define the rules in writing with your accountant or a labour-law professional, and keep a person accountable for them.
Where PROOF48 fits
Automate the collecting and the telling, not the deciding: one place for availability, one published rota, swaps that need a yes, a reminder the evening before. A shared calendar may already do it. If your rules need more, PROOF48 would build it as a custom automation, because no plan lists staff scheduling. AUTOMATE costs 2,997 EUR a month and does not cover WhatsApp or phone.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.