# The Pipedrive deal progress bar now shows stage names and days in stage: how to read one deal in a minute

https://salesbond.app/blog/pipedrive-progress-bar-days-in-stage/
Published: 2026-10-03 · Updated: 2026-10-20

The progress bar at the top of a Pipedrive deal card shows which stage the deal is in and, per Pipedrive’s help page, the number of days it took to complete each stage. Since the August 2026 update, the stage names and the days in stage sit on the bar itself, with no hover needed. Read it for one thing: a segment that is much longer than the others. That segment is a question to bring to the rep, not a verdict on the deal.

## Sixty-two days, forty-one of them in one stage

Here is a made-up deal, built to show the reading. The team, the dates and the numbers are invented; the Pipedrive behaviour is from the sources linked below.

It is Thursday, October 1. A sales manager has a 1-on-1 in ten minutes and opens the biggest open deal on the rep’s board. The deal was created on Friday, July 31, so it is 62 days old. The bar runs across the top of the card: Qualified, 4 days. Discovery, 8 days. Demo, 9 days. Then Proposal, where the deal sits now. The rep moved it there on Friday, August 21. Forty-one days ago.

Three stages took three weeks between them. One stage has taken six.

![Hypothetical deal progress bar: Qualified 4 days, Discovery 8, Demo 9, Proposal 41 days (current stage)](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-progress-bar-days-in-stage-2.png)

That is the whole read and it took less time than finding the rep’s name in the calendar. The deal did not drift everywhere. It moved at a steady pace through qualification, discovery and the demo, then stopped at exactly one point: after the proposal went out.

So the conversation has a shape before it starts. Not “what is going on with this deal”, but “what happened after August 21”.

## What the bar shows now: stage names and days in stage

Pipedrive’s product updates page lists the change under August 2026: “Stage names on progress bars. See which stage a deal is in without hover-over tooltips thanks to stage names with day counts directly on the deal detail progress bar” ( [Pipedrive product updates](https://www.pipedrive.com/en/product-updates)). A small change. Before it, you had to hover over the bar to see which stage a deal was in. Now the name and the day count are printed on the bar.

The help article on the deal detail view describes what the bar measures: “you’ll find the deal progress bar, showing you what pipeline stage the deal is currently at and the number of days it took to complete each stage” ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)).

Two details in that sentence matter. The days are counted per stage, and they are the days it took to complete each one. So the bar is a history of the deal’s path through your pipeline, stage by stage. It is not the deal’s age, and it is not the time since anyone touched the deal.

People mix that last one up with rotting, and they shouldn’t. Rotting, Pipedrive’s flag for deals nobody has updated, is based on the deal’s last updated time ( [Pipedrive: the rotting feature](https://support.pipedrive.com/en/article/the-rotting-feature)). The progress bar is a separate clock. A deal can sit in Proposal for six weeks and never rot if the rep keeps logging emails on it. If you are tuning that flag, here is [how teams set rotting thresholds](https://salesbond.app/blog/pipedrive-rotting-deals/). The bar answers a different question: not “is anyone working this”, but “where did this deal get stuck”.

## A one-minute read before the 1-on-1

We think the bar is the fastest preparation a manager can do for a deal conversation. The trick is to read it in the same order every time, so it takes about a minute and you don’t skip a step on the deals you already have an opinion about.

1. Find the current stage, the one named on the bar where the deal sits. Say it out loud. Reps often describe a deal by where they hope it is, not where the card says it is.
2. Look at the completed segments and find the odd one out: the segment several times longer than its neighbours.
3. Check whether that long segment is a completed stage or the current one. Completed means the deal already got past its sticking point, and the question is what unblocked it. Current, as in the example above, means the deal is stuck right now.
4. Write down one question about something the buyer did. For the example deal: “What has the buyer done since the proposal went out on August 21?” Not “why is this taking so long”. The first question has an answer in the CRM or in the rep’s inbox. The second one gets a story.

Step four is where the bar stops helping and teh manager starts. The bar tells you where the time went. It cannot tell you whether the time was spent waiting on the buyer’s legal review or waiting on nothing at all. We keep a short list of questions that separate those two cases in [deal review questions that ask about buyer action](https://salesbond.app/blog/deal-review-questions-buyer-action/); the one about the last thing the buyer did, with a date, is the one to bring to this meeting.

One caution on step two. A long segment on a single deal is a question about that deal. A long segment on the same stage across many deals is your pipeline, not the rep. If every deal on the board shows the same fat Proposal segment, the fix is in how the team proposes, and no 1-on-1 will solve it. That pattern is easier to see in a report than card by card, and it belongs with [stage conversion rates](https://salesbond.app/blog/pipeline-stage-conversion-rates-pipedrive/).

## What the bar does not tell you: won deals, other pipelines, buyer action

The help page is explicit about the first limit: “The progress bar won’t be updated once the deal is won” ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)). So the bar is a tool for open deals. Open a won deal from last quarter and you are looking at the bar as it stood when the deal was marked won. To study how closed deals travelled, go to a report. For the length of the whole journey on won deals, from created to won, the method is in [sales cycle length in Pipedrive](https://salesbond.app/blog/sales-cycle-length-pipedrive/).

The second limit is about pipelines. Pipedrive’s help on the pipeline view says: “Moving a deal to another pipeline affects reporting in Insights. Deal progress reports only reflect movements within the current pipeline” ( [Pipedrive: pipeline view](https://support.pipedrive.com/en/article/pipeline-view)). If your team moves deals between pipelines, say from a new-business pipeline to a renewals one, keep that in mind the moment you leave the card for a report. The report shows the deal’s moves in the pipeline it is in now, not the road it took to get there.

Renaming, inserting or deleting a stage changes what the bar and the reports show for deals already in the pipeline; we list what each [stage edit](https://salesbond.app/blog/pipedrive-edit-pipeline-stages-live/) does and what to write down first.

The third limit matters most, and no setting fixes it. The bar measures stages, and stages are something the rep sets. A deal that has been in Proposal for 41 days might have a buyer who went silent on August 22, or a buyer who asked for a revised quote on September 25 that is sitting in a draft folder. Both look identical on the bar. Stage time is a record of what your team did to the card, filtered through how disciplined the team is about moving cards at all.

That is why the bar and the close date should be read together. A rep who keeps pushing the expected close date forward is touching the deal without moving it. The bar says 41 days in Proposal; the close date says “next Friday” for the fifth time. We covered that pattern in [pushed close dates in Pipedrive](https://salesbond.app/blog/pushed-close-dates-pipedrive/). On its own each signal has an innocent explanation. Together they rarely do.

This is usually where a manager asks whether there is a way to see these signals across the board without opening every card. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal in the connected CRM against more than 20 rules in categories such as Activity, Progression and Forecast, assigns a health score, shows the specific violations and explains what to do about each one. It does not replace the minute with the card. It tells you which cards to spend the minute on. [Check your CRM with SalesBond](https://salesbond.app/) if you want that list before the next round of 1-on-1s.

## When to leave the card and open Insights

The card is for one deal. Once the question becomes “how do deals in general move through our Proposal stage”, the card is the wrong place to be, and Pipedrive says so itself: “If you wish to track the overall progress of deals throughout your pipeline, we suggest using the deal progress report” ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)).

The practical rule we use: if the thing you want to know has a deal title in it, stay on the card. “Where did the Northwind deal lose five weeks” is a card question. If it has the word “usually” or “on average” in it, close the card and open Insights. “Do our deals usually stall after the proposal” is a report question, and the deal progress report is where Pipedrive points you for it.

This also protects you from a a specific mistake. One long Proposal segment, read on one card, is a story about one buyer. Reading five cards in a row and concluding that “our proposals take too long” is a sample of five, chosen because they happened to be on one rep’s board that Thursday. The report looks at all of them.

And if you are reading cards one by one because you do not trust the report, that is a different problem. It usually means stages are not being moved consistently. A short [Pipedrive audit](https://salesbond.app/blog/pipedrive-audit/) of how stages are actually used fixes the report, and then the cards are only for the conversations.

## A one-line rule

Before your next 1-on-1, open the rep’s biggest deal, find the one segment on the bar that is out of proportion with the others, and turn it into a question about what the buyer did last. Everything the bar cannot see, the rep’s last three emails can.