Group chats vs rostering apps: why message-thread rosters break down

A group chat is where many small teams start rostering. It is free, everyone is already in it, and a photo of the roster takes seconds to send. It works until the team, the number of changes or the cost of a mistake grows. Here is where message-thread rosters break down, what the rules add, what a chat is still good for, and how to separate the two.

Written by Roster Flow. Published 5 August 2026.

Picture a team of 15 in one group chat. On Wednesday night the manager posts a photo of next week’s roster. By Friday there are dozens of new messages: two swaps agreed in replies, a question about Saturday answered three times, a birthday, a lost jacket, and a changed start time somewhere in between. On Monday someone arrives at the time in the photo, which is no longer the time. Nobody did anything unusual. The chat did what chats do.

That is the core problem. A chat keeps messages in the order they were sent, and a roster needs one current answer to "when am I working?". This article sets out where the two pull apart and how to keep the chat for what it is good at. It follows on from communicating roster changes and getting staff to confirm their shifts.

A man lying in bed at night, looking at a phone that lights up his face — Photo: Pexels

Ask AI about this article

Add as a preferred source on GoogleGoogle shows the sources you choose more often in Top Stories, and can mark them as preferred in AI Mode and AI Overviews.

Why group chats became the roster

There are good reasons chats took over. Everyone already has one on their phone. Messages arrive at once and cost nothing. The manager can often see who has opened a message. A photo of the printed roster is quicker than setting up anything else. For a team of five on the same shifts every week, it can work for a long time.

The trouble is that each of those strengths has a cost, and the cost grows with the team.

Where message-thread rosters break down

What a roster needs, and what a group chat gives it
A roster needs	What happens in a group chat
One current version	The photo from Wednesday, the correction on Thursday and the swap on Friday all sit in the thread, and nothing marks which is current
Each person to find their own shifts	Everyone scrolls the whole team’s messages, or zooms in on a photo of the grid
Changes to reach the people affected	Changes go to everybody, and the person affected may read them last or not at all
A clear record of what was agreed	A thumbs up can mean agreed, seen or thanks
Availability and leave kept up to date	Requests arrive as messages the manager has to remember and copy somewhere else
Hours worked, for payroll	Nothing in the chat records start and finish times, so hours are rebuilt from memory or paper
Personal details kept private	Every member sees every message, and often every other member’s phone number

Changes get buried

A roster change in a chat is one message among many, and nothing about it says it matters. It sits between a question about the milk order and a photo of a lost key. People who read the chat at the end of a shift skim, and a changed start time looks like everything else.

There is no single version

Each new photo of the roster adds another version. People save the first one, screenshot it, or scroll back to whichever they find. When the roster and the thread disagree, nobody can say for sure which is right, and the argument happens at the start of the shift.

Silence looks like agreement

A read receipt shows a message was opened, not that it was understood or agreed to. "Can anyone do Saturday?" followed by a thumbs up from two people is not a roster decision, and the manager is left guessing who is coming.

It goes off at all hours

A busy chat notifies everyone of every message, including late at night and on days off. People mute it to get some peace, and then miss the one message that mattered.

What the rules add

The right to disconnect gives employees the right to refuse to monitor, read or respond to contact from their employer outside their working hours, unless the refusal is unreasonable. It has applied to employees of small business employers since 26 August 2025. Among the factors the Fair Work Ombudsman lists for deciding whether a refusal is unreasonable are the reason for the contact and how it is made and how disruptive it is. Posting a change to a team chat at 10 pm and relying on everyone having read it by 6 am is relying on people reading work messages outside their working hours, which they may be entitled to refuse.

Awards also expect the roster to be somewhere people can find it. The Restaurant Industry Award (clause 15.3) and the Hospitality Industry (General) Award (clause 15.5) require a roster showing each full-time and part-time employee’s name and start and finish times, posted in a conspicuous place that is easily accessible by the employees. The General Retail Industry Award (clause 15.9) allows the roster to be on a noticeboard or available through accessible electronic means, and requires a copy of each completed roster to be kept for at least 12 months. A photo that has scrolled out of sight in a busy thread is a poor fit for either.

Then there are records. The Fair Work Ombudsman says employers have to keep time and wages records for 7 years, and for casual and irregular part-time employees paid for time worked, those records include the hours they work. A chat thread does not record those hours, so they are rebuilt from something else every pay run. Some awards also require agreed changes to a part-time employee’s hours to be recorded in writing. The General Retail Industry Award notes that an exchange of text messages can be that record (clause 10.6), and under the Fast Food Industry Award, if no record is kept of an agreed variation to a rostered shift, hours beyond the regular pattern are paid at overtime rates (clause 10.6). An agreement buried in a thread of hundreds of messages is hard to produce when it is needed. Find my award will tell you which award, and which clauses, apply to your team.

What a group chat is still good for

None of this means deleting the chat. It is good at things a roster does not need to do:

Team news: a new menu, a delivery running late, a reminder about stocktake
Thanks after a big weekend, and the social side of a team
A heads-up that the roster is out, with a pointer to where it is rather than a photo of it
Quick questions that do not change anyone’s shift

Separate the chat from the roster

Pick one place for the rosterA shared file, a rostering app or the noticeboard, as long as there is one current version and each person can find their own shifts.
Stop posting roster photosPost that the roster is out, and where to find it. Old photos in the thread become old versions.
Take changes out of the threadSwaps, cover and changed times go directly to the people affected and onto the roster, not to the whole team.
Collect availability and leave in one placeUse a form or the roster system instead of messages. The staff availability form and the leave request form are free.
Agree what the chat is forWhat goes in it, what does not, and that nobody is expected to read it outside their working hours. Write it down and pin it to the top of the chat.
Record hours somewhere elseUse timesheets or clock ins, so hours worked never depend on the chat. The roster vs actual hours calculator shows the gaps to look for.

A mechanic in blue overalls sitting on a tyre under a raised car, looking at a phone in his hand — Photo: Pexels

A worked example: counting one week in the chat

A 15 person restaurant runs its roster through a group chat. For one week the manager counts every message about shifts and roughly how long each took to deal with. This shows how to count, not what your numbers will be.

Shift messages in one week
Kind of message	Messages	Minutes the manager spent
Questions about when someone is working	18	27
Swap and cover requests, and the replies	31	62
Changes the manager posted	6	12
Corrections after a change was misread	4	20
Total	59	121

In a chat of 15 people, each of those 59 messages lands on the other 14 phones: 826 notifications in a week, most of them to people the message did not concern. The manager spent just over two hours on them. The four corrections cost the most, 5 minutes each, because each followed a misunderstanding on the day. Counting your own week the same way shows whether the chat is still saving more time than it costs.

Signs it is time to move the roster out of the chat

Roster changes come through the thread every week
Someone has turned up at the wrong time because a change was buried
Availability and leave requests exist only as messages
Hours for payroll are rebuilt from the chat or from memory
People have muted or left the chat to get some peace

A shared sheet solves some of this, as in the staff roster in Google Sheets. If you are moving the whole roster out of messages and spreadsheets, moving from Excel rosters covers the move step by step.

Where a chat falls short, Roster Flow covers the roster itself: availability and leave from staff phones, the roster published to everybody at once, clock ins that become timesheets, and approved hours sent to Xero, MYOB or a CSV file.

A checklist for chat and roster

The roster lives in one place, with one current version
The chat carries a pointer to the roster, not photos of it
Changes go directly to the people affected and onto the roster
Availability and leave are collected in one place, not in messages
Agreed changes to part-time hours are recorded where you can find them again
Hours worked are recorded outside the chat
The team has agreed what the chat is for, and that nobody has to read it outside working hours

Questions

Is it OK to post the roster in a group chat?

It is fine as a heads-up that the roster is out, with a pointer to where it lives. As the only copy it falls short: it scrolls away, old versions stay in the thread, and some awards require the roster to be posted where employees can easily access it.

Can I expect staff to read the group chat on their days off?

Not as a rule. Employees can refuse to monitor, read or respond to contact outside their working hours unless the refusal is unreasonable. Agree how urgent changes will reach people instead, such as a direct call.

Does a thumbs up in a group chat count as agreeing to a shift change?

It is a weak record, because it can mean agreed, seen or thanks. Where an award requires an agreed change to be recorded in writing, ask for a reply that states the new day and times.

Do I need to keep roster messages?

Keep anything that records an agreement or a change to someone’s hours. Employers must keep time and wages records for 7 years, and the General Retail Industry Award requires a copy of each completed roster to be kept for at least 12 months.

What should a team group chat be used for?

Team news, reminders, thanks and a heads-up that the roster is out. Keep individual shifts, swaps, availability and leave out of it.

How do I stop staff asking shift questions in the chat?

Reply with where to find the answer rather than the answer itself, make the roster easy to open on a phone, and pin a short note about what belongs in the chat.

Sources

Communicating roster changesTelling the people affected, directly.Staff confirming shiftsGetting every shift seen each week.Staff availability formAvailability in one place, not in messages.Moving from Excel rostersMoving the roster somewhere better.

Back to the blog