The policy nobody read
Internal comms, and the end of the intranet
Three weeks after a policy ships, ask ten people what changed. Insights is for the zero who can answer: a weekly briefing of five items at most, every quote checked against the source file, with the practice attached.
You
You published the new escalation policy three weeks ago. You have no idea whether anyone read it.
The AI plays
The intranet
Where everything important goes to be ignored
Holds everything your people need to know, in files nobody opens, behind a search nobody trusts.
“It is all in there. You just have to know where to look.”
The intranet opens.
An illustration of the problem, not a product screen. What Insights reads is whatever you connect.
The weekly briefing, with example data. What changed, quoted from your own files, with the practice attached.
What lands in their inbox
A short briefing, written from your own files, with the quote from the document sitting right there so nobody has to go and check. Your comms lead approves it before it goes anywhere, and each item carries the practice for what changed.
- 01
Finds what changed since last week
- 02
Drafts a short briefing, quoting the source
- 03
Checks every quote against the original file
- 04
Attaches the practice for what changed
Built from your own material
The policies and handbooks you already wrote
The product docs your team never gets around to reading
Only the places you choose to connect, and nowhere else
What it will not do
Copy your files out of your tenant
Publish anything before a person approves it
Quote a document without checking the quote
Who runs it
Internal communications
HR and people teams
Compliance and policy owners
Enablement
People find out what changed because it arrived, not because they went looking.
Bring us your version of this conversation
We write the character on the other side of it, then walk you through a real scored session.
Book a demoTeams that start here often add
Compliance and security awarenessManagers and difficult conversations