Building an Internal Communication Strategy for a Venue That Runs on Shifts

Search for advice on internal communication strategy and you will get a template built for a company where everyone has a desk, an email address and a predictable week. Set a cadence. Segment your audiences. Build an intranet. Measure open rates.

Now try to apply that in a 20,000-seat arena on a Saturday. Two thirds of your crew are part-time. A third of them are new this month. None of them will open an email before doors. The all-hands moment you have is eight minutes in a back-of-house corridor, and it is competing with people trying to find their section assignment.

This is not a small mismatch. Emergence Capital's research found that roughly 80 percent of the world's workers are deskless, and that 60 percent of them are unsatisfied with the technology they are given to do their jobs. Internal communication is where that dissatisfaction shows up first, because it is the one function every organisation assumes it has solved.

What follows is the strategy we see working across stadiums, arenas, hotels and amphitheaters. It is less about tools than about being strict on one distinction.

Separate Action From Information, and Never Mix Them

The single most useful thing you can do is sort every message your venue sends into one of three tiers, and refuse to let them share a channel.

Most venues we work with have exactly one channel and use it for all three. Usually that is a radio, or a group text, or in the more modern failure mode, a single busy chat channel. The result is predictable: the tier-one messages that cost money get buried under tier-three messages that could have waited a week.

Treat the Pre-Shift Briefing as Infrastructure

The pre-shift briefing is the only moment in a venue's week when you have most of the crew in one place and paying attention. In most buildings it is run as a formality, and that is a waste of the highest-bandwidth channel you own.

What separates a briefing that works from one people endure:

• It is short and it is fixed. Same place, same time relative to doors, same running order. Predictability is what makes attendance possible for people who work three shifts a month.
• It covers only what changed. Standing information belongs in writing. If a briefing repeats the same six things every event, people stop listening to the seventh.
• It names people. Who is covering what, who to find for what, who is the escalation point tonight. Anonymous instructions do not survive contact with a busy floor.
• It ends with a question. Thirty seconds of "what am I missing" from the people who worked the last event catches more problems than any reporting process.
• It is written down afterwards. One short recap to supervisors, so the people who missed it and the people who arrive mid-shift are not guessing.

Supervisors who cannot attend a briefing, and staff arriving for a split shift, are the two groups most likely to be operating on stale information. A scheduled message to the affected roles closes that gap without another meeting. Listo supports scheduled task requests and messages for exactly this pattern, so the 16:00 briefing content reaches the 19:00 arrivals automatically.

Design for the New Hire, Because There Always Is One

Venue staffing turns over constantly. The Bureau of Labor Statistics JOLTS series put the overall quits rate at 2.0 percent in June 2026, and accommodation and food services has sat above the private-sector average for years running. Practically, that means your communication system is always being used by somebody encountering it for the first time, under time pressure, in front of guests.

That has three design consequences that most strategies miss.

Onboarding cannot be a prerequisite

If a new hire needs a training session before they can receive and complete a task, your first shift is a communication blackout. The test is whether someone can accept a request and mark it complete having been shown once, in thirty seconds, in a corridor. Two buttons is about the limit.

Personal devices create a fairness problem

Asking part-time staff to install work software on their own phone, use their own data and share their number is a request many will quietly decline. Shared tablets, house phones and wearables avoid the issue entirely, and they survive turnover because the device stays when the person leaves.

Institutional knowledge has to live in the system

In a stable team, knowing that the third-floor ice machine is unreliable lives in someone's head. In a high-churn team it has to live somewhere retrievable, which in practice means the request history. A venue that can see it logged 40 requests against the same piece of equipment last quarter is not relying on anyone's memory.

Give Silence a Consequence

Every communication strategy has a plan for sending messages. Almost none have a plan for the message that lands and gets ignored, which on a venue floor is the failure that actually costs you.

The fix is structural rather than cultural. An unanswered request should produce a reminder, and then move up to a supervisor automatically, without anyone noticing it was stuck. Listo does this with an explicit accept or decline step, reminder notifications on unanswered requests, and automatic escalation to management. The point is not to catch people out. It is that silence is information, and a system that treats silence as success will lie to you.

Once escalation exists, two useful things follow. Managers stop spending the event doing verbal follow-up, because the system surfaces what is stuck. And you get a genuine number for how often requests go unclaimed, which is usually the most uncomfortable and most valuable metric in the building.

Write Down Who Owns Each Decision

A surprising share of what looks like a communication failure is actually an authority failure. Somebody knew about the problem, told the right person, and then waited, because nobody had said who was allowed to decide.

The classic version happens with money. A suite guest asks for something off-menu, or a party wants to extend past the contracted end time, or a piece of equipment needs a part that is not in stock. The request travels up three levels not because the information moves slowly but because each level has to check. By the time an answer comes back the moment has passed and the revenue with it.

Fixing this takes one uncomfortable exercise. List the ten decisions your floor staff most often need made mid-event, and against each one write a name and a dollar limit. Comp authority up to a stated amount. Authority to open an extra point of sale. Authority to pull a staff member from one location to another. Authority to call a contractor. Then say it out loud in the briefing, because a delegation nobody has heard about is not a delegation.

Two things change once this exists. The action channel gets quieter, because fewer requests are really questions in disguise. And the escalations that remain are genuine, which makes them worth a manager's attention rather than something to be triaged past.

Build the Cadence Around the Event Calendar

Weekly newsletters make sense in an organisation with a working week. A venue runs on an event calendar, and communication should follow it.

1. Before each shift - The briefing. What changed, who covers what, who to escalate to.
2. During the shift - Only routed tasks and time-critical operational notices. Nothing else. This is the discipline that makes the channel trustworthy.
3. After each event - A short written recap to supervisors: what broke, what ran long, what to carry into the next event. Ten lines is plenty.
4. Each month or series - One genuine all-crew update, covering results, changes and recognition. This is where you spend the goodwill you have preserved by not spamming the action channel.
5. Each quarter - Review the data with supervisors. Median response times, unclaimed request rate, which locations generate the most demand. Change something as a result, and say what you changed.

That last step is the one that converts a communication plan into a management system. If the numbers never change what you do, the crew works that out quickly and the whole thing becomes theatre.

What Good Looks Like in Practice

The venues that get this right tend to show the same pattern: fewer messages, more of them acted on, and a much shorter tail of requests that go nowhere.

At TD Garden, Delaware North runs 90 premium suites on Listo with average response times under five minutes, and completed 1,472 guest requests over six months. What matters in that number is not the total but that each request had an owner and a completion record, so nothing depended on someone remembering. At Great Wolf Lodge Niagara, response to 24 private cabanas runs one to two minutes.

Across its customer base Listo reports an average 15 percent reduction in monthly labour hours, which is largely a communication result rather than a scheduling one. Time spent finding the right person, walking to check whether something was done and repeating instructions over a radio is labour that produces nothing. Results vary by venue, and any number quoted as an average should be treated as one.

A Short Diagnostic

Before you rewrite anything, answer these five questions honestly. Most operators find two or three of them uncomfortable, and those are the ones worth fixing first.

• If a guest request went unanswered last event, would you know? Could you say how many did?
• What percentage of the scheduled crew attended the last pre-shift briefing? If you are guessing, that is the answer.
• Where does a staff member go to find out something they were told last week and have forgotten?
• Can a new hire receive and complete a real task on their first shift without a training session?
• Which channel carries urgent action, and is anything else allowed in it?

A strategy that answers those five is worth more than a twenty-page plan. If you want to see how the action tier works in a live platform, our platform page walks through routing, accept and decline, escalation and reporting, and the broader intelligent venue management guide covers how it fits alongside the rest of your operation.