# Pipedrive and PandaDoc: what a viewed or signed document should change on the deal, and what it should not

https://salesbond.app/blog/pipedrive-pandadoc-signed-proposal-deal-stage-check/
Published: 2026-10-24 · Updated: 2026-10-24

PandaDoc’s Pipedrive integration can mark a deal Won the moment a document is completed. Whether it should is a separate decision. A view means call today. A signature makes the deal a Won candidate, and you switch on the automatic Won only once three conditions hold. A deal sitting in Won without a signed document is a gap a manager reviews weekly, because it turns into a forecast number nobody can collect.

## A signed document and a won deal are not the same event

Most teams connect PandaDoc to Pipedrive for the first half: the proposal gets built from the deal instead of a blank template. A week later someone asks what “Completed” means for the Pipedrive stage, and three reps give three answers: Won on signature, Won on countersignature, Won on invoice. All three are defensible, which is exactly why the pipeline report stops being comparable.

Our position: the document status is evidence, the stage is a decision. A signature is strong evidence, but the decision depends on things the document does not know, like whether work starts before payment.

## What the PandaDoc integration actually does in Pipedrive

More than most teams switch on. Per [PandaDoc’s help article on the integration](https://support.pandadoc.com/en/articles/9714881-pipedrive) (Business and Enterprise plans), documents are created from Pipedrive deals, people and organizations, with deal, contact and product data pulled into the template. The document status shows inside the Pipedrive record.

The part that matters here sits in the template’s sync rules. PandaDoc can:

- attach the signed PDF to the deal’s Files when the document is Completed;
- change the deal stage based on the document status, say Proposal to Negotiation;
- set the deal to Won or Lost, with statuses like Completed and Declined as the trigger;
- push field values, document value and line items back to the deal when the document is Sent or Completed.

So Pipedrive can react to a signature on its own. The real question is when to allow it. We would not switch on “Completed sets Won” until the three checks below are true for your sales process. Until then map Completed to a stage, not to Won.

## Document status to deal action: a four-row rule

We keep this to four rows on purpose. More rows and reps stop reading it.

| PandaDoc status | What it tells you | What happens on the Pipedrive deal |
| --- | --- | --- |
| Sent | The proposal left the building. | Nothing on the stage. Set the next activity: a call, with a date. |
| Viewed, no reply | Someone opened it and did not answer. | Nothing on the stage. Call today, about the content, not about “did you get it”. |
| Completed | Every recipient has signed and finished the document. | Won candidate. Run the three checks below, then Won or an “Awaiting prepayment” stage. |
| Declined or expired | The proposal is dead in this form. | Stage back one step, with a note on why. Not Lost yet, unless the reason says so. |

Viewed is the row that makes the most money and gets the least attention. Why a count of opens is not a count of readers is in [what Smart Docs view tracking tells a manager](https://salesbond.app/blog/pipedrive-smart-docs-view-tracking/); it applies to PandaDoc too. And a view followed by “can you change a couple of things” is a revision request: [a third version of the quote](https://salesbond.app/blog/revised-quote-versions-pipedrive/) is its own warning sign.

Completed is the row the automation acts on. Three checks decide whether it should.

First, does Completed include your side? PandaDoc marks a document Completed when all recipients have signed, so it covers your countersignature only if your signer is a recipient on the document. Otherwise Completed arrives one signature early; we covered that case for HubSpot in [which e-signature status should move a deal to Closed Won](https://salesbond.app/blog/signed-contract-closed-won-hubspot/).

Second, does the signed total match the deal? A discount given in PandaDoc and not on the deal makes the Won amount wrong, unless the line-item sync rule is on.

Third, does Won happen on signature in your business at all? If work starts only after prepayment, Completed should move the deal to an “Awaiting prepayment” stage instead, as described in [signed but not paid](https://salesbond.app/blog/pipedrive-won-not-paid-prepayment-invoice/).

Three yeses, and the automatic Won is safe to switch on. Any no, and Completed maps to a stage.

![Decision card with four rows: Sent, Viewed, Completed and Declined, each mapped to an action on the Pipedrive deal](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-pandadoc-signed-proposal-deal-stage-check-2.png)

## Won without a signature, signed without Won

Won without a signed document is usually an honest rep problem. The customer said yes on the phone, the month is ending, the deal goes to Won while the document sits at Viewed. Three weeks later procurement sends a redline and the report has already counted the deal. The fix is the rule: Won requires a Completed document or a written reason on the deal. If the customer signed a printed copy, PandaDoc lets you [set the status to Completed by hand](https://support.pandadoc.com/en/articles/9714842-manually-change-document-status) and attach the scan, so the paper trail stays in one place.

Signed without Won is quieter. The customer signed on Friday, the rep was out on Monday, the deal is still in Proposal Sent on Wednesday, and the weighted pipeline understates the month. Teams that map Completed to a stage rarely see this one, which is a good argument for setting the rule up.

## The weekly manager check

Ten minutes, once a week, two lists. We do ours on Friday, because the week’s stage changes are in and a rep has the weekend to think about a question rather than answer it on the spot.

List one: deals in Won, closed this month, where the PandaDoc document is not Completed. The rep gives the signed document or a reason in a note on the deal. No reason, the deal moves back. The point is not to catch anyone; it is that Won means one thing.

List two: deals in your proposal stage where the document is Viewed and the last activity is older than the view. Ask the rep when they opened it and when the call is. If the honest answer is “I sent a follow-up email” the deal stays on the list.

If you haven’t mapped Completed to a stage yet, add a third pass for Completed documents on deals that are neither Won nor in “Awaiting prepayment”. It’s usually two deals, and the the one list that moves the forecast up.

## When Smart Docs is enough

If your proposals are a priced quote with one signature line, Pipedrive’s own documents with view tracking are enough, and the four-row rule works on top of them.

PandaDoc earns its place when the document is the negotiation: content a rep swaps per customer, options the customer picks in a pricing table, a countersignature on your side. A Reddit thread that ranks for this search is titled “Pipedrive Smart Docs is so basic, it’s unusable”, and that is a fair reason to move. “The integration will keep my pipeline honest” is not. The automation does what you map it to do; the three checks decide what that is.

A disclosure, since we are at the “someone has to do the weekly check” point: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. [Check your CRM with SalesBond](https://salesbond.app/).