How to Track HR Documents in Real-Time with PandaDoc: A Step-by-Step Guide

Status-chasing is the silent tax on every HR team. Offer letters sitting in someone’s inbox, onboarding agreements waiting on a counter-signature, policy acknowledgments with no confirmation they were read — every one of these is a tracking failure, not a people failure. The fix is not sending more follow-up emails. It is building a document pipeline where status surfaces automatically, escalations trigger without human intervention, and your HRIS reflects reality without anyone manually updating it.

This guide shows you exactly how to configure real-time HR document tracking with PandaDoc in six steps. It is one component of a broader HR document automation strategy — but it is the component that unlocks every other efficiency downstream. If your documents are invisible after they leave your outbox, nothing else in your pipeline can be optimized.

McKinsey research finds that employees spend roughly 28% of the workweek managing email and another 20% searching for information — much of it document-status information that should be surfaced automatically. That overhead compounds in HR where document delays directly affect time-to-hire, onboarding experience, and compliance standing.

—

Before You Start

Real-time document tracking requires the right foundations before you build. Confirm these before touching PandaDoc settings.

• PandaDoc plan: Document activity tracking and recipient notifications require PandaDoc’s Business plan or higher. API and webhook access for automation integration also requires Business tier or above. Verify your current plan before proceeding.
• Automation platform access: You need an automation platform capable of receiving webhooks and writing data to your HRIS or ATS. This guide uses generic automation platform language — confirm your platform supports webhook triggers and multi-step HTTP actions.
• HRIS/ATS write access: Your HR system must accept inbound data writes (via API or native integration) to update document status fields on employee records. Confirm this with your HRIS administrator before building.
• Document inventory: You need a current list of every HR document type your team sends — offer letters, onboarding packets, NDAs, policy acknowledgments, performance reviews. The setup process maps each type to a tracking configuration.
• Time investment: Plan two to four hours for a standard document type. Complex multi-stage approval workflows may require a full day to build and test. Do not attempt to migrate all document types simultaneously — start with one high-volume, high-risk document and expand from there.

—

Step 1 — Audit Your HR Document Types and Assign Tracking Priority

Start by cataloguing every document type your HR team sends and receives, then rank them by two criteria: compliance risk and send volume. High-risk, high-volume documents get configured first.

Build a simple spreadsheet with four columns: document type, average send volume per month, compliance consequence of a missing or delayed signature, and current status-tracking method (email thread, shared drive, manual log, or none). Fill in every row honestly. Most HR teams discover three to five document types with no tracking at all — these are your starting point.

Assign each document type to one of three tiers:

• Tier 1 — Immediate: Offer letters, employment contracts, NDAs, I-9 supporting documents. High compliance risk, high send volume, direct hiring impact.
• Tier 2 — Near-term: Onboarding packets, benefits enrollment forms, direct deposit authorizations. Moderate compliance risk, moderate volume.
• Tier 3 — Subsequent: Performance reviews, policy acknowledgments, training completion forms. Lower immediate compliance risk but important for long-term audit trail.

This prioritization prevents scope creep. Build Tier 1 tracking first, verify it works, then expand. Asana’s Anatomy of Work research consistently finds that teams that attempt to automate everything simultaneously complete significantly fewer automations than those that sequence by priority.

Once your inventory is complete, pick one Tier 1 document type and proceed to Step 2.

—

Step 2 — Build or Update PandaDoc Templates with Tracking-Ready Fields

PandaDoc can only track what is explicitly defined in your template. Vague templates produce vague tracking data. Before you configure any notifications or automations, make sure each template is tracking-ready.

Open the PandaDoc template editor for your chosen document type and confirm the following:

• Named recipient roles: Every person who needs to view, approve, or sign the document must be defined as a named role (e.g., “Candidate,” “Hiring Manager,” “HR Director”). Generic “anyone” recipients break tracking attribution.
• Required fields assigned: Every signature, date, and acknowledgment field must be assigned to a specific recipient role. Unassigned fields do not generate completion events.
• Completion rules configured: Set the document’s completion condition explicitly — typically “all required fields completed by all recipients.” This is what triggers PandaDoc’s “Completed” status event, which your automation will act on.
• Document name convention: Establish a consistent naming format (e.g., “Offer Letter — [Candidate Name] — [Date]”) so that when document names appear in your HRIS or automation logs, they are immediately identifiable without opening the document.

For automated offer letters specifically, also confirm that merge fields (candidate name, role, salary, start date) are pulling from a data source rather than being typed manually. Manual field entry is where transcription errors enter the pipeline — and those errors have downstream payroll consequences.

Save and test the template by sending a test document to yourself in each recipient role. Confirm that every required field triggers a completion event in PandaDoc’s activity feed before moving forward.

—

Step 3 — Configure PandaDoc Notification Rules and Reminder Schedules

Notifications are the first layer of real-time tracking — they push status information to people rather than requiring anyone to pull it. Configure these at the document level, not globally, so each document type gets behavior appropriate to its urgency.

In PandaDoc’s notification settings, configure the following for each Tier 1 document type:

Sender notifications (HR team)

• Document opened by recipient — immediate alert
• Document completed — immediate alert
• Document declined — immediate alert
• Document not opened after [X] hours — alert (set threshold based on document urgency; 24 hours for offer letters is a reasonable starting point)

Recipient reminders

• Initial reminder: 48 hours after send if unsigned
• Second reminder: 96 hours after send if unsigned
• Final reminder: 120 hours after send with escalation language in the email

Customize the reminder email copy for each document type. A reminder for a candidate offer letter should read differently than a reminder for an internal policy acknowledgment. PandaDoc allows custom email body text per document — use it. Generic reminder emails get ignored; contextually appropriate ones get action.

This notification layer handles the majority of follow-up volume without any automation platform involvement. Most documents will complete before they ever trigger an escalation. For the ones that do not, Step 5 covers automated escalation logic.

—

Step 4 — Connect PandaDoc to Your HRIS or ATS via Webhook Automation

Notifications tell people what happened. Webhooks tell your systems. This step is where real-time tracking moves from visibility to operational infrastructure — and where integrating your ATS with PandaDoc delivers its full value.

PandaDoc fires webhook events for every major document status change: document sent, document viewed, document completed, document declined, and others. Your automation platform listens for these events and routes the data to the appropriate system.

Build the following automation scenario in your automation platform:

1. Trigger: PandaDoc webhook — document status changed
2. Filter: Document name contains your naming convention identifier (e.g., “Offer Letter”) to route only the relevant document type
3. Action 1: Parse the webhook payload to extract document ID, recipient name, status, and timestamp
4. Action 2: Look up the matching employee record in your HRIS using the candidate name or a shared identifier (email address works reliably)
5. Action 3: Update the document status field on the employee record with the current status and timestamp
6. Action 4 (optional): Post a notification to your team’s communication channel (e.g., a hiring channel) confirming the status update

The result: the moment a candidate signs an offer letter, your HRIS shows “Offer Letter — Signed — [timestamp]” on their record, your recruiter gets a channel notification, and the next workflow step (onboarding packet send, background check trigger, etc.) can fire automatically without anyone manually advancing the process.

Parseur’s Manual Data Entry Report puts the average fully-loaded cost of an employee performing manual data entry at $28,500 per year. Every automated status write eliminates a manual update — those minutes aggregate into meaningful hours across a full hiring cycle. For context on broader error costs, see our analysis of error-proofing HR documents.

—

Step 5 — Build Escalation Logic for Stalled Documents

Even with automated reminders, some documents will stall. The question is whether those stalls are invisible (the current state for most HR teams) or surfaced automatically. This step makes them visible and actionable without human monitoring.

Build a second automation scenario — separate from your status-sync scenario — specifically for escalation:

1. Trigger: Scheduled — run every morning at 7:00 AM
2. Action 1: Query PandaDoc’s API for all documents with status “Sent” (not yet completed)
3. Filter: Return only documents where the “sent” timestamp is older than your defined escalation threshold (e.g., 72 hours for offer letters, 5 business days for policy acknowledgments)
4. Action 2: For each stalled document, look up the assigned HR owner from your HRIS
5. Action 3: Send an escalation alert to the HR owner AND their manager with the document name, recipient, days outstanding, and a direct link to the document in PandaDoc
6. Action 4 (optional): Create a task in your project management system assigned to the HR owner with a due date and the escalation context

This scenario runs passively every day. Most days, no documents meet the escalation threshold and nothing fires. On the days a document has genuinely stalled, the right people are notified automatically — before the stall becomes a compliance issue or a candidate experience failure.

SHRM research indicates the cost of an unfilled position can reach $4,129 per month in productivity loss. A stalled offer letter that causes a candidate to accept a competing offer is not an administrative inconvenience — it is a measurable business loss. Escalation automation converts that risk into a manageable operational signal.

—

Step 6 — Verify, Audit, and Optimize Using PandaDoc Analytics

Setup is only complete when you can confirm the system works without manual intervention. This step defines what verification looks like and how to use PandaDoc’s analytics for ongoing optimization.

Verification checklist

• Send a test document to a real recipient (or yourself in a test account) and confirm the “sent” event updates the employee record in your HRIS within two minutes.
• Open the document without signing and confirm the “viewed” event fires and is logged.
• Complete the document and confirm the “completed” status writes to the HRIS record with the correct timestamp.
• Manually trigger a stalled-document scenario (set the escalation threshold to one hour for testing purposes) and confirm the escalation alert fires to the correct recipient.
• Check that PandaDoc’s activity feed, your HRIS record, and your automation platform’s run log all show consistent, matching data for the same document events.

If every item on this checklist passes without you manually touching anything between trigger and outcome, the setup is working. If any item fails, isolate the failure to the specific step in the automation scenario — do not rebuild from scratch.

Ongoing optimization with PandaDoc analytics

After your first 30 days of live operation, pull PandaDoc’s document analytics for your Tier 1 document types. Look specifically for:

• Average time-to-completion by document type: Is your offer letter completing faster than before? If not, the bottleneck is not in the tracking — it is in the process upstream.
• Stage-level time data: Which recipient role takes the longest to act? If candidates complete quickly but hiring managers are slow, the bottleneck is internal approval — a process problem, not a document problem.
• Decline rate: Documents that are declined frequently need content review. High decline rates on NDAs often signal language concerns. High decline rates on offer letters signal a process breakdown between verbal offer and written offer.

This data is what converts document tracking from an administrative tool into a strategic one. Gartner research consistently identifies process analytics as a primary driver of HR technology ROI — not the technology itself, but the decisions made using the data it surfaces. For a full ROI framework, see our analysis of the ROI of HR document automation.

—

How to Know It Worked

Real-time document tracking is working when the following three conditions are true simultaneously:

1. No one on your HR team is sending manual status-check emails for tracked document types. If they are, the notification configuration is incomplete or the automation is not surfacing status in the right place.
2. Your HRIS shows current document status on every employee record without anyone manually updating it. The webhook-to-HRIS sync is the operational test. If the HRIS is accurate and current, the automation is running correctly.
3. Stalled documents generate escalation alerts before anyone notices the stall manually. If your team is still discovering stalled documents by accident, the escalation scenario is not configured or is not triggering at the right threshold.

All three conditions must be true. One or two out of three means the pipeline has gaps.

—

Common Mistakes to Avoid

Treating tracking as a reporting tool instead of an operational trigger

The most common configuration mistake is building a beautiful PandaDoc dashboard and then continuing to act on it manually. Tracking data should trigger automated actions — status syncs, escalations, next-step workflow launches — not just inform human decisions. Passive visibility is a start. Automated response is the goal.

Using generic recipient names in templates

Templates with unnamed or generic recipient roles (“Signer 1,” “Approver”) produce ambiguous tracking data. When a document stalls, you cannot tell which role is responsible. Named roles — tied to actual job functions — make every tracking event attributable and actionable.

Setting escalation thresholds too conservatively

Escalation alerts that fire after 24 hours will generate noise for normal documents. Alerts that fire after 10 business days will miss genuine compliance failures. Calibrate thresholds by document type and urgency — and plan to adjust them after your first 30 days of data.

Skipping the verification step

Automations that are built but not tested often have silent failure modes — the scenario runs, no error fires, but the data does not write correctly to the HRIS. The verification checklist in Step 6 is not optional. Run it on every new document type you add to the tracking pipeline.

—

Expand the Foundation

Once Tier 1 document tracking is running reliably, the expansion path is straightforward. Apply the same six-step process to Tier 2 and Tier 3 document types. Then layer in more sophisticated capabilities: automated compliance documentation with version-controlled templates, self-service HR document access portals that surface real-time status to employees directly, and cross-system analytics that correlate document completion times with onboarding outcomes.

The six steps in this guide are the foundation. Every HR document automation capability — conditional logic, multi-party approval routing, AI-assisted review flagging — performs better when the underlying tracking infrastructure is solid. Build the tracking layer first. Everything else builds on top of it.

For the complete framework connecting document tracking to your broader automation strategy, return to the HR document automation strategy guide.