How do we keep our email and messaging records program current as employees adopt new collaboration apps faster than IT can approve them?
When collaboration tools spread faster than IT can vet them, the gap is rarely about technology. It is about governance moving slower than behavior. A durable program treats new apps as an expected, recurring event rather than a one-time crisis.
Anchor the program in content, not channels
The legal definition of a record turns on content and function, not the platform it lives on. A decision approved in a chat thread is as much a record as the same decision sent by email. Write your policy so it is technology-neutral: it should already cover “messaging and collaboration tools” as a category, so a new app is in scope the moment someone uses it, even before IT formally approves it.
Close the lag with policy, not just controls
You cannot wait for technical capture to catch up. Bridge the gap with:
- A clear, public rule on which tools are approved for official business, and that work records must not live only in unapproved apps.
- A simple path for employees to request review of a tool they want to use, so shadow adoption surfaces early.
- Guidance to copy or export substantive content from unsanctioned apps into a managed repository until proper capture exists.
Build a recurring review cycle
Treat tool intake as a standing process. Convene records, IT, security, and privacy on a regular cadence to assess newly adopted apps, decide whether they are sanctioned, and confirm how their content will be captured, retained, and disposed of under your schedule. Map each channel to existing retention categories so nothing defaults to “keep forever” or silent deletion.
Train for the behavior, not the tool
Because apps change constantly, train people on the principle: if it documents a decision, transaction, or obligation, it is a record regardless of where it was created. Reinforce this at onboarding and when new tools appear.
For more foundational guidance, see the email and messaging topic hub.
A program designed around content, a fast intake path, and a recurring cross-functional review will stay current no matter how many new apps appear, because it is built to absorb change rather than react to it.
Sources & further reading
Authoritative government and non-profit references.
- Records management policy and guidance — National Archives (NARA)
- ISO 15489-1 Records management — ISO
How to cite this page
APA
RM University Editorial. (2026). How do we keep our email and messaging records program current as employees adopt new collaboration apps faster than IT can approve them?. Records Management University. https://www.recordsmgmt.org/questions/how-to-keep-email-and-messaging-records-program-current-as-new-collaboration-apps-emerge/
MLA
RM University Editorial. "How do we keep our email and messaging records program current as employees adopt new collaboration apps faster than IT can approve them?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/how-to-keep-email-and-messaging-records-program-current-as-new-collaboration-apps-emerge/.
Related questions
- Are emails between teachers and parents considered education records under FERPA?
- Are emails in my Sent folder and Inbox both records, or just one copy?
- Are emails on my personal phone discoverable in a lawsuit?
- Are ephemeral or disappearing messages legal to use for work, or do they violate recordkeeping rules?
- Are text messages and chat business records?