Nonprofit work increasingly happens through text messages, Microsoft Teams chats and other informal messaging tools.
A program director approves an exception in Teams. An executive confirms a vendor decision by text. A board officer sends instructions through a group chat. An employee explains a grant-reporting change in a private message.
These conversations may contain information the organization later needs, but they are rarely treated as official records. Messages disappear, employees leave and decisions become difficult to reconstruct.
Convenient communication should not create invisible institutional memory.
Decide Which Messages Are Records
Not every message needs to be preserved. Routine scheduling, casual conversation and duplicate information may have little long-term value.
Messages may require retention when they document:
- Approvals or significant decisions
- Changes to procedures
- Contract or grant obligations
- Financial instructions
- Personnel actions
- Participant-service decisions
- Safety or incident responses
- Board direction
- Legal notices
- Commitments made to partners or vendors
The IRS requires tax-exempt organizations to maintain records that support their receipts, expenditures and reported activities. Its recordkeeping guidance for exempt organizations focuses on the substance of the record, not merely whether it began as a formal document.
The National Archives also recognizes texts, chats and instant messages as forms of electronic messaging that may require management as records. Its electronic-message guidance provides a useful framework, even though its formal requirements apply to federal agencies.
Move Important Decisions Into an Approved System
Employees should not be expected to preserve every conversation indefinitely. Instead, the nonprofit should establish a simple rule:
When a message creates an important decision, obligation or exception, the responsible employee must transfer the essential information into the approved system.
That might involve:
- Updating the relevant SharePoint procedure
- Saving an approved decision summary
- Recording a task in the project system
- Adding a note to the grant-management platform
- Updating the participant record
- Filing the final approval with the contract
- Documenting the decision in board minutes
This helps the nonprofit retain institutional knowledge without turning every chat into permanent clutter.
The receiving system depends on the subject. The CRM remains authoritative for donor activity. The case-management system remains authoritative for participant records. Accounting software remains authoritative for financial transactions. Approved board minutes remain authoritative for board action.
Set Retention Rules for Teams
Microsoft Teams messages can be governed through Microsoft Purview retention policies. Microsoft explains that different policies may apply to chats, channel messages, group-connected content, SharePoint files and OneDrive files. Review Microsoft’s Teams retention guidance before assuming that every related item is preserved together. (Microsoft Learn)
The organization should determine:
- Which messages must be retained
- How long different categories are kept
- Who may configure retention policies
- How legal holds are handled
- Whether personal texting is permitted for business
- How employees capture decisions made outside Microsoft 365
- What licensing and technical configuration are required
Retention should reflect legal, contractual, operational and privacy requirements. Keeping everything forever creates its own cost and risk.
Make the Rule Easy to Follow
SharePoint should contain the approved electronic-communications policy, examples of records, retention responsibilities and instructions for transferring important information.
Copilot Studio provides the conversational layer. Through Maisy, employees could ask:
- Does this Teams message need to be documented?
- Where should this approval be recorded?
- Which system holds the authoritative decision?
- How long are channel messages retained?
- May I use personal texting for participant information?
- Who manages our Microsoft 365 retention policies?
Maisy should retrieve approved guidance. It should not determine legal-retention periods, preserve messages automatically or expose private conversations to unauthorized employees.
How Maisy Helps
Pixeldust begins by identifying where employees communicate, which decisions are commonly made through messages, what information is being lost and which systems should receive the official record.
Pixeldust then helps define practical capture rules, assigns content owners, reviews permissions and organizes approved guidance in SharePoint. Microsoft Purview and Teams retention features can be evaluated separately based on licensing, security, technical requirements and legal review.
Maisy is then configured through Copilot Studio and tested with realistic questions. This helps the nonprofit retain institutional knowledge created in everyday communication without treating every message as permanent or confusing informal conversation with the authoritative record.
