# How to solve announcements that do not reach operations | Vindula > See how to organize audiences, channels, priority, and evidence so important announcements reach the people who need to act. Source: https://vindula.ai/blog/como-resolver-comunicados-que-nao-chegam-na-operacao Intranet # How to solve announcements that do not reach operations See how to organize audiences, channels, priority, and evidence so important announcements reach the people who need to act. Fabio Rizzo Specialist in employee experience, intranet, and artificial intelligence @fabiorizzomatos May 1, 2026 3 min read When **announcements do not reach operations**, the problem is rarely just lack of notice. Usually, the company did publish the message, but in the wrong channel, to an audience that was too broad, without clear priority, or without reading confirmation. The effect appears on the shop floor, in units, shifts, construction sites, and field teams: people follow the old procedure, miss deadlines, ask the same thing to leaders, or discover the change through parallel conversations. ## The real pain The pain is not "sending an announcement." The pain is making the right information reach the right person at the right moment, with clarity about the expected action. Common signs include HR or Communication publishing while operations says it did not receive it, leaders becoming manual relayers, employees without corporate email staying outside the flow, critical announcements mixing with lightweight campaigns, nobody knowing who read or acknowledged, and each unit creating its own relay method. Without governance, internal communication becomes dependent on local goodwill. ## Why it happens The problem usually comes from four combined failures. The first is lack of segmentation. The company communicates to everyone because it does not trust groups, roles, units, or audience rules. The second is lack of priority. A procedure change competes with institutional news, internal campaigns, and operational messages. The third is channel fragmentation. Part goes by email, part by chat, part by board, part by meeting. Later, nobody knows which version is valid. The fourth is lack of evidence. If the announcement was mandatory, the company needs to know who received, read, or acknowledged it. ## How to solve it Classify announcements by criticality: news, campaign, operational guidance, procedure change, and mandatory communication. Each class should have its own rule. Define real audiences. "All employees" is not enough. Use unit, area, role, shift, operational profile, or functional group when it makes sense. Choose an official publication point. Chats and emails can support distribution, but the official version must be somewhere people can consult later. For critical announcements, use evidence. Simple reading can be enough in some cases. In others, explicit acknowledgment is needed, especially for rules, policies, safety, or procedures. Review the role of leaders. They should reinforce critical messages and track pending items, not carry the entire distribution. ## What to measure Measure reading rate by audience, pending status by unit, time to reading, acknowledgment in mandatory communications, recurring questions after publication, and republications caused by unclear messaging. These data show whether the issue is channel, audience, text, or operational routine. ## Where Vindula fits Vindula supports [internal communication](/plataforma/comunicacao), [corporate intranet](/plataforma/intranet), and [intranet software](/software-intranet) to centralize announcements, segment audiences, and track evidence when the message requires control. It is also worth going deeper in [segmented communication on the intranet](/blog/comunicacao-segmentada-na-intranet-publicos-regras-e-evidencias). Solving announcements that do not reach operations requires less improvisation and more rule. The intranet works better when it makes clear who needs to receive, what needs to be done, and how the company tracks the flow. ### Fabio Rizzo Specialist in employee experience, intranet, and artificial intelligence Professional passionate about digital transformation and employee experience, committed to creating more engaging and productive work environments. @fabiorizzomatos Explore the platform ### Want to see this in practice? Discover how Vindula applies these concepts in day-to-day operations. Learn about the Intranet module ## Related Articles Intranet ### How to solve the problem of each unit communicating in its own way See how to standardize internal communication in companies with multiple units without losing local context. Fabio Rizzo May 1, 2026 • 3 min read Intranet ### How to solve lack of evidence in critical announcements Understand when to measure reading, when to ask for acknowledgment, and how to reduce risk in critical announcements without making everything mandatory. Fabio Rizzo May 1, 2026 • 3 min read Intranet ### How to solve information scattered across HR, IT, and Operations See how to reduce scattered information across areas using intranet, editorial governance, an official source, and shared indicators. Fabio Rizzo May 1, 2026 • 3 min read View All Articles