How to Post Team Announcements and Message Staff

Quick answer Post notices where staff already look at their shifts. In Biznsbook Labour Scheduling, a manager posts a title and message to everyone or one position, can pin it or hide it after a date, and sees how many people have read it. Staff read it in My Work → Inbox and press Got it. Managers can also message one person, and staff can reply.

Why important notices get missed in group chats

Changes to opening hours, a safety reminder or a new rule are usually sent to a group chat. Messages scroll away, new starters are not in the chat, and the manager cannot tell who has seen it.

Important notices end up repeated verbally at every shift, and people still say they did not know.

An announcement tied to the schedule gives the notice a home and a count of who has acknowledged it.

Why this happens

  • Notices go to a chat group that not everyone is in.
  • There is no way to see who has read a message.
  • Notices for one role reach everyone and get ignored.
  • Old announcements stay visible after they stop mattering.
  • Private questions get answered in public threads.

Biznsbook addresses this through team announcements with read receipts, announcements by position, direct messages to staff in Labour Scheduling, on the same roster, clock and swaps as the rest of the module.

Small gaps in scheduling rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Post Team Announcements and Message Staff

Written for owners, managers and shift supervisors who roster staff in Biznsbook Labour Scheduling, with or without HRMS.

  1. Open Announcements. Open Labour Schedules → Announcements.
  2. Write the notice. Post a title and message to everyone or one position, optionally pinned or hidden after a date.
  3. Staff read it. Staff see announcements in My Work → Inbox and press Got it to record a read receipt.
  4. Check who has read it. You see how many people have read each announcement.
  5. Message one person. Managers can message one person; staff can reply to a message they received but cannot start a conversation.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

  • Mistake 1: Notices go to a chat group that not everyone is in. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
  • Mistake 2: There is no way to see who has read a message. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
  • Mistake 3: Notices for one role reach everyone and get ignored. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
  • Mistake 4: Old announcements stay visible after they stop mattering. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.
  • Mistake 5: Private questions get answered in public threads. Repeating this each month usually shows up first in overtime, short-notice changes or unfilled shifts.

Each of these turns into a question the manager cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

  • Open Announcements — Open Labour Schedules → Announcements.
  • Write the notice — Post a title and message to everyone or one position, optionally pinned or hidden after a date.
  • Staff read it — Staff see announcements in My Work → Inbox and press Got it to record a read receipt.
  • Check who has read it — You see how many people have read each announcement.
  • Message one person — Managers can message one person; staff can reply to a message they received but cannot start a conversation.

Set the rule once in settings, let staff enter their own information, and review the results weekly before you publish the next roster.

How Biznsbook supports this workflow

team announcements with read receipts is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

announcements by position is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

direct messages to staff is part of Biznsbook and works on the same records as the rest of scheduling, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Labour Scheduling works on its own. Managers need the Labour Scheduling Manager role (or Shift Supervisor for schedules and attendance); invited staff get the Shift Worker role. HRMS, Payroll, Inventory and Accounting are optional.

Suggested implementation timeline

  1. Week 1: Set up team announcements with read receipts and the permissions the people involved need.
  2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
  3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
  4. Month 2: Roll out to every team or site.
  5. Ongoing: A routine for announcements.

What to post, to whom, and for how long

Announcements work best when each one has a single purpose. A change to opening hours, a new procedure, a reminder about a deadline or a safety notice are all good candidates. Long mixed updates are easy to skim past, so split them into separate announcements with clear titles.

Use the audience choice deliberately. Post to everyone only when it really applies to everyone, such as a change to the pay calendar or a company-wide closure. Use a single position for notices that concern one role, for example a new procedure at the till for the sales floor position or a new cleaning routine for the kitchen. Staff learn to pay attention when most of what they receive is relevant to them.

Pin the notices that must stay visible, such as a safety rule or a standing procedure, and keep the number small. For everything else, set a date after which the announcement is hidden, so the inbox does not fill up with last month's news. If something changes, post a new announcement rather than relying on people to notice an edit.

Use the read count to follow up. You see how many people have read each announcement, and staff record it by pressing Got it in My Work, Inbox. If the count is low the day before the change takes effect, mention it in person or send a direct message to the people who have not responded.

Keep direct messages for matters that concern one person, such as a request to swap a shift or a question about their availability. Staff can reply to a message they received but cannot start a conversation, so a manager decides when a thread begins. Messages stay inside the company, so there is no need to share personal phone numbers. Review the list of announcements now and then, hide the ones that no longer apply, and keep the pinned ones current.

Writing announcements people act on

Keep the title specific, put the action in the first line and aim the announcement at the position it concerns. A kitchen notice sent to the kitchen position will be read; the same notice sent to everyone becomes noise. Pin the few that matter for weeks, and set a hide date on the rest so the inbox stays short.

Use the read count as a prompt, not a punishment. If half the team has not pressed Got it by the next shift, mention it in the pre-shift briefing.

Direct messages and boundaries

A manager can message one person, for example about a shift change, and the employee can reply. Staff cannot start a conversation, which keeps the inbox a place for management to staff communication rather than a general chat. Messages stay inside the company, so personal numbers are not needed.

Metrics to track monthly

  • Pending time-off requests
  • Labour % against target by day
  • Open shifts left after auto-fill
  • Short-notice changes and premium hours
  • Missed-break exceptions

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook team announcements with read receipts and the related capabilities.

CapabilityManual / SpreadsheetBiznsbook
Where notices live❌ Group chat✅ Announcements and the staff Inbox
Audience❌ Everyone in the chat✅ Everyone, or one position
Proof of reading❌ None✅ Read count and Got it receipts
Old notices❌ Scroll away✅ Pinned, or hidden after a date
Private messages❌ Personal phones✅ Messages stay inside the company
Who can start a conversation❌ Anyone✅ Managers start; staff can reply

A routine for announcements

Post notices after you publish the schedule, so staff see both in the same visit. Review unread counts before each shift, hide expired items and keep pinned notices to a minimum.

Write the rule down in your staff handbook so the settings and the policy say the same thing.

Frequently asked questions

Can I send an announcement to one role only?

Yes. Post it to everyone or to one position.

How do I know staff have seen it?

Staff press Got it in My Work → Inbox, and you see how many people have read each announcement.

Can staff start a conversation with a manager?

No. Managers can message one person, and staff can reply to a message they received. Staff cannot start a conversation.

Can an announcement expire?

Yes. You can pin it or hide it after a date.

Do messages leave the company?

No. Messages stay inside the company.

How this differs by industry

Retail

A shop manager pins a returns-policy change for the sales floor position and checks the read count before Saturday.

Wholesale & distribution

A depot supervisor posts a loading-bay safety reminder to the warehouse position and hides it after the audit date.

Manufacturing

A shift lead announces a changeover to the line operators and messages one operator about a swapped shift.