One approver, no delegate
The whole approval chain depends on a person who is in back-to-back meetings or on leave. There is no escalation, so the document waits as long as they do.
Workflow · Approvals · Triggers Documents do not stall because they are slow to build.
Documents do not stall because they are slow to build.
They stall because nobody moves them.
Generation was never the bottleneck. A proposal takes under a minute and then waits four days for an approver who is on holiday with no delegate, or sits unopened because nobody was told the buyer viewed the pricing page three times. Automation is the work of making documents move on their own. Routed, chased, escalated and closed without a human remembering.
1
0
Real-time
Auditable
Trusted by 500+ organizations — including revenue, sales operations and legal teams running document generation, quoting and e-signature on Salesforce and HubSpot with Twopir Consulting.
What We Automate
- Salesforce Partner
- HubSpot Partner
- Approval Workflows
- Conditional Approvals
- Triggered Generation
- Renewal Automation
- Bulk Send
- Escalation Paths
The six places a document sits doing nothing
Cycle time is mostly waiting, not working. Each of these has a rule that removes it.
Nobody knows the buyer engaged
The recipient opened the pricing section four times yesterday. That is the strongest buying signal you will get, and it reached nobody.
Approval is a policy, not a gate
Discounts above a threshold are supposed to be approved. Nothing enforces it, so approval happens when someone remembers and is missing from the audit trail when they did not.
Renewals are a calendar reminder
Contract end dates sit in a field nobody watches. Renewal documents get built late, or after the customer has already started looking elsewhere.
Signature is the end of the automation
The deal closes and nothing downstream happens automatically. Provisioning, onboarding and invoicing all wait for a person to notice.
Bulk sends are done one at a time
Two hundred renewal notices, an updated policy, a price-change letter. Somebody is generating them individually because nobody configured the bulk path.
What Automation Covers Here
Rules about movement, not about content
This page is about what happens to a document and when: which event causes it to be generated, who has to approve it and under what conditions, what chases it while it is out, what happens when it is signed, and what happens when it is ignored. It is built with PandaDoc's approval workflows and rules engine plus your CRM's own automation, and it is configuration rather than code.
Two mechanisms do most of the work. Approval workflows are configured once on a template, so every document created from that template follows the same path automatically — which is the difference between a policy and a control. Conditional approvals evaluate the document's own values, including totals from its quote and pricing blocks, so a quote above a discount threshold routes to a manager without anyone deciding to send it there.
Where this page ends and the next begins. Automation covers movement; customization covers what the document says and how it assembles itself. They meet at conditional content, and in practice most engagements touch both — but they are different design problems with different owners, and confusing them produces rules that duplicate template logic.
One caution worth stating: PandaDoc's rules engine processes rules sequentially, so the order they are defined in changes the result. A rules set that grew by accretion usually contains conflicts nobody has noticed. Designing the order deliberately, and documenting it, is a real part of the work rather than an implementation detail.
Route, orchestrate, or automate beyond the rules engine
Three levels of automation with three very different cost profiles. Start at the first.
Route
Approval and follow-up inside PandaDoc. The highest return per hour of work on this page.
- Approval paths configured per document type
- Conditional approvals on value, discount or product mix
- Delegates and escalation so no step has one dependency
- Reminder cadence and expiry handling
- Engagement alerts when a buyer opens a document
- Rule ordering documented and conflict-checked
Orchestrate
Automation that crosses systems: CRM triggers in, downstream actions out.
- Generation triggered by a CRM stage or date
- Renewal documents built from contract end dates
- Signature triggering provisioning, onboarding or invoicing
- Stalled-deal alerts routed to the owner
- Bulk and scheduled send configuration
- Failure handling so a missed trigger is visible
Build On
Where the rules engine cannot express the requirement. Development, priced as development.
- Logic the sequential rules engine cannot state
- High-volume generation beyond bulk-send limits
- Multi-system orchestration with transactional guarantees
- Generation from objects the connector does not surface
- Custom webhook services with retry and dead-lettering
- Approval routing against an external system of record
| Requirement | Mechanism | Engagement |
|---|---|---|
| Route quotes over 20% discount to a manager | Conditional approval on document value | Route |
| Remind a buyer who has not signed in 5 days | Reminder cadence on the document | Route |
| Alert the rep when the buyer opens pricing | Engagement notification | Route |
| Escalate when an approver is unavailable | Delegate and escalation on the step | Route |
| Build a renewal 90 days before contract end | CRM date trigger into generation | Orchestrate |
| Create the invoice when the quote is signed | Signature event to billing | Orchestrate |
| Send 200 policy updates at once | Bulk send | Orchestrate |
| Approve against a system PandaDoc cannot see | API-side routing service | Build on |
The first four rows are configuration and usually deliver the largest cycle-time improvement available. Teams routinely skip them and go straight to asking about custom development.
The boundary, in one sentence: the rules engine evaluates conditions over data the document and the CRM already hold, in sequence. If your rule needs to look outside that, needs a guarantee across several systems, or cannot be stated as an ordered WHEN/THEN, it is an API build — and we will say so before it is a maintenance problem.
The six automations that take days out of a cycle
Ranked roughly by return. Most teams have not done the first three.
Approval Routing & Conditional Gates
Configured on the template so it applies to every document, not the ones somebody remembered to route.
- Thresholds on discount, margin, deal value or product
- Multi-step routing across sales, finance and legal
- Template-level and workflow-level approval design
- Rule order designed deliberately, since evaluation is sequential
- Approval state written back to the CRM record
Delegates, Escalation & Coverage
The single cheapest cycle-time fix available, and the one most often missing.
- A delegate on every approval step
- Time-based escalation when a step is held too long
- Out-of-office and coverage handling
- Escalation notifications to a manager, not a channel
- Reporting on which steps escalate most often
Follow-Up, Reminders & Engagement Alerts
Turning document analytics into action rather than a report nobody opens.
- Reminder cadence tuned per document type
- Alerts when a recipient opens a key section
- Stall alerts when a document ages past a threshold
- Expiry handling and automatic re-issue
- Follow-up tasks created on the CRM record
Renewal & Recurring Document Automation
Contract dates driving document generation instead of sitting in a field nobody watches.
- Renewal generation triggered ahead of contract end
- Pre-populated with current pricing and terms
- Uplift and escalation clauses applied by rule
- Renewal pipeline visible in the CRM
- Non-response escalation before the date passes
Triggered Generation from CRM Events
Documents that build themselves when the deal reaches the point of needing one.
- Stage-change triggers into document creation
- Date and milestone triggers
- Template selection driven by deal attributes
- Guardrails so a trigger cannot fire twice
- Failure visibility when a trigger does not fire
Post-Signature Triggers & Bulk Send
Closing the loop so signature starts the next process rather than ending the automation.
- Provisioning or onboarding started on signature
- Invoice or subscription creation from signed line items
- Filing and retention applied automatically
- Bulk send for policy updates and mass renewals
- Rate-limit-aware scheduling for large runs
What sets automation off, and what it sets off in turn
Each one named, with the direction and the business purpose.
Salesforce events → PandaDoc
Stage changes, date milestones and field updates trigger document creation from the right template, populated from the record — so the document exists when the process needs it.
HubSpot events → PandaDoc
Deal stage, property changes and workflow actions drive quote and contract generation, with template selection driven by deal attributes.
PandaDoc events → CRM
Sent, viewed, commented, completed and expired events land on the record, where they trigger tasks, alerts, stage changes and sequences.
Document value → approval routing
Conditional approvals evaluate the document's own totals, including values from quote and pricing blocks, so routing reflects what the buyer is actually being offered.
Signature → billing
Signed line items creating an invoice or a subscription, so what was agreed and what is billed are the same thing without a person in between.
Approval requests → Slack or Teams
Routed to the individual who must act, with the document, the deal value and the reason for the gate attached, rather than broadcast to a channel.
Contract dates → renewal generation
Renewal documents built ahead of the end date with current pricing applied, so the renewal conversation starts before the customer has begun looking.
Webhooks → your systems
For downstream systems with no connector. Development work — covered on our PandaDoc API development page.
Five phases, and we measure the waiting first
Automation is only worth building where documents actually wait. Phase 01 finds that, and it frequently contradicts what the team expected.
Cycle-Time & Wait Analysis
We measure where documents actually sit: creation to send, send to view, view to signature, and time held at each approval step. This is what stops automation being built where it changes nothing.
Rule & Routing Design
We design the approval paths, conditional thresholds, escalation and follow-up cadence — and the order rules evaluate in, because the engine processes them sequentially and order changes outcomes.
Build & Conflict Check
Rules built in a sandbox workspace and tested against real scenarios, including the ones that match more than one rule. Conflicts are found here rather than in production.
Trigger & Downstream Integration
CRM triggers wired in and post-signature actions wired out, with failure visibility so a trigger that does not fire is noticed rather than assumed.
Launch, Tune & Re-measure
Go-live, then tuning: reminder cadences that are too aggressive, thresholds set too low, escalations that fire constantly. Re-measured against the Phase 01 baseline.
What changes when documents move themselves
Real engagements, with the scope each number was measured against.
Automated Generation & Status Sync
Generation, e-signature and bi-directional status writeback · 500+ documents a month
1 click
From CRM record to sent document
Real-time
Sent, viewed, signed, completed
0
Manual status chasing
<60s
To a ready-to-send document
Proposal creation used to take a rep 45 minutes of copying data, fixing formatting, and hoping nothing was wrong by the time it reached the customer. Now they click one button inside Salesforce and a fully accurate, branded document is ready to send in under a minute. The eSignature alone has cut our average close cycle by days.
Contracts, Offer Letters & KYC Onboarding
Documents generated automatically the moment a record reaches the document stage
3
Document families triggered
0
Manual generation steps
Auto
Generation on stage change
Native
Salesforce trigger source
Engagement scope: contracts, offer letters and KYC onboarding forms generated automatically from Salesforce Opportunities at the point a deal reaches the document stage. Outcome metrics for this engagement are being confirmed with the client before publication.
Teams whose cycle time is mostly waiting
If documents are fast to build and slow to close, this is the right engagement.
Sales leaders with a cycle-time target
Deals take too long and generation is already instant. The time is going somewhere else and nobody has measured where.
Finance teams enforcing discount policy
The threshold exists in a policy document. You need it to exist in the workflow, with an audit trail attached.
Teams losing renewals to inattention
Contract end dates pass without anyone starting the conversation. Automating the trigger is usually a fast, high-return build.
RevOps teams closing the post-signature gap
The deal closes and provisioning, onboarding and invoicing all wait for someone to notice.
Legal ops teams handling volume
NDAs, policy updates and mass re-papering done one document at a time because nobody configured the bulk path.
Teams with rules that have grown by accretion
Approval rules added one at a time over two years, now conflicting in ways nobody can predict. Sequential evaluation makes that a real problem.
We automate where the time actually goes
Most automation projects speed up the fast part. We measure first so the build lands where the waiting is.
We measure the wait before we build
Time held at each approval step, time from send to view, stall rates by document type. Automation built without that measurement usually optimises the minute, not the four days.
We design rule order deliberately
The rules engine evaluates sequentially, so order changes outcomes. Rule sets that grew by accretion almost always contain conflicts, and we document the order we set.
We always build the escalation path
Every approval step gets a delegate and a time-based escalation. A gate with a single dependency is a bottleneck with governance language attached to it.
We wire both ends
As a Salesforce Partner and HubSpot Partner, we build the CRM triggers and the downstream actions, not just the middle.
We tune after launch
Reminder cadences that irritate buyers and thresholds that route everything are normal first-pass outcomes. The tuning pass is in scope, not an upsell.
250+ deployments, 40+ consultants
Serving 500+ clients over 12+ years across the US, Canada, UK, UAE, Australia and New Zealand.
What teams ask about automating document workflow
The questions that decide whether this is configuration or a development project.
Yes. Conditional approvals evaluate the document's own values — including the totals from its quote builder and pricing table blocks — so a quote above a discount or value threshold routes to the right approver automatically. The approval is configured once on the template, which means every document created from that template follows the same path. That is the difference between a discount policy and a discount control.
Because the rules engine processes rules sequentially rather than evaluating them all at once. A document that matches two rules is handled according to which one comes first, so ordering changes outcomes. This is the most common cause of approval behaviour teams describe as unpredictable, and it is why we design and document the order rather than adding rules as requirements arrive.
Yes, through your CRM's automation. A Salesforce stage change or a HubSpot workflow can create a PandaDoc document from the appropriate template, populated from the record. The design work is mostly in the guardrails: making sure a trigger cannot fire twice, choosing the right template from deal attributes, and making a failed trigger visible rather than silent.
Adding a delegate and a time-based escalation to every approval step. It is quick to configure, needs no integration work, and in most deployments the largest block of dead time in the whole cycle is a document held by one unavailable approver. Teams routinely skip it and ask about triggered generation instead, which usually saves minutes rather than days.
Yes, and it is usually one of the better-value builds. Contract end dates in the CRM trigger generation of a renewal document ahead of the date, pre-populated with current pricing and any uplift applied by rule, with escalation if the customer does not respond. The value is less in the document creation than in the conversation starting before the customer has begun looking elsewhere.
Customization is about the document — what it contains, how it assembles itself, how it looks. Automation is about what happens to it and when — generation triggers, approval routing, reminders, escalation, and what signature sets off downstream. They meet at conditional content, and most engagements touch both, but they are separate design problems and treating them as one produces rules that duplicate template logic.
It can, and untuned reminder cadences are the usual culprit. A reminder every day on a contract that a buyer's legal team is genuinely reviewing reads as pressure. We set cadences per document type and tune them after launch based on actual response patterns — which is why there is a tuning phase rather than a go-live and a handshake.
Not through the rules engine, which evaluates conditions over data PandaDoc and the connected CRM already hold. Routing against an external system of record — an HR system, a delegation matrix, an ERP approval hierarchy — needs an API-side routing service. That is development work with a maintenance cost, and we scope it as such on our PandaDoc API development page.
Next Step
If your documents are fast to build and slow to close
Give us a quarter of document data and we will show you where the time actually goes — which approval step, which document type, which stage. The fix is usually smaller and cheaper than teams expect.
12+ years · 500+ clients · 40+ consultants · Salesforce Partner · HubSpot Partner
