The Internal-Comms Audit Every 50+ Person Company Needs

After watching 30+ owners cross the 50-person line, my conclusion is this: the moment your company stops fitting in one all-hands and one Slack channel, internal comms quietly breaks — and nobody tells you, because the people who notice are the ones who've already given up trying.

Why does internal comms break around 50 people?

Below 30 people, every important conversation happens in a shared room — physical, Slack, or weekly all-hands. The CEO hears the friction directly. Around 50, three things change at once: you add a layer of managers, you split into functional teams, and the volume of daily decisions crosses what any one person can hold in their head.

The result is what I call the comms middle layer — and it's where information goes to die.

Definition: Comms middle layer — the band of managers and team leads who sit between executive intent at the top and individual contributor reality at the bottom. They translate both directions, and most companies have zero visibility into how well they do it.

You don't notice the break in any single missed message. You notice it when the same question gets asked three times by three teams in one week, or when a strategic decision made in May resurfaces in August as if it were new.

What does a comms audit actually measure?

Four questions, asked of every meaningful information flow:

1. Did the intended audience receive it? (Reach.)
2. Did they understand what was decided and what changes for them? (Clarity.)
3. Did the right next action happen, by the right person, on time? (Action.)
4. Was there a place to ask follow-up questions and get a real answer within 48 hours? (Loop closure.)

If you can't answer "yes" to all four for a given message — that's a leak.

Definition: Comms leak — a moment where leadership believes information was transmitted, but the receiving side either didn't get it, didn't act, or couldn't ask. Leaks compound silently.

The honest framing for owners: a comms audit is the Plan → Fact → Gap loop applied to communication itself. The plan is what leadership intended to convey. The fact is what reached and changed behaviour. The gap is everything in between — and that's your audit output.

The 5 channels to map

In a 50-500 person company, almost every meaningful message rides one of five rails. Audit each one.

1. All-hands / monthly company meetings — strategic context, big decisions, leadership tone.
2. Slack / Teams (or equivalent) — operational decisions, fast questions, ambient awareness.
3. Email — formal announcements, external-facing alignment, HR-adjacent topics.
4. Manager 1-on-1s and team standups — translation layer, blockers, individual context.
5. Documents / wikis / project tools — durable record, the place a new joiner reads to catch up.

A healthy 50-person company uses all five intentionally. A broken one uses Slack for everything, prays at the all-hands, and treats the wiki as a graveyard.

The 3 message types to track

Not every comm is equally costly when it fails. Sort everything you send into three buckets:

• Decision messages — "We're going to do X starting Monday." Highest cost if it leaks.
• Context messages — "Here's why the market is changing." Medium cost; affects judgment downstream.
• Operational messages — "Submit Q3 expense reports by Friday." Low cost individually, but cumulative friction if the channel is unreliable.

The audit asks: for each channel, which message type rides on it, and does that match what the channel is actually good at? Decisions on Slack thread #42 buried under memes is a structural error, not a one-off.

Copy/paste audit template

Run this as a one-week exercise. One owner or analyst, no consultants.

INTERNAL COMMS AUDIT — Week of [DATE]

Step 1: Inventory (Mon)
- List the last 20 important messages sent by leadership over 4 weeks
- For each: channel used, message type (decision/context/operational), intended audience

Step 2: Reach check (Tue)
- For each of the 20 messages, ask 3 random ICs in the target audience:
  "Did you see this? When? Where?"
- Mark each as: reached / partial / missed

Step 3: Clarity check (Wed)
- For 5 of the 20 (the most important decisions), ask:
  "In your own words, what changed for you because of this?"
- Mark as: clear / partial / wrong / "didn't notice"

Step 4: Action check (Thu)
- For each decision message: did the expected next action happen?
- If yes — by whom? On time? If no — why not?

Step 5: Loop closure (Thu pm)
- For each message: was there a place to ask a follow-up?
- Did anyone use it? Was it answered within 48 hours?

Step 6: Heatmap (Fri)
- One page: 5 channels × 3 message types = 15 cells
- Color each cell green/yellow/red based on reach + clarity + action
- Pick the 3 reddest cells. Those are your fixes.

The whole thing takes one week and roughly 12 hours of one person's time. The output is not a report. It's three commitments for the next sprint.

Tool tip (AIAdvisoryBoard.me): A daily Plan → Fact → Gap digest closes the audit loop on an ongoing basis — you don't have to re-run the manual audit every quarter. The Plan layer captures what leadership intends to communicate; the Fact layer pulls what teams actually report back in standups, 1-on-1s, and Slack; the Gap layer surfaces the deltas as a 2-minute owner digest each morning. For 50-500 person companies, this is the difference between hearing about a leak in week 8 and catching it on day 2. See how the 7-day diagnostic captures your current comms reality at https://aiadvisoryboard.me/?lang=en.

Manager scan (2-minute digest example)

A real two-minute morning digest for a 90-person SMB might read like this:

• Plan: Q3 OKR cascade communicated in all-hands 2 weeks ago — three teams owe a tactical plan response.
• Fact: Two teams submitted, one (Operations) is silent and has not referenced the OKRs in standups for 9 days.
• Gap: Likely either the OKR didn't reach the Ops lead with enough clarity or the Ops lead disagrees and hasn't escalated.
• Plan: Customer-success policy change announced via email 5 days ago.
• Fact: Three CS reps still quoting the old policy on calls (sample of 6 calls reviewed).
• Gap: Email channel underperforming for policy decisions on this team — try Slack pin + manager confirmation next time.
• Plan: Hiring freeze conveyed in last week's all-hands.
• Fact: Two open reqs still being actively recruited by hiring managers.
• Gap: Either the freeze wasn't clear, or there was an exception — which means an undocumented decision is now floating.

That digest takes 90 seconds to read and 4 minutes to act on. Without it, each of those three leaks compounds for two more weeks before someone notices.

Micro-case (what changes after 7-14 days)

A 75-person logistics SMB ran this audit after the founder noticed the same warehouse issue being raised in three separate channels over six weeks. The audit took one ops analyst eight days. The output: of 22 leadership messages reviewed, 7 reached the warehouse team late or partially, and decisions about shift changes were riding on the wrong channel (email instead of standup). Two weeks after the fix — moving decision messages to standup, Slack for operational, email reserved for HR/formal — the same warehouse issue stopped recurring, and the founder's "did we already decide this?" Slack messages dropped sharply. The founder kept a one-page heatmap on her wall and re-ran a lighter version every quarter.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30-500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

Tool tip (AIAdvisoryBoard.me): The audit gives you a snapshot; what you want next is continuous Plan → Fact → Gap visibility so leaks surface in days, not quarters. Our 7-day diagnostic plugs into your existing tools (Slack, email, standup notes, project trackers), maps the same five channels and three message types automatically, and gives the owner a morning digest. It's not a new tool for the team — it's a new layer of visibility for the owner. Try the diagnostic at https://aiadvisoryboard.me/?lang=en.

FAQ

How often should we re-run a full audit? Once a year as a full deep audit. Lighter quarterly check-ins on the three reddest cells from the last round. If you have continuous Plan → Fact → Gap monitoring in place, the deep audit becomes a confirmation exercise rather than a discovery exercise.

What if we're under 50 people — is this overkill? Probably yes for under 30. Between 30 and 50, do a lighter version — 10 messages instead of 20, no formal heatmap, just a one-page note. The structural break is more about layers of management than headcount itself, so a flat 60-person team can delay this longer than a hierarchical 35-person team.

Who should run it — owner, COO, or external? The owner or a trusted COO/Head of Ops who has the political license to ask ICs frank questions. An external consultant introduces a Hawthorne effect — people perform comms hygiene for the audit week and then revert. Internal also keeps the artifact ownable.

What's the most common fix that comes out of this? Decision messages riding on the wrong channel — usually Slack threads where they should be in a recorded standup or a pinned doc. Second most common: missing loop-closure mechanism (no place to ask follow-up, or follow-ups go unanswered for a week).

Conclusion

Internal comms doesn't break loudly. It breaks in repeated questions, in decisions that resurface months later, in the gap between what leadership thinks it conveyed and what teams actually heard. A one-week audit makes that gap visible. The fix is rarely "more communication" — it's putting the right message type on the right channel and closing the loop.

Pick a week. Map the last 20 messages. Build the heatmap. Ship three fixes. Then make the visibility continuous so the next break surfaces on day 2, not week 8.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works at https://aiadvisoryboard.me/?lang=en.