After a major announcement, the questions pile up in a Slack channel. There will always be the practical inquiries about timelines and immediate impact, as you might expect. But others might try to dig deeper and ponder what the employee base isn’t being told. This can lead to a situation in which managers keep answering the same questions in their team meetings and when a town hall rolls around, you can bet leadership will be inundated.
A great way for communicators to avoid these types of situations is by building a living FAQ document.
Samantha Hillstrom, global head of internal communications at Eventbrite, told Ragan what she considers when she sets out to create a living FAQ document.
“I’m thinking about three things — what’s emotionally charged, what’s ambiguous or evolving and what people will ask privately but hesitate to ask publicly,” Hillstrom said. “In moments like a significant organizational transformation, a living FAQ needs to reduce noise and anxiety and provide stability.”
When they’re done well, a living FAQ document prevents rumor cycles and saves managers from answering the same question 20 different ways.
Here are four steps that make the process work.
1. Define the purpose and scope at the outset.
A living FAQ document succeeds when it is intentionally scoped around business priorities and employee needs. Karen Testa, director of global communications at Bell Flight, told Ragan that setting the parameters at the outset can keep things narrow and clear.
“Define what the FAQ will cover and decide if it’s companywide or department-specific,” Testa said. “That determines the distribution channel. For instance, when we’re looking at an FAQ document that’ll be accessible to employees across the world, we focus primarily on globally relevant content and business priorities.. Location-specific or job-specific questions are usually handled by team supervisors.”
Testa added that grouping questions by theme can help grab employee attention.
“Categorize the FAQs by theme and tie them to strategic priorities like growth, compliance or transformation,” she said. “When priorities shift, update the categories first. Then you can adjust the answers. If the structure doesn’t reflect what the business cares about right now, employees notice.”
Scope does more than keep things organized. It signals what the business cares about right now.
2. Build an intentional feedback loop for updates.
If your FAQ document isn’t evolving, it isn’t living. The best living docs are built from employee questions that comms pros mine directly from the source. Hillstrom treats the FAQ process as a live listening exercise.
“Any adjustments we make are signal-driven,” she said. “I monitor Slack threads, all-hands meetings, Q&A sessions, anonymous submissions and manager feedback to get the material we need. If the same question surfaces multiple times, that’s a clarity gap in the strategy or the communication. Then we either refine an answer, split a broad question into more specific ones or add a new entry entirely.”
Testa offered a candid reminder that the sustainability of the document matters just as much as strategy.
“FAQ pages are only as useful as the amount of updating and maintenance you can realistically do,” she said. “Otherwise, your living document dies a slow death.”
3. Write in a voice that’s easily accessible for employees.
Tone determines whether employees trust the answer they’re getting. Hillstrom said that a living FAQ doc should be composed in language that isn’t mired in corporate speak.
“Write the questions in the voice employees would actually use,” she said. “‘Will I still report to the same manager?’ is more effective than ‘How will this impact organizational structure?’ Lead with the headline in the answer and avoid corporate vagueness. Say ‘we don’t know yet’ when it’s true — don’t overpromise and don’t overexplain.”
She added that language choice is always key, especially in moments of major change like layoffs or reorganizations.
“The tone should be calm, direct and human,” she said. “There’s nothing worse than an answer that says nothing. The only thing that might be is a statement that wraps nothing in corporate jargon.”
Testa said that the wording should be structured in a way that makes the FAQ document simple to update when needed.
“If it’s a long document, make each section easy to update independently so changes don’t disrupt the whole page,” she said. “Link to deeper resources like policies or maps so the FAQ remains a gateway rather than a dumping ground.”
4. When you’ve built (or updated) the doc, make it accessible.
A living FAQ only works if employees know where to find it. Hillstrom said that at Eventbrite, she puts the docs on the company’s intranet and links to them on Slack and email.
“The goal is always a single source of truth,” she said. “Over time, that reinforces the behavior we want — if you have a question, start there. By shifting the burden from individual conversations to a single trusted source, you reduce the load on managers and leadership.”
She added that transparency around changes to the doc matters just as much as telling employees where it lives.
“For minor clarifications, we update the document and note the revision date,” Hillstrom said. “For material changes like timelines, policy clarifications and structural updates, we proactively communicate what’s new. The guiding principle is simple — just treat people like adults. Don’t quietly change something that materially affects them, and don’t make them hunt for what’s new.”
Living FAQ documents are more than answer repositories. They signal that the organization is listening. Done right, they become trust-building tools and not just informational ones.
Sean Devlin is an editor at Ragan Communications.
