Fifteen people, and the same round of asking every week
Who can work Saturday, and how many hours did you do. Two questions you put to everybody separately every week, and the answers come back as fifteen loose messages that somebody has to add up at the end of the month.
Yourteamalreadyknowswhenitcanwork.Whatismissingissomewheretoputit.
How does a team report its own hours and availability?
Itself, in the same app where it sees its shifts. Nivora builds it so your team marks when it can work for the coming weekends, and enters its own hours after each shift. You get that as one list you confirm with a single click, rather than as fifteen messages you have to count up yourself. When a busy day is coming, the people who said they were free that day get asked, instead of you working down a phone list on Thursday evening.
What comes out is a proposal, not a rota. Who actually stands there, under which status and with which Dimona, stays your business and your payroll office's, and we say that before we start rather than in a clause afterwards.
It runs on the phone your team already has in its hand. No badge, no clocking machine, no second device that ends up in the sand. Somebody who starts in July is set up in the time it takes to send them a link.
Where that round of asking sits in your week
Availability comes in however it comes in. Somebody answers in the group, somebody messages you separately, somebody says it at the bar and somebody does not answer at all. What you are left with is a sheet with names crossed out and a fair chance that you asked one person twice.
The hours come afterwards. Fifteen people who roughly know at the end of the month how much they worked, and one person who has to add that up before it goes to the payroll office. Whoever is out by half an hour is out by half an hour, and nobody can check it back.
And on the days it really matters, you ring around. On Thursday evening it turns out Saturday is going to be heavier than you thought, and then the row of phone calls starts to people who already have something else on.
How this is put together
The team fills it in itself
Availability for the weeks that are coming, in half a minute, from the phone. Not a form with twelve fields but the days with a yes, a no and a maybe. Whoever has not filled anything in is visible instead of invisible, which is the whole difference with a group chat.
Hours after the shift, not at the end of the month
They enter it as they walk out, while they still know exactly when they came in. You confirm with one click. Anyone who enters something different from what was planned stands out rather than disappearing, and both of you can see the same thing, which takes the discussion out of it before it starts.
We do not make your rota
This says who is available and how many people a day looks like it needs. Who you put on, under which status, with which Dimona and inside which sector agreement stays with you and your payroll office. That is not modesty, it is a line we do not cross: those rules change and getting them wrong is not our risk to carry for you.
Other solutions for a beach bar
The rest of what we build for this trade. Each one is a separate thing you can ask for.
How busy it gets
One sheet every evening for the day after tomorrow, out of your own till, the weather and the tide, with an honest monthly score.
See what this looks like
Off WhatsApp
Your guest books through your own site or app, with a waiting list when you are full. Three hundred messages a week become one list per day.
See what this looks like
Who gets the bed
Regulars confirmed straight away, unfamiliar names on hold until you know. You keep the decision, the system prepares it.
See what this looks like
The day on one screen
Every booking, the places still free, who is working and the forecast per hour. One picture, behind the bar, for whoever opens the shift.
See what this looks likeDoes this sound familiar?
If two or more of these land, there is almost certainly something to gain.
- Every week you ask fifteen people the same question
- The hours get scraped together at the end of the month
- On Thursday evening you ring around for Saturday
- There has been a discussion about hours nobody could check back
What we are not going to claim
We are not going to say this makes your rota. Planday, Shiftbase, Eitje and Nostradamus do exactly that, and if you already work with one of them this comes alongside it or it does not come at all. What we build is for the business that runs on messages today and does not want a second subscription in order to stop.
We are not going to promise time registration that counts for an inspection. Dimona, the attendance rules and the flexi-job regime run through your payroll office and they stay there. What stands here is what your team entered and what you confirmed, which is worth a great deal internally and is not a legal record.
And we are not going to say everybody fills it in. In the first weeks not everybody fills it in. The difference is that you can see who, on Tuesday, instead of finding out on Friday at four.
Stop worrying about AI
We weigh up what AI can genuinely do for a business like yours, cut through the noise, and keep you posted on what actually matters. You stay in the loop, without the hype.
Questions, answered
The things people usually want to know before they reach out.
No, and we would rather be blunt about it than let you find out later. What is in here is what your team entered and what you confirmed. Dimona, the attendance registration where it applies to you, and everything around flexi-jobs and student contracts runs through your payroll office exactly as it does today. This sits next to that, to stop the counting up by hand.
Still have a question?
Visit the Help CenterSend us last week's round of asking
The messages you filled last Saturday with, and the hours as they eventually reached your payroll office. We show you which part of that could have run by itself and which part stays work for people, before anything is agreed or signed.
