Signing completion rate: measure what matters

If your team sends 100 proposals and 40 come back signed, that number tells you something important. Not about your reps. Not about your pipeline. It tells you about your templates.

Signing completion rate is the percentage of documents that reach "Signed" after being sent for signature. I track it for every team I work with that runs document automation in HubSpot, and it is consistently one of the most useful and most ignored metrics in the reporting stack.

Most teams watch close rate, time to close, and win rate by rep. Almost none of them break those numbers down by the document that went out. That gap is where template performance hides.

Why signing completion rate matters

Close rate tells you how your pipeline is performing overall. Signing completion rate tells you something more specific: once a buyer has seen your terms and you have asked for a commitment, how often do they follow through?

That distinction matters. A healthy pipeline can still have templates that slow things down. If your Standard Proposal converts at 75% but your Enterprise Agreement sits at 40%, the enterprise version might be too long, too complex, or missing information the buyer needs to say yes.

Without this data, template changes are guesswork. With it, you can make decisions based on evidence. Which template needs rewriting? Which one should become the default? Where is the real friction in the last mile of the deal? The numbers answer those questions.

What signing completion rate measures

The formula is straightforward.

Signing completion rate = (Documents signed / Documents sent for signature) x 100

It only counts documents that reached the "Signature Requested" stage. Drafts, previews, and documents that were created but never sent do not enter the calculation. This keeps the metric honest. You are measuring the last mile: the buyer received the document, and either they signed or they did not.

In Portant, every document created from HubSpot gets its own record with a Document Status property. That property tracks the full lifecycle: Created, Signature Requested, Signed, Expired, and other stages. These status values give you a clean filter for building the report.

Signing rate vs close rate

These two numbers answer different questions.

Close rate covers the whole deal. It includes every reason a deal might not close: budget changes, lost champions, timing, competitive displacement. A lost deal does not always mean the document failed. The buyer might never have reached the signature stage at all.

Signing rate is about the document step. It only looks at deals where you actively sent something for signature. If a buyer received your contract and did not sign, the document was part of that failure. Maybe the only part, maybe not. But it is now in the frame.

The most useful insight comes from comparing the two. If your overall close rate is strong but signing rate is weak on certain templates, the template is the bottleneck. If signing rate is high across the board but close rate is low, the problem is upstream, in qualification or deal structure, not in your documents.

Setting up the report in HubSpot

Portant saves every document as its own object in HubSpot, with properties you can report on directly. The three properties you need for this report are:

• Document Status: tracks where the document is in its lifecycle (Created, Signature Requested, Signed, Expired, and others)
• Portant Workflow Name: maps to the template or workflow that generated the document, so you can group by template type
• Document Created: the date the document was generated, useful for filtering by time period

You can see these properties on any deal record once Portant is connected. The Portant documentation on viewing documents in HubSpot walks through where to find them.

Here is how I set up the report:

1. Go to Reports in HubSpot and create a custom report.
2. Choose Portant Documents as your primary data source. If you need deal context (deal size, owner, pipeline), add Deals as a secondary source.
3. Add a filter where Document Status is "Signature Requested" or "Signed." This gives you the full population of documents that were actually sent for signing.
4. Create a calculated field or use a pivot to show the count of "Signed" documents divided by the total count (Signature Requested plus Signed), multiplied by 100.
5. Group the results by Portant Workflow Name. This breaks your data down by template.
6. Save the report and add it to a dashboard your team reviews regularly.

Breaking it down further

Template name is the first dimension, but it is not the only one worth exploring.

By rep. Group by deal owner alongside template name. If one rep consistently gets lower signing rates on the same template, the issue might be how they position the document, not the template itself. Or it might reveal that certain reps handle deal types where signing is naturally harder.

By deal size. Add deal amount as a dimension. Signing rate often drops as deal value increases. That is not always a template problem. Larger deals involve more stakeholders, longer legal review, and more negotiation. But if signing rate drops sharply above a certain threshold, your template might not scale well to complex commercial terms.

By time period. Filter by Document Created to compare signing rates across months or quarters. Seasonal patterns, product launches, or pricing changes can all affect how templates perform. Tracking over time helps you separate systemic issues from temporary ones.

By pipeline. If your team runs multiple pipelines (new business, renewals, upsells), signing behavior will differ across them. A renewal contract and a new business proposal have very different dynamics. Comparing signing rates within the same pipeline keeps the numbers meaningful.

What the data tells you

Once the report is running, patterns show up quickly.

Template performance is the most obvious signal. If two templates serve similar deal types but one converts significantly better, the lower performer deserves attention. Look at length, complexity, layout, and the information included. Sometimes a template underperforms simply because it asks the signer to review too many pages before they find the signature block.

Process friction is less obvious but just as common. A template might have a strong signing rate when sent within 24 hours of verbal agreement but drop off after 48 hours. That is a timing issue, not a template issue. The report alone will not always explain why, but it tells you where to look.

Deal complexity shows up when you cross-reference with deal properties. Templates that work well for straightforward transactions might struggle on multi-product or multi-entity deals. If you see this pattern, consider building a separate template for complex deals rather than stretching one template to cover everything.

Diagnosing low signing rates

A low signing rate is a symptom. The cause usually sits in one of three places.

Template issues: the document itself creates friction. It might be too long, use unclear language, bury important terms, or lack the information the signer needs. I look at the template with fresh eyes and ask whether someone outside the deal could read it and understand what they are agreeing to. If the total is hard to find, the payment terms are ambiguous, or the scope description runs for three pages, the template is making signing harder than it needs to be.

Process issues: the way the document reaches the signer creates friction. Maybe it is sent too early, before the buyer has verbally committed. Maybe it arrives as a bare attachment with no context. Or the follow-up cadence is wrong, either too aggressive or too passive. I see this a lot with teams that automate sending but forget to automate the follow-up.

Buyer issues: the signer's organization creates friction. Procurement teams, legal review, multi-party approval chains, and budget cycles can all delay or block signing. These factors are real. But they tend to affect signing rates consistently across templates, not selectively. If one template performs worse than others with the same buyer profile, the buyer is probably not the problem.

When a low signing rate is not a template problem

Not every low number needs fixing.

Enterprise and multi-party deals naturally have lower signing rates. The buying process involves more people, more review cycles, and longer timelines. A 50% signing rate on a six-figure enterprise agreement might actually be healthy if the average deal in that segment takes 90 days to close and involves legal redlines. Compare it to similar deals, not to your simplest template.

Procurement delays can suppress signing rate within a given reporting period. If you send contracts in December but procurement does not approve until January, your December signing rate looks worse than it really is. Filtering by a wider time window or tracking "days from sent to signed" alongside the rate helps account for this.

Seasonal patterns matter too. Some industries slow down during specific months or quarters. If your Q4 signing rate dips but recovers in Q1, you are probably looking at normal buyer behavior, not a template problem.

The question I always come back to is: is this template performing differently from comparable templates, or is the entire category behaving this way? If the whole category is low, the cause is probably external. If one template is the outlier, start there.

What to do with the data

Once you have identified templates that underperform, here is what I recommend.

Simplify first. The most common fix is making the document shorter and clearer. Remove sections the signer does not need for their decision. Move supporting detail to an appendix or a separate attachment. Make the signature block easy to find and the total easy to read. I have seen signing rates jump by double digits just from cutting a template from eight pages to three.

Test one change at a time. If you change the layout, the length, and the language all at once, you will not know which change moved the number. Pick the most likely issue, adjust it, and watch the signing rate over the next 20 to 30 documents. That is enough volume to see whether the change made a difference.

Build template variants for different deal types. If your Standard Proposal works well but your Enterprise Agreement does not, you might need a dedicated enterprise template rather than a longer version of the standard one. Teams using Portant can set up separate workflows so each deal type triggers the right template automatically based on deal properties.

Add eSignatures if you have not already. Sending a PDF that someone has to print, sign, scan, and return will always have a lower completion rate than a document with a built-in signature step. Portant's eSignatures let you add signing directly to the document workflow, so the signer clicks rather than prints. The fewer steps between "document received" and "document signed," the higher your completion rate.

Review the follow-up process. A strong template with no follow-up will still see lower completion rates. Make sure your team has a clear sequence for what happens after the document is sent: when they check in, how they check in, and what happens if the document stalls. Portant can trigger automatic reminders when a signature has not been completed, which removes one more manual step from the process.

Frequently asked questions

What is a good signing completion rate?

It depends on your deal type and industry. For straightforward proposals and quotes, I typically see healthy teams in the 65% to 85% range. For complex enterprise contracts with legal review, 40% to 60% can be perfectly normal. The most useful benchmark is your own data over time: track the trend and compare templates against each other rather than chasing an arbitrary number.

How many documents do I need before this metric is useful?

I start paying attention once a template has at least 20 to 30 signature requests. Below that, a single unusual deal can swing the percentage by 10 points or more. At 50 or more, the patterns become more reliable. If your team sends a high volume, you can start seeing useful signals within a few weeks.

Should I track expired documents separately?

Yes. Expired documents (where the signing window closed before the buyer acted) are a different signal from outright non-completion. A high expiration rate might mean your signing deadlines are too tight, or that buyers need more time in your sales cycle. I report on expired documents as a separate metric alongside signing completion rate.

Can I use this data to compare reps?

Carefully. Signing rate by rep is useful for identifying coaching opportunities, but only if you control for deal type and complexity. A rep who handles enterprise deals will naturally have a lower signing rate than one who handles small, standard quotes. Compare reps within the same deal segment, not across the entire pipeline.