Use HubSpot's two example risk score rules to flag deals before the review and choose which ones to discuss first.
Key takeaways
- Mark each open deal whose chosen reference date is more than 14 days old.
- Count Close Date pushes from your own records.
- Total the points for each flagged deal, and treat the total as your team's working tally rather than a published score.
- Check the records behind each flag before drafting follow-up emails.
- Read survey percentages as background only, not as measures of your own pipeline.
Why risk scores matter before a deal review
A weekly deal review goes faster when the group agrees beforehand on which deals to raise first. Two simple flags give the team a shared starting list, and that list is easier to discuss than one built from memory. The two rules below are only a small part of what a team could track, so keep the list short enough to check in one sitting.
Decide the order of discussion before the call starts. Write the flagged deals at the top of the sheet and the unflagged deals beneath them, then have the group work down the sheet in that order. The same sheet can carry the tally, so nobody has to rebuild the list during the meeting.
A revenue operations page makes a broad point about the same problem: according to Captivateiq, "It's more crucial than ever to ease administrative burden to help your team focus on strategy and drive bottom line growth."
Rule 1: activity age
According to HubSpot, "14 Days Without Activity Score: this formula calculates that if the time since the last note update (or last activity date property) is greater than 14 days, 10 risk points will be added."
The source names two dates as the reference point: the last note update and the last activity date property. Before you count anything, decide which of the two your team will use, and write that choice at the top of your review notes. Using one date for every deal keeps the flag comparable from week to week.
For each open deal, count the days since that date and record the result. A deal at exactly 14 days is not marked under this example. Put the marked deals at the top of the discussion list, and discuss them before deals that carry no flag.
Sort the open deals by the date you chose, oldest first, and count the days down that list in one pass. Record the day count as a number next to each deal, not only the flag. A flag on its own does not show how far past the limit a deal sits, so the count gives the group more to discuss.
Keep the assigned points as a fixed value in your tally rather than adjusting them by feel. A fixed value lets the group compare one flagged deal with another without debating the weight each time.
Rule 2: close date pushes
According to HubSpot, "Push Count Score: this formula calculates that if the Close Date has been pushed three or more times, 20 risk points will be added."
This rule depends on a count, so the count has to be kept somewhere. Keep a plain tally of Close Date changes for each open deal, updated each time the date moves. A deal with two or fewer pushes does not meet this example rule, so leave it unflagged under this rule.
When a deal meets the push rule, mark it and add the example value to its tally. If a deal meets both rules, add the two example values together. Discuss those deals first, because they carry both flags.
Start the tally on the day you begin using this list. If you have no record of earlier moves to the Close Date, say so in the notes rather than estimating a count. Estimated counts make the flag hard to defend when the owner asks why a deal was marked.
A deal can meet this rule while its last note update or last activity date is recent, because the two rules look at different things. Treat each flag separately when you add the points, and record which flags a deal carries.
Review the push tally in the meeting itself. Ask the owner why the date moved, and record the answer next to the tally so the note stays with the deal. Keep each note short, such as the old date, the new date, and the owner's reason, because a short note is easier to scan during the call. For help keeping that record, see Close date change log: why the date moved.
Where to find the reports in HubSpot
In your HubSpot account, according to HubSpot, click More, then navigate to Reporting > Reports.
Next, according to HubSpot, "Select a Quick answer to go to the most relevant report that answers your questions." Choose the Quick answer that matches the question you are bringing to the review.
Before you rely on a report, check what it measures. According to HubSpot, "To read more about the type of report you've selected, including its description and the properties it uses, navigate to the About this report tab in the right panel."
Open the About this report tab before the review and write down the properties the report uses. This keeps the team reading the same fields that the flag rules use. If a property in the report is not the one your team chose for the 14-day rule, fix that mismatch before the meeting rather than during it.
Write the report name in your review notes so the next person can open the same view.
Record the date you opened the report next to the flagged list. That gives you a way to check later which view the list came from. Use the weekly pipeline snapshot guide when preparing a separate record for comparison.
Follow-up emails on flagged deals
The Nutshell page gives a direct description of what to base a follow-up on. According to Nutshell, "Effective email personalization focuses on high-value data points, such as deal stage, interaction history, and behavioral signals."
For each flagged deal, draft the follow-up email using those inputs you already have for that contact. Write the draft before the review so the discussion covers the message, not only the date.
Keep each draft in a shared place the team can open during the call, and label it with the deal name and the flags it carries. A label like that lets the group see the reason for the message without reopening the deal.
When a deal carries both flags, draft the message with the push history in view as well as the activity history. The two flags come from different records, so a draft written from only one of them can miss the other.
The same page names two measures for checking whether personalized emails are working. According to Nutshell, "An increase in email reply rate and sales meetings booked are signs that your personalized emails are working."
Track reply rate and meetings booked for flagged deals in your own records. Compare the weeks before a flagged review with the weeks after it, using the same deals. A small firm's sample will be small, so read the numbers as trends in your own notes rather than as proof.
Note the date each follow-up email goes out next to the deal. Then, when you compare reply rate and meetings booked, you can line each reply up against its send date rather than against memory.
What these rules do not tell you
The point values come from HubSpot's example formulas, so treat the 10 and 20 values as one publisher's example rather than a standard for every CRM. A total of points does not show whether a deal will close. Use the flags to choose the order of discussion, not to forecast the outcome.
Survey figures are context only. According to Nutshell, HubSpot's 2025 State of Sales Report reveals that 83% of sales professionals agree that AI can be used to personalize prospect engagement. Those figures describe survey respondents, not the deals on your list.
The same page also cites a Gartner survey conducted in 2026. According to Nutshell, 72% of sales organizations fail to invest in high-value sales activities, such as email personalization. This is background on how common the gap is, and it does not measure your own team's investment.
A 2021 study by McKinsey, according to Nutshell, found that 71% of consumers expect personalized brand interactions, while 76% don't respond well to messaging that feels invasive or misses the mark. Read this as consumer context, not as a result your emails will get.
Nutshell also says that companies that personalize their messaging generate 40% more revenue from their personalization efforts than standard messaging, according to Nutshell. That is research context and not a promise of revenue gains for a small firm.
A deal that stays on the list may have a reason in the notes, such as a reason the owner gave for a date change. Record that reason beside the flag rather than removing the flag, so the list still shows what the group saw.
A clean list is a product of applying the two rules, not a sign that the pipeline is healthy. Keep a separate note of anything the rules do not check, so the group remembers what the flags leave out.
Illustrative example: a single activity flag
An illustrative deal has gone 20 days since the chosen reference date and has no close date pushes. Its working tally is 10 points for activity age. Keep the day count beside the flag, then prepare the follow-up draft using the deal's existing records.
Your next step before the review
Today, list your open deals, check the chosen activity date and recorded close date pushes, and total the points before your next deal review. Use a sheet like the one below to record each deal, with a separate row for each open deal.
| Deal | Days since chosen reference date | Close date pushes | Points |
|---|---|---|---|
| Example | Record the day count | Record the known count | Record the working tally |
Your questions
Does exactly 14 days without activity count?
No, a deal at exactly 14 days does not meet HubSpot's example wording. Check the day count against the activity formula before marking it.
What if earlier close date pushes are missing?
Record the missing history in your notes rather than estimating a count. Keep that uncertainty beside the tally when applying HubSpot's push count formula.
What should I check before using a report?
Check its description and properties in About this report. Use HubSpot's report guidance to confirm that the view matches your chosen fields.
What should I bring to the follow-up discussion?
Bring a shared draft labelled with the deal name and its flags.