In short: A changed opportunity close date is a timing signal, not proof that a deal is lost or that revenue will arrive later. Compare a fixed starting cohort with its current state, count deals moved beyond the period, and record the buyer or process reason. This shows whether forecast timing is becoming less reliable before the team reacts by adding demand or changing coverage targets.
The current CRM view answers, “Where do open opportunities sit now?” It does not always answer, “Which deals were expected this quarter, and how many moved out after the quarter began?” That second question requires a baseline and a history of changes. Without them, a report can hide repeated pushes or confuse a deal that was always expected next quarter with one that just slipped.
1. Define the close-date question and its time window
Write the question in one sentence before building a report. For example: “Of the opportunities open on the first day of this quarter with a close date in this quarter, how many moved beyond quarter-end, and what changed during the quarter?”
That wording sets two different clocks:
- The close-date window: the period the opportunity was expected to close in, such as the current quarter.
- The change window: the period in which the close-date edit happened, such as quarter start through today.
Keep both dates visible in the report. If you only filter on opportunities whose close dates are currently in the quarter, you will omit deals that were in the quarter at the start and then moved out. If you only look at edits made this week, you may miss the baseline that tells you whether those deals were actually pushed.
Use one consistent cutoff, time zone, and definition of “open.” A snapshot taken at 9 a.m. on the first day of the quarter is not identical to a report pulled at the end of that day after several records have changed.
2. Separate pushed dates from other pipeline movement
For a close-date review, define a pushed opportunity as one that was open at the baseline, had a close date inside the selected period, and had that date moved outside the period during the review window. Count each opportunity once in the push rate, even if it was edited more than once. Keep the edit count as a separate diagnostic.
Track related movements separately:
- A pulled-in opportunity moves from outside the period to inside it.
- A won or lost opportunity exits the open pipeline; it is not merely a date push.
- A stage or amount change can alter forecast meaning without changing the close date.
- A new opportunity created after the baseline was not part of the original cohort.
HubSpot’s Deal push rate report focuses on deals whose close date moved from inside the selected timeframe to outside it. Its Deal change history report covers a broader set of deal changes, so the two views should not be treated as the same metric. Salesforce also exposes opportunity history for close-date changes. Confirm the rules and fields in your own CRM before comparing reports across teams or tools.
3. Preserve the starting value and change history
For each opportunity, keep the original close date, current close date, edit timestamp, editor, owner, stage, and amount at the baseline. Add the amount at the time of review if you want to understand the current forecast exposure, but label it separately. Otherwise, a changed amount can make a date movement look like a change in pipeline value.
Salesforce’s standard Opportunity Stage History records changes to Amount, Probability, Stage, and Close Date, with details about the change and who made it. Other field history depends on what an administrator has chosen to track. Field history starts only after tracking is enabled, so an organization without a usable baseline should start recording one now instead of reconstructing old values from memory.
If your CRM does not retain the needed history, use a dated export or snapshot before the next reporting period. Store its cutoff time, filters, and included fields. The guide to setting an as-of date before comparing pipeline reports explains why the same snapshot rule matters when teams compare pipeline over time.
4. Report a rate, a deal count, and the value moved
Use an explicit denominator so the metric stays interpretable:
Close-date push incidence = eligible baseline opportunities moved beyond the period ÷ eligible baseline opportunities.
Report the numerator and denominator alongside the percentage. Also show the number of separate date edits, the baseline amount attached to pushed deals, and the current amount as a second view. Baseline amount makes period-to-period comparisons steadier; current amount helps a manager understand today’s exposure. Do not add both amounts together.
Suppose 20 open opportunities were expected to close this quarter at the quarter’s start. Four moved to a later quarter. The push incidence is 4 of 20, or 20%. If those four opportunities were edited six times, report four pushed deals and six date-change events. The second number reveals repeated movement without inflating the number of deals affected.
Call the value “pipeline moved out” or “baseline value of pushed opportunities.” It is not realized revenue, a loss, or a guarantee that the same value will close next quarter. For definitions of pipeline coverage and pipeline velocity, keep those separate: they answer different questions about volume, timing, and deal quality.
5. Look for patterns before judging the forecast
Review pushed opportunities by baseline stage, owner, segment, deal-size band, new versus expansion, and reason. Compare multiple periods with the same cohort and date rules. A single quarter can move because of seasonality, a change in deal mix, or a few unusually large opportunities.
Ask whether the new date has evidence behind it. Did the buyer confirm a decision date? Is a procurement, security, legal, or budget step still open? Is a next meeting scheduled with the person who owns that step? A close date copied forward without a new buyer action is different from a date updated after the buyer moved an agreed procurement review.
Do not reward teams for leaving dates unchanged when the evidence no longer supports them. Do not use one push percentage as a universal performance target or as a stand-alone ranking of salespeople. Honest date changes can improve forecast quality. Repeated late-stage pushes, missing next steps, and the same unaddressed blocker across many opportunities are stronger prompts for investigation.
6. Turn each reason into a useful next action
Use a short reason list that matches your sales process, with a note for context. Examples include buyer timing change, procurement or legal delay, security review, internal approval, no confirmed decision date, and CRM correction. Avoid a long list of vague labels that teams can use interchangeably.
For each moved opportunity, record the next buyer action and its owner. Then choose a response that fits the evidence: confirm the new timeline, schedule the next step, involve a specialist, revise a forecast category, return the opportunity to nurture, or close it as lost when that is what happened. A date edit alone should not trigger more marketing spend; first establish whether the bottleneck is demand, qualification, buyer process, or internal follow-up.
At the process level, cluster reasons by stage and segment. If several qualified opportunities pause at security review, document what information is missing and who can provide it. If dates move because no decision meeting is booked, fix the next-step routine. If the CRM change log is incomplete, improve capture before making a performance claim from the report.
7. Make the review part of the forecast cadence
Take a consistent snapshot at the start of each forecast period, then compare it with the current opportunity history before the forecast meeting. Bring a short list of the largest or most repeatedly pushed deals, not just a percentage. Include pulled-in deals, wins, losses, new opportunities, and stage movement as separate lines so the team can see how the pipeline changed.
Use the review to improve assumptions and follow-up. The purpose is not to force every opportunity to keep its original date. It is to make changes visible early enough for the right owner to update the buyer plan, forecast, or demand decision. The monthly revenue marketing review can connect timing changes with campaign and pipeline decisions.
Close-date change review worksheet
- Baseline cutoff and time zone: ______
- Close-date period and change window: ______
- Baseline open opportunity cohort: ______
- Pushed deals / eligible baseline deals: ______ / ______
- Separate date-change events: ______
- Baseline value moved out / current value: ______ / ______
- Breakdowns to review: stage, owner, segment, deal size, new or expansion
- Reason and evidence for each change: ______
- Next buyer action, owner, and date: ______
- Snapshot or history source and known gaps: ______
- Decision for the forecast or demand plan: ______
A close-date review is useful when the starting cohort, comparison window, and change history are clear. It helps the team see timing risk while keeping date movement distinct from lost revenue, pipeline coverage, and sales-cycle speed.
If close dates change across teams or connected CRM tools without a shared baseline, map the reporting fields, history, and follow-up owners.
Sources and scope
- HubSpot: Create sales reports in the sales analytics suite — definitions for Deal push rate, Deal change history, and related deal reports.
- Salesforce: Opportunity History — opportunity history for Amount, Probability, Stage, and Close Date changes.
- Salesforce: Field History Tracking — tracking begins when an administrator enables it.
CRM report names, available history, retention, and permissions vary by product, edition, and configuration. Confirm the fields and report definitions on your account before using the metric for forecast or performance decisions. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.