Did Your Client Read the Report? Page-by-Page Tracking for Consulting Deliverables

First: this is not BI report usage

If you searched for report tracking and landed on Power BI usage metrics or a ServiceNow dashboard, that is a different problem. Those tools measure how often people open adashboard you host. This page is about the other kind of report — the PDF deliverable a consultant writes, sends once, and then wonders about: the findings deck, the audit, the strategy document, the post-engagement write-up. Different artefact, different question, different tooling.

Delivered is not read

A proposal and a deliverable fail in opposite directions. A proposal that goes unread simply loses you the work, and you find out when nobody replies. A report that goes unread still gets paid for — and you find out six weeks later, in a meeting, when someone asks a question the report answered on page 14.

That is the practical reason to track a deliverable: not suspicion, but evidence for the next conversation. Knowing that your sponsor read the recommendations section twice and never opened the appendix changes how you run the readout. Knowing that nobody opened it at all changes whether you send a summary before the meeting or after it.

Delivery as an attachment forecloses all of this — an emailed file leaves your control the moment it is sent, and nothing about it is observable afterwards. That constraint is the same for every document type, and we cover the mechanics of it in how to know who opened your PDF. For a deliverable the fix is the same: host it, share a link, send the link.

Did it circulate past your sponsor?

This is the question that separates a deliverable from a proposal, and almost nothing is written about it. A proposal goes to one buyer. A report gets forwarded — to a steering committee, to a finance lead who was not in the kickoff, to the executive who signs the next statement of work. Circulation is the signal that the engagement landed.

A tracked link makes circulation visible in a way an attachment never can. Distinct reading sessions from different devices and locations tell you the document moved. If you turn on the email gate, each session carries the address the reader entered, so forwarding shows up as new names rather than anonymous sessions. That is the difference between “the report was opened eleven times” and “four people read it, and two of them were not on the distribution list.”

What the numbers mean for a long report

Reading metrics were mostly designed for short documents, and a 60-page deliverable breaks the intuition behind them. Three figures from our own data are worth recalibrating against.

The median reading session runs 45.7 seconds, with a 90th percentile of 5.8 minutes. On a six-page proposal, 45 seconds is a skim. On a sixty-page report it is a glance at the summary and nothing else — and that is the typical case, not the failure case. The median time on a single page is 3.1 seconds (90th percentile 38 seconds), which is long enough to decide whether a page is worth reading and not long enough to have read it. Judge a deliverable by the pages that hold a reader past the 38 second mark, not by page count reached.

The drop-off curve then does the rest of the work: 65.6% of readers reach page two, 55.0% reach page four, and 37.8% are still there at page ten. If your recommendations sit at page 30, the curve is telling you something about document structure rather than about your client. What each of these metrics does and does not prove is covered in what page-by-page reading data tells you.

Tools compared, for this job

Most comparisons of these tools rank them on price and free-plan volume. For a delivered report the axis that matters is different: can you tell readers apart, does the history survive long enough to matter, and does the tool keep every view or only the recent ones? A consulting engagement has a long tail — the question “did anyone go back to the report before renewal?” is asked months later.

Read that table for the job rather than as a scoreboard. For a single delivered report tracked across a long engagement, PDFTrackr is the straightforward pick — 12 months of history against everyone else's 30 days, every view kept rather than a rolling window, and automated opens excluded from the counts, which matters more here than almost anywhere else (see below). The honest exceptions are specific and real: Papermark and Peony both send real-time open alerts on their free plans, and PDFTrackr's free tier sends a daily digest instead — if you want a notification the moment the client opens the file, without paying, they do that and we do not. If your engagement runs on paid tooling already, DocSend and Digify are deeper products with correspondingly deeper pricing.

The automated-opens column deserves a note, because it is the one place this category is quietly broken. Corporate mail security opens links before the human does. Microsoft's own documentation for Safe Links states that URLs are:

“scanned prior to message delivery”— Microsoft Learn, Safe Links in Microsoft Defender for Office 365

So the first open on a delivered report is frequently a mail server, not your client. Industry measurement puts automated traffic above half of all web requests, and vendors know it — Qwilr's own help documentation states plainly that it cannot suppress scanner opens from its notifications. In our own unfiltered production data, roughly one recorded view in seven is not a real reader. On a report sent to one client, a handful of phantom opens is not a rounding error — it is the difference between “they read it” and “their mail server did.”

What deliverable tracking can't tell you

It cannot tell you whether the report was understood, whether the recommendation was accepted, or whether the person reading was the decision-maker. Reading time measures attention, not comprehension — a page held open during a phone call reads identically to a page studied closely.

There is also a structural limit worth naming plainly, because it bites hardest on exactly this use case. PDFTrackr tracks one file per link and has no grouping above a single document — no folders, no rooms, no bundles. A consulting deliverable is often a set: the report, the appendix, the model, the slide summary. Today you would share those as separate tracked links and read their analytics separately. If your engagement genuinely needs a single room with one set of aggregate numbers across a bundle, a data-room product is the right tool and this is not one.

How to set it up (free)

1. Upload the finished report and create a share link. The viewer that renders it is what can observe which page is on screen.
2. Turn on the email gate before you send it. This is what makes circulation legible later — without it, a forwarded copy is an anonymous session.
3. Send the link in place of the file, and do not also attach the PDF. Any reading of an attached copy is invisible, which quietly defeats the whole exercise.
4. Read it before the readout, not after. Check which sections held attention and who has opened it, then structure the meeting around what was skipped.

Keep reading: how to know who opened your PDF, what page-by-page reading data tells you, and why one in seven PDF views is not a real reader.