Forecast definitions
What forecast categories and weighted deal amounts mean in tools like HubSpot and Pipedrive, and how to use them consistently.
A forecast only adds up when everyone uses the same words the same way. These guides explain categories such as Pipeline, Best Case and Commit, show how each sales tool works out a weighted amount, and give you a worksheet for agreeing on the rules.
Forecast definitions
Renewal close dates: 2 windows for Closed Won and Closed Lost
Set Closed Won and Closed Lost for renewals with two date windows: an early window before the renewal date and a 15-day window after it.
SMS length limits: 3 checks before a follow-up
Check three SMS length limits before sending a follow-up, then test personalization and the full message in your platform's preview.
Small sales team CRM: 4 checks before you choose
Choose a CRM for a small sales team with four trial checks: team size, setup time, pipeline shape and room to scale. Compare claims with results.
Okta admin console session timeout: 6 checks
Review Okta admin console session lifetime, idle time, allowed ranges and popup timing with six checks and a written record of each decision.
SUMIF totals by deal stage: 5 forecast checks
Check deal totals by stage with SUMIF: align ranges, test criteria, compare a hand-added sum, review text limits and use SUMIFS for extra conditions.
Rollup limits: 4 checks before a deal total column
Microsoft's 4 published rollup limits and relationship rules that decide whether a deal total column can be trusted in a forecast review.
Recognized and deferred revenue: 3 invoice figures
Stripe's example splits a 36 USD invoice into 22 USD recognized by end of January and 14 USD deferred to February, shown as three figures.
SKU rules: 3 checks for annual and multi-year deals
Check annual-payment SKUs, renewal terms and multi-year ramp quotes against GitLab's rules before carrying a quoted amount into the forecast.
Gong to-do rules: 7 checks before your deal review
Check Gong to-do expiry, reply handling and out-of-office snoozes with seven practical steps before reporting paused contacts in a deal review.
Failed payment: 2 subscription changes to check
Check two cases where a failed payment blocks a subscription from starting or changing, then compare billing records before counting the booking.
Commission payout mistakes: 4 checks before quarter close
Four commission payout mistakes to check before quarter close, each tied to a state wage rule on timing, deductions, returned pay, or plan terms.
Sales tool review figures: 4 checks before you trust one
Four checks for sales tool review figures: read the rating with its review count, the average setup time, the analyst scope, and each vendor claim.
5 lead rules to settle before a deal enters your pipeline
Five shared lead rules to settle before a lead becomes a deal: definition, entry, conversion, ownership, and disqualification.
Dynamics 365 Sales scoring needs 2 deal-count minimums
Dynamics 365 Sales scoring needs 40 won and 40 lost closed deals, plus 40 in the last stage for stage-level models. Check your history against both.
Hold deals at $10,000 or more: 8 steps to set the rule
Set a deal value threshold, send deals at or above it to a manager for sign-off before any proposal goes out, and keep smaller deals moving.
Daily flow email caps: 3 domain rules to check
Three Gong rules decide how flow emails to one company domain count toward your daily cap, and how to plan a multi-contact follow-up around them.
AVERAGEIFS errors that skew average deal size: 4 checks
Four AVERAGEIFS mistakes can quietly skew average deal size by segment. Check your export, amounts, segment names and blanks before you report it.
Currency amount examples: 3 checks before a deal total
Stripe's examples give the amount value 500 for JPY, ISK and UGX. Check each currency and amount value beside the deal amount before you add a total.
Commission automation figures: 5 to test on your cycle
Five published commission automation figures explained plainly, with a test for each against your own quarterly cycle time and process.
CRM seat prices to check before adding a seat: 5 steps
Published CRM price figures from Copper and Nutshell, their trial terms, and 5 steps to work out your own seat cost before you add a seat.
Stage report audit: 4 checks before weekly review
Four checks for a stage report audit: configured stages, the reporting table, pipeline structure, and funnel counting before the weekly review.
Deal label caps: 100 on one deal, 1000 in an account
Pipedrive caps a deal at 100 labels and an account at 1000; HubSpot caps association labels at 50 for each object pair. Check these caps before review.
What 100 percent means in 4 tools before the weekly call
See what 100 percent means in 4 sales tools before the weekly call, in one filled table, so 100 on an open deal is not a closed deal.
Forecast category rules in 4 tools before the call
See how Freshsales, HubSpot, Microsoft, and Close place a deal in or out of the weekly forecast, including the five-category cap and omitted labels.
Sales calculation tools: 4 options for deal arithmetic
Compare documented calculation rules for Airtable, Google Sheets, Freshsales, and Pipedrive to select the right deal arithmetic for your forecast.
CRM validation: 4 tools to govern forecast data entry
Compare documented validation controls in Microsoft, HubSpot, Freshworks, and Zoho to govern forecast data entry without treating them as interchangeable.
Archive item cap: 300,000 before the weekly board
Pipedrive counts archived items toward a 300,000 cap. Five fields lock on an archived deal, and HubSpot, Close, and Odoo delete or restore rules differ.
File size limits: 8 checks before evidence uploads
Check 8 attachment and storage limits across Help Scout, SupportBee, Freshdesk, and Atlassian before sending deal evidence for forecast calls.
Verify 8 catalog steps for accurate forecast totals
Check 8 catalog and pricing rules from four CRM vendors to ensure product line items calculate correctly before they impact your pipeline totals.
Product catalog: 7 rules for the weekly forecast
Review 7 product catalog rules across three sales tools, covering product records, access permissions, pricing, and deal adjustments.
Activity linking: 8 rules for deals and visibility
Compare 8 activity rules in Pipedrive, HubSpot, and Microsoft, covering deal links, user access, property storage, source detail, and creation times.
Stage count warnings at 10, above 8, and below 3
Close says a 10-stage pipeline brings update fatigue and noisier data. Above 8 it gets bureaucratic. Below 3 you lose progress tracking. Freshsales needs 3.
Sales data imports: 5 field checks before upload
Check 5 CRM field rules before importing sales data: length limits, type changes, API validation, visibility, and permissions for managing fields.
Log seller emails to the right deal: 4 CRM rules to check
Check four CRM rules for logging seller emails: routing, deal attachment, size limits, and sync timing to fix your deal reviews.
Forecast period rules: read 4 before the weekly number
Four forecast period rules from HubSpot, Microsoft, Pipedrive, and Freshsales show which time bucket sits behind the weekly revenue number.
Where a software deal came from across 4 tools
See how HubSpot, Pipedrive, Close, and Zoho store each deal source, then copy the stored value before you rename a channel.
Line-item rounding rules in 4 sales tools
Compare line-item rounding in HubSpot, Microsoft, Pipedrive, and Close, including two HubSpot steps and a 0 to 4 precision range.
Deal and quote line-item rules from 4 publishers
Compare the line-item rule each of 4 publishers states for deals and quotes, including separate record IDs, a freeze after publish, and product association.
Weekly pipeline export checks for 4 vendors
Match your weekly pipeline export to the review, then apply the download windows and row limits documented for 4 vendors.
Export a weekly pipeline snapshot in 4 systems
Save a weekly pipeline snapshot in four systems by setting filters, fields and format, then downloading before the access window ends.
Recover deleted sales records with 4 retention checks
Triage missing sales records by checking deletion type, recovery window, access permissions, and related-data limits across four CRM publishers.
Choose a deal field type: 4 systems and storage rules
Select the right data type for a new recurring qualification field. Compare storage rules and limits across four sales systems.
Bulk-edit sales records: 4 checks before saving changes
Verify selection, save old values, confirm update mode, and check required-field rules before saving bulk sales record corrections.
Weighted deal amount: 5 fields to check HubSpot, Pipedrive
Weighted deal amount in HubSpot and Pipedrive: both formulas in one table, plus Microsoft's 0 to 100 likelihood field and a 5-field worksheet.
Pipeline, Best Case, Commit: Forecast Categories Explained
Define forecast categories, check amount basis and period, and use a blank policy worksheet to reconcile rollups without double counting.