How to track close date pushes in HubSpot

The deal is still in “Contract sent.” The amount has not moved, the champion still answers email, and the rep says it will sign next month. That is the same thing the rep said last month, and the month before. Nothing on the deal record says so, unless you open the property history and scroll.

A pushed close date is the cheapest early warning a CRM produces, and many HubSpot portals I have worked in throw it away. This paper shows what HubSpot tracks on its own, how to build a push counter, which changes to keep out of the count and what to do when a deal reaches its third push.

Does HubSpot track how many times a close date changes?

Partly. HubSpot records every change to Close date in each deal’s property history, with the date and the source of each change. Depending on your subscription, the sales analytics suite also reports deals whose close date was pushed out of or pulled into a period. What HubSpot does not give you is a deal property that holds the count.

That gap matters more than it sounds. Property history works one deal at a time, so nobody reads it during a pipeline review. The push-rate report answers a team-level question about a period, but a system-calculated report metric cannot sit on the deal record, filter a view, trigger a workflow or appear next to the deal in a forecast. The number that should travel with the deal stays locked inside a report.

So the fix is a property. Once the count lives on the deal, you can sort a view by it, show it in the forecast, alert a manager when it climbs and report on it by owner, stage or source.

Why does a pushed close date say more than the deal stage?

Stage tells you what the rep believes. The close date history tells you how often that belief has been wrong. Ebsta and Pavilion’s 2024 B2B Sales Benchmarks, an analysis of 4.2 million opportunities across 530 companies, found deal slippage rose to 44% in 2023, and that deals with close dates moved more than three times saw win rates drop 77%. Slipped deals overall saw win rates drop 67% in the same report.

The trend points the wrong way, too. A year earlier, Ebsta and Pavilion’s 2023 B2B Sales Benchmark Report, an analysis of 3.2 million opportunities across 364 companies, found deal slippage hit 37% in 2022, up 21% year-over-year. That report also found 17% of opportunities had their close date moved three or more times by more than a week.

Older survey data tells a similar story from the forecasting side. According to InsightSquared and RevOps Squared’s 2021 State of Sales Forecasting benchmark research, a survey of nearly 400 B2B enterprise organizations fielded in April 2021, 47% of opportunities close within the original forecast date. That is a timing number, not a win rate. It measures how often the first date a rep sets turns out to be the real one.

The cost shows up in the forecast before it shows up in the bookings. Salesloft’s 2026 U.S. Revenue Benchmark Report, fielded by Censuswide among 500 U.S. sales and revenue decision-makers, found an estimated 19.7% of pipeline is affected by stalled deals, slipped close dates and other execution breakdowns. A push counter will not shrink that number on its own. It makes it visible deal by deal, while there is still time to act.

How do you build a close date push counter in HubSpot?

You need two custom deal properties and one deal-based workflow. The workflow re-enrolls a deal every time its close date changes, adds one to a counter and remembers the date it just saw, so the next change can be compared with it. Plan on about an hour, including a test on a handful of deals before you switch it on for the whole pipeline.

Create the properties first, in your deal property settings:

1. Close date changes (number). The counter. Start it empty.
2. Last recorded close date (date picker). The value the workflow saw last time. It lets the workflow skip the first date a deal ever gets, and it gives you a before-and-after pair when you audit a deal.

Then build the workflow:

1. Create a deal-based workflow. Set the enrollment trigger to Close date is known.
2. Turn on re-enrollment for that trigger, so a deal re-enrolls each time its close date gets a new value. Without re-enrollment the workflow runs once per deal and the count never passes one.
3. Add a filter that leaves out deals in closed won and closed lost stages (the first trap below explains why).
4. Add an if/then branch on Last recorded close date. If it is unknown, the deal is getting its first close date: copy Close date into Last recorded close date and stop. Do not count it.
5. Otherwise, increase Close date changes by 1, then copy Close date into Last recorded close date.
6. Optional: add a second branch that notifies the deal owner’s manager when Close date changes reaches 3.

Before you turn it on, decide what to do about history. The workflow counts changes from the day it goes live. For open deals that already slipped, a one-time export of property history gives you a starting count, or you can accept a clean start and read the counter from next quarter onward.

Four things that inflate the count

A naive counter adds one every time Close date changes. Close date changes for reasons that have nothing to do with a deal slipping, and each one adds noise that makes reps distrust the number. Four sources cause most of it, and the workflow above handles the first two. The last two need a decision from you.

• The closing automation. When a deal moves into a closed won or closed lost stage, HubSpot sets Close date to the current date, per its default deal properties documentation. You can turn that automation off in pipeline settings, but many teams keep it. A counter without the closed-stage filter adds a push to every deal at the moment it closes, won or lost.
• The first date. New deals often get a close date at creation, from the rep or from a pipeline default. That is a forecast, not a push. The Last recorded close date branch skips it.
• Pull-ins. A deal that moves earlier is good news, and the simple counter scores it like a slip. If you only want pushes, you need a step that compares the new date with the old one. In the portals I have worked in, that has meant a custom code action, which needs a Data Hub (formerly Operations Hub) Professional or Enterprise subscription. In my experience the simple count is usually good enough, because pull-ins tend to be much rarer than pushes.
• Bulk edits and integrations. A manager who bulk-moves twenty close dates at quarter end adds twenty pushes in one click, and an integration that rewrites Close date can add more. Property history shows the source of each change, so you can spot these. Decide whether a bulk move counts as a push (I would count it: the dates still moved) and tell the team.

What should you do when a deal reaches its third push?

Treat the count as a trigger for a conversation, not as a verdict on the rep. What I recommend now is a simple ladder: a first push needs a note on the deal, a second push gets a question from the manager in the next one-to-one, and a third push moves the deal to best case at most, whatever its stage says, until a buyer-side date replaces the rep’s estimate.

The third-push rule follows the evidence above: past three moves, the win rate falls hard. It also takes pressure off the rep. Moving a deal to best case on its third push is a rule, not a judgment the manager has to defend in the room.

The conversation itself matters more than the category change. A question I often ask on a deal like this is what the buyer has done since the last date was set, as opposed to what the rep has done. After a deal gets pushed out the third time, I start reading between the lines of the rep’s activities. The rep will tell you, “They were really excited, I have a good feeling about this,” and then you watch the close date slip three months in a row, each time with its own excuse. Dig into their meetings, emails and calls with the prospect, and you will often find a pattern: they failed to uncover context early because the first meeting went so well. Decision-making power, budget or a real desire to solve the problem are easy to overlook when the prospect seems excited. This is why companies run sales methodologies, but even those companies often stop enforcing them, and then wonder why their forecasts constantly slip.

Keep the counter out of compensation and out of public rankings. Once a number like this becomes a scorecard, reps learn to avoid moving the date, and the dates stop meaning anything. We covered that dynamic in your pipeline review is teaching your reps to lie.

The count by owner shows a team pattern

Run the same counter as a report and it stops being about single deals. A deal report grouped by owner, with the average of Close date changes on open deals, shows who tends to set optimistic dates. Grouped by deal stage, it shows where deals stall. Grouped by source, it shows which channel brings in deals that drift.

When the pushes trace back to optimism after a strong first meeting, the fix is how the first date gets set, which why sales reps are bad at forecasting covers in more depth. For how close date drift feeds the HubSpot forecast itself, see why is my HubSpot forecast always wrong.

Count the pushes, or keep trusting the stage

You can keep reading the pipeline the way many teams do, by stage and by what the rep says this week. Or you can let every deal carry its own history, and accept that the forecast will look smaller the first quarter you do it. The second option costs an hour of setup and some uncomfortable one-to-ones. The first one costs you the deals you could have saved while they were only on their second push.

If you want to see how close date drift, stale deals and the rest of your pipeline data look in your own CRM, book your free diagnostic.