# Deals stuck in legal and procurement: track the paper stage in Pipedrive

https://salesbond.app/blog/deals-stuck-in-legal-procurement-pipedrive/
Published: 2026-10-02 · Updated: 2026-10-25

When a deal is stuck in procurement or legal review, ask the buyer who else is reading the document and by what date, write both answers into Pipedrive as separate fields, and count the days the deal has spent in that stage. If the paperwork has not moved by the date you agreed, the deal goes back to a conversation with your champion. Waiting is not a strategy. It is a stage with no owner.

“Legal is reviewing it” is the most comfortable sentence in sales. It sounds like progress, the buyer said it, and nobody wants to argue with a lawyer. This article treats that stage like any other: with questions, fields, a clock and an exit. It is about the sales process, not the contract. What the agreement should say is a job for your counsel; how long it sits in someone’s inbox is yours.

## The deal that went quiet at “legal is reviewing”

One example runs through this whole article. We invented it, but you have probably owned a deal exactly like it. An $18,000 annual subscription, a 40-person company, a verbal yes on a call. The rep sends the order form and the master agreement on Friday, September 11. The champion writes back the same afternoon: “Great, it’s with legal now. Should be about two weeks.” The rep moves the deal to Contract Sent and puts the date the champion gave, September 25, into the deal.

Then nothing. It is October 2, three weeks since the documents went out, and the last three notes on the deal all say “waiting on legal.” The expected close date has already slid once (we wrote separately about [pushed close dates in Pipedrive](https://salesbond.app/blog/pushed-close-dates-pipedrive/)), and the deal still counts in this month’s number at whatever probability the Contract Sent stage carries.

Now list what the sales side actually knows. Not who at the buyer has the document. Not whether procurement has received it, or whether legal means an in-house counsel or an outside firm that bills by the hour. Not whether a redline is sitting in someone’s drafts. The deal looks like it is closing because the stage name says so.

For the general diagnosis of slow deals against dead ones, see [stalled deals vs dead deals](https://salesbond.app/blog/stalled-deals-vs-dead-deals/). This piece is narrower: what to do when the stated reason is paperwork.

## Why the paper stage hides deals

The first reason is that the excuse cannot be checked from the outside. “Legal has it” is true until someone asks the buyer a specific question, and asking feels like pressure, so reps don’t.

The second reason is that your own activity dries up on purpose. There is “nothing to do” while the document is with the other side, so nobody touches the deal, except to move the close date. And Pipedrive’s rotting won’t flag it: any edit to the deal, a custom field or the close date included, sends a rotten deal back to healthy ( [Pipedrive: the rotting feature](https://support.pipedrive.com/en/article/the-rotting-feature)); more in [rotting deals in Pipedrive](https://salesbond.app/blog/pipedrive-rotting-deals/). In this stage a moved date is a symptom. The signal is the document.

The third reason is that late stages carry a confident probability, so a paper-stage deal flatters the forecast more than a deal stuck at demo. Pipedrive does show, in the deal’s progress bar, how many days a deal took to complete each stage ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)). That is honest information and in our experience nobody opens it until the quarter is over.

## Four questions to ask before the contract goes out

Ask these on the call where the buyer says yes, before you send anything. After three weeks of silence the same questions sound like an interrogation; on the day of the verbal yes they sound like competence.

1. **Who reads this after you?** Names where you can get them, roles where you can’t: counsel, procurement, security, finance, the person who signs. If the champion says “just legal,” ask who in legal. One person with a name is a reviewer. “Legal” is a department, and departments don’t have deadlines. If the buyer works with purchase orders, add one more name: [whoever issues the PO](https://salesbond.app/blog/purchase-order-number-before-invoice-pipedrive/).
2. **Which documents will they want from us?** A vendor registration form, a security questionnaire, a data processing agreement, proof of insurance. Every one of those that arrives late is a delay the buyer will file under “legal.” It helps to decide [who answers a security questionnaire](https://salesbond.app/blog/sales-security-questionnaire-pipedrive/) before the first one arrives.
3. **What date have they given you?** Not “how long does it usually take,” which gets you a shrug. Ask what date the champion would use if thier own manager asked. A buyer who has done this before has a number. A buyer who hasn’t will say “a couple of weeks,” and you write that down as a date anyway, with their name next to it.
4. **What could stop it?** A pricing clause they already know finance dislikes. A liability cap their counsel always pushes back on. A second vendor in a parallel review. This answer becomes the blocker field below, and it is the one reps most often skip because it invites bad news. A buyer who wants net 60 on signing day is one such blocker; see what to do when [procurement asks for net 60](https://salesbond.app/blog/net-60-payment-terms-request-pipedrive/).

If the champion cannot answer the first and the third, the deal is not in legal review. It is a deal without a plan, and the fix is the one-page plan from [mutual action plans for small teams](https://salesbond.app/blog/mutual-action-plan-small-teams/), agreed with the buyer before any document goes out.

## What to record in Pipedrive

Four custom deal fields ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)), created under Personal preferences > Data fields. Only four, because custom field limits depend on your plan.

- **Paper stage start**, a date field. The day the document left your hands, which is rarely the day the deal entered the stage.
- **Buyer-side reviewers**, a text field. The answer to question one, as names or roles.
- **Buyer-promised date**, a date field. The answer to question three. This is the field the clock runs against.
- **Paper blocker**, a single-option field: Redlines open, Procurement form, Security review, Signer unavailable, None known, Unknown. “Unknown” is a legitimate value and a loud one.

Two settings help the fields survive a busy team. A field description shows up behind the info icon next to the field, so the instruction “the date the buyer gave you, not your guess” lives where the field is filled rather than in a wiki. And both date fields can be marked as important, which highlights a blank in the deal detail view without blocking the save. Both are available on Growth and above. Required fields (Premium and above) would block saving the deal until they are filled, which we think is too much for a stage the buyer controls.

Add all four as columns in the deals list view, next to value and expected close date. Pipedrive’s changelog records changes to custom fields along with stage and expected close date, so when a blocker moves from Redlines open to Signer unavailable, the trail is there for the review.

Why fields instead of a note? Because a filter can match a date field and cannot read “waiting on legal” in a note. The next buyer-side step belongs in the deal’s next activity, with the buyer-side owner in the subject, exactly as we set it up for action plans: “Redlines back from their counsel, owner: Priya.” That way the step shows up where the team already looks every morning.

![Example Pipedrive deal card with four paper-stage fields and a timeline from Sep 11 to Oct 2](https://salesbond.app/wp-content/uploads/2026/10/deals-stuck-in-legal-procurement-pipedrive-2.png)

## A clock for the paper stage

The clock does not run against the calendar. It runs against the date the buyer gave you.

Our rule, offered as a starting point: when the buyer-promised date passes and no document has moved for five business days after it, the deal leaves “legal is reviewing” and goes back to a conversation with the champion. A document moving means something concrete: redlines came back, a form was submitted, a signature landed, the reviewer asked a question. “They said it’s close” is not movement.

Why five business days? One week absorbs the ordinary (counsel was out on Thursday, procurement meets on Tuesdays) without absorbing a quarter. In our example the documents went out on September 11, the champion said “about two weeks,” and the rep wrote Friday, September 25 in Buyer-promised date. Five business days after that is Friday, October 2, which is where the example deal stands today. Not a lost deal. A deal that goes back to the champion with a direct question instead of a fourth “just checking in.”

If the buyer gave no date at all we run the clock from Paper stage start and bring the deal back after ten business days. The missing date is itself the finding: the champion could not say how long their own process takes, and that is worth knowing before you build a forecast on it.

The weekly list comes from one saved filter ( [Pipedrive: advanced filtering](https://support.pipedrive.com/en/article/filtering)): open deals, ALL conditions, Paper stage start is not empty, and Buyer-promised date is before today. Pipedrive’s help pages don’t spell out the date operators, so use whichever one your account offers for “earlier than today.” The filter shows every paper-stage deal past its promised date; the five-day check is a glance at the deal’s history. Save it, set the visibility to shared, and open it at the start of the pipeline review. Deals that fail the five-day check drop one forecast category until a document moves; how we name the categories is in [commit vs best case](https://salesbond.app/blog/commit-vs-best-case-forecast/). A fresh close date doesn’t reset this clock.

## What to send so the buyer’s reviewers don’t wait on you

Send the complete packet once, before the reviewer has to ask for anything.

In deals we’ve looked at, a fair part of what reps log as “legal delay” turned out to be the reviewer waiting on the seller. That’s an observation, not a statistic, but it repeats. A data processing agreement nobody sent. A security questionnaire that [sat in a shared inbox](https://salesbond.app/blog/pipedrive-team-inbox-shared-mailbox/). Redlines forwarded to a rep who forwarded them to no one.

So the first job is the packet. Everything question two surfaced, in an editable format if the buyer’s counsel is going to mark it up, with the name of the person on your side who answers questions about it and the date you are working towards, in one sentence, at the top of the email. A reviewer who has to ask for a missing document starts their own clock over again, and that clock is longer than yours. If those answers need a technical person, [mark who is in on the deal](https://salesbond.app/blog/sales-engineer-handoff-pipedrive/) before the packet goes out.

The second job is to agree, out loud, who on your side answers redlines and within how many days. Put that commitment in the the deal’s next activity. If your counsel takes a week to turn a redline, that is a week you should be adding to the buyer-promised date on day one, not discovering on day twelve.

The third is an introduction. Ask the champion to copy you to the reviewer directly, procurement or counsel, for a short call about process only: what is open, what they need, when they expect to be done. You are not negotiating clauses on that call. You are getting a date from the person who actually owns it, and that date goes into the field instead of the champion’s guess.

And stop checking in. Every touch during the paper stage carries something: an answered question, a document, a date. The cadence for that is in [follow-up after a proposal](https://salesbond.app/blog/follow-up-after-proposal-pipedrive/); here, what each touch carries is the part that matters.

## When it is no longer legal, it is a no-decision

Some signs that the stage name has stopped describing the deal. The buyer-promised date has been passed and re-set twice. The champion still cannot name the reviewer. Paper blocker has read Unknown for a month. Redlines are always “coming this week.” None of these is a legal problem. Together they describe a buyer who has not decided, and the sequence for that is in [no-decision deals](https://salesbond.app/blog/no-decision-deals-pipedrive/), with the first-contact script in [when a prospect goes silent](https://salesbond.app/blog/prospect-went-silent-after-demo/).

The action is a direct question to the champion, asked once and in plain words: “Is this still happening this quarter, or has something changed on your side?” A buyer who is serious will tell you what changed, usually in the same reply. Then move the deal back a stage so the forecast says what you know, and leave the date alone until the buyer gives you a new one with a reason you can check.

A disclosure, since this is the kind of signal we build for. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health flags a deal whose expected close date has passed with no next activity scheduled, and shows the manager that reason next to the deal, which is close to what the saved filter above does by hand. Check your CRM with SalesBond if you’d rather not maintain the filter. The four questions still have to be asked by a person.

So, this week: open the deals sitting in your contract stage, fill Paper stage start and Buyer-promised date for each, and ask the champion for a date wherever the second field stays blank. Legal will still take as long as legal takes. You will just know which deals are waiting on a lawyer and which are waiting on a decision.