Where do your hours go
every week?

Book a 15-minute demo — bring your real week
See how it works

Got a question?

The staffing app that helps run your shifts

Rota. Cover. Timesheets. and a lot more

RunStaff builds your staff rota, fills the gaps when someone calls in sick, and lets your team see and confirm the shifts they're working — from their phone.

Whatever your time’s worth, RunStaff gets it back. Six to eight hours of it, every week.

The four things that eat your week

Auto-Cover

The 6am sick call, handled before you've had coffee.

Time saved1–2 hours, every week

BeforeRinging round, hoping someone answers.

AfterThe right person's asked automatically — one text when it's sorted.

  • Handles sick days, no-shows and holiday gaps — not just the odd one
  • Only asks people who are free and trained, with their hours on screen before anything goes out
  • One message when it's sorted — not six replies to chase

Three phones, one sick day — and not one phone call.

Adam’s phone showing tonight’s shift due at 16:45 and tomorrow’s shift on Tue 25 Aug.
Frame 1 of 14 — Adam’s set for tomorrow. Marked: tomorrow’s shift, Tue 25 Aug.
The request screen in the staff app, offering Sick, Holiday, Time off, Swap and Question.
Frame 2 of 14 — Sick, holiday, a swap — same place. Marked: the Sick option.
Adam calling in sick: Tue 25 Aug picked on the calendar and a short note, “Feeling rough.”
Frame 3 of 14 — He’s ill — he tells you from bed. Marked: “Calling in sick — your manager will be told straight away”.
A confirmation that Adam’s sick request was sent, showing the date and his note back to him.
Frame 4 of 14 — Sent. Your phone hasn’t rung. Marked: the sent request — sick, Tue 25 Aug.
The manager’s day view: an AI summary flagging one cover to send, and Adam listed as off sick tomorrow.
Frame 5 of 14 — It waits for you — it doesn’t ring you. Marked: “Tomorrow — Adam (sick)”.
A Cover needed card reading “Adam Hussain — sick on Tue 25 Aug: best cover is Usha Tanwir”, with a Send to Usha button.
Frame 6 of 14 — It’s picked who to ask — and why. Marked: the cover-needed card naming Usha.
The Find cover screen showing Usha Tanwir as the best match with her hours and role, the message that will be sent, and everyone else held back as a last resort.
Frame 7 of 14 — Free that day, right role, hours checked. Marked: Usha’s match, with the reasons.
The manager’s day view updated to “Cover sought for Adam Hussain — 1 of 1 awaiting reply.”
Frame 8 of 14 — One tap, and the ask goes out. Marked: “1 of 1 awaiting reply”.
Usha’s phone showing the cover ask for Tuesday 25 August with Yes, No and Reply buttons.
Frame 9 of 14 — Usha gets it — Yes or No. Marked: the cover ask, and the two buttons that answer it.
Usha’s phone confirming she accepted the cover, with a notification that she has been added to the rota.
Frame 10 of 14 — She says yes. She’s on the rota. Marked: “Cover confirmed — you’ve been added to the rota”.
A Cover found card telling the manager Usha Tanwir accepted Adam’s sick day and the shift has been assigned to the rota.
Frame 11 of 14 — One message back: it’s sorted. Marked: the cover-found card.
Adam’s phone showing his sick day approved, with a note that Usha Tanwir is covering his shift.
Frame 12 of 14 — Adam’s told who’s covering. Marked: “Usha Tanwir is covering your shift”.
Usha’s week now showing Tuesday 25 August as a working day with the 16:45 to 23:30 shift next up.
Frame 13 of 14 — And it’s already in Usha’s week. Marked: Tue 25 Aug, now a shift.
The team rota for the week with Adam struck through on Tuesday evening and Usha shown in his place.
Frame 14 of 14 — The rota updated itself. Marked: Monday beside Tuesday — Adam struck through, Usha in his place.

Smart Rota Generation

A fair week's rota, in minutes, not a Saturday afternoon.

Time saved1–2 hours, every week

BeforePieced together by hand, most weeks.

AfterBuilt for you in minutes — you check it, tweak it, send it.

  • If something's unclear, RunStaff asks you — it never guesses
  • Works out who should get priority so shifts are handed out fairly
  • Plans change mid-week? Regenerate it and it catches up
The portfolio home: five venues, each flagged CRITICAL — NO ROTA with a Generate rota button.
Building a rota in three quick steps: Plan what the week needs, Team to set who matters most, Generate a draft checked against the rules.
The Plan step: the standard week grouped by day, with 350.75 hours needed in total.
The Plan step scrolled to Any changes this week, with suggestion chips and a box to type or speak a change.
Same as last week applied, above the four things the AI always respects: contracted hours, availability, preferences and roles.
The Team step: a coverage bar per role showing hours needed against hours available, above the priority cards.
Lower priority tiers, with a warning that Prep-Middle cover at high is 32 hours more than the week needs.
Before you generate: every role marked covered, and who will likely get hours, who depends on demand, who only fills gaps.
Building your rota: placing the team within your priorities, then checking hours, leave and cover.
The review draft: three issues and eleven warnings, each written in plain English, above the generated rota.
Why this rota, expanded: the reasoning behind each person's placement, named one by one.
The published rota: 59 shifts across the week, none confirmed yet, with Chase all and Confirm all on their behalf.
The week grid by role and shift, with the legend for confirmed, pending, gap, critical gap and role under minimum.

Generate Weekly Timesheets

Get your Monday morning back.

Time saved2 hours, every week

BeforePiecing together who actually worked what.

AfterStaff confirm from their phone, you approve once, done.

  • Staff confirm their own hours, right from their phone
  • Anything that doesn't add up gets flagged for you to check
  • One approve step, ready for payroll — with the real £ cost of the week's hours alongside
  • Pay rates and the £ cost sit behind an owner-only door — managers can approve hours without seeing money

One week’s hours, from the clock to the payroll number — and no spreadsheet.

The manager’s Timesheets screen for 20–26 Jul: ten open weeks, nine still to be confirmed, and every person’s net hours already worked out against what was scheduled.
Frame 1 of 15 — The week’s already added up. Marked: Adam Hussain’s row — 43h 51m net against 47h scheduled.
Adam’s week opened out: seven daily rows showing clock-in, clock-out and break, each with how far short of the scheduled shift it ran, totalling 43h 51m of 47h.
Frame 2 of 15 — Every day, in and out, to the minute. Marked: The daily breakdown — Mon 20 to Sun 26, clock in, clock out, break.
Adam’s phone: his day, a new rota to confirm, and a timesheet card asking him to confirm his hours for 20 Jul 2026.
Frame 3 of 15 — Adam’s asked to check his own hours. Marked: The timesheet card — “Confirm your hours for 20 Jul 2026”.
Adam’s My hours screen for 20–26 Jul: a week total of 43h 51m net worked against 47h scheduled, then a daily breakdown of every clock-in and clock-out.
Frame 4 of 15 — His week, net against what was scheduled. Marked: The week total — 43h 51m net, 47h scheduled, 3h 9m short.
The end of Adam’s week: “Do your hours look right?”, with a green Confirm hours button and a red Flag a problem button.
Frame 5 of 15 — Confirm — or say something’s wrong. Marked: The two choices — Confirm hours, or Flag a problem.
The Flag a problem sheet: “Tell your manager what looks wrong — they’ll see this and can correct any times”, with an example, “Monday I clocked in at 9:30 not 9:00”.
Frame 6 of 15 — A problem comes straight to you. Marked: The flag form, addressed to the manager.
Adam’s week after he confirms: the button now reads Confirmed in green, and the week header carries a Confirmed badge.
Frame 7 of 15 — He confirms — you didn’t chase him. Marked: The Confirmed button, and the week marked confirmed.
The manager’s Timesheets list updated: one confirmed, and a card reading “1 week ready to approve — staff confirmed, no issues outstanding” with an Approve all button.
Frame 8 of 15 — One week, ready to approve. Marked: The ready-to-approve card, with Approve all.
Adam’s timesheet marked APPROVED, his daily rows still visible underneath, and a line at the bottom reading “Approved 24 Aug”.
Frame 9 of 15 — One tap, and the week’s signed off. Marked: The APPROVED badge on Adam’s week.
The owner’s More menu across five stores, with the first row reading “Labour & pay reports — hours, cost & CSV export · owner / PIN”.
Frame 10 of 15 — Pay sits behind its own door. Marked: The Labour & pay reports row, marked owner / PIN.
The labour report for the week of 20 Jul: every person’s net hours, contracted hours and cost in pounds, grouped by role with a subtotal for each.
Frame 11 of 15 — Hours and cost, per person. Marked: The cost column, in pounds, per person.
The foot of the labour report: a period total of 321h 29m and £3475.55, above collapsed Pay rates and Report PIN sections.
Frame 12 of 15 — What the week actually cost. Marked: The period total — 321h 29m, £3475.55.
The Pay rates panel, headed OWNER ONLY: an hourly rate per person, with one row flagged because that person’s role changed since the rate was last reviewed.
Frame 13 of 15 — Rates only the owner can see. Marked: The panel header — PAY RATES (OWNER ONLY).
Adam’s cost opened out: every clock-in and clock-out for the week of 20 Jul, each marked on time, late or early to the minute.
Frame 14 of 15 — Every clock behind the number. Marked: The clock events — in, out, and how late or early.
The same report switched to Monthly: one person’s month broken into its weeks, each with its own net hours and cost, including a week with no clock events at all.
Frame 15 of 15 — And the month adds itself up. Marked: The Monthly view, alongside Weekly.

Live Attendance late & no-show alerts

Know what's happening, without being there.

Time saved2 hours, every week

BeforeRinging the venue, hoping someone picks up.

AfterSee who's clocked in right now — and get told the moment someone hasn't.

  • See live who's actually on shift — not just who's rota'd
  • Get flagged the moment someone's late or hasn't clocked in
  • Works across every site you run, not just the one you're standing in
  • Your team sees the same week — who’s on, every day — so nobody rings to ask

One evening, five sites — and you’re not standing in any of them.

The manager’s day at Dixy Chicken Hillford, headed by an AI summary reading “3 no-shows — find cover now”, with attendance, shifts and missed clock-ins broken out, and who is off this week underneath.
Frame 1 of 9 — You open it — it’s already looked. Marked: The summary — 3 no-shows, 0 of 6 replied to the clock-in prompts.
Today on the floor: 3 scheduled, 0 in, 0 late, 3 no-show, with Adam Hussain, Niku Smita and Santra Billa each named and marked no clock-in.
Frame 2 of 9 — Three didn’t turn up, and it says so. Marked: The count — 3 scheduled, 0 in, 0 late, 3 no-show.
Further down the same day: a NUDGE SENT card reading “4 missed clock-in prompts sent — no one has responded yet”, with a Check Responses button.
Frame 3 of 9 — It chased them before you did. Marked: The nudge — prompts already sent, no reply yet.
The live Attendance board for the 16:45–23:30 shift: 3 scheduled, 0 in, 0 late, 3 no-show, and a Needs attention list naming all three with a Find cover button each.
Frame 4 of 9 — Scheduled, in, late, no-show — per person. Marked: The four counters the board is built on.
The owner’s view across five stores, marked LIVE: “6 not turned up across 2 stores”, naming Dixy Chicken Hillford at 0 of 3 and Sweet Spot Islington at 0 of 3.
Frame 5 of 9 — Six missing, across two of five sites. Marked: Six not turned up, and which two stores they are.
The same view with Dixy opened out, naming Adam Hussain, Niku Smita and Santra Billa as the three no-shows, each with their role.
Frame 6 of 9 — Down to who, at which store. Marked: The three names, from the all-stores view.
Sweet Spot Islington’s own day, with its own AI summary: 3 no-shows, shifts 6 of 6 confirmed for today, and no staff messages waiting.
Frame 7 of 9 — And the next store reads the same way. Marked: The second store’s own summary, same shape as the first.
Usha’s own rota for 24–30 Aug: her confirmed shift today, then a Who’s on this week grid of the whole team, with her own name picked out in blue. Tuesday evening shows Adam struck through and Usha in his place.
Frame 8 of 9 — Your team sees the same week. Marked: The Who’s on this week grid, and which name is hers.
The same grid scrolled on to Wednesday through Sunday: cashier, prep-middle and kitchen staff listed for each morning and each evening, with everyone rostered by name.
Frame 9 of 9 — Every role, morning and evening. Marked: The role rows — every job, both halves of the day.

What just happened

One sick call, start to finish, and nobody rang anyone. It is one job of four — the same AI builds your rota, totals your timesheets and keeps an eye on your floor.

Real RunStaff screens

  1. 01

    Gap spotted

    Adam calls in sick from his phone. Nobody rings you at 6am.

    A staff member’s phone: Calling in sick — your manager will be told straight away.

  2. 02

    Cover matched

    It picks who to ask and shows you why. And who it’s holding back.

    The manager’s phone: Usha Tanwir, best match — cashier, 32.75 hours scheduled this week against a 25-hour contract, off this day, top role-match.

  3. 03

    Cover sought

    Nothing goes out till you approve it. Then Usha gets one question.

    Usha’s phone: if you accept, you’ll be confirmed automatically — no further steps needed, with Yes, No and Reply buttons.

  4. 04

    Cover found

    She says yes. The rota updates itself, and Adam’s told.

    Adam’s phone: approved, sick — your sick for Tue 25 Aug is approved, Usha Tanwir is covering your shift.

This is one of four. Your rota, your timesheets and your floor are handled the same way. See everything that’s built in →

Who it's for

Built for teams that run on shifts, not desks.

Anywhere a team is staffed by rota — not a fixed 9-to-5 — RunStaff fits. Hospitality, care, retail, and beyond.

The single-site operator

One location, a tight team, no time for admin between covers. You own it and you work it.

yours
One site. One team. You’re in it.

The multi-site owner

Running several locations, needing one view of the whole estate without ringing round.

yours
Every site, every team, one screen above them.

The manager in the middle

Building the rota, fielding the requests, answering upwards and downwards. It isn’t your business, but it is your week.

owner you
Owner above, team below. You’re the bit in between.

Works even when you’re not looking

  • Background checks run around the clock — nudging staff who haven’t responded, escalating unanswered cover requests, flagging attendance issues
  • That work happens whether or not anyone is signed in — overnight, on your day off, in the middle of service

Works wherever you are

  • Runs from a browser or the app — no VPN, nothing tied to being on-site
  • Owners see every venue; managers action a shift from anywhere; staff check a rota while away

And when it needs you, it comes to you

You don’t go looking for RunStaff. It taps you on the shoulder, and that notification is the way in most days.

  • On your lock screen

    A real push notification you can act on from the lock screen — not a badge you only find once you’ve opened the app.

    A cover request and a sick-cover alert on the lock screen, actionable without opening the app.

  • On your wrist

    The one thing that can’t wait reaches your watch, so it isn’t the one you miss with the phone in an apron.

    The same question on a watch face: Aisha Khan asking to talk in confidence Tuesday.

  • One message at 7am

    The whole day in one message before you’ve opened anything — what needs you, and what doesn’t.

    Three RunStaff summaries waiting together: across your stores, today's opening, and a cover search still running.

  • Shift opened, shift closed

    A message at each end of the shift, so you know it ran properly without being there to watch.

    The attendance summary landing on the lock screen: three no-shows, none of three in. The stacked summaries: what opens at 10:30, what is still unconfirmed, and where cover is short.

A week with RunStaff

Whose week do you want to see?

Pick the person. The week is theirs, not the software’s.

Every moment RunStaff handles for them, grouped by how often it comes round.

4 hourly moments

On the floor, moment to moment

You stop walking the floor to count heads, and you hear about a no-show while you can still do something about it.

One push if someone is late or hasn’t shown — not a stream, and nothing at all on a clean shift. The same screen shows who is actually on the floor right now, across the whole site.

Live attendance: three scheduled, none in, three no-shows, each with Find cover. The same shift from the day view, with the AI summary naming the three no-shows.

One question out to the team, and the answers come back to one place instead of six threads.

Ask the whole team in one shot — every response lands together, with who has and hasn’t replied.

The manager asking the team a question in plain English, with Voice alongside Send. The same question arriving on the staff member's day, with Yes, No and Reply.

Cover, swaps, holiday, timesheet queries — every open thing in one list, so nothing is sitting in someone’s texts.

Every request lands in the same place, with its history attached — so you can see what was asked, by whom, and what happened to it.

Resolved requests in one list, each carrying its outcome: approved, cover found, declined. The one request still needing a reply, with Reply and Mark done.

Say what you need in whatever language you speak, and RunStaff works out what to do with it.

Type it or say it, in your own words — no menu to learn, and no need to write it in English if that isn’t how you think.

A manager's question typed in French, with Voice beside Send to Staff.

3 daily moments

The bookends of the working day

You used to piece the day together from five screens. Now it arrives at 7am, already sorted.

Who’s off, who’s due on the floor and what is already handled — the day laid out before you have had to ask anyone. The message itself is shown further up; this is what it opens onto.

The morning summary naming the two things that need attention, and who is off this week.

The shift opens and closes properly whether or not you’re there to watch it happen.

A message at each shift’s start and end, so you know it opened and closed the way it should have.

The floor summary at the top of the shift: who is scheduled, what still needs a decision, and the nudge already sent.

One screen each morning tells you which sites are fine and which one needs you.

Live attendance across every location at once, with the count of what needs you today and any major issue flagged where you will see it.

Every store on one screen, each with what needs attention today.

5 weekly moments

Building the week, then closing it out

Monday comes and the rota isn’t built. RunStaff has already drafted one for you to check.

The draft comes with its reasoning, and nothing publishes until you have reviewed it.

The reminder that no rota is published for the week, with Create rota. The five-step checklist that follows: publish the rota, check who's off, fill cover gaps.

You stop building a week around people who were never going to be there.

Who is off and who is free, on one calendar, before you start building.

The team availability calendar, with holiday, sick and absence marked and keyed. The same month per person: holiday, sick and absence counts side by side. Every confirmed leave item for the month in one list.

Who’s confirmed, who’s pending, who’s off — without chasing anyone to find out.

Confirmed, pending, on leave, can’t-do — at a glance, with a breakdown per person.

The week's shift status - confirmed, pending, on leave - with total hours and the per-person breakdown.

Queries about hours get settled before payroll, not after someone’s been paid wrong.

Flagged hours land with you like any other request — nothing goes to payroll unresolved.

The staff member's flag as it is raised: two hours short against the week, sent to the manager. The manager's timesheet week: Usha flagged and overtime scheduled, Thursday recorded with no clock-in. The manager adding the missing clock event, with the reason recorded against it. The same week once corrected: Thursday reads 6h 16m and the week is ready to approve.

A shift missing a required role gets flagged before it becomes your problem.

A shift that doesn’t have enough people in a role it requires is caught before it publishes — and flagged separately from simply being one person short.

The week's coverage grid, keyed for gaps, critical gaps and roles under their minimum. Sunday evening: cashier under the role minimum, kitchen staff critical, with Find cover. The gap stated plainly: kitchen staff needed, Sunday 30 August.

3 hourly moments

On the floor, moment to moment

One tap and you’re confirmed. Nothing to reply to, nothing to find again later.

Confirm you’re in with one tap; RunStaff reminds you if you haven’t.

The shift awaiting confirmation on the staff member's day, with I'm coming and Problem. The week's shifts in a list, each with Confirm, and an overtime shift marked. Confirming from the rota itself, with Confirm all offered for the six still waiting.

A request that’s logged and answered, instead of buried in a text thread.

Queries and requests go on the record, so you can see what you asked and what came back.

A staff member raising a question, with Voice beside Send to your manager. The confirmation that it sent, and where to watch for the reply. The same question in the manager's inbox, waiting for a reply.

Ask in whatever language you speak, and it understands what you meant.

Type it or say it, however you’d say it out loud. There is no form to fill in and no need to write it in English.

A question typed in French, with Voice beside Send.

3 daily moments

The bookends of the working day

What you’re working and what’s changed, without opening anything.

One message a day with your shifts and anything that has moved — you don’t have to go looking for it.

The staff daily view: today's shift, hours to review, and the one thing to sort. The messages behind it, each request carrying its outcome.

A missed tap gets flagged the same day, not argued about on payday.

Wrong clock time, missed tap — flag it straight from that day’s entry and it goes to your manager.

Flagging a timesheet problem in your own words. The flag on the week total, marked Flagged to manager. The day's hours with Confirm hours or Flag another problem.

Holiday asked for from your phone. No form to find, nobody to chase.

Pick the dates in the app and the request goes straight to whoever approves it.

Asking for time off: the dates picked, and the request written in plain words. The acknowledgement, and the cover search starting without anyone chasing. The same request on the manager's side, waiting for a decision.

1 weekly moment

Building the week, then closing it out

You sort the swap between you; the manager approves it and the rota updates itself.

Pick who you’re swapping with and what you’re swapping. Once it’s approved, nobody has to redraw anything.

Starting a swap from the same place every other request is raised. Picking your shift and a colleague's to swap it with. The check before it sends: different hours, so the manager reviews.

Everything underneath

Everything else that’s built in

Nine more things you’ll use without thinking about them.

Getting started Set up in about an hour, and your team joins by tapping a link. 6 screens

From nothing to a working rota in about an hour.

The first-run checklist: publish the rota, check who's off, fill cover gaps.

Join by Link

Staff join by tapping a link. Nothing for you to type.

No Password, Ever

Their personal link is their login. Nothing to reset.

Add to the home screen. No app store, no download.

The add-to-home-screen setting

Replayable walkthroughs on every page.

The list of replayable guided tours

Promote or revoke manager access yourself.

Managing who has manager access

How your team is organised Separate rotas where you need them, shared cover where you want it. 3 screens

Front of house and kitchen run as separate rotas — but you choose who can be pulled across. RunStaff calls these Pods.

Setting up a separate rota for front of house and kitchen

Wears Two Hats

A promoted manager keeps their own shifts too.

Every location, one screen.

Every location on one screen, each with what needs attention today.

Use cases

Bought for one thing. Used for the rest.

There are no sector editions and nothing is locked behind a plan. Every business gets the whole tool — what changes is only which part you reach for first.

  • Hospitality reaches first for the 6am sick call.

  • Care and childcare reaches first for qualification cover.

  • Franchise and multi-unit reaches first for one view of every site.

  • Cleaning and facilities reaches first for knowing people actually arrived.

  • Retail reaches first for swaps between staff.

  • Warehouse, logistics, events reaches first for building the rota at all.

A nursery buys RunStaff for qualification cover and ends up living in the timesheets. A pub buys it for the 6am sick call and ends up running its whole week on it. Nothing is switched off either way.

What makes it different

One job, done completely.

Big platforms bury staffing under payroll, HR and a stack of tabs you will never open. A plain rota app publishes whatever it generates. RunStaff does neither — and nothing reaches your team until a person says so.

  1. 01

    What the AI weighs

    Availability, contracted hours, role, priority and fairness — with its reasoning written down in plain English.

  2. 02

    What the rules enforce

    Headcount, qualifications and hour limits, checked separately. The AI cannot override them.

  3. 03

    What you actually do

    Adjust anything you disagree with, then sign it off. Nothing reaches your team until you do.

Pricing

Simple, transparent pricing

One tool, everything included, priced per venue.

Committed is a 6-month minimum term, then cancel any time with 30 days’ notice.

Starter

1 venue only

£9/week per venue

£40/month equivalent

  • All features except the portfolio dashboard
  • Rota, cover, clock-in and timesheets in full
Book a demo
2–5 venues

Growth

2–5 venues — whole estate, one price

£16/week for 2 venues

£70/month equivalent

Each venue after your first adds £7/week — so 3 venues is £23/week, 5 is £37

  • Everything in Starter, plus the portfolio dashboard
Book a demo

Portfolio

6+ venues

POAsales-assisted

Price on request

  • Same Growth plan, tailored rollout and rate
  • Built for larger estates

What you'd actually pay

1 venue
£9/wk total
£40/month
2 venues
£16/wk total
£70/month
3 venues
£23/wk total
£100/month
5 venues
£37/wk total
£160/month

Compared to thin tools

Thin rota toolsRunStaff

  • Manual rota buildingA rota drafted for you
  • No cover-findingAuto-Cover asks round for you
  • Tablet or PIN clock-inStaff tap their own phone
  • Bolted-on compliance moduleQualification gaps caught before publish
  • Separate payroll exportPayroll-ready timesheets, no re-keying

Common questions

Before you book

How long does setup actually take?About an hour, in one sitting.

About an hour, in one sitting. Pick a coverage template close to your type of venue and RunStaff pre-fills the roles, shift patterns and staffing requirements you are likely to need. Everything stays editable afterwards.

Do my staff need to download an app?No — they join by tapping a link.

No. Staff join by tapping a link, and that personal link is their login — no password to set or reset. They can add it to their home screen if they want, but there is no app store download.

What happens when someone calls in sick?Auto-Cover finds the gap before you do.

Auto-Cover spots the gap without you noticing it first, then asks whoever is genuinely free, trained and not already over their contracted hours. You get one notification, approve it, and the rota updates itself.

Can I cancel?Flexible has no lock-in at all.

Flexible has no lock-in. Committed is a six-month minimum term, after which you can cancel any time with 30 days notice.

Does it work for my sector?Hospitality is best proven; the rest share the core.

Hospitality is where RunStaff was built and is best proven. Care and childcare, franchise and multi-unit, cleaning and facilities, retail, and warehouse or events teams all run on the same core rota, cover and clock-in.

Where is our data held?Being finalised — we will not invent an answer.

Being finalised, and we would rather say that than invent an answer. Hosting location, encryption, retention and GDPR specifics will be published here once confirmed — ask on the demo and you will get the current position straight.

About

Built by someone who saw the problem firsthand

RunStaff started with a simple observation: independent hospitality operators were losing hours every week to rota admin that software should have solved years ago. It is built by a founder who worked directly with a real multi-site hospitality operator, using their actual rota and cover problems as the starting brief — not a generic feature list, and not a theoretical one.

Your team’s data, handled properly

Hosting, encryption, retention and GDPR details are being finalised. Real answers land here — not marketing claims.

  • Where your data lives to be confirmed
  • How it is protected to be confirmed
  • How long it is kept to be confirmed
  • GDPR compliance to be confirmed

See it running your week

Book a 15-minute walkthrough — no setup, no commitment, just your actual staffing week, sorted.

Book a demo

Ask us anything

A question, not a demo. Tell us what you need to know and how you’d rather be reached.

How should we reach you?