More than four years. 567 people. An average message that reaches 61 of them.

The measurement behind that phrase is reach: the average number of people a message is delivered to, rather than a count of who opened it.

When information is shared across a care team, its value extends past the sender and the recipient. The nurse picking up the next shift, the therapist seeing the patient on Thursday, the manager who will have to answer for the episode — all of them are downstream of something somebody sent on Monday. A space keeps that conversation available to the people responsible for delivering the care, rather than to the two people who happened to be typing.

Usage shows engagement. Collaboration shows that information travels, and that is what separates a platform from a messaging app.

An organization where an average message reaches two people has bought a messaging tool. One where it reaches sixty has changed the way it works. Reach is the number that tells those two apart.

Divide received by sent and the answer is 61.7. That is not a coincidence sitting next to a Collaboration Index of 61. It is the same fact stated twice. Every message is counted once when it is sent and once more for each person it is delivered to, so the received figure is the fan-out of the sent figure rather than a separate body of traffic.

Which makes the honest statement of this organization's traffic 3.1 million messages sent, 192 million received, 195 million vectors through the delivery network.

The smaller number is the impressive one anyway. 3.1 million messages is what 567 people produced, an average of roughly five and a half thousand messages for every active person on the account. That is not a pilot. That is how an organization talks to itself.

In most organizations, leadership sits outside the communication and receives an account of it. Somebody attends the conversation, writes it up, and carries the write-up upward; by the time a decision comes back down, the thing it was about has moved, and the person who has to act on it is reading a summary of a summary.

In the organizations with a Collaboration Index like the one in the panel, leadership and the other stakeholders are in the Buzz environment with the people doing the work. Nothing has to be relayed, because nobody is outside the room. Reach is the measurable trace of that: a message delivered to sixty-one people is a message that did not need to be summarized for anybody.

What makes that reach possible

• Categories — a space belongs to a kind of work rather than to a person, so the right roles are in it by default instead of being remembered and invited one at a time.
• Cloning — a space that works becomes the pattern for the next one, so the hundredth episode is set up like the first rather than like whoever happened to open it.
• History for somebody newly added — a person added to a space can be given the conversation that came before, where your organization has chosen to allow it, so joining does not mean starting from nothing.
• Adding staff in bulk — a whole discipline or shift goes into a category at once, which is the difference between a policy and somebody's to-do list.

BuzzSpace is where these are described in detail, including who may set them.

BuzzInsights reports on usage rather than on content. The figures are counts and averages — messages sent, messages delivered, people active, groups and conversations in existence — and not the text of anything anybody wrote.

And the platform's access rules do not change because an administrator is looking at a chart. What a person is entitled to see inside Buzz is the same before and after this page is opened.

If your privacy officer wants the model underneath that — how message content is protected, which operations decrypt it on our servers and why, and the business associate agreement that governs all of it — it is set out in full on the security page.

Buzz security and compliance is written so that it can be quoted verbatim in a vendor risk assessment.