Review Velocity Calculator

What review velocity measures and why it matters

Review velocity measures the rate at which a business accumulates new public reviews — typically expressed as new reviews per month. It is a momentum metric: the absolute number of reviews a business has matters, but so does the rate at which that number is growing. A business with three hundred reviews that has not received a new one in six months signals stagnation to prospective customers and search algorithms alike.

The formula is: new reviews received in the tracking period divided by days tracked, multiplied by thirty. This gives a comparable monthly rate regardless of the length of the window you are measuring. Running it consistently over time lets you see whether your review generation efforts — ask sequences, follow-up emails, post-service texts — are producing results or flattening out.

For local businesses, review velocity matters because it signals current activity to both potential customers and to local search ranking factors. A business that is actively serving customers and consistently collecting reviews sends a different signal than one with a static review count. Content teams can use velocity data to time review-ask campaigns and to calibrate how much effort should go into review generation versus responding to existing reviews.

How to use this calculator

Enter the number of new reviews received and the number of days in the tracking period. The calculator returns your estimated monthly velocity. For the most useful data, track velocity across your primary review platforms separately — a business may have high velocity on one platform and near-zero on another, which shapes where review-ask efforts should be directed.

Compare velocity across consecutive periods to identify whether a specific campaign or operational change produced a meaningful lift. A review-ask text sequence launched in one month should produce a noticeable velocity increase in that same window if the volume is sufficient.

How to improve review velocity

The most reliable way to increase velocity is to systematize the ask. Businesses that request reviews only occasionally or only when they remember to get inconsistent results. Building a repeatable ask into your post-service workflow — a text message two days after service completion, an email follow-up three days after a product delivery — produces a predictable stream of review requests that generates proportionally more new reviews over time.

Timing and friction both affect completion rates. A review request sent while the service memory is fresh — within the first forty-eight to seventy-two hours for most service businesses — tends to produce a higher response than one sent a week later. And a request that links directly to the review form rather than asking the customer to search for your listing removes a step that causes many well-intentioned customers to abandon the process.

Platform concentration matters for velocity. Asking every customer to leave a review on a platform they rarely use produces poor completion rates. Matching the ask to the platform your customers actually use — which you can gauge by where your existing reviews are concentrated — gives your requests the best chance of completing.

• Build review asks into a defined post-service sequence rather than relying on memory
• Send requests within forty-eight to seventy-two hours of service completion
• Link directly to the review form — do not make customers search for your profile
• Concentrate asks on the one or two platforms where your customers are most active

Common mistakes when tracking review velocity

Tracking only total review count rather than velocity misses the momentum signal. A business with five hundred reviews and zero new reviews in the past ninety days is in a very different position from one with one hundred fifty reviews and twenty new ones this month. The latter is showing active customer engagement and a consistent experience that motivates public praise.

Teams sometimes also measure velocity without distinguishing between unsolicited organic reviews and reviews generated by an active ask sequence. Understanding which portion of your velocity is coming from your own outreach versus happening organically tells you how dependent your current rate is on active effort — and whether it would fall sharply if you stopped asking.