What I would ask someone who reached the last page
A PDF’s last-page marker can feel like proof that a document landed. An imagined design review asks which questions should come after that observation.
Start with the table at the end
Imagine sending a PDF before a design review. Background comes first, an architecture diagram sits in the middle, and a table of review items closes the document.
The recipient opens the final table first. They want to know what must be decided today, then return to the diagram.
The sender’s dashboard records a visit to the last page. Interpret that as ‘they read everything’ and the two people arrive at the meeting with different assumptions.
PDF to Link’s introduction describes reading sessions, page reach and active time. Its distinction between reaching the last page and completing a read caught my attention.
Reaching the end is useful information. The route the reader took to get there is still unknown.
A page left open
Now suppose the imaginary recipient spends a long time on the diagram. They might be struggling with missing explanation. They might be comparing it with another document.
It would be pleasant to assume focused reading. I would hesitate to store that interpretation as though it were the observation itself.
Time since opening can include time spent in other tabs. The product page describes active time while the document is visible and focused.
MDN’s Page Visibility API describes a document becoming visible or hidden. Knowing a tab’s state is different from knowing whether a person understood its content.
In this example, visible time can be a more specific observation. It still does not reveal which arrow the reader understood or which assumption they accepted.
Exit records can have gaps too. PDF to Link explains that some exits cannot be detected and presents unknown exit locations separately.
Assign those gaps to either first-page departures or completed reads without evidence and we have added information the record never contained.
Questions for the meeting
If I were writing this hypothetical document, concentrated time on the middle diagram would make it a candidate for investigation. I would use it as a reason to ask where explanation is needed, before declaring that the page is difficult.
‘What did you look at first in the diagram?’ could produce an answer: ‘I was trying to find out what the arrow between the systems means.’ The long visit now has a more particular interpretation.
Or the reader might have found the diagram especially useful and been making meeting notes from it. The same trace needs a conversation to distinguish those possibilities.
I would treat the last-page marker similarly. It can suggest that the review items were encountered, without standing in for a reply agreeing to them.
Confirming that a file was sent, observing that it opened and checking that its explanation was understood each lead to different next actions. Naming an earlier trace as the later confirmation can end the questions too soon.
I would like the dashboard to act more like a note helping me choose the next question than a person answering on the recipient’s behalf.
The meeting begins. The author knows a last-page visit was recorded.
I would still avoid opening with ‘You read everything, right?’
‘Which page should we look at together first?’