Your rota in your pocket: the BookingNinja staff app is live on iPhone and Android

The BookingNinja staff app is live in the Apple App Store and on Google Play. It's free, it's invite-only, and it covers the four things a team needs from...

Release artwork for Your rota in your pocket: the BookingNinja staff app is live on iPhone and Android

The BookingNinja staff app is live in the Apple App Store and on Google Play. It's free, it's for staff at venues that run their rota on BookingNinja, and it covers the four things a team actually needs from a rota: knowing when they're on, changing it when they can't be, booking time off, and clocking in.

Download on the App Store Get it on Google Play

Managers carry on building rotas exactly where they do now. This is the other side of it.

How your team gets on it

The app is invite-only. You invite staff by email from the rota admin, they tap the link, set a password, and they're in. Nobody can create their own account, so the only people who can see your rota are people you put there. Deactivating someone cuts their access immediately, on every device they're signed in on.

Anyone who would rather not install an app still has the browser portal, which does the same job.

The home screen

The home screen answers "what's happening today" without any navigation.

The staff app home screen showing the time clock, shifts to acknowledge, the next shift and weekly hours

Top of the screen is the time clock: clocked in or not, how long the current shift has been running, and buttons to start a break or clock out. Under that, a banner for any shifts waiting to be acknowledged. Then the next shift — date, start and finish, team, role and rostered break — followed by hours worked this week and next against contracted hours.

Clocking in

Staff clock in, start and end breaks, and clock out from the app. Three details matter:

  • The server stamps every punch. The app never sends a time, so a phone with a fast, slow or deliberately-set clock cannot pad anyone's hours.
  • The shift is matched at clock-in, to the nearest published shift within four hours of its start time. An early arrival or a late start still attaches to the right shift, and re-rostering afterwards never moves worked time. No matching shift is still a valid entry — it's recorded as unscheduled and flagged for you.
  • Breaks are derived, not typed in. Punched breaks are totalled. If nobody punched a break but the shift had one rostered, the rostered break is applied and marked as such.

App punches and kiosk punches are the same records, so someone can clock in on the tablet by the door and clock out on their phone. Everything lands in your timesheets for approval. While a shift is running the app polls the server rather than counting locally, so a punch made at the kiosk shows up on the phone too.

Staff also get a "My hours" screen with their own history.

The schedule, and acknowledgements

The schedule tab is a week view of shift cards. Each shift can be acknowledged, or flagged with a concern if there's a problem with it.

Acknowledgement is tracked per person per shift. Publishing a rota creates a pending acknowledgement for everyone rostered; if a published shift then changes meaningfully, that shift's acknowledgement resets to pending so the change gets seen rather than assumed. Anyone still sitting on an unacknowledged shift less than 48 hours away gets a nudge.

Swaps, giveaways and open shifts

Claims, giveaways and swaps are one system with three shapes:

  • Claim an open shift nobody is assigned to.
  • Give away a shift you're rostered on, either to a specific colleague or to anyone who'll take it.
  • Swap one of your shifts for one of theirs.

Proposing a trade in the app — step one of three, choosing which shift to hand over

Proposing is a three-step flow: pick the shift, pick the shape, send. The other person accepts or declines from their own phone. On an open giveaway the first person to accept gets it, and the rest are told it's gone.

Nothing moves without you. Every trade lands in your approvals queue, and approval re-checks conflicts at that moment rather than trusting the ones checked when it was proposed. A trade covering a shift that has already ended can't be approved at all, so a stale queue can't reassign worked time. Losing claimants are notified when a competing claim wins.

Open shifts sit on their own tab with the date, time, team and role, and a claim button.

The open shifts tab, listing unfilled shifts with claim buttons

Time off and availability

Leave requests are holiday, sick, personal or other, over a date range with an optional note.

The request time off form with leave type, first and last day, and a notes field

Requests don't have to be whole days — a request can carry start and end times for an afternoon off, and only counts against shifts it genuinely overlaps. If you've set a holiday allowance, staff see their remaining balance before they ask; if you haven't, no balance is shown rather than a made-up number. Every request tracks its status, so nobody has to chase you for an answer.

Separately, staff set availability: days and times they'd prefer to work, and days they can't. Both can be one-off or a recurring weekly pattern, and both surface on your scheduler while you're building the rota — preferred availability as a hint, unavailability as a conflict.

Notifications

Push notifications are the reason the rest of it works. The app sends one when:

  • a new rota is published
  • a shift is changed or cancelled
  • someone proposes a trade, or accepts or declines yours
  • a manager approves or rejects a trade or a claim
  • a leave request is approved or rejected
  • a shift is coming up

Publishing only notifies people whose shifts were newly published, so republishing a week to fix one typo doesn't alert the venue. Later edits notify only the people affected.

Each staff member controls this per event and per channel — push, email and SMS separately — so someone can keep rota publications by email and turn everything else off.

Everything also lands in an in-app inbox with 90 days of history, and it lands there whether or not push is switched on. Turning notifications off means "stop buzzing me", not "hide this from me" — the inbox is exactly what someone checks when no alert arrived. Tapping an entry opens the screen it refers to.

The rest of it

  • Calendar. Add a single shift to the phone's own calendar through the OS sheet, or subscribe to the whole rota so it stays in step.
  • App lock. Face ID, fingerprint or device passcode, opt-in per person, with a short grace period so flicking to another app doesn't demand a re-unlock. It's a local lock on a device, not a second login.
  • Messaging. If your venue enables it, staff get real-time messaging with read receipts, typing indicators and image attachments.
  • Team rota. Where you've enabled it, staff can see who else is on.
  • A tour on first sign-in, replayable later from the profile screen.

Available now

The app is free on both stores and works with your existing rota — there's nothing to migrate and no new admin screen to learn. If your venue isn't using the rota yet, it's included on every BookingNinja plan.

There's a full rundown on the staff rota page. As always, tell us what you'd like to see next.

Discussion

Sign in to join the discussion.

Try the platform behind the update.

Get started free with full access for 7 days. No card details, no long contract, and no paid feature add-ons.