Did they see the shift? Confirmation tracking and team messaging in Humanz

Every site manager has lived this one. The roster was published a week ago, the shift was right there in the app, and the worker still didn’t show. “I never saw it.” And you have no way to prove otherwise, or better, to have caught it three days earlier.

Most no-shows aren’t defiance. They’re communication failures: a shift change that didn’t reach the worker, a message sent to the wrong person, a worker who didn’t know who to contact when their flight got cancelled. And there’s plenty of change to communicate. The Australian Bureau of Statistics found 17% of employees, 2.0 million people, don’t usually work the same number of hours each week (August 2025). Rosters genuinely move, so publishing once and hoping isn’t communication. We covered the cost side in how real-time rostering reduces no-shows. This article is about the specific Humanz rostering software features that close the loop.

1. Seen/unseen tracking: know who hasn’t looked

Humanz records whether each allocated shift has actually been viewed by the worker on their mobile app. On the schedule, the Show Unseen button filters the entire Gantt view down to only the shifts workers haven’t seen.

That turns follow-up from guesswork into a two-minute task. Switch the filter on, and every shift still showing is a phone call or message to make before it becomes a gap on site. Switch it back to Show All Shifts when you’re done. It’s cheap insurance in a market with no slack. The ABS counted 19,900 construction job vacancies sitting unfilled in May 2026, so a shift that stays unseen until the morning becomes a hole the labour market won’t fill for you.

A couple of practical notes from how the feature works:

• A shift needs to be on screen for roughly 200 milliseconds to register as seen, so a worker who scrolls past at speed may still show as unseen. Treat it as a conservative indicator.
• The My Organisation page also shows each user’s last login date and time, which is handy for spotting workers who haven’t opened the app at all.

For rosters with long lead times (FIFO swings, shutdown mobilisations) this is the difference between discovering a problem at the airport and discovering it a week out. It pairs directly with putting flights and accommodation on the roster, since travel shifts get the same seen/unseen visibility.

2. Chat templates: workers always know who to message

In large or rotating teams, remote workers often don’t know who is rostered on in the office today. So they message the person they know, who’s on days off, and the sick call sits unread until 9am.

Chat templates fix this by creating standing group chats aimed at a function, not a person. You build them once in your business profile:

• Create a template (for example Sick Day or Missed Flight)
• Choose who receives it, by individual user, role, team, or any combination
• Activate it, and it appears as a global chat for your workforce

A worker who misses a flight taps the Missed Flight chat and types one message. Everyone currently responsible for handling it sees it immediately. No hunting for names, no single point of failure. For shift-change communication this also supports the practical side of Fair Work obligations around notice of roster changes, since changes and responses happen in one traceable channel.

3. Business notification routing: alerts go to the right people

The third leg is making sure the business side notifications (the system alerts your office team relies on) land with the right people. In Business Notifications, each notification type can be routed to specific users, roles, teams, or a combination.

That means the scheduling team gets scheduling alerts, the HR coordinator gets onboarding ones, and nobody learns to ignore a flooded inbox. (Worker-facing notifications are unaffected. This only controls internal routing.)

There’s a compliance angle here too. Consultation and communication are explicit elements of managing WHS risk under Safe Work Australia’s guidance, and routing that records who was told what, and when, is the difference between demonstrating consultation and merely asserting it.

What this looks like in practice

A typical setup for a trades or mining services business using a mobile workforce app for contractors and employees:

• Roster published → workers get push notifications on their phones
• Three days out → scheduler runs Show Unseen, follows up the stragglers
• Worker problem (sick, missed flight, vehicle issue) → worker uses the matching chat template, the rostered office crew responds, the shift is recovered or refilled
• System alerts → routed by role and team so the right person acts on them

Each step removes a place where “nobody told me” can happen. The same confirmation loop matters wherever shifts change at short notice, including rostering for retail, hospitality, and events, where last-minute casual changes are the norm, and aged care, where an unconfirmed night shift is a compliance problem as well as a staffing one. For businesses comparing platforms, this confirmation-and-escalation loop is a capability worth testing in any workforce management software Australia shortlist. Publishing a roster is table stakes. Proving it was received is not.

Frequently asked questions

What is seen/unseen shift tracking? It’s a record of whether each allocated shift has actually been displayed on the worker’s phone. The Show Unseen button filters the whole schedule down to only the shifts workers haven’t viewed, which turns follow-up from guesswork into a two-minute task. Every shift still showing is a call or message to make before it becomes a gap on site.

Is the seen indicator 100% reliable? Treat it as a strong signal, not a guarantee. A shift must display for about 200 milliseconds to register, so very fast scrolling can leave a viewed shift marked unseen. When in doubt, follow up.

Can workers tell they’re being tracked as seen/unseen? The seen status is a scheduler-side view. Workers use the app as normal, and the schedule records whether allocated shifts have been displayed on their device.

How do I spot a worker who never opens the app? Check their last login. The My Organisation page shows each user’s last login date and time, which catches the workers who haven’t opened the app at all rather than just missed one shift. Those are the people to ring rather than message, and the ones to sort out before a roster with a long lead time.

Who can be in a chat template? Any combination of individual users, roles, and teams. Membership updates with your org, so if the rostered supervisor changes, the role-based chat still reaches whoever holds it.

Do chat templates replace normal one-to-one chat? No. They sit alongside it as global chats for defined scenarios, so workers always have a guaranteed-monitored channel for time-critical issues.

Does notification routing change what field workers receive? No. It only controls which internal users, roles, or teams receive business notifications. Worker notifications are unchanged.