Forecast period rules: read 4 before the weekly number

Before the weekly number is read aloud, confirm which time bucket the forecast screen is using, as each tool defines that bucket differently. The four period rules below come from one source each: HubSpot, Microsoft, Pipedrive, and Freshsales.

• HubSpot applies one period to all pipelines. The forecast period indicates the time period used for revenue goals and forecast submissions for all pipelines, according to HubSpot.
• Editing the HubSpot period resets data. If you edit the forecast period, the forecastable revenue goals and forecast submission will be reset for all pipelines, according to HubSpot.
• Pipedrive uses the expected close date. The forecast view projects revenue by using the expected close date of the deal, according to Pipedrive.
• Freshsales uses month, quarter, or close date. Committed deals are those sales reps are confident of closing in the month or quarter, or by the expected close date, according to Freshsales.
• Microsoft documents specific calendar shapes. One shape uses the most-widely used Gregorian calendar with 12 weeks in each quarter, according to Microsoft. These figures are calendar shapes, not sales results.

The weekly number you read aloud is not a free-floating total; it is the sum of deals that fall inside a specific time window. Each sales tool defines that window using different logic, and the label on your screen tells you which logic is active. If you treat the number as "this month's revenue" when the tool is actually projecting by a different date field, the number you report will not match the date you claim. See Pipeline, Best Case, Commit: Forecast Categories Explained.

HubSpot defines the window as a single setting that applies across the board. This is a system-level choice: one period, one set of goals, one set of submissions. The period is the container for the entire forecast, not a filter you apply after the fact.

Pipedrive takes a different approach. The forecast view projects your revenue by using the expected close date of the deal, according to Pipedrive. Here the bucket is defined by the deal's own date field. An open deal is placed when its expected close date falls in that period, and a won deal uses the won date instead. It reads the date on each open deal and places it accordingly. This means two deals with different expected close dates can sit in different forecast periods.

The following table lists the specific period rule for each of the four publishers. Each row names the publisher and defines the period rule as stated in its source.

The 4 in the title refer to one period rule from each of these four publishers: HubSpot, Microsoft, Pipedrive, and Freshsales. Microsoft's 28 days, 35 days, 13 months, and 364 days are calendar shapes on that page, not a result from a customer.

The "Forecast period rules and scheduling formats | Microsoft Learn" page lists multiple calendar shapes rather than a single fixed month. One shape uses the most-widely used Gregorian calendar with 12 weeks in each quarter, according to Microsoft. This structure divides the year into quarters where each quarter contains exactly 12 weeks.

Another option on the same page describes broadcast calendar months. These months have either 28 days or 35 days, according to Microsoft. This specific day count applies to the broadcast calendar shape and does not apply to every calendar shape listed on the page.

Microsoft states: "This pattern divides a year into 13 months of 4 weeks each, with three 3-week months and one 4-week month in each quarter," according to Microsoft. The 13-month structure is a scheduling format for organizing time periods, not a sales result or a performance metric.

A fourth pattern divides a year into four quarters of 13 weeks each, according to Microsoft. Each quarter in this pattern contains two 4-week months and one 5-week month. The 13-week quarter is one of several available shapes for defining forecast periods.

The page also notes that the 4-4-5/4-5-4/5-4-4 and 3-3-3-4/3-3-4-3/3-4-3-3/4-3-3-3 calendars have only 364 days (7 days × 52 weeks), according to Microsoft. This 364-day count is a property of the specific calendar shapes mentioned, not a standard calendar year length.

These figures—12 weeks, 28 days, 35 days, 13 months, and 364 days—are calendar shapes documented on the Microsoft Learn page. They define how time is segmented for forecasting purposes. They are not sales results, win rates, or performance benchmarks. When reviewing the weekly number, confirm which specific calendar shape is active in your system. The period rule determines which deals appear in the forecast view. Check the current shape setting before interpreting the number as a monthly or quarterly figure. The shape choice affects the time bucket used for aggregation. Verify the active shape in your system settings to ensure the weekly number aligns with the intended period.

This single setting applies across the entire system rather than varying by individual pipeline. When you configure this tool, you are selecting one specific time bucket that will govern how revenue goals and forecast submissions are calculated everywhere in the platform.

To set either a monthly or quarterly forecast period, in the "Select the forecast period for all pipelines" setting, click the dropdown menu and select a time period, according to HubSpot. The interface presents these two options as the available choices for the global period. You choose one of these two shapes, and that choice becomes the standard for every pipeline in the account. There is no separate period setting for individual pipelines; the selection made in this dropdown menu is the only one that applies.

A critical warning accompanies this setting. If you edit the forecast period, the forecastable revenue goals and forecast submission will be reset for all pipelines, according to HubSpot. This is not a minor adjustment; changing the period triggers a reset of both the goals and the submissions. Before the weekly number is read aloud, verify that the period currently set matches the period you intend to report. If the period is wrong, correcting it will wipe the existing goals and submissions, requiring them to be re-entered.

Check the dropdown menu in the "Set up the forecast tool" page to confirm which period is currently active. If you need to change it, understand that the reset will affect every pipeline simultaneously. This single point of control means that one mistake in the period selection impacts the entire forecast structure. The period is the foundation for the revenue goals and submissions, so getting it right before the meeting is essential.

The deal forecast view calculates revenue projections based on specific date fields assigned to each deal record. For deals that remain open, the system uses the expected close date to project revenue. According to Pipedrive, the forecast view projects your revenue by using the expected close date of the deal. This date represents the point in time when you expect a deal to be marked as WON or LOST. When a deal is still active in the pipeline, this future date determines where the deal’s value appears in the forecast timeline.

Once a deal is marked as WON, the date logic changes. According to Pipedrive, if a deal is marked as WON, that deal’s won date will be used instead of the expected close date for calculating value in the forecast view. The won date replaces the expected close date in the calculation. This shift means the deal no longer projects based on a future expectation but on the won date used instead of the expected close date. The forecast view adjusts the revenue attribution to reflect this closed status.

Understanding which date drives the number helps clarify why a deal might appear in one period or another. If a deal’s expected close date falls in the current month, it contributes to that month’s projection while open. If it is won before the expected close date, the won date becomes the reference point for the forecast value. The transition from expected to actual date is the key mechanism for how closed-won deals are treated in the revenue projection.

Check the expected close date on each open deal to confirm it aligns with your actual close timeline. For a won deal, the won date is used instead of the expected close date when calculating forecast value. These checks ensure the date fields driving the revenue projection match the actual status of each deal. See Close date change log: why the date moved.

The forecast screen displays a specific time bucket that defines which deals are included in the current number. Freshsales describes committed deals as those sales reps are confident of closing in the month or quarter, or by the expected close date, according to Freshsales. The same source notes that projecting revenue for a given week, month, or quarter is useful for assigning and fulfilling sales quotas, according to Freshsales. Because different tools use different date fields to place deals in these buckets, the period visible on your screen today may differ from the period used in last week’s report.

One weekly number is read in week 4 of a quarter that holds 12 weeks. Two open deals with an expected close in week 4 sit in that bucket. One open deal with an expected close in week 8 sits later. One won deal uses a won date in week 2.

Write down the period showing on the forecast screen and the date field that put each deal in that period.

Which period does HubSpot apply to every pipeline?

The forecast period indicates the time period used for revenue goals and forecast submissions for all pipelines, according to HubSpot.

Which date does Pipedrive use for an open deal in the forecast view?

This date determines the time bucket for open deals in the projection.

Which date does Pipedrive use after a deal is won?

If a deal is marked as WON, that deal’s won date will be used instead of the expected close date for calculating value in the forecast view, according to Pipedrive. The system switches the reference date upon the status change.

What do 12 weeks and 364 days refer to on Microsoft's period page?

The 12 weeks in each quarter figure refers to a shape using the most-widely used Gregorian calendar, according to Microsoft. These figures describe calendar shapes and scheduling formats, not sales results or performance metrics.