Staff scheduling

Your crew do not need an account.

A shift is short, the callout goes out as a text, and whoever taps yes lands on the roster. Casual staff will never install an app — so CaterCloud asked them not to.

Your roster · Sat 26

4 of 6

Two short for service

Their phone

Available Saturday 4pm at Stonefields? Tap to answer.

YesNo

No login. No app. No password to reset.

Back on the board

6 of 6

Filled, and you did not chase it

A shift is short, the callout goes out as a text, and the answer lands back on the board. src/lib/staff/acceptCallout.ts — the crew page is public, so nobody installs anything or takes a seat on your bill.

What goes wrong

Where the time goes

The parts of the job that cost you, before any software is involved.

  1. 01

    You are texting people one at a time

    A shift needs two more. You go down your contacts, send the same message six times, and then keep track of the replies in your head and your thumb.

  2. 02

    The people who say yes are not written down anywhere

    The answers come back across three apps and a phone call. The roster in the software says what you last typed into it, which is not the same thing.

  3. 03

    Casual crew will not install anything

    You can buy every seat you like. A casual who works four Saturdays a year is not downloading an app, creating a password and remembering it.

  4. 04

    Adding people to the software costs money

    On a per-seat plan every casual you add is a line on the bill, so the roster in the system quietly stops matching the roster in real life.

How it works

How it works

  1. The shift is short

    The roster knows how many it needs and how many it has. You do not have to notice.

  2. Send the callout

    One tap, from the van. It goes to the people who can actually do that role.

  3. They tap yes or no

    A link in a text opens a public page. No login, no app, no password to reset.

  4. The board fills itself

    The answer writes straight to the roster, and the short count clears.

Their own day

Send one person just their part of it

Nobody needs the whole event. A crew member needs the four lines that are theirs — and they get them as a message, on the phone they already have.

Hartwell Wedding · People
Jack’s run Sat 26 September
  • 07:30Load out — van packed, esky in
  • 10:00On site, set up
  • 12:00Service
  • 15:30Pack down
⚠ Dana is not rostered on this day — check before sending hers
Share
Sent Jack’s run for the event

Message · now

Hartwell Wedding — your run

Saturday 26 September

07:30Load out — van packed, esky in
10:00On site, set up
12:00Service
15:30Pack down

No app. No login. No seat on the bill.

03In their words

Caterers who love CaterCloud

The moment I realised this was actually working was waking up in the morning and having the leads in my inbox already — without chasing the business. I've gone from one booking a month to three or four.

Michelle

Owner, Michelle's Catering

50–60% of leads converted

Michelle, Michelle's Catering
1 / 5

Who it is not for

Where this is the wrong tool

You need full time-and-attendance

There is no clock-in terminal and no biometric. If payroll compliance needs a punch clock, that is a different product.

Your staff are all salaried and fixed

If the same six people work every job, the callout solves a problem you do not have.

You need award interpretation

Pay rates are recorded and used, but this is not a payroll engine and does not interpret an award for you.

Questions

What people ask

Do my staff need to download an app?
No. The callout is a text with a link to a public page. They tap yes or no and it lands on your roster.
Does adding crew cost more?
No. CaterCloud is flat monthly, not per seat, so your whole crew being on it does not change the bill.
Can I see who is available before I ask?
Yes — availability and existing shifts are on the roster, so the callout goes to people who could actually do it.
What if nobody answers?
The shift stays short and visibly so. Nothing pretends it is filled.

By using CaterCloud, you agree to our use of cookies. See our Cookie Policy.