--- title: "PandaDoc Reporting: The Workspace Numbers That Show Whether Your Proposal System Works" description: "How PandaDoc reporting works in 2026: the Reports views (workflow overview, documents overview, data analytics, content library usage), which numbers to review monthly, the counting rules that skew readings, and how to pair it with CRM reporting." canonical: https://pureproposals.com/pandadoc-reporting-analytics-guide/ published: 2026-10-28 image: https://pureproposals.com/images/blog/pandadoc-reporting-analytics-guide/0.png site: Pure Proposals type: article --- # PandaDoc Reporting: The Workspace Numbers That Show Whether Your Proposal System Works > How PandaDoc reporting works in 2026: the Reports views (workflow overview, documents overview, data analytics, content library usage), which numbers to review monthly, the counting rules that skew readings, and how to pair it with CRM reporting. _Source of truth: https://pureproposals.com/pandadoc-reporting-analytics-guide/_ PandaDoc reporting lives under Reports in the left panel on Business and Enterprise plans, and it aggregates every document in your account into five views: Workflow overview (the created, sent, completed funnel with close rate and transition times), Documents overview (status tiles with counts and total value), Data analytics (a customisable table with saved reports and CSV export), Content library usage, and Document data custom reports. Data reaches back up to 4 years, and access is limited to account owners plus Admin, Manager, or custom roles with reporting permission. That is where the reports are. What most teams are missing is not the dashboard, it is a reason to open it. Document-level tracking answers "did this client read my proposal", and we covered it in the [document tracking guide](/pandadoc-document-tracking-guide/). Reporting answers a different question: is the proposal system itself working? How long does it take your team to get a document out the door, what share of sent proposals complete, which templates earn their keep, and whether this month was better than last. Those are the numbers an owner reviews monthly, and this guide covers what each view shows, verified against PandaDoc's current documentation in October 2026, plus the counting rules that quietly skew readings if you do not know them. The stakes are familiar from our own research: 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, noting they would send more if it was easier. That is a reporting finding before it is a tooling finding. A team that never looks at time-to-send or monthly volume cannot see that cap, which is exactly why reporting review belongs in the standing admin routine. ## Key takeaways - PandaDoc reporting is available on Business and Enterprise plans, under Reports in the left panel. Account owners, Admins, Managers, and custom roles with reporting permission can see it; a Manager sees only the workspaces where they hold that role. - Workflow overview charts the funnel: created, sent, and completed document counts, movement between those stages as percentages with a close rate, and median status transition times. Documents are counted by creation date, not send or completion date. - Documents overview shows one tile per status, from Draft through Completed, Paid, Expired, and Declined, each with a count and total value, filterable by team member. This view is capped at one year of history. - Data analytics is the working layer: a table you can group by workspace, document creator, template, or document name, with default Leaderboard, Document efficiency, and Template efficiency reports, your own saved reports, and full CSV export. - Four counting rules matter when reading the numbers: bundles count as one document, manually changed statuses record only the first and last status, time metrics are medians, and Documents overview totals values only in the default workspace currency. - Reporting shows document health, not revenue attribution. Pair it with CRM reporting built on status writeback for pipeline numbers that reps and managers already look at. ## Reporting and tracking are different layers It is worth being precise about the boundary, because PandaDoc has two features that both get called "analytics". Recipient and page analytics sit on an individual document: who opened it, how many times, how long they spent on each page. They answer a rep's question about one deal, and the [document tracking guide](/pandadoc-document-tracking-guide/) covers them along with notifications, reminders, and the audit trail. Reporting sits above all of that. It does not care whether one client read page four; it cares that 60 documents were created last month, 48 were sent, 31 completed, and the median document took two days to go out. Tracking is a rep tool with a same-day horizon. Reporting is a manager tool with a monthly horizon. ## Workflow overview: the funnel and the close rate Workflow overview is the first tab and the one that answers "is this working" fastest. It charts your document funnel over a selected time period and set of workspaces, defaulting to the last month across all workspaces. Four charts make up the view. Document progress plots created, sent, and completed document counts over the range as three lines, which is where a volume cap shows up at a glance: a created line far above the completed line is a system leaking proposals somewhere between draft and signature. Total document progress turns the same data into percentages, movement from created to sent to completed, and gives you a close rate. Status transition time shows the median time documents spend moving between statuses, by day, week, or month. Total status transition time summarises the two halves of that journey: how long your team takes to prepare and send a document, and how long recipients take to complete it. That last split separates the two problems teams habitually blur. Time-to-send is your problem: templates, approvals, and how documents get built. Time-to-complete is the deal's problem: recipient urgency, follow-up discipline, deadlines. If proposals take four days to leave the building, the fix lives in [implementation](/pandadoc-implementation/) work, not in sales coaching. One counting rule governs the whole tab: documents appear in these charts based on when they were created, regardless of when they were sent or completed. A document created in September and signed in October counts in September's funnel. Comparing months is still valid; just know which month owns each document. ## Documents overview: pipeline at a glance The Documents overview tab shows a tile for each document status: Draft, For approval, Sent, Viewed, Suggest edits, Completed, Waiting for payment, Paid, Expired, and Declined. Each tile carries a count and the total value of documents in that status, and managers and admins can filter the view by team member. Time ranges run from 1 week to 1 year, and a year is the cap on this tab. Read it as a stock check rather than a flow chart. A healthy system has documents distributed down the funnel; a stuck system shows a pile-up. Twenty documents sitting in Draft is a creation bottleneck. A fat Sent tile with a thin Viewed tile is a delivery or follow-up problem, and the per-document signals for chasing those live in the tracking layer. A crowd in For approval means the approval design is gating routine deals instead of exceptions. The value figures come with a caveat: tiles total value only in the default workspace currency, so multi-currency workspaces should treat the sums as directional rather than bookkeeping. ## Data analytics: the table you will actually work in Data analytics is the most useful tab for a monthly review because it is a real table rather than a chart. You can group rows by workspace, document creator, template, or document name, base the report on created, sent, or completed documents, filter by custom date range, choose your columns, save the result as a named report, and export the full table as CSV, with dates in UTC+0 and timing metrics in seconds. Three default saved reports ship with it and cannot be renamed or deleted: Leaderboard, Document efficiency, and Template efficiency. The metric set behind them is substantial: created, sent, viewed, completed, expired, and paid counts, send rate, completion rate, decline rate, expired rate, template rate (the share of created documents built from templates), time to send, time to view, viewed-to-completed, time to complete, and document value. All the time metrics are medians, which is the right choice: one proposal that sat for a quarter does not drag the average. Two of those metrics are underrated diagnostics. Template rate tells you whether the [template architecture](/pandadoc-services/pandadoc-templates/) you built is actually being used or whether reps are still duplicating old documents, which is how brand drift and stale pricing creep back in. And grouping by template turns Template efficiency into a portfolio review: a template with many creations and a weak completion rate is earning its traffic but losing its deals, which usually points at content or pricing rather than process. A word on the Leaderboard: grouping by document creator makes rep-level numbers visible, and the temptation is to read it as a ranking. Treat it as coaching data instead. A rep with a slow time-to-send is usually fighting the system, rebuilding documents by hand or waiting on approvals, and the fix is structural. The report shows who to talk to, not who to blame. ## Content library usage and custom document data Two smaller tabs round out the module. Content library shows how often each library item is used in documents: title, times used, percentage of usage, and creator. Unlike the other tabs it covers only the current workspace. It is the pruning tool for the quarterly cleanup in the [admin routine](/pandadoc-admin-guide-ongoing-management/): items with real usage earn maintenance, items nobody has touched in a year are candidates for retirement before they go stale in a live proposal. Document data lets you build custom reports from document data fields, pick columns and filters, save them, and export CSV. PandaDoc notes this one is being released gradually, so it may not be in your account yet. ## The monthly review: five numbers worth a standing look The failure mode with reporting is not misreading it, it is never opening it. The fix is the same one that works for every governance habit: a short, fixed checklist on a calendar. Our [admin guide](/pandadoc-admin-guide-ongoing-management/) puts a monthly health check at the centre of the role, and reporting is the evidence half of that check. Five numbers cover it: 1. **Created, sent, and completed counts vs last month.** Volume trends are the earliest signal that something changed: a new hire, a broken template, a stalled quarter. 2. **Close rate.** The percentage of sent documents that complete. Movement here matters more than the absolute number, which varies by industry and deal size. 3. **Median time to send.** The purest measure of whether the system is doing its job. If your team still takes most of an hour to get a proposal out, you are paying the 45-to-50-minutes-per-proposal tax that came up again and again in our call data, just with better software underneath it. 4. **Template rate.** Falling template rate means the system is being bypassed, and everything downstream of it, branding, pricing accuracy, reporting itself, degrades quietly. 5. **Expired and declined counts.** A rising expired count is a follow-up discipline problem, and the reminder automation in the tracking layer is usually the cheapest fix. Fifteen minutes, once a month, written down. The point is not the dashboard; it is the one structural fix per month the dashboard points at. ## Counting rules that skew readings Four mechanics are worth knowing before you present these numbers to anyone: - **Bundles count once.** Bundled documents are counted as a single document in reporting, so bundle-heavy teams undercount raw volume. - **Manual status changes flatten history.** If a document's status was changed by hand, say marking a paper-signed contract completed, only the first and last statuses are counted in charts and the analytics table. The transition times in between are not real for that document. - **Date basis changes totals.** A report based on created documents excludes anything created before the range, even if it was sent or completed inside it. If a total looks low, check which date basis the report is on. - **Currency differs by view.** Document value in the Data analytics table uses each document's own currency settings, while the Documents overview tiles total in the default workspace currency. The two views can legitimately disagree. None of these are flaws, but each one has a way of surfacing in the middle of a management meeting if you have not met it before. ## Pair it with CRM reporting for revenue numbers PandaDoc reporting measures documents. It does not measure revenue attribution, pipeline conversion by source, or anything else that lives in the deal record, and it should not: reps and managers run their week from the CRM, not from a documents tool. The join between the two is status writeback. The native [HubSpot integration](/pandadoc-integrations/hubspot/) writes document status back to the deal, which means your CRM reports can answer "what happens to deals after a proposal goes out" while PandaDoc reporting answers "how well does the proposal machine itself run". In practice the split looks like this: monthly system health in PandaDoc Reports, deal and revenue reporting in the CRM, and the document statuses flowing between them so neither side is typing numbers by hand. If that wiring does not exist yet, it is a small piece of [implementation](/pandadoc-implementation/) work with an outsized reporting payoff, because it puts document data where people already look. ## Honest limits Three things PandaDoc reporting does not do. It does not aggregate send batches as campaigns: a bulk send produces individually counted documents, not an open-rate dashboard for the batch, consistent with what we noted in the tracking guide. It is plan-gated: Starter accounts get document statuses and the audit trail but no Reports module, which makes reporting a genuine part of the Business plan's case for any team that wants to manage the function rather than just use it. And it reaches back 4 years at most, with the Documents overview capped at one year, so long-baseline analysis means exporting CSVs on a schedule and keeping them. If nobody in your team owns this review, that is the gap to fix first. It is the kind of standing responsibility that our [ongoing PandaDoc support](/pandadoc-services/pandadoc-ongoing-support/) retainers exist to carry: we run the monthly numbers, flag what moved, and make the one fix the data points at, so the system keeps earning its licence fee instead of quietly drifting. ## FAQ **Which PandaDoc plans include reporting?** Business and Enterprise. The Reports section appears in the left panel, and the data behind it covers up to the past 4 years. Starter plans get per-document statuses, notifications, and the audit trail, but not the aggregate Reports module. **Who can see reports?** Account owners, and users with an Admin, Manager, or custom role that includes reporting permission. Access follows workspace roles: a user who is a Manager in one workspace and a Member in another sees reporting data only from the workspace where they are a Manager. **Can I export PandaDoc reporting data?** Yes. The Data analytics tab exports a full CSV including workspace, user, document and template names, recipients, status, date fields in UTC+0, document values, and timing metrics in seconds. Custom Document data reports export CSV as well. The chart visualisations themselves are not exportable, so screenshots or the CSV are the route into a slide deck. **What is the difference between reporting and recipient analytics?** Recipient analytics sit on a single document and show who viewed it, how often, and for how long: a rep's follow-up signal. Reporting aggregates all documents into funnel counts, rates, and median times: a manager's system-health view. They are separate features, and recipient analytics are covered in our document tracking guide. **Why do my report totals look lower than the documents I can see?** Usually one of the counting rules: the report's date basis excludes documents created outside the range, bundles count as one document, or a manually changed status skipped the intermediate states a chart is counting. Check the date basis first; it explains most surprises.