You Sent a Report to Nine People. How Do You Find Out Who Read It?

A proposal has one reader and one question: did they look at it. A report — a monthly summary, a project status, a findings document, a handover — has an audience, and the question is different in kind. It is not “was it read”, it is “who of the nine has not read it”, and that is a much harder thing to answer.

Harder, and answerable, but only if you set it up before you send. Almost everything that goes wrong here is decided at the moment of sharing, not at the moment of reading.

The mistake that makes the question unanswerable

One link, pasted into one email, sent to nine addresses. Every visit that follows is a visit to the same link, and nothing in it distinguishes one recipient from another.

You might expect the addresses on the email to help. They do not, and it is important to understand why rather than to assume it is a limitation. The address a link was mailed to is a fact about your mailing list, not about your reader — a link forwards, and the moment one does, that address describes somebody who may never have opened the document. So it is never treated as an identity: an unidentified visit on a link you mailed shows as “someone with the link sent to …” rather than being printed as that person’s name.

It reads as clumsier copy. It is the truthful version, and on a nine-recipient report the difference is not cosmetic — a tool that guessed names here would hand you a list of nine attendance records that were never observed.

The setup that answers the question

1. One link per recipient. Nine shares rather than one. This is the whole trick, and it costs a couple of minutes. Each link is now a channel with one name on it, and a visit to it is attributable — with the standing caveat that any of the nine may have forwarded theirs.

2. Signed-in access where the stakes justify it. A reader who is signed in when they open a document is the only case that constitutes proof of who read it. It is friction, and for a board pack or a regulated handover it is friction worth having.

3. An email gate on links you cannot address. For the copy that goes into a channel, or to a distribution list you do not control, a gate asks for an address before the document opens. Nobody verifies it, so it is labelled self-reported wherever it appears — evidence of intent, not of identity. Whether the friction is worth it depends on the send.

Reading coverage rather than engagement

With per-recipient links, the useful view flips. For a proposal you study the reading — how long, how often. For a report you mostly study the gaps.

• Who has not opened it at all. This is the actionable list, and it is almost always shorter than people fear and different from who they guessed.

• Whether the people it was written for are in that list. A report read by everybody except the one person whose decision it was meant to inform has failed, even at eight out of nine.

• Whether anyone came back. On a report, a return visit usually means the document is being used rather than consumed — someone is checking a figure in it. That is the highest compliment a report gets.

• Whether new readers appeared. A recipient count of nine and a reader count that will not stop climbing means it is circulating further than you sent it, which for a report is often the point.

If the extra readers arrived together rather than gradually, that is its own pattern — a burst of opens and what it means covers reading it.

Two ceilings to know about before you rely on this

The first is arithmetic. The reader count is a floor rather than a total — “≥ 7” rather than “7” — because a reader who blocks cookies looks new on each visit. On a nine-person report that means your count can exceed your recipient list without anyone having forwarded anything, and it should not be read as spread on its own.

The second is a plan limit and it bites specifically on documents with a large audience. On the free plan, reader identity is withheld rather than blurred: the first three readers of each document are shown, up to twenty people in total across the workspace, and once you have seen someone they never lock again. For a nine-recipient report that is the first three and then a wall. What each plan includes sets out where that line sits.

If the report is internal as well as external

Reports frequently go to your own team and to a client in the same breath. Reads by you and by active members of your workspace are marked and kept out of the client-facing numbers, and reported separately as a count with no names — so “nobody has read it” never means “nobody except the four of us”.

That separation has edges worth knowing, particularly around personal devices — what your own opens do to your data has them.

What you must not conclude

• Not “seven of nine read it” from a single shared link. Without per-recipient links you have seven visits and no attendance record.

• Not “she read it” from an address the link was mailed to. That is a fact about your email, not about your reader.

• Not “he has not read it” from a per-recipient link that stayed quiet. Somebody may have forwarded him theirs, and the copy he read is not the copy with his name on it.

The honest summary of a group send is usually two sentences: this many links were opened, by at least this many people, and these three were not opened at all. The third sentence is the one worth acting on.