Q4 sales pipeline audit: how to identify stalled deals in September and organise the next 90 days

A Q4 sales pipeline audit should begin not by adding up the value of all open deals, but by testing each deal against reality. In September, capture a single snapshot of your CRM data, define the exit criteria for each stage and check whether every deal has a confirmed need, an involved decision-maker, a credible timeline and a specific next action. Then divide the deals into four groups: active, re-engageable, deferred and to be closed as lost. Use only active deals as the basis of the Q4 forecast. Assign the others a clear re-engagement task, move them into a long-term workflow or remove them from the pipeline. The result is a verifiable 90-day plan rather than an optimistic CRM summary.

What exactly does a pipeline audit examine?

A sales pipeline is the set of active sales opportunities organised into consistently defined process stages. It is not the same as a sales funnel. A funnel may cover the entire journey from audience and enquiries to customers, while a pipeline usually begins when a specific sales opportunity has been created with an owner, a value and a process for moving it forward.

The purpose of an audit is not to make the CRM look tidier. It should answer three management questions:

1. Which deals can genuinely progress or close within the next 90 days?
2. What exactly is blocking the other deals, and can that obstacle be influenced?
3. Does the team have enough time and new opportunities to close the forecast gap?

This perspective differs from general Q4 planning. Annual targets may remain unchanged, but a pipeline audit tests whether the current deals are capable of supporting them at all.

Capture a single data snapshot before the audit

If salespeople continue changing stages, values and dates during the audit, it becomes impossible to tell whether the situation has improved or only the way the data is presented. Choose an audit date and export the current pipeline. Retain the original version so that it can be compared with the Q4 outcome.

Each open deal should include at least the following fields:

•      deal name, company and owner;
•      current stage and deal value;
•      expected closing date;
•      date of the last meaningful contact;
•      next action, its deadline and owner;
•      primary contact and decision-maker, if known;
•      known obstacle or unanswered question;
•      a brief explanation of why the deal is in its current stage.

A meaningful contact is not an automatically sent email or an unanswered call. It is an interaction that has produced new information, an agreement, a document, a decision or a next step. This distinction helps prevent overestimating activity that has not actually changed the state of the deal.

Check what each stage means before assessing deals

A pipeline stage should describe an achieved state in the customer’s journey or sales process, not the salesperson’s hopes. For example, “proposal sent” is a verifiable fact. By contrast, “nearly ready” is not a stage that everyone can interpret consistently.

Define entry and exit criteria for each stage. If a stage is called “Qualified”, it may require confirmation of the problem, fit with the offering, people involved and approximate decision timeline. If the stage is “Proposal”, check whether the customer is expecting a proposal, understands what it contains and has agreed to a follow-up discussion. The criteria must be adapted to the specific sales cycle; no universal stage model suits every company.

HubSpot’s pipeline configuration documentation, Microsoft Dynamics 365’s opportunity management overview and Salesforce Trailhead’s opportunity process material demonstrate different approaches to implementing a CRM. They are useful examples of system configuration, not universal sales benchmarks. The content of each stage must reflect the company’s actual decision-making process.

Deal review: seven questions in a consistent sequence

Review every deal using the same template. This reduces the risk of assessing a large or emotionally important deal more leniently than the others.

Pay particular attention to the expected closing date. If it has been moved repeatedly without new information from the customer, the date is not a forecast—it is an administrative guess. Similarly, sending a proposal does not by itself prove that the customer is evaluating it.

A deal may also be stalled even when there is frequent communication. A typical pattern is an ongoing conversation with a responsive contact who cannot move the decision forward. In this situation, sending more emails will not solve the problem. The next action should help clarify the decision path or involve the necessary person.

Divide deals into four action groups

After the review, assign each deal one status that determines what happens next.

Active. There is sufficient evidence for the current stage, the obstacle is understood and the next step has been mutually agreed. The deal may remain in the active Q4 pipeline.

Re-engageable. The need may still be current, but recent information, access to the decision-maker or a specific next step is missing. Define one re-engagement attempt with a deadline and clear objective. If no new evidence is obtained, the deal should not remain active indefinitely.

Deferred. The opportunity may be valuable, but the customer’s timeline falls outside Q4 or it is not currently a priority. Move it into a separate long-term workflow with a date for the next review.

Close as lost. There is no fit, priority, accessible decision-making process or genuine responsiveness. An accurate loss reason is more valuable than an artificially large pipeline.

Create a forecast that does not repeat the CRM total

The total value of open deals is not a sales forecast. It does not reflect deal quality, closing time, team capacity or interdependencies. A weighted forecast—the deal value multiplied by the stage probability—also creates false precision if the probabilities are not based on the company’s historical data and the stages are not used consistently.

It is more practical to maintain three separate views:

•      evidence-based forecast—deals with a customer-confirmed decision timeline and a verifiable next step;
•      potential upside—qualified deals that may close in Q4 but still face a significant obstacle;
•      pipeline development—early-stage or re-engageable opportunities that must not yet be treated as forecast revenue.

There is no universal ratio between pipeline value and target. The required volume depends on the company’s actual conversion rate, sales cycle, deal size and concentration risk. If a large part of the forecast depends on one deal, the total may look sufficient while the forecast remains fragile.

Turn the audit into a 90-day action plan

An audit without deadlines and owners becomes a one-off CRM clean-up. In the Q4 plan, separate deal progression, re-engagement and new pipeline development.

The first two weeks of Q4: remove uncertainty

Complete the review of re-engageable deals, correct their stages and agree next steps with active customers. At this stage, the most important outcome is information: whether the deal is genuine, who makes the decision and what will happen next. If those answers are unavailable, move the deal out of the evidence-based forecast.

Weeks three to six: move the decision process forward

Plan actions that reduce specific obstacles: clarifying requirements, conducting a technical review, discussing the proposal or involving the necessary people. “Follow up” is not a sufficient task. Each step should change the state of the deal or provide information needed to decide whether to close it.

Continue creating new opportunities at the same time. If the audit reveals a forecast gap, it cannot be resolved simply by increasing the probabilities assigned to existing deals.

Weeks seven to ten: verify the conditions for delivery

For deals approaching a decision, clarify not only commercial agreement but also the practical process: contract review, procurement procedures, required documents, implementation resources and responsible parties. The details of these activities will differ by company and customer; the purpose of the audit is not to predict the customer’s legal or procurement process without confirmation.

The final weeks of Q4: prevent artificial date changes

If the customer’s decision objectively moves into the next quarter, update the forecast and record the actual reason. Moving the deal date to the final day of the quarter without customer confirmation does not make it more likely to close. It only reduces the quality of management information.

Establish a brief weekly management rhythm

A weekly pipeline review should not involve reading out every CRM record. Discuss only changes and decisions:

•      which deals have moved to the next stage and what evidence supports the move;
•      which deals have missed their previously planned next step;
•      which timelines have changed based on information from the customer;
•      where a management decision, resource or involvement is required;
•      which deals should be removed from the forecast;
•      whether the flow of new qualified opportunities compensates for deals that have dropped out.

CRM automation can provide reminders about overdue tasks, empty mandatory fields, prolonged inactivity or changes to closing dates. However, automation should not declare a deal qualified by itself. Define the process, stage criteria and exceptions first; only then does it make sense to automate alerts and reports.

Common audit mistakes

Using the same inactivity threshold for every deal. In some sales cycles, a week without contact is significant; in others, it is normal. The threshold should be linked to the stage, the customer’s commitment and the typical cycle rather than an arbitrary number of days.

Changing closing dates in bulk. This preserves the desired total but destroys the opportunity to learn from forecasting errors.

Treating a smaller pipeline as a poor result. The total value may decrease after a thorough audit. This may mean that unsupported deals have been removed from the forecast, not that sales performance has deteriorated.

Confusing activity with progress. The number of calls and emails does not confirm that the customer is moving closer to a decision.

Automating before defining the process. An inconsistent process becomes faster in an automated system, but not more accurate.

Limitations and situations where the method must be adapted

A 90-day audit is not a guaranteed revenue forecast. The customer may change priorities, budget or the decision timeline, and the CRM contains only the information available to the team. In long enterprise procurement cycles, public procurement, seasonal businesses and projects involving multiple approving parties, progress during Q4 may mean reaching an interim milestone rather than closing a deal.

If CRM data has not been maintained for a long time, the first audit will mainly assess data quality. A new product or sales team may also lack sufficient historical data for calculating stage probabilities. In such cases, it is better to use conservative categories and document assumptions than to create a seemingly precise percentage forecast.

September audit checklist

•      The initial pipeline snapshot has been saved.
•      Every stage has verifiable entry and exit criteria.
•      Every active deal has a next action, date and owner.
•      The customer’s decision timeline has been verified, not just the date in the CRM.
•      One specific review task has been defined for each re-engageable deal.
•      Deferred deals have been separated from the Q4 forecast.
•      The actual reason has been recorded for lost deals.
•      The evidence-based forecast has been separated from potential upside.
•      Capacity for creating new opportunities has also been reserved in the Q4 plan.
•      A weekly review of decisions rather than activities has been scheduled.

Related next steps

A logical next step after the audit is “Q4 planning in September: how to turn annual targets into a 90-day execution plan”. If CRM automation is planned, “Business process mapping before automation” will be useful beforehand. If the initial opportunities are poor quality, the qualification stage described in “How to create a customer enquiry form that helps identify higher-quality prospects” should also be assessed.

Conclusion

A good Q4 pipeline audit reduces uncertainty, not ambition. It should produce a shorter and more credible list of active deals, a clearly separated forecast and an action linked to every significant obstacle. If the team organises its stages, timelines and responsibilities honestly in September, the next 90 days can be managed using verifiable information rather than the hope that every open deal will close on time.