--- title: "PandaDoc Document Tracking: Analytics, Notifications, and the Audit Trail" description: "How PandaDoc document tracking works in 2026: statuses, recipient and per-page analytics, view notifications, auto reminders and expirations, the audit trail, and how reps should act on each signal." canonical: https://pureproposals.com/pandadoc-document-tracking-guide/ published: 2026-10-18 image: https://pureproposals.com/images/blog/pandadoc-document-tracking-guide/0.png site: Pure Proposals type: article --- # PandaDoc Document Tracking: Analytics, Notifications, and the Audit Trail > How PandaDoc document tracking works in 2026: statuses, recipient and per-page analytics, view notifications, auto reminders and expirations, the audit trail, and how reps should act on each signal. _Source of truth: https://pureproposals.com/pandadoc-document-tracking-guide/_ PandaDoc document tracking covers four layers: a status on every document (sent, viewed, completed, paid, expired, declined), recipient analytics showing who opened a proposal, how many times, and how long they spent on each page, account-level notifications that alert the sender in real time, and an exportable audit trail that records every event from creation to completion. Statuses and the audit trail are available from the Starter plan; recipient and page analytics are gated to Business and Enterprise. That is the short answer. The longer answer is that most teams use a fraction of it. They see "Viewed" in the document list, feel briefly reassured, and go back to waiting. The value of tracking is not the dashboard, it is what a rep does differently in the hour after a signal arrives, and what an admin does monthly with the patterns those signals form. This guide covers the mechanics as they stand in late 2026, verified against PandaDoc's current documentation, and then the part the documentation does not cover: how to turn each signal into a follow-up rule your team actually runs. The context is familiar if you have read anything else we publish: manual document creation was the top pain in 82 of the 129 sales calls we analysed, and one company was sending only around 5 proposals a month because creating them was so cumbersome, with the telling note that they would send more if it was easier. Tracking is the other half of that story. A proposal that took 45 to 50 minutes to build and then sits unopened for a week with nobody noticing has failed twice. ## Key takeaways - Every PandaDoc document carries a live status through its lifecycle: draft, sent, viewed, completed, plus payment, approval, expiry, and decline states. Statuses update automatically and are visible in the document list without opening anything. - Recipient analytics (Business and Enterprise) show times viewed, total time spent, last view, PDF downloads, and link clicks per recipient, plus time and views per page. Tracking stops 30 seconds after the recipient leaves the document. - Editing a sent document deletes its analytics. To keep them, duplicate the document and send the new version instead of editing in place. - Notifications are set per user under Settings and include first open, every open, completion by one or all recipients, delivery failures, comments, and suggestions. The first-open alert is the one that should trigger a same-day follow-up. - Auto reminders (Business and Enterprise) chase unsigned documents by email or SMS, up to 10 per recipient per document, and expirations put a real deadline on every proposal. Together they automate the follow-up most teams do by memory, or not at all. - The audit trail records creation, sending, views, signatures, approvals, payments, recipient changes, and status changes for every sent document, exportable as CSV, and is the record you reach for in a dispute. ## The status layer: what PandaDoc tracks on every document The foundation is the document status, which updates on its own as recipients act. A document moves from draft to sent, flips to viewed the first time a recipient opens it, and lands on completed once every recipient has finished signing. Around that spine sit the conditional states: waiting for approval and approved where an internal [approval workflow](/pandadoc-approval-workflows-setup-guide/) is in play, waiting for payment and paid where the document carries a payment block, and expired or declined when a deadline passes or a recipient refuses. Two details here are worth knowing before they surprise you. First, statuses can be changed manually, which exists for a good reason: a client who signs on paper or pays by bank transfer never triggers the automatic transition, so you mark the document completed or paid yourself to keep the record straight. A manually completed document gets no signature certificate, since nobody signed it electronically. Second, if a document includes a payment block and the client signs but does not pay, the status sits at waiting for payment rather than completed, which is exactly what you want your pipeline view to show. The status layer is available on every paid plan, updates without anyone refreshing anything, and is the single most useful column in the document list. If your team checks nothing else, it should check this: every document still showing sent after three days is a follow-up someone owes. ## Recipient and page analytics: who read what, for how long On Business and Enterprise plans, PandaDoc tracks engagement beneath the status. Open any sent, viewed, or completed document, click the three-dot menu next to a recipient, and choose Recipient analytics. Per recipient you get the number of times viewed, total time spent, the last view, whether they downloaded the PDF, and whether they clicked any links. Below that sits the page-level breakdown: time spent on each page, the percentage of total reading time it represents, how many times each page was viewed, and when it was last viewed. The measurement rules, as published: analytics stop counting 30 seconds after the recipient is no longer on the document, so an open tab left over lunch does not record an hour of reading. Page Break blocks do not split analytics into separate pages, so build genuinely distinct sections if you want distinct numbers. And for bundled documents, analytics are available per page of every document in the bundle. One caveat matters more than all the others: editing a sent document removes its existing analytics. If you need to revise a live proposal and keep the engagement history, duplicate it and send the new version rather than editing in place. There are other reasons to prefer that route too, covered in our guide to [editing after send](/pandadoc-cant-edit-after-send-workarounds/). What the numbers are for: the pricing page is the tell. A recipient who opened the proposal four times and spent most of each session on pricing is deciding, and probably comparing. A recipient who read the scope pages carefully and never reached pricing stopped for a different reason. Same status, viewed, two different follow-up calls. That distinction is invisible at the status layer and obvious one click down. ## Notifications: the signal that reaches the rep Tracking that requires someone to go looking is tracking that gets ignored. The notification layer pushes the signal out instead. Each user sets their own under Settings, and the options cover the lifecycle: an alert when a document could not be delivered, when it is opened for the first time, on every open, when one recipient completes it, when all recipients complete it, when someone comments or suggests a change, and when a document is sent on your behalf. A configuration note from the published docs that catches teams out: if the "document is completed by all recipients" notification is switched off, a user with a PandaDoc account does not receive the final PDF by email. More than one "PandaDoc stopped sending us signed copies" support thread resolves to this checkbox. Our recommended minimum for a sales team: delivery failure, first open, and completed by all recipients switched on for every rep; every-open alerts reserved for high-value deals, because on a busy pipeline they become noise and noise gets muted. The delivery-failure alert earns its place more often than anyone expects, since a proposal that bounced is otherwise indistinguishable from a proposal being ignored. ## Acting on the signals: follow-up rules that use the data The mechanics above are table stakes. The return comes from pairing each signal with a standing rule, so follow-up stops depending on whoever happens to remember. Four rules cover most of it: **First open, same day.** The first-open notification is the highest-value timing signal PandaDoc produces: the proposal is in front of the buyer right now, or was within the hour. A short, specific follow-up that day ("any questions on the rollout plan in section 2?") lands while the content is fresh. Waiting for the weekly pipeline review to notice the open wastes the signal entirely. **Sent but never viewed after 2 to 3 days.** This is not a pricing objection, it is a delivery or attention problem. Check for a delivery failure first, then chase by a different channel. The common silent failure is a proposal filtered to spam or sitting with a gatekeeper, and no amount of waiting fixes either. **Viewed repeatedly without completion.** Multiple opens across several days, especially with pricing-page concentration, means an internal conversation is happening without you. That is the moment to offer the call, add the missing decision-maker as a viewer, or send the ROI one-pager, not to send a bare "just checking in". **Signed by one recipient, stalled on another.** Per-recipient analytics tell you exactly which signer is the holdup, so the reminder goes to the right person instead of the whole thread. None of this requires software beyond what the plan already includes. It requires the rules to be written down, which is a one-page exercise, and somebody owning the monthly check that they are being followed. That ownership question, who watches the watchers, is a core part of [ongoing PandaDoc support](/pandadoc-services/pandadoc-ongoing-support/), and the monthly review loop is described in our [PandaDoc admin guide](/pandadoc-admin-guide-ongoing-management/). ## Reminders and expirations: the automated layer Manual follow-up rules still depend on humans. PandaDoc automates the baseline with two features that belong on every template. **Auto reminders** (Business and Enterprise) chase signers who have not completed the document, by email or SMS. The default workflow cadence is a reminder every 5 days after sending; you can set when the first reminder goes and how often they repeat, up to a published ceiling of 10 auto reminders per recipient per document. Manual reminders are separate, limited to once per day, and still work when auto reminders are off. Reminders go to signers only, and each sent reminder shows up in the document's activity log. The practical advice from the docs is the right one: configure reminders on the template, not per document, so every proposal created from it inherits the cadence. Set at the template level once, during [implementation](/pandadoc-implementation/), the follow-up baseline simply exists from then on. **Expirations** put a deadline on the document. Expiration is available on every plan, but only Business and Enterprise accounts can change the period; Starter and Free eSign documents are fixed at 60 days. The configurable range runs up to 3,650 days, workspace defaults can be set account-wide, and you can switch on a warning notification to signers one day before expiry. For proposals, a 30-day expiration with the warning enabled does two jobs: it creates honest urgency while the deal is live, and it stops the document list silting up with zombie proposals that will never close. An expired document can be reset if the deal revives, so the deadline costs nothing. Between them, reminders and expirations convert the follow-up rules above from "things reps should do" into "things that happen unless a rep intervenes", which is the correct default for a team where the founder is still the only person who chases reliably. ## The audit trail: tracking as evidence Everything so far serves the deal in flight. The audit trail serves the deal after the fact. For every sent document, PandaDoc records a step-by-step history: creation, sending, and completion, every view, signature, and approval, payment events, recipients added, edited, deleted, or reassigned, verification attempts and their results, and status changes including approved, rejected, declined, and expired. The record of the send even includes the text of the email the recipient was sent. You reach it from the sent document under File, and you can export the whole trail as CSV. The audit trail is on by default for Starter, Business, and Enterprise plans, and admins can toggle it per workspace. Leave it on. Its job is the conversation that starts "we never agreed to that": the trail shows when the document was sent, to which address, when it was opened, and when it was signed, with timestamps on every step. Alongside the signature certificate on electronically signed documents, it is the evidence pack for a signed agreement, and the CSV export is what you hand to a lawyer or an auditor without giving them workspace access. One connected point from earlier: a document you marked completed manually carries no signature certificate, so for anything contractual, the electronic signature path is worth insisting on. ## Honest limits Three things PandaDoc document tracking does not do, so you can plan around them rather than discover them. **No aggregate campaign analytics.** Tracking is per document. If you send 400 renewal agreements through [bulk send](/pandadoc-bulk-send-guide/), you get 400 individually tracked documents in a batch folder, not a dashboard of open rates across the batch. Rolling numbers up means the API, or a CRM report built on status writeback. **Engagement analytics are plan-gated.** On Starter you get statuses, notifications, expirations, and the audit trail, but not recipient or page analytics. For a sales team, the analytics layer is a real part of the Business plan's case, alongside the approval and reminder features. **The data is only as visible as your CRM makes it.** Reps live in the CRM, not in PandaDoc. The native integrations write document status back to the deal record, so "sent, viewed, completed" appears where the pipeline review actually happens; the [HubSpot integration](/pandadoc-integrations/hubspot/) does this well. Without that wiring, tracking data sits in a tab nobody opens, which is how teams end up paying for analytics they never act on. ## FAQ **Can recipients tell they are being tracked?** There is no banner announcing analytics. Viewing and signing events are recorded server-side as the recipient interacts with the hosted document, and the audit trail they can request shows the same events. If a client asks, the honest answer is that PandaDoc records document activity for both sides' protection, which is also the answer that sounds exactly as reasonable as it is. **Why does my document still say sent when the client swears they opened it?** Usually one of three things: the client read the PDF attachment from a forwarded email rather than opening the hosted document link, a colleague opened it from a different address, or the open happened and the status did update but the rep is looking at a stale list. Check recipient analytics for the authoritative record, and check for a delivery failure notification before assuming anything. **Does forwarding break tracking?** Activity is recorded against the recipient whose link was used. If your contact forwards their link to a colleague, the colleague's reading shows up under your contact's name. For deals with several real stakeholders, add each one as a recipient or viewer so the analytics separate them, and so the right person gets the reminder. **Can I get tracking data out of PandaDoc?** Per document, yes: the audit trail exports as CSV. Across documents, status data flows to your CRM through the native integrations, and the API exposes document status for anything custom. What you cannot do is export a cross-document analytics report from the UI, per the campaign-analytics limit above. **We have the data and nobody acts on it. What is the fix?** Ownership, not features. Write the four follow-up rules into the sales process, wire statuses into the CRM views reps already use, and give one person the monthly job of checking signals against actions. If nobody internal will reliably own that loop, that is precisely the gap an [ongoing support](/pandadoc-services/pandadoc-ongoing-support/) arrangement closes: someone accountable for the system working, not just existing.