One event, four weeks of impact: how to turn your town hall into a content campaign

The all-hands ends. You send the recording to everyone who missed it. The slides go into the intranet. You close your laptop and move on.

Three weeks later, a manager asks you what was actually decided at that meeting.

This isn't a story about one forgetful colleague. It's a description of how most internal events end — not with a bang, but with a quiet disappearance. And it points to where most internal communications investment silently goes to waste: not in the planning of the event, but in everything that doesn't happen afterward.

The effort-to-impact gap

Think about the last major all-hands your team ran. The prep time alone — speaker briefings, leadership alignment, technical rehearsals, design iterations — likely spanned two to three weeks. The event itself: sixty minutes. The post-event communication: one email, one recording link, maybe a summary document written under pressure the following morning.

The ratio is striking. Weeks of input for one hour of output, followed by a follow-up strategy that's largely improvised.

This isn't a resourcing problem. It's a framing problem. Most internal teams think of an all-hands as an event with a beginning and an end. The more useful frame is to think of it as the centrepiece of a communication cycle — with a before, a during, and an after that each deserve deliberate attention.

Why messages don't stick after a single broadcast

Memory research offers a useful frame here. Ebbinghaus's forgetting curve — one of the most replicated findings in cognitive psychology — shows that under passive conditions, people forget roughly 70% of new information within 24 hours and up to 90% within a week. Without active reinforcement, a message delivered once is a message largely lost.

Internal communications adds a layer of complexity on top of this. Employees aren't sitting in a quiet room absorbing your town hall. They're half-watching on a laptop, fielding messages in another window, managing the reality of their actual workday at the same time. The live event is already competing for attention. The single follow-up email is competing with everything else in an inbox that's already full.

The solution isn't to shout louder or send more messages. It's to design a communication architecture that distributes the message across time and formats — so it finds employees where they are, not just when the calendar says the event happened.

Phase 1 — Before the event: building anticipation, not just logistics (week −2 to 0)

Most pre-event communication treats the town hall as a scheduling problem: get it on calendars, send a reminder, done. From a logistics perspective, that's sufficient. From a communication perspective, it's a significant missed opportunity.

The two weeks before an event are the only window you have to shape the mindset employees bring with them. And that mindset has a direct effect on how much they retain. Cognitive research on the pre-exposure effect shows that people process and remember information more deeply when they've encountered the topic beforehand — even briefly, even casually.

Three pre-event formats that actually move the needle:

A teaser with real substance: Not "we look forward to seeing you" — but a short clip from a senior leader that raises a genuine question without answering it. "We've made a decision this quarter that changes how we think about X. We'll walk through the reasoning live on Thursday." This creates genuine curiosity rather than a compliance-driven obligation to attend.

A pre-event survey with a visible payoff: Two or three questions that show the agenda was shaped around what employees are actually thinking about — not only what leadership wants to communicate. Opening the event by showing the survey results is one of the simplest trust signals in internal communications: we listened before we spoke.

Advance question submissions: Employees who've already submitted a question arrive invested. They have a personal stake in the event before it begins. And they're far less likely to drift if their question is still unanswered.

Phase 2 — During the event: producing content, not just delivering it

The live event is your communication moment. It's also your content production window for everything that comes after.

The difference between teams that extract three assets from a town hall and those that extract ten rarely comes down to budget or team size. It comes down to whether someone decided beforehand which content would be repurposed — and planned for it.

In practice, that means three things decided before the event goes live:

• Identify two or three segments that will work as standalone short clips — a CEO statement, a key announcement, a moment of unusual clarity on a complex topic
• Structure the Q&A documentation in real time as categorisable units (topic, question, answer, any open items) rather than freeform notes
• Designate one person whose only job during the event is structured content capture — not moderation, not technical support, just systematic documentation

Phase 3 — After the event: this is where the campaign begins (weeks 1–4)

This is where most teams stop thinking strategically — and where the highest-leverage communication work actually happens.

The challenge isn't motivation. Most IC professionals know they should do more after an event. The challenge is structure: what gets created, for whom, through which channel, by when. Without a clear framework, post-event communication either gets skipped or becomes reactive, rushed, and under-resourced.

Here's a concrete four-week model — scalable to your team size and cadence.

Days 1–2: the immediate package

This window is the most critical. Employees who attended are still in context. Employees who missed it are wondering what they need to know. Both represent a communication opportunity — but only if you move quickly.

• Three headline takeaways from the event (not a full summary — half a screen at most, written for someone who wasn't there)
• The top five Q&A questions with written answers — in plain language, not meeting-speak
• Recording link with chapter markers, so no one needs to scrub through 60 minutes to find what's relevant to them

Week 1–2: the depth layer

Not every message needs immediate depth. But the topics that generated the most questions in the room deserve a second communication wave — one that goes beyond "here's the recording."

• A 60–90 second clip of the event's strongest content moment, packaged as a standalone asset that works without the surrounding context
• A short intranet post or follow-up article on the topic that raised the most questions — with an explicit invitation to continue the conversation
• A manager briefing document: not the full event replay, but a one-page translation of the key messages into team-level language. "What does this mean for us, specifically?" is the only question employees ultimately care about — and only their direct manager can credibly answer it

Weeks 3–4: the long tail

Most internal teams have mentally moved on by this point. That's precisely why content in this window is disproportionately effective.

• A concrete progress update on whatever was announced or committed to in the event. "We said we'd do X. Here's where we are." This is one of the most powerful trust signals in internal communications — and one of the most consistently underused
• Targeted surface of on-demand content for employees who've since hit a relevant moment in their own work — a new team member who just joined, someone now working on a project that was announced at the event
• Early teaser for the next event, with an explicit callback to the last one: "At the last all-hands, many of you asked about Y. Here's what's happened since — and what we'll be covering next."

→ How MEETYOO automatically generates chapters, summaries and a searchable archive from a single live event

What one well-documented town hall actually produces

To make this concrete:

None of this is hypothetical. Every asset in this list is extractable from a single 60-minute event — if you decide in advance to extract it.

Why this works for everyone, not just the communications team

It's easy to read this framework as more work for an already stretched IC function. In practice, when it's built into the workflow rather than added on top of it, it reduces reactive work significantly.

For employees: the message reaches them when and where it's relevant to their actual work — not only when the calendar said the event was happening. Communication finds them, rather than requiring them to find it.

For senior leaders: their statements work harder. A clear position from the CEO, pulled as a standalone clip and shared a week after the town hall, lands with more focus and attention than the same words delivered mid-event to a partially distracted audience.

For the IC function itself: a structured content strategy is far easier to defend than a collection of reactive one-offs. When leadership asks why the message didn't land, "we communicated it across eight touchpoints over four weeks" is a credible answer. "We sent it at the all-hands" is not.

→ How to make your internal event engagement and reach measurable

Conclusion: the event is the beginning, not the destination

A town hall that ends when the stream goes offline was always going to underperform. Not because the content was poor or the production was inadequate — but because a single broadcast moment was never designed to do the work of a sustained communication strategy.

The teams that treat internal events as the centrepiece of a deliberate campaign — with structured phases before, during, and after the live moment — don't just reach more employees. They build something harder to manufacture and more valuable than any single event: the expectation that internal communication means something. That announcements have follow-through. That the next event is worth showing up for, because the last one was.

One event. Four weeks. A campaign worth running.

FAQ

How much additional time does this approach realistically require?

The largest investment is upfront — building the workflow and role assignments the first time. Once the framework exists, the incremental time per event is roughly two to three hours: one for structured content capture during the event, one for the immediate package the following day, and one for coordinating the follow-up assets. Much of that can be parallelised across team members.

What if the town hall doesn't contain major announcements?

Not every all-hands is a landmark event. But every event contains something employees are still thinking about afterward — a question from the Q&A, a leadership comment that needs context, a metric that raises more questions than it answers. The starting point isn't "what was spectacular?" It's "what will employees still be wondering about tomorrow?" That's your post-event content.

How do you serve employees who missed the live event?

The immediate package — summary, Q&A in writing, recording with chapter markers — is designed specifically for this group. The critical design principle is that each asset should stand alone, without requiring the full event as context. No references to "what we discussed earlier." Self-contained, navigable, accessible whenever is relevant to each person.

Should every manager do their own follow-up communication?

Yes — but as a local translation, not a repetition. "What does this mean for our team specifically?" is the question employees actually want answered, and it's the one only their direct manager can credibly provide. A brief briefing document (three to five bullet points) from the IC team gives managers the foundation without asking them to reconstruct the whole event themselves.

How do you build this structure when there's no dedicated IC team?

Start with the immediate package only — it has the highest leverage for the least effort. Then add one element per event: a pre-event survey the next time, a leadership clip the time after that. The approach works incrementally. What it doesn't work as is improvisation — the decision to do it at all needs to happen before the event, not after.