Key takeaways
36% of employees prefer all-hands or department meetings for receiving critical company updates, making the format one of the most trusted channels in the internal communications stack.
The problem is execution. When an all-hands runs as a one-way broadcast, employees disengage from it the same way they disengage from a company-wide email.
A well-run all-hands meeting gathers the entire company around the same information at the same time, creates space for real dialogue with leadership, and connects individual work to company-wide strategy.
The format earns its place in the calendar when it's built around conversation rather than broadcast.
Running the meeting well handles the first challenge. Getting it to employees across time zones, shifts, and distributed offices is the second. Internal podcasts are one way companies extend the all-hands reach to employees who couldn't make the live session.
An all-hands meeting is a company-wide gathering where every employee, regardless of department or seniority, comes together to receive the same information at the same time.
The format originates from the naval phrase "all hands on deck," where every crew member was needed for an urgent task.
In a business setting, the all-hands meeting gathers the entire company to align on strategy, hear from leadership, and connect across departments and levels.
It differs from a team meeting in scope. Team meetings handle operational coordination within a department; an all-hands addresses content that affects everyone in the company.
It's sometimes called a town hall, though the formats aren't identical (more on the differences below).
Companies typically hold all-hands meetings on a fixed cadence: monthly, quarterly, or biannually. Smaller companies often run them more frequently because the format scales more easily with under 100 employees.
How is an all-hands meeting different from a town hall? And how does either one differ from a regular staff meeting? The terms get used interchangeably in casual conversation, but the formats serve different purposes:
The all-hands meeting tends to be more structured, with leadership walking the company through prepared content (financials, strategic updates, recognition) before opening up to questions.
The town hall format flips that ratio, putting employee questions and leadership response at the center, often with less prepared content.
A staff meeting works at a different scope entirely, focused on a single department's operational rhythm rather than company-wide context.
In practice, many companies blend the formats. A monthly all-hands might run mostly as a town hall (Q&A-heavy), and a quarterly all-hands might lean toward the structured leadership-presents format.
The labels matter less than matching the format to the goal of each session.
The most common question after deciding to hold an all-hands is: What should I cover in a company all-hands meeting? The answer depends on cadence (a quarterly all-hands covers different ground than a monthly one), but the core structure holds across most companies.
Lead with the metrics that matter to employees: revenue trajectory, key results against quarterly goals, pipeline health, retention or NPS trends, and any major customer wins.
The discipline is to share context alongside the numbers. A revenue figure without explanation tells employees little; the same figure with the underlying drivers (new logos, expansion, churn pressure) gives the workforce something to actually understand.
Skip vanity metrics that don't connect to how the business is performing.
Cover what the company is working toward in the next quarter or year and how each team's work connects to the bigger picture.
The all-hands meeting helps employees see the throughline between their daily tasks and company-wide strategy, especially in larger organizations where individual contributors can lose sight of how their work compounds.
Reference specific goals and the trade-offs being made to hit them.
Public wins, spotlights, and shout-outs serve a real morale function.
Recognizing a team that shipped a major project, an individual who stepped up, or a cross-functional effort that solved a hard problem gives the all-hands a moment of celebration that connects work to people.
Keep recognition specific and earned. Without a name, a clear contribution, and the impact, the section starts to feel formulaic, and employees gradually tune out.
Brief updates from each function (engineering, marketing, sales, ops) on what they're shipping or working on. The point is to break down silos between teams that rarely interact in their daily work.
Marketing seeing engineering's roadmap, or sales hearing about a new product feature ahead of customers, builds the cross-functional context that makes collaboration easier later.
The Q&A session is the most engagement-driving element if it's run well.
Collect questions in advance through a chat channel or an async submission form so leadership can prepare thoughtful answers. Allocate at least 20% of the meeting time for Q&A.
Live questions from employees, with real responses from the exec team, separate an all-hands that builds trust from one that performs trust.
Close with what employees should know, do, or remember after the meeting.
Clear commitments from leadership (what gets shipped next, what decision is pending, what to expect at the next all-hands) give the meeting a concrete output rather than a vague "thanks for joining" closer.
The next steps section is what makes the all-hands feel productive instead of performative.
Once the content is planned, the harder question is: what's the best way to run an all-hands meeting that employees actually engage with? The difference between a meeting that energizes the team and one that becomes a passive broadcast comes down to structure and discipline.
The agenda goes out at least 24 hours before the meeting, ideally 48 hours.
Employees who know what's coming can prepare relevant questions, line up context for sections that affect their work, and decide where to focus their attention.
Build the agenda with time-blocked sections, named speakers for each segment, and an explicit Q&A allocation at the end.
A clear agenda also signals respect for everyone's time, which sets a different tone than a meeting that opens with "let me figure out what we're covering today."
For recurring all-hands, the agenda template stays mostly stable across sessions, with only the specific content updating each time.
Live polling, anonymous Q&A platforms, and pre-submitted question forms give employees a structured way to engage, surfacing the highest-voted questions to leadership rather than leaving them buried in a chat thread no one can follow at scale.
The risk to avoid is engagement theater: leadership scrolling through the chat without actually addressing what's there.
Real responses to actual questions, delivered in the meeting rather than deferred to a follow-up email, are what separate an all-hands that builds trust from one that performs it.
Cap each all-hands meeting at 90 minutes maximum, with most landing closer to 60.
For hybrid or virtual all-hands across time zones, shorter is always better since employees joining at off-hours have even less attention to give.
Cut content rather than extending the runtime.
An all-hands that consistently runs over erodes the format's credibility and trains employees to schedule conflicting commitments at the back end of the slot.
Remote and hybrid attendees often feel like second-class participants in all-hands meetings, watching from a small video square as in-room employees dominate the conversation.
A few structural fixes help.
Without these structural choices, hybrid all-hands meetings tend to favor in-person participants and quietly disengage remote workers.
Distributed teams, frontline workers, and employees across multiple time zones rarely all attend the live all-hands.
Recording the session solves the access problem, but consumption is a different challenge entirely.
Supporting Cast handles this layer by distributing all-hands recordings as internal podcast episodes through Apple Podcasts, Spotify, and YouTube Music.
Employees subscribe in two taps with no copying or pasting of private RSS feeds, and the recordings reach them where they already listen during commutes, walks, and focus blocks.
Episode-level analytics show exactly who listened to the all-hands, how far they got, and on which platform, giving comms teams visibility into who actually caught up versus who got the email and ignored it.
Run a short post-meeting pulse survey (three to five questions) covering relevance, clarity, and whether employees got what they needed.
If the recording is distributed through an audio platform, listen-through rates show what's actually landing across the workforce, not just what shows up in self-reported survey data.
Track engagement metrics over time. A single survey result is noise; the trend across six months reveals whether the all-hands format is improving or declining.
Use the data to refine cadence, length, and content mix, then test the changes against the next round of measurement.
The all-hands meetings that hold up across years share a structural trait: they treat the company-wide gathering as a conversation rather than a broadcast.
Leadership shows up prepared but open, employees feel safe asking real questions, and the content connects what's happening in the company to what each employee is working on every day.
The meeting itself is only half the work. Who actually gets reached by it and what employees do with the information afterward is the other half.
Supporting Cast extends the all-hands to employees who couldn't make the live session, with audio episodes they can consume during commutes, walks, or focus blocks. Talk to our team about getting listen-through analytics that show which segments of the workforce actually replayed your last all-hands.
An all-hands meeting is structured around prepared content from leadership (business updates, strategy, recognition), followed by Q&A. A town hall flips that ratio, leading with employee questions and leadership responding with less prepared content. Both formats reach the entire company, but the all-hands tends toward alignment and the town hall toward transparency. Many companies blend the two depending on the goal of each session.
Quarterly is the most common cadence for companies with 200 or more employees, with many running it monthly when under that threshold. The right frequency aligns with a clear business rhythm: a monthly all-hands works well during high-growth periods or major transitions; quarterly works better during more stable operating periods. Avoid setting a cadence that exceeds the volume of substantive content you actually have to share each session.
Distribute the agenda 24-48 hours in advance so employees can prepare. Build in real interactivity through live polling and anonymous Q&A tools, not just a chat box. Keep the meeting under 90 minutes. Design specifically for remote and hybrid participants with one-laptop-per-person and named facilitators. Allocate at least 20% of the time to leadership Q&A with real responses, and close with concrete next steps.
Recording the session is the baseline, but getting employees to actually watch the replay matters more than just making it available. Distributing recordings as audio episodes through internal podcasts lets distributed teams and remote workers consume the all-hands during commutes or focused time, with listen-through data showing comms teams who caught up and who didn't.