Most organizations don’t have a communications channel problem. They have a channel confusion problem: no shared understanding of which tool a given message belongs in, and no agreed process for what happens when the wrong thing lands in the wrong place. The result is predictable regardless of professionalism — an HR matter debated in a Slack channel, a half-finished donor figure emailed to a funder before it’s checked, a factual error sitting live on the website for months because nobody was sure whose job it was to fix it.
None of this requires new software. It requires a shared answer to two questions: where does this message belong, and what happens if it goes out wrong anyway? and most importantly in the age of AI and accuracy issues, common sense.
Match the channel to the message, not the habit
Chat tools like Slack and Microsoft Teams are built for speed, not permanence. Average response time on a Slack direct message runs under ten minutes, which is exactly what makes it the wrong home for anything that needs to be found again in six months, needs a formal record, or is going to an external party. One communications team that documented its own Slack habits found the same failure mode over and over: big decisions and anything requiring real accountability kept drifting into chat, where they were easy to lose track of, simply because chat was the path of least resistance. Email remains the better tool for anything formal, anything external, or anything that has to be retrievable as a record months later — external stakeholders and official updates belong there, not in a channel they can’t even see.
A simple way to sort it:
| Channel | Best for | Avoid using it for |
|---|---|---|
| Slack / Teams | Quick coordination, day-to-day questions, status pings, informal brainstorming | Formal decisions, anything needing a durable record, sensitive HR or personnel matters, external-facing communication |
| Official updates, anything going to a board member, funder, journalist, or other outside party, decisions that need a paper trail | Urgent same-hour coordination, back-and-forth that needs five replies to resolve | |
| Website | Information meant to be public, stable, and citable — programs, policies, impact reporting, official statements | Anything not yet fact-checked, anything that changes weekly, internal-only material |
The pattern holds regardless of sector. A university’s web policy, for instance, assigns a named content editor to every department page specifically so that nothing goes live without someone other than the author checking it first — the same logic an NGO or school newsletter needs, just at a different scale.
Internal doesn’t mean private
The most common etiquette mistake in Slack and Teams isn’t tone — it’s the assumption that a channel with a small membership is effectively off the record. It isn’t. Employment lawyers are blunt about this: there is no legal right to privacy in workplace chat, and internal messages — including edited or deleted ones — are treated the same as email if an organization ever faces a lawsuit or formal complaint. For an NGO, NPO, or school, that has a practical consequence beyond litigation risk: a screenshot of an internal channel can travel just as far as a public post, and often faster, because it arrives with the implied credibility of “this is what they really think.” The safest working rule is to write every Slack or Teams message as if a board member, a journalist, or the person being discussed might eventually read it — not because that’s likely, but because the two moments it happens are exactly the moments an organization can least afford it.
That standard doesn’t mean sanitizing every message into corporate flatness. It means keeping three categories out of chat entirely: personnel and disciplinary matters, anything a lawyer would call privileged, and unverified claims about a person, partner organization, or program outcome. Those belong in a conversation, a properly logged HR file, or an email with the right people copied — not a channel that anyone with access can screenshot out of context.
Websites need an owner, not just a publisher
A website is the one channel that functions as an organization’s permanent public record, which is exactly why it needs the most deliberate governance. A recent breakdown of nonprofit web policy put the core problem well: without a governance policy that spells out who can publish and who approves changes, the loudest internal voice wins, and it’s rarely the voice making the best call for the people the website actually serves — the fundraising team wants a donation button on every page, programs wants exhaustive service detail, the board wants governance documents front and center, and nobody is assigned to adjudicate between them. The fix isn’t complicated: name one person or small group with final publishing authority, require a second set of eyes on anything factual before it goes live, and set a regular review cycle so outdated material doesn’t sit there accumulating credibility it no longer deserves.
Common sense is still the biggest tool in the kit
None of the frameworks above substitute for the most basic filter an organization has: would this be fine if the wrong person saw it, and does the person writing it actually know this to be true? Most channel disasters don’t happen because a policy was missing. They happen because someone hit send on something they’d have caught with a second’s pause — the reply-all that should have been a direct message, the figure typed from memory instead of checked against the report. Policies and tools narrow the room for that kind of mistake; they don’t replace the judgment call in the moment.
Where tools genuinely help is in making that judgment call visible to more than one person before something goes out. A project management platform like Asana or Monday.com won’t stop a bad piece of writing, but it will stop a bad piece of writing from publishing itself. Nonprofit Marketing Guide’s own writeup on running a communications calendar in Asana describes tracking every piece of content’s progress, platform, and approval status in one shared view, so a post can’t quietly skip the review step just because the person who wrote it is in a hurry. Asana’s own nonprofit templates build the same idea in directly, with an editorial calendar that tracks approval status alongside content type and platform rather than leaving sign-off as a separate, skippable step. The tool doesn’t do the thinking. It just makes it much harder for a piece of content to slip out the door without anyone else having looked at it.
AI raises the speed, not the accuracy — build the safeguard in early
Generative AI tools can draft a newsletter, a grant report summary, or a social post in a fraction of the time a person would take, and that speed is exactly what makes the risk different in kind, not just degree. A tool that writes faster than a human can also produce a confident, well-formatted, completely wrong fact faster than a human would ever type one. The clearest cautionary case remains the 2023 U.S. federal court filing in which a New York attorney submitted a legal brief built on case citations ChatGPT had fabricated entirely — plausible-sounding, properly formatted, and nonexistent. Thomson Reuters’ own guidance on the episode makes the fix sound almost too simple: the lawyers would have avoided the entire mess by checking the sources before filing, which is the same discipline any communications team needs to apply to AI-drafted material before it goes anywhere near a donor, a journalist, or the website.
The safeguard has to sit at the front of the process, not the back. Treat AI-drafted copy the way an editor treats a byline from an unfamiliar freelancer: assume every name, number, date, and quote needs independent verification before publication, not a read-through for tone. Build that check into the same approval step already sitting in the project management tool, rather than trusting that someone will remember to do it separately. An organization that adds the verification gate after the first AI-generated error goes out is adding it one embarrassment too late.
When something goes out wrong
Every organization eventually sends, posts, or publishes something it shouldn’t have — a typo that changes a donor figure by an order of magnitude, an internal message forwarded to the wrong list, a photo posted without proper consent, or a post that simply reads wrong once it’s live. What separates a minor embarrassment from a lasting credibility problem is almost never the mistake itself. It’s the speed and honesty of the response.
Newsrooms have the most developed thinking on this because they publish constantly and get things wrong often enough to have built real systems for it. The American Press Institute’s guidance on digital corrections lays out three things every organization needs, regardless of sector: someone designated as the final call on whether a correction is needed, a clear workflow for who writes and approves it, and a policy of fixing the visible record rather than silently editing it away. The Washington Post’s own template is a useful model for the language: state plainly what was wrong and what’s now correct, rather than vaguely alluding to an “update.”
A simple severity framework keeps the response proportional:
| Severity | Example | Response |
|---|---|---|
| Minor | Typo, broken link, small formatting error | Fix it directly; no notice needed |
| Factual error | Wrong figure, date, name, or misattributed quote | Correct the content and add a visible, dated note explaining what changed |
| Reputational or sensitive | Photo published without consent, an internal message sent externally, a post that reads as insensitive | Take the content down or correct it immediately, notify whoever was affected directly, and consider whether a public acknowledgment is warranted |
| Serious | Confidential information disclosed, a claim that could cause real harm if left uncorrected | Escalate immediately to the person with designated authority (communications lead, executive director, legal counsel as needed); do not wait for a scheduled meeting; document everything |
The American Red Cross’s 2011 Twitter mishap is still one of the clearest real examples of getting the response right. A staff member using a shared social media tool accidentally posted a personal message about beer to the organization’s account instead of her own. The organization deleted the post, acknowledged it publicly within about an hour, and did so with a short, honest line about the mistake rather than a defensive non-explanation — “we’ve deleted the rogue tweet but rest assured the Red Cross is sober and we’ve confiscated the keys.” Because the response was fast, factual, and unafraid to admit what happened, the story became a case study in good crisis handling rather than a lasting reputational dent — it was even picked up by national outlets as an example of a mistake handled well, not a scandal. Acknowledge mistakes.
The lesson generalizes past social media. Whether the mistake lands in an inbox, a Slack channel, or a live webpage, the same four steps apply: assess severity honestly rather than minimizing it, correct or remove the content without delay, tell the people directly affected before they find out some other way, and leave a visible, dated record of what was fixed rather than quietly scrubbing it. Organizations that skip that last step tend to get caught, and getting caught editing history costs more trust than the original mistake ever did.
Sources
- MailOver, “Email vs Slack vs Teams: The Definitive Communication Guide,”
- Uproer, “Steal our Slack vs Email Policy for Optimal Team Communications,”
- Gmelius, “When to Use Email vs. Slack? 7 Team Communication Tips,”
- South Puget Sound Community College, Web Content Governance Policy
- Fast Company, “Yes, your Slacks and text messages are fair game in a lawsuit,”
- Socialectric, “Why Your Nonprofit Needs a Website Governance Policy,”
- Nonprofit Marketing Guide, “How to Use Asana to Organize a Social Media and Communications Calendar,”
- Asana, Nonprofit Templates — Editorial Calendar
- Thomson Reuters, “Accuracy in AI: Reducing hallucinations at work,”
- American Press Institute, “How news organizations can correct website and social media errors effectively,”
- American Red Cross, “Twitter Faux Pas,” Red Cross Chat
- CNN Money, “Dogfish Head, Red Cross make Twitter oops a marketing boom,”
