PandaDoc Renewals: How to Track, Remind and Re-Sign Agreements Before They Lapse

PandaDoc handles renewals through its Agreement Renewals feature: you set a renewal date on a document or template, PandaDoc emails the document owner a set number of days before that date, and every agreement with an approaching date shows up in an Upcoming renewals tab in your document list. What PandaDoc does not do is renew anything automatically: the alert is the trigger, and creating the renewal document, with current pricing and a fresh signature, is a workflow you have to design.

That second half is where renewals actually go wrong. Most teams that lose a renewal did not forget the date; they scrambled the week it landed, duplicated last year’s document, and sent out stale pricing or copy that had been fixed everywhere else months earlier. This guide covers both halves: the mechanics PandaDoc gives you (renewal dates, notifications, the renewals tab, AI date extraction, all verified against support.pandadoc.com in November 2026) and the renewal workflow that the feature deliberately leaves to you.

Key takeaways

• Agreement Renewals lets you set a renewal date on any document, or a renewal rule on a template that every document created from it inherits, and emails an alert a chosen number of days before the date
• Renewal alerts are internal only: the document owner gets the email, recipients and signers are never notified, so client-facing renewal communication is still your job
• Manual renewal dates are available on Starter, Business and Enterprise plans (rolling out gradually); AI-extracted renewal dates are Enterprise, or a $20 per seat per month add-on on Business
• The Upcoming renewals tab in the document list shows everything with an approaching date and filters by date range, status, owner and counterparty
• PandaDoc never auto-creates or auto-sends the renewal document: build that step deliberately, by regenerating from the current template rather than duplicating last year’s document, so renewals never carry stale pricing or outdated terms

What Agreement Renewals does, and what it leaves to you

Agreement Renewals is an extension, so if you do not see renewal options the account owner needs to enable it under Extensions first; some newer accounts have it on by default, and accounts with multiple workspaces choose which workspaces get it. Once it is on, three things exist that did not before: a Renewal setting on documents and templates, renewal notification emails, and the Upcoming renewals tab.

It helps to be precise about the boundary. PandaDoc will track the date and tell you it is coming. It will not draft the renewal agreement, notify your client, update the pricing, or chase the signature. In PandaDoc’s own framing, renewal notifications are internal only. That boundary is sensible, because renewal terms usually change, but it means the feature is a reminder system, not a renewal system. The workflow sections later in this guide are about closing that gap.

One vocabulary note: PandaDoc calls these agreement renewals, and the obvious use case is contracts. If contracts are your main document type, our guide to running contract management in PandaDoc covers the wider lifecycle this feature slots into. But the feature is just as useful for retainer proposals, annual service agreements and support plans: anything with a term and a lapse date.

Setting renewal dates on documents and templates

There are two places to set a renewal, and choosing the right one is most of the setup.

On a template, open the template in edit mode and go to File, then Template, then Renewal. Templates offer two options: Not set, or After document completion, which sets the renewal date a fixed number of months after each document created from the template is completed. Every document generated from that template inherits the rule. This is the right home for anything with a standard term: a 12-month retainer template gets a 12-month renewal rule once, and every retainer you send afterwards is tracked without anyone remembering to do it.

On a document, open it in edit mode and go to File, then Document, then Renewal. Documents get more options than templates: Not set, After document completion, On specific date (a date picker, for agreements whose end date was negotiated rather than standard), and Auto-set date where AI extraction is available. You can also set this at send time: in the Configure delivery and settings step, open the Renewal tab under Document settings, toggle renewals on, pick the date option and the notification lead time, and select Done.

A specific calendar date can only be set on an individual document, not on a template, which is the correct constraint: templates carry rules, documents carry facts.

For the notification itself, you choose how many days before the renewal date the alert email goes out. Pick a lead time that matches how long your renewal conversation actually takes, not how long you wish it took. If repricing a retainer takes a call, an internal approval and a round of edits, a 7-day alert guarantees a rushed renewal; 30 to 60 days is the practical floor for anything with negotiated terms.

AI-extracted renewal dates for uploaded contracts

Documents built in PandaDoc know their own completion date, so After document completion works cleanly. Contracts signed elsewhere and uploaded, or legacy agreements imported during a migration, do not, and someone would normally have to read each one and key the date in. AI Data Extraction closes that gap: with both Agreement Renewals and AI Data Extraction active, PandaDoc reads the uploaded contract and sets the renewal date itself, enabling the alert automatically.

The extraction follows a first-match rule set worth knowing before you trust it: an explicit expiration date is used directly; failing that, an agreement date plus an initial term length; failing that, a term length alone counted from the document’s completion date. If the contract contains only an agreement date, with no expiration or term, no date is set and you fall back to setting it manually.

Plan-wise this is the premium half of the feature: AI renewal dates are included on Enterprise and available on Business as a paid add-on at $20 per seat per month, with a gradual rollout, so availability can lag the published plan line. Manual renewal dates, by contrast, reach Starter, Business and Enterprise. If you only send documents you built in PandaDoc, the manual tier is usually enough; the AI tier earns its price when you inherit a drawer full of third-party paper.

Tracking renewals: the Upcoming renewals tab

The Upcoming renewals tab lives in the document list and shows every document with an approaching renewal date; hovering over a date shows the exact time, and filters narrow the list by renewal date range, status, owner, counterparty and other data fields.

Two habits make the tab useful rather than decorative. First, review it on a schedule instead of waiting for alert emails. Alerts go to each document’s owner, and in any team with turnover that is eventually someone who left; a weekly scan of the tab by whoever owns revenue catches the agreements whose owner is gone, on leave, or ignoring their inbox. Second, filter by owner before anyone goes on holiday and reassign what will land while they are away. The owner-only alert design makes ownership hygiene a renewal-revenue issue, not an admin nicety.

This is also where renewals earn their place in your reporting. The tab is effectively a forward book of re-signable revenue; across the 105 sales calls behind our research, 82 of 129 recorded pain points were about manual document creation time, and renewals are the one document type where the volume is entirely predictable months in advance. There is no excuse for a predictable document being an emergency.

Creating the renewal document: regenerate, never duplicate

When the alert fires, the tempting move is to find last year’s document, duplicate it, change the dates and send it. Resist it. Duplicating last year’s agreement copies last year’s pricing, last year’s terms, last year’s logo and every error that has been fixed in your templates since. This is template drift in its purest form: the live template improves all year while renewal documents keep cloning an ancestor from before the improvements. Our guide to the PandaDoc content library covers why single-sourced blocks exist; duplicating old documents bypasses every one of them.

The reliable pattern is to regenerate: create the renewal from the current template, exactly as you would a new agreement, and let it pull current standard terms, current branding and current pricing. Where prices live in the product catalog, the pricing table fills with today’s rates rather than whatever was quoted at the original signing, which turns your annual price review into something that propagates to renewals automatically instead of depending on whoever edits the duplicate. If your templates are not in a state you would trust to regenerate from, that is the real problem, and a PandaDoc template build that moves shared copy into the content library and pricing into the catalog is the fix that makes every future renewal safe.

What carries over from the original is the counterparty data: recipient details, company information and any negotiated specifics you store as variables. In a CRM-connected setup these fill from the CRM record rather than from the old document, which is another reason the regenerate pattern beats duplication: the data flows from systems that are maintained, not documents that are frozen.

Auto-renewal clauses and conditional content

Some agreements renew by signature, others renew by silence: an auto-renewal clause that extends the term unless either party gives notice. If some of your agreements auto-renew and others do not, do not maintain two near-identical templates; one template with a conditional auto-renewal clause is easier to keep correct. PandaDoc’s smart content handles this: our conditional content guide covers the mechanics, and the renewal clause is one of its best use cases, a single field choice toggling the clause in or out without anyone editing legal text.

Two operational notes for auto-renewing agreements. Set the renewal alert anyway, timed before the notice deadline rather than the renewal date, because the decision point on an auto-renewal is the last day you can cancel or renegotiate, not the day it rolls over. And remember the client’s procurement team has the same clause in their calendar; an alert that fires after their notice window has opened is an invitation to a cancellation email.

Triggering renewals from the CRM

Renewal dates can live in PandaDoc, in the CRM, or both, and mature setups push the workflow to wherever the team actually works. If your sales team lives in HubSpot, a renewal deal created 60 to 90 days out, moving through its own pipeline, beats an email alert: it is visible, assignable and reportable. From there, the same automation that generates new-business documents can generate the renewal: our guide to creating PandaDoc documents from HubSpot deal stages covers the exact pattern, where moving the renewal deal to a Renewal proposal stage generates the document from the current template with CRM data filled in.

That stack, renewal deal in the CRM, document generated on stage change, pricing from the catalog, is what turns renewals from a scramble into a pipeline. A properly built PandaDoc HubSpot integration is the prerequisite, and it is worth noting the sequencing: automating renewal document creation before the templates and catalog are trustworthy just produces wrong documents faster. The teams we work with average 45 to 50 minutes per manually built proposal; a CRM-triggered renewal from a clean template takes minutes, but only because the template work came first.

The renewal workflow for agencies and retainer businesses

If your revenue is retainers, renewals are not an edge case, they are the business, and the full loop looks like this:

1. Template rule: every retainer and service agreement template carries an After document completion renewal matching its standard term, so tracking is automatic from the day of signature.
2. Lead time: alerts fire 45 to 60 days out, far enough for a value conversation and a repricing rather than a rubber stamp.
3. Weekly tab review: one owner scans the Upcoming renewals tab weekly, reassigns orphaned documents, and opens a renewal deal in the CRM for everything inside the window.
4. Regenerate, reprice, send: the renewal document comes from the current template with catalog pricing, goes through the normal approval flow, and is sent with time to spare.
5. Close the loop: the completed renewal carries its own renewal rule, so next year starts tracked.

None of this is exotic, but each step sits in a different part of PandaDoc (template settings, extensions, document list, CRM integration), which is why renewals are rarely set up well in a self-service implementation. It is exactly the kind of workflow an ongoing PandaDoc support arrangement exists to build and keep tuned: the renewal rules go onto the templates once, the drift that would poison regeneration gets caught in routine audits, and the CRM trigger is maintained as pipelines change. If your implementation predates Agreement Renewals entirely, a broader PandaDoc implementation review will place renewals alongside the template, catalog and integration work it depends on.

The feature itself takes minutes to switch on. The renewal revenue it protects compounds every year it runs.