Check 8 date and score rules before you trust a weekly forecast number.
Key takeaways
- HubSpot updates the Close date value to today's date when a record moves to a closed stage, according to HubSpot.
- HubSpot clears the previously set Close date value when a ticket moves from a closed stage to an open stage, according to HubSpot.
- HubSpot may display an updated deal score within up to 6 hours if the new score is significantly different by ±3%, according to HubSpot.
- Pipedrive allows users to edit the won time date by clicking the pencil icon next to the won time value after adding the column, according to Pipedrive.
- Freshworks states that enabling date restrictions does not prevent admins or API updates from setting past dates, according to Freshworks.
How close date automation and deal scores impact weekly forecast accuracy
The weekly forecast relies on two distinct data streams within your CRM stack: the timing of deal closure and the probability of that closure. When these elements drift due to manual errors or misconfigured automations, the final number presented to leadership loses its reliability. You must verify that the system updates these fields automatically and consistently before you trust the aggregate pipeline value.
HubSpot documentation explains that consistent, automated close dates across pipelines support more accurate forecasting and reporting, limiting the need for manual corrections when records change stages, according to HubSpot. This automation reduces the risk that a rep manually entering a date creates a mismatch between the actual deal stage and the date recorded in the system. If the date does not update when the stage changes, your forecast buckets for the current week or month become inaccurate. You should confirm that your specific object settings trigger date updates automatically upon stage transitions.
Simultaneously, the deal score provides a quantitative measure of deal health. HubSpot notes that deal scores predict the probability of winning the open deals in your pipelines, which can help teams to prioritize and focus on deals with higher chances to close, according to HubSpot. For existing deals, the score will be updated if the new score is significantly different (±3%), and the updated score may appear within up to 6 hours, according to HubSpot.
HubSpot: managing close date automation and score updates
HubSpot allows you to adjust automation settings on each pipeline to stop setting the close date, or to clear the close date when a record moves to an open stage, according to HubSpot. This configuration provides a specific mechanism to control how dates are handled during stage transitions. When you move a record to a closed stage, the Close date value will be updated to today's date, according to HubSpot. This rule applies specifically to the transition into a closed state. If a ticket is moved from a closed stage to an open stage, the previously set Close date value will be cleared, according to HubSpot. Note that this clearing behavior is described for tickets in the source documentation.
Regarding deal scores, HubSpot states that for existing deals, the score will be updated if the new score is significantly different (+/- 3%), according to HubSpot. This threshold determines when a recalculation is triggered for existing records. If the new score is significantly different (±3%), the updated score may appear within up to 6 hours, according to HubSpot. This lag time is a critical factor to consider when verifying data before a forecast call.
To verify these rules in your environment, check the pipeline-specific automation settings to confirm whether close date clearing is enabled for open stages. Confirm that the "closed stage" rule updates the date to today's date as described. For scores, test a deal with a predicted score change greater than 3% and observe the update time to confirm the 6-hour window. Do not assume that all CRM systems clear dates upon reopening; HubSpot's documentation specifically describes this behavior for tickets moving from closed to open stages. The 3% threshold and 6-hour lag are specific to HubSpot's deal score functionality and should not be applied to other platforms without verification.
The Current Score in HubSpot is the deal's current score between 0 and 100, according to HubSpot.
Ensure your team is aware that the 6-hour lag means real-time score verification is not possible immediately after a significant change. Plan your forecast data pull to account for a wait of up to 6 hours when a HubSpot deal score is significantly different (±3%). The automation settings on each pipeline allow for granular control, so verify each pipeline individually if your organization uses multiple pipelines. The distinction between tickets and deals in the date clearing rule is important; the source specifies tickets for the clearing action, so verify if this applies to your deal objects as well.
Pipedrive and Freshworks: manual overrides and date visibility
Verify how manual edits and field configurations interact with your forecast data in Pipedrive and Freshworks. These systems allow specific manual interventions and administrative settings that directly impact the dates and scores you present.
In Pipedrive, a deal is marked as WON when it is closed and a sale was made, or the intended marketing goal was met, according to Pipedrive. This definition establishes the baseline for when a deal contributes to your won metrics. See Open, won, and lost stage rules in 4 sales tools. To adjust this timestamp, you must first add the won time column to your view. After you add the won time column, edit the date by clicking the pencil icon next to the won time value, according to Pipedrive. This manual editing capability allows you to correct the won time if it was entered incorrectly or if the deal closed on a different date than initially recorded. Ensure that your team knows this manual override exists so that discrepancies between the actual close date and the recorded won time can be resolved before the forecast call.
In Freshworks, you can configure the field properties such as making it a required field, read-only field, unique field and also opt to display the field in the quick add form, according to Freshworks. These configuration options determine how users interact with deal fields during data entry. For example, making a date field required ensures that a close date is always present, while making it read-only prevents accidental changes. See Required-field rules in 4 tools before stage change. However, administrative controls have limits. Enabling the above does not prevent admins or API updates from setting past dates, according to Freshworks. Review your API integrations and admin permissions to understand which updates might set past dates.
Check your Pipedrive list views to confirm the won time column is visible and editable. Verify that your Freshworks date fields are configured as required if they are critical for forecasting. Audit your API connections to ensure they are not inadvertently setting past dates that could distort your weekly forecast. These manual overrides and configuration settings are the final layer of control before you present your numbers.
Microsoft Dynamics: visualizing opportunity limits in pipeline views
When reviewing the pipeline view in Dynamics 365 Sales, the bubble chart serves as a visual summary of opportunity data. However, this visualization has a specific constraint that revenue leaders must account for before presenting forecast numbers. According to Microsoft, to maintain clarity, the bubble chart shows only the first 50 valid opportunity entries. This limit means that if your pipeline contains more than 50 valid opportunities, the chart will not display the full scope of your active deals. You must verify whether your current pipeline volume exceeds this threshold to determine if the visual representation is sufficient for your weekly forecast review.
The configuration of this view relies on specific settings within the deal manager. According to Microsoft, it lets users read the deal manager settings configuration to show the bubble chart in the pipeline view. This setting determines whether the visual component appears in your standard pipeline layout. If the bubble chart is not visible, check the deal manager settings to ensure the configuration is enabled. This step is necessary to confirm that the visual data source is active before you rely on it for quick assessments during the forecast call.
Beyond the visual limit, the integrity of the data feeding into these views depends on consistent field values. A mismatch in status values can lead to errors in opportunity closing and pipeline reporting. According to Microsoft, make sure matching values exist for both the Status Reason field on the Opportunity entity and the opportunitystatuscode attribute on the Opportunity Close entity. This requirement ensures that when an opportunity is closed, the system correctly maps the status reason to the corresponding close entity attribute. If these values do not match, the pipeline view may not accurately reflect the state of closed deals, potentially distorting your historical and current forecast accuracy.
A filled reference table of date and score rules by publisher
The following table summarizes the eight specific configuration and behavior rules that impact forecast accuracy. Each row corresponds to a distinct rule identified in the publisher documentation, ensuring that the data points used in your weekly forecast are verified against the correct source behavior.
| Publisher | Rule ID | Specific Behavior or Limit | Source Context |
|---|---|---|---|
| HubSpot | 1 | When you move a record to a closed stage, the Close date value will be updated to today's date. | HubSpot |
| HubSpot | 2 | When you move a ticket from a closed stage to an open stage, the previously set Close date value will be cleared. | HubSpot |
| HubSpot | 3 | Current Score: the deal's current score between 0 and 100. | HubSpot |
| HubSpot | 4 | If the new score is significantly different (±3%), the updated score may appear within up to 6 hours. | HubSpot |
| Pipedrive | 5 | After you add the won time column, edit the date by clicking the pencil icon next to the won time value. | Pipedrive |
| Pipedrive | 6 | A deal is marked as WON when it's closed and a sale was made, or the intended marketing goal was met. | Pipedrive |
| Freshworks | 7 | Enabling the above does not prevent admins or API updates from setting past dates. | Freshworks |
| Microsoft | 8 | To maintain clarity, the bubble chart shows only the first 50 valid opportunity entries. | Microsoft |
Verify that your team’s access to these settings aligns with the behaviors listed above before the next forecast review.
Illustrative example of a weekly check
A weekly review covers 50 open deals. 20 have a close date this week. Treat 10 of those 20 as the group you will defend on the call, and leave the other 10 in the open pipeline. Read scores on a scale from 0 to 100. Keep a deal scored 80 on the priority list. Give a deal scored 50 one more look before you speak. Check the close date on the 10 you will defend, then check the score, and only then say the number out loud. These round figures are illustrative. They show the order of the check and do not describe a named company, person, or product.
Do this before the forecast call
Review the close date automation settings in your CRM admin panel and verify the won time visibility in your list views to ensure manual corrections are possible. Do that check today, before the forecast call.
FAQ: how to verify close date and deal score rules before the weekly forecast call
What happens to the close date when a HubSpot record moves to a closed stage?
When you move a record to a closed stage, the Close date value will be updated to today's date. This behavior is part of the close date automation for objects, as described by HubSpot.
How long might it take for a HubSpot deal score to update after a significant change?
If the new score is significantly different (±3%), the updated score may appear within up to 6 hours. This lag applies when using deal scores to predict likelihood to close, according to HubSpot.
Can Freshworks admins set past dates on deals through the API even if restrictions are enabled?
Enabling the above does not prevent admins or API updates from setting past dates. This rule applies to deal fields and customization in Freshsales, as stated by Freshworks.
How many valid opportunity entries does the Microsoft Dynamics bubble chart display?
To maintain clarity, the bubble chart shows only the first 50 valid opportunity entries. This limit is part of fixing opportunity closing and pipeline errors in Dynamics 365 Sales, according to Microsoft.
How does Pipedrive allow users to edit the won time of a deal?
After you add the won time column, edit the date by clicking the pencil icon next to the won time value. This manual editing process is documented in the Pipedrive knowledge base, according to Pipedrive.