Your pipeline shows 47 open deals worth $1.2 million. Your forecast says you’ll close 30% of that this quarter. But when you dig into the individual records, half those deals haven’t had a logged activity in six weeks. That $1.2 million figure is not a forecast — it’s a wish list.

A deal review process is the mechanism that keeps your pipeline honest. It’s not a punishment tool for underperformers. It’s a regular, structured habit that prevents bad data from compounding into bad decisions.

Why Pipeline Data Becomes Unreliable Without a Review Process

Deals accumulate in “proposal” or “negotiation” stages for months because no one officially decides to close them as lost. Reps know, deep down, that a deal has gone cold — but moving it out of the pipeline feels like admitting failure. So it sits there, inflating the coverage number and distorting the forecast.

The forecast becomes fiction. Your VP of Sales is making hiring and resource decisions based on a pipeline that hasn’t been cleaned since last quarter. Your finance team is modeling revenue against deals that have been effectively dead for two months.

What a deal review process actually fixes is the accumulation problem. It creates a regular forcing function that prompts reps to make a decision about every open deal: is this alive, at risk, or dead? It also surfaces the coaching conversations that need to happen before deals are permanently lost.

What it doesn’t fix is the underlying behavior that creates stale deals in the first place — that requires qualification standards and manager follow-through. But a review process is the earliest warning system you have.

Designing the Deal Review Cadence

A review cadence has two distinct rhythms: a shorter tactical check and a longer strategic one. Both serve different purposes and should not be collapsed into one bloated meeting.

Weekly Pipeline Review

The weekly review is a working session, not a status report. It should involve the sales manager and the reps whose pipeline is being reviewed. Keep the scope tight: what deals were added, what moved forward, and what has stalled since last week.

Time-box this meeting firmly at 30 to 45 minutes. When it runs over, it’s usually because you’re solving problems that should be handled in a separate coaching conversation. Use the review to surface issues, not to solve them in the room.

Focus your attention on movement, not static value. A deal that moved from “Discovery” to “Proposal” in the past seven days is worth noting. A deal sitting in “Proposal Sent” with no activity for three weeks needs a flag and a plan.

Monthly Deep-Dive Review

The monthly review is where you apply harder scrutiny. Any deal that has been stalled for more than a defined threshold — say, 21 days longer than your average stage duration — gets escalated to a direct conversation.

Deals with no logged CRM activity in the past 30 days should either get a documented re-engagement attempt or be removed from the active pipeline. This is also when you compare your forecast accuracy from the previous month against actuals. If your forecast said $180,000 and you closed $90,000, the gap tells you something about either your qualification standards, your stage criteria, or both.

The Deal Review Criteria to Apply

Applying the same criteria to every deal in every review removes the subjectivity that lets stale deals hide. Here are the five criteria that matter most.

Last activity date tells you when the deal was last touched in any meaningful way — a call logged, an email tracked, a note added. A deal with a last activity date from five weeks ago is not actively being worked.

Deal age compares how long this opportunity has been open against your typical sales cycle. If your average deal takes 45 days to close and this one is on day 90, something needs to change.

Next step is perhaps the most important signal. Every deal in your pipeline should have a defined next step with a scheduled date. “Follow up with Jim” is not a next step. “Call Jim on Tuesday the 14th to discuss contract terms” is.

Engagement level looks at the prospect side. When did the prospect last respond to you? A rep can be very active on their side while the prospect has effectively gone dark.

Stage accuracy asks whether the current stage reflects what has actually been agreed. A deal listed as “Verbal Commitment” where no verbal commitment has been documented is a data quality problem.

Review Criterion	Pass Condition	Flag Condition	Action If Flagged	CRM Field to Check
Last Activity Date	Activity logged within 14 days	No activity for 15–30 days	Schedule next touchpoint this week	Last Activity Date field
Deal Age	Within 1.5x average sales cycle	More than 2x average sales cycle	Manager review; re-qualify or archive	Deal Created Date
Next Step	Defined task with a future due date	No task or overdue task	Rep creates specific next step immediately	Open Tasks / Next Step field
Engagement Level	Prospect responded within 14 days	No prospect response in 21+ days	Attempt re-engagement; set dead date	Last Prospect Response Date
Stage Accuracy	Stage reflects documented buyer decision	Stage not supported by logged activity	Correct stage; add supporting note	Stage field + Activity log

Setting Up the Review Workflow in Your CRM

The practical mechanics of your review process depend on being able to filter and sort your pipeline quickly before and during the review meeting.

Create a saved filter in your CRM that pulls all open deals sorted by last activity date, oldest first. This single view tells your manager exactly where to focus before the meeting even starts. Reps can see their own version of the same filter and come prepared.

Add a “Deal Health” field — a dropdown with values like “On Track,” “At Risk,” and “Stalled” — that reps are required to update weekly. This field becomes a rapid signal in any pipeline view without requiring the manager to audit every deal in detail.

Configure automated alerts for deals that have had no logged activity beyond a threshold you set — typically 14 to 21 days depending on your sales cycle. These alerts should go to both the rep and the manager. They’re not accusations; they’re reminders to take action before a deal goes fully cold.

When marking deals, use a consistent vocabulary: “At Risk” means the deal is alive but needs intervention. “On Hold” means the prospect has asked you to pause. “Dead” means you’ve confirmed it won’t move forward. Each status should trigger a different follow-up protocol.

What to Do With Stale Deals

Before removing a deal from your pipeline, make one documented re-engagement attempt. Send a direct, brief message to the prospect that acknowledges time has passed and asks a clear question: is this still a priority, and does it make sense to continue the conversation? Log this attempt in your CRM with the date sent.

If there’s no response after a set window — typically 7 to 10 business days — archive the deal rather than deleting it. Archiving keeps the record intact for future reference without having it pollute your active forecast. Move it to a “Closed Lost” status with a loss reason documented.

The loss reason is critical. Before you close any deal as lost, log the specific reason in the designated CRM field. This data is what tells you, six months from now, where your pipeline is leaking. Common reasons include budget constraints, timing, competitor selection, no decision, or champion departure. Each reason points to a different improvement area.

When closing a deal as lost, also log any key contacts involved, what stage the deal reached, and what the last substantive conversation was about. This history becomes valuable if the prospect re-engages in the future.

FAQ

How often should we run deal reviews? Run a weekly tactical review for every rep, capped at 45 minutes. Run a monthly deep-dive that includes forecast accuracy comparison and stale deal cleanup. Quarterly, review your stage definitions and criteria to make sure they still reflect how deals actually progress.

What if reps resist removing deals from the pipeline? Frame the conversation around data quality rather than performance. A smaller, accurate pipeline is more useful to everyone than a large, inflated one. Make it clear that closing a deal as lost doesn’t remove it from their history — it just makes the active forecast more meaningful. Managers can also make this easier by not treating every lost deal as a coaching event; sometimes deals just don’t close, and that’s normal.

How do we prevent stale deals from reappearing? Set a minimum qualification standard for any deal re-entering the pipeline after being closed. If a prospect comes back six months later, they should go through your qualification criteria again before being added as an active opportunity. Don’t simply reopen the old record and move it back to “Proposal.”

What metrics should we track for pipeline accuracy? Track the percentage of open deals with a logged activity in the past 14 days. Track what percentage of deals in your forecast actually close. Track average deal age compared to your stated sales cycle. These three metrics, reviewed monthly, tell you whether your pipeline data is trustworthy.