Our own rostering and clock-in app for Australian hospitality. Managers build the roster in the browser, and staff clock in from their phone or the venue tablet.

Built for
Pubs, cafés and venues
Platforms
Web, and a staff phone app
Stage
Private beta

kasluwork.com.au ↗All our projects

A roster gets built without knowing what it will cost under the award. Penalty rates, public holidays and super only show up when the pay run does.

Attendance is hard to prove. Paper sign-in sheets go missing, and phones lose signal in cellars and back rooms.

  • The roster costs itself

    Wage cost sits on the roster as you build it, with penalty rates, super and each venue’s own public holidays.

  • Publishing checks the rules

    Before a roster goes out it checks rest gaps, the 38-hour limit, meal breaks, a week’s notice and the two-hour casual minimum.

  • Clock-in inside the fence

    Each venue draws its boundary on a map. A clock-in only counts inside it, and taps made without signal wait and send later.

  • A tablet by the door

    Staff clock in on the venue tablet with the last four digits of their phone, a photo and the closing checklist.

  • Swaps and leave

    Staff ask, and managers approve or decline with a note. Managers can see what was sent to each person and whether it arrived.

  • Called-out shifts

    A manager can clock in someone who was called out, so the hours are still on record.

Schematic of the Kaslu Work manager roster on a phone: sections as tabs, shifts on a timeline, a late start flagged and open shifts dashedFloor plan of a pub with bar, kitchen, floor and gaming inside a dashed clock-in boundary: a clock-in inside counts, one outside is refused

The server decides
The phone only proposes a clock-in. The database accepts, rejects or flags it in one step, and corrections are new rows, so a pay dispute always has the original.
Offline is normal
Taps queue on the device and send once, even with several tabs open on the venue tablet.
One set of rules
Costing, award rules and roster drafting live in one shared package used by the web and the phone, tested once.
Each business walled off
Separation between businesses is enforced in the database itself, not only in the app.
Web
Next.js and Tailwind
Phone
Expo and React Native
Data
Supabase, Postgres and PostGIS

A pilot group is lined up. Next come payroll export to Xero, sales forecasts and an assistant that explains the roster’s numbers.

Book a free intro call

Want something like this for your business?

Free 30-minute call. A fixed quote the next day.