Your forecast is only as reliable as the pipeline underneath it. If reps interpret deal stages differently, required fields sit empty, and stale opportunities inflate your numbers, the weekly pipeline review devolves into speculation.
A HubSpot pipeline audit provides a structured method for identifying those gaps before they reach your board deck. RevLayer helps RevOps teams run precisely this kind of diagnostic. In this guide, you will learn how to conduct one yourself.
Below is a six-step process for reviewing your HubSpot deal pipeline, identifying data quality issues, and converting findings into a concrete action plan. Each step is designed so a VP of RevOps or RevOps Manager can execute it independently, whether you run this quarterly or ahead of a major CRM rebuild.
Before you open a single HubSpot settings page, align with your sales leadership on what "clean" actually means. This conversation should cover three things: what each deal stage represents from the buyer's perspective, which properties must be filled at each stage, and how long a deal can sit in one stage before it needs attention.
Capture these standards in a shared document your team can reference throughout the audit. Without this baseline, every finding becomes a debate rather than a clear action item.
A good starting point is to list your current deal stages in a table with columns for stage name, buyer action that triggers entry, required fields, and maximum days allowed. This table becomes your audit rubric for the next five steps.
Open your HubSpot deal pipeline settings and compare what you see against the standards you just defined. Start by counting your pipelines. If your company has fewer than two distinct sales motions but more than two pipelines, consolidation belongs on your list.
For each pipeline, check three things. First, do the stage names describe buyer milestones or rep activities? "Contract reviewed by legal" is a buyer milestone. "Proposal sent" is a rep activity. Buyer-milestone stages yield more accurate win probabilities.
Second, review the default close probabilities HubSpot assigns to each stage. Most teams never update these after initial setup. If your "Negotiation" stage shows 80% but your actual win rate from that stage is 55%, your weighted pipeline is misleading leadership every week.
Third, look for stages with zero deal movement in the past 60 days. Dormant stages introduce confusion for reps and clutter your reporting. Flag them for removal or consolidation.
Pull a deal report grouped by stage and sort by "days in current stage." You are looking for two patterns: deals that have been sitting in a single stage far longer than your defined maximum, and clusters of deals in stages that do not match their actual status.
Filter for deals where the last activity date is more than 30 days ago. These stale records inflate your pipeline value and distort conversion rates. In many audits, stale deals represent 15 to 25 percent of total pipeline value.
Next, spot-check 10 to 15 deals across different reps. Open each record and verify that the deal stage matches the most recent activity. If a deal is marked "Demo Scheduled" but the last logged activity was a discovery call three weeks ago, the stage-consistency problem extends beyond one rep.
Go to your HubSpot deal properties and identify which fields are set as required at each stage. Then run a report filtering for deals where those fields are blank. The most frequent gaps include missing close dates, empty deal amounts, and absent loss reasons on closed-lost records.
Missing close dates make time-based forecasting impossible. Empty deal amounts mean your pipeline value is understated. And without loss reasons, you cannot run win-loss analysis to improve your sales process. RevLayer frequently finds that loss-reason fields are the single most neglected property in HubSpot pipelines.
If HubSpot is not enforcing required fields through conditional stage rules, this is the time to set that up. Navigate to Settings, then Objects, then Deals, and configure conditional properties so reps cannot advance a deal without completing the fields your team agreed on in step one.
By now you should have a list of findings from steps two through four. Not every issue deserves the same urgency. Group your findings into three categories based on impact.
High impact covers anything that directly distorts your revenue forecast. Missing close dates, incorrect stage probabilities, and stale deals older than your average sales cycle belong here. Fix these first.
Medium impact includes issues that slow rep productivity or break downstream reports. Duplicate pipelines, unused deal stages, and inconsistent property naming fall into this group. Schedule these for the next two weeks.
Low impact captures nice-to-have improvements such as renaming stages for clarity or adding optional properties for better segmentation. These go on the backlog.
Assign an owner to each finding. Unowned audit items tend to remain open indefinitely.
Take your prioritized list and turn it into a project plan with three time horizons. The first horizon covers fixes you can ship in the next 48 hours: enabling required fields on closed-lost, updating stage probabilities, and archiving empty stages.
The second horizon covers changes that need two to four weeks: consolidating pipelines, retraining reps on stage definitions, and building automated deal-hygiene workflows in HubSpot.
The third horizon covers structural rebuilds that take one to three months: redesigning your entire stage model, migrating historical data, and integrating pipeline health scores with your forecasting process.
Document each change with a before-and-after description so you can measure improvement in the next quarterly audit. RevLayer recommends running this full audit cycle every quarter, and a lighter stage-consistency check monthly, to prevent pipeline drift from compounding.
The clearest warning sign is a consistent gap between your weighted pipeline forecast and actual closed revenue. If your team misses the forecast by more than 15 percent for two consecutive quarters, your pipeline data has a structural problem, not a forecasting-model problem.
Other red flags include reps interpreting the same deal stage in different ways, deals sitting in "Negotiation" for months with no logged activity, and reports that show different pipeline values depending on which filters you apply. When two managers pull the same report and get different numbers, trust in the CRM erodes quickly.
Watch for a sudden spike in deals pushed to the next quarter right before close. This pattern, sometimes called "deal slippage," often means stage criteria are too loose and deals are advancing before genuine buyer commitment exists.
If your audit uncovers mostly data-hygiene issues, such as missing fields, outdated probabilities, and a handful of stale deals, your RevOps team can handle the fixes internally. Set aside a focused sprint, work through the rebuild plan from step six, and schedule the next audit.
Outside help makes sense when the findings are structural. If your deal stages no longer match your sales motion, your pipeline was built for a product or market you have since outgrown, or your team lacks the HubSpot technical depth to redesign conditional properties and automated workflows, a specialist can compress months of trial and error into a focused engagement.
A good rule of thumb: if more than half of your audit findings fall into the "high impact" category, and you do not have a dedicated HubSpot admin on staff, engaging a RevOps partner is likely the faster path to accurate pipeline data.
RevLayer works with RevOps teams to turn audit findings into a fully rebuilt HubSpot pipeline. Instead of handing you a report and walking away, RevLayer partners with your team through the entire rebuild: redefining stage criteria, configuring conditional properties, building automated hygiene workflows, and training your reps on the new process.
The result is a pipeline that reflects your actual sales motion, enforces data quality at every stage, and gives leadership a forecast they can trust. RevLayer's approach is built for B2B revenue teams running HubSpot, and every engagement starts with a diagnostic audit similar to the one you just learned.
If your audit uncovered more issues than your team can tackle alone, reach out to RevLayer for a pipeline diagnostic. You will receive a clear picture of what needs to change and a prioritized roadmap for making it happen.
Run a full audit every quarter and a lighter stage-consistency check monthly. RevLayer recommends increasing frequency to monthly during periods of rapid hiring, territory changes, or product launches, because these events accelerate pipeline drift.
HubSpot's built-in deal reports, the Data Quality Command Center, and custom report builder are your primary tools. You can filter deals by stage, time-in-stage, and property completion without any third-party software. RevLayer uses these native features as the foundation for every audit engagement.
Yes. Research from RevHeat analyzing 187 companies found that companies with structured pipeline management hit their forecasts 73 percent of the time, compared to 39 percent for those without pipeline discipline. Cleaning your pipeline data directly improves the reliability of every forecast built on top of it.
Enable a required loss-reason field on your closed-lost stage. This is a five-minute configuration change in HubSpot that immediately starts capturing data you need for win-loss analysis. RevLayer considers this the single highest-ROI fix in most audits.
A focused audit following the six steps in this guide takes roughly two to three hours for a single pipeline. If you have multiple pipelines, complex automation, or integrations syncing deal data from other systems, plan for a full day. RevLayer's guided audits typically wrap up in one to two working days.