Build log, weeks 2 and 3: no signal, night shifts and a quieter dashboard
A clock-in made with no signal is now held and sent later, a 10pm to 2am shift stays on the night it belongs to, and the dashboard stopped treating a slow day as an emergency.
These two weeks were less about new screens and more about the moments where a real shift breaks software.
The biggest one is signal. Staff clock in from cool rooms, basements and car parks, and plenty of apps just fail there. Now the phone saves the clock-in with the time and place it actually happened, then sends it when the connection comes back. The server still makes the call when it arrives, and it recognises a clock-in it's already seen, so a patchy connection can't turn one shift into two.
Night shifts and slow days
A shift from 10pm to 2am used to drop off the board at midnight, which is exactly the moment a manager is most likely to be looking. It now stays on the night it started, the way anyone who's closed a bar thinks about it.
The dashboard had the opposite problem. It raised the alarm over a quiet Saturday as if the place were on fire. It now saves its warnings for the gaps worth acting on.
The small things that make it feel finished
Invitations open when you tap them now, which they should have from the start. The setup checklist remembers where you were if you close the app halfway. Fixes reach phones without a trip through the App Store each time, and sign-in is kept in the phone's secure keychain rather than ordinary storage.
Two fixes came straight from using it. When you copy a week and a venue gets skipped, you're told which one instead of finding out on Friday. And managers can now see the hours somebody actually worked sitting next to what was rostered.
The week after this, we changed who Kaslu Work is for.
Control every hour, at every venue.
Rostering and clock-in for hospitality groups. Join the waitlist.
Keep reading
Build log, week 1: the server decides who's on the clock
The first week of Kaslu Work: venues drawn on a map, a roster that publishes in one step, and a clock-in the phone can't approve by itself.
2 min read
Build log, week 4: hospitality, a new staff app, and rows that are places
We moved Kaslu Work to Australian hospitality, rebuilt the staff app around the clock-in, and laid the roster out by the bar, the floor and the kitchen instead of by person.
1 min read
The Best Rostering App for Australian Hospitality Groups
Most rostering apps are built for one venue running one way. Here's what to ask before you commit, especially if you run more than one site.
7 min read