# Why the pipeline number changed since Monday: a weekly bridge from Pipedrive data

https://salesbond.app/blog/pipeline-movement-report-pipedrive/
Published: 2026-10-07 · Updated: 2026-10-26

To track sales pipeline movement in Pipedrive, write down the value and count of your open pipeline on Monday morning. On Friday, put every deal that changed into exactly one of five buckets: new, slipped or pulled in, value changed, won or lost, and stage changed. Add the money buckets to Monday’s number. If the result is not Friday’s number, a deal changed in a way none of the buckets can see, and that remainder is the first thing to look at in the weekly review. Pipedrive keeps no weekly snapshot, but it keeps every deal’s history, so all you need is a spreadsheet with the same five columns on both days and, in our experience, about twenty minutes a week.

## The Friday question: why is the pipeline $40k lower than Monday?

The team below is invented, and so are the numbers. The arithmetic is real.

Friday afternoon. Perpetua runs a five-person team and is filling in the weekly report. Monday’s open pipeline for the quarter was $310,000. Today it is $270,000. Nothing was won this week, and she would remember $40,000 of lost deals.

She asks in the team chat. Florian says he closed nothing and moved nothing. Esperanza pushed one deal to next quarter after the buyer went quiet, maybe $18,000. That leaves $22,000 nobody claims, and “probably a few small edits” is what goes into the report.

Pipelines are supposed to move. The problem is that the number moved and nobody can say how, so the the forecast built on the same deals can’t be trusted either. A balance tells you where you are. A bridge tells you how you got there.

## Five buckets of sales pipeline movement, each deal in exactly one

Vendors who sell pipeline movement reports agree on the shape: beginning pipeline plus movements equals ending pipeline. Coffee.ai uses six categories ( [Coffee.ai: track weekly changes in your sales pipeline](https://coffee.ai/articles/track-weekly-changes-sales-pipeline)), and Backstory gives pulled-in deals a column next to slipped ones ( [Backstory: pipeline changes](https://help.backstory.ai/en/articles/15252598-pipeline-changes)). Five buckets will do.

New: a deal created this week that is open on Friday inside the period you track.

Slipped or pulled in: an older deal whose expected close date crossed the period boundary, out of Friday’s list or into it. A pulled-in deal is not new, even though it also appears from nowhere: its Changelog shows a close date line, not a creation date this week.

Value changed: same deal on both lists, different amount.

Won or lost: the deal left the open pipeline with a result.

Stage changed: same deal on both lists, different stage. This is a count, not money, and forward and backward moves are counted apart, because a deal dropped from Negotiation back to Qualified is not progress.

A deal can do several of these in a week and still goes into one bucket, or the bridge double-counts. So the first question is which list it is on. Only on Monday’s: an exit, subtracted at its Monday value. Only on Friday’s: an entry, added at its Friday value. Only a deal on both lists can be value changed.

Take Esperanza’s deal. It was $18,000 on Monday, she trimmed it to $15,000 on Tuesday, and on Thursday she moved the close date into next quarter. It leaves the bridge as slipped out at $18,000. The $3,000 trim is worth a sentence in the review but not a line, because counting it in value changed too would subtract it twice.

## Where each bucket lives in Pipedrive

Most of the raw material sits in the Changelog tab under History in the deal detail view, which records stage, value and expected close date changes among others ( [Pipedrive: deal detail view](https://support.pipedrive.com/en/article/deal-detail-view)). How to read it is in [the deal Changelog before you trust a forecast](https://salesbond.app/blog/pipedrive-deal-changelog-close-date-audit/).

| Bucket | What counts | Where to see it |
| --- | --- | --- |
| New | Created this week, open on Friday | Friday’s list against the Monday snapshot |
| Slipped or pulled in | A close date change across the period boundary | Deal detail view, History, Changelog |
| Value changed | On both lists, different value | The two lists side by side; the Changelog says who and when |
| Won or lost | Marked won or lost this week | Closed deals in the pipeline view |
| Stage changed | On both lists, different stage | Changelog per deal; team-wide, Deal progress in Insights |

The last row needs a warning. Deal progress shows how deals moved through stages in a time frame ( [Pipedrive: Insights reports, deal progress](https://support.pipedrive.com/en/article/insights-reports-deal-progress)), but it is not a snapshot. It uses the most recent stage updates, so a deal moved from stage two back to stage one is shown in stage one, and it counts skipped stages as entered. A backward move never shows up as one.

For won and lost you need only the names and Monday values of deals closed this week; [the closed deals toggle](https://salesbond.app/blog/pipedrive-closed-deals-toggle-weekly-review/) covers the rest of the review, and [pushed close dates in Pipedrive](https://salesbond.app/blog/pushed-close-dates-pipedrive/) the habit behind the slipped bucket.

## Doing it by hand with a Monday snapshot

The report no CRM gives a small team for free is the one that compares two moments in time. So make the first moment yourself.

![Two-column worksheet: Monday 9:00 deal list with total and count, Friday 14:00 bridge table with remainder and a rule for a non-zero remainder](https://salesbond.app/wp-content/uploads/2026/10/pipeline-movement-report-pipedrive-2.png)

1. **Pick the number you are bridging.** We use open deals with an expected close date inside the current quarter. Its the number the forecast rests on, and it gives “slipped” a meaning: a date pushed past quarter-end leaves the number, a date pushed from the 12th to the 26th does not.
2. **Monday, before the first call.** Filter the deals list to that set and copy five columns into a spreadsheet: deal, owner, stage, value, expected close date. Write the total, the deal count and the date at the top.
3. **Friday, same filter, same five columns.** Paste the new list next to the old one.
4. **Match the rows.** Monday-only deals are exits: the Changelog says won, lost or slipped out. Friday-only deals are entries: new if created this week, pulled in if the close date moved into the quarter. Deals on both lists go to value changed (Friday minus Monday) and, if the stage differs, to the stage count.
5. **Write the bridge.** Monday total, plus new, plus pulled in, plus or minus value changed, minus slipped out, minus won, minus lost. That is expected Friday. Under it, the stage count.
6. **Record the remainder.** Expected Friday minus actual Friday. Any deal you could not put in a bucket ends up here, and goes into the weekly report as “not yet explained”.

With several currencies, keep the snapshot in one and note the rate, because a rate change between Monday and Friday is a remainder no deal caused.

## When the bridge doesn’t close

Here is the position this whole article rests on: a bridge that does not close is not a failure of the method. It is the finding.

Every bucket is backed by a trace: a creation date, a Changelog line, a won or lost mark. A remainder means a deal left or joined a list without one. In our experience the candidates are few. A deal was deleted, archived, moved to another pipeline or given to another owner while your filter is per owner. Or the mirror image: a lost deal reopened. Note that Deal progress includes archived data by default ( [Pipedrive](https://support.pipedrive.com/en/article/insights-reports-deal-progress)), so a report can keep counting a deal your filter no longer shows.

Here is Perpetua’s week after she matched the rows:

| Line | Amount |
| --- | --- |
| Monday total | $310,000 |
| \+ New (one deal) | +$9,000 |
| \+ Pulled in (one deal, close date moved from January) | +$6,000 |
| ± Value changed (two deals, −$3,000 and −$1,000) | −$4,000 |
| − Slipped out (Esperanza’s deal, at its Monday value) | −$18,000 |
| − Won | $0 |
| − Lost | $0 |
| − Left without a result (archived on Wednesday, found in History) | −$33,000 |
| = Expected Friday | $270,000 |
| Actual Friday | $270,000 |
| Remainder | $0 |

Before she opened the History of the one Monday deal that fit no bucket, the remainder was $33,000. It was a duplicate Florian archived on Wednesday, which he did not count as moving anything. So Monday’s $310,000 had been $33,000 too high, and the forecast with it. Under the money lines: six stage moves forward, one back.

Twenty minutes of Changelog reading on Friday is cheaper than a Monday forecast call built on a number nobody can reconstruct. And once the team knows the bridge gets reconciled every week, silent deletions tend to stop.

Two things the bridge never flags, because they net out. A value raised by $5,000 on Tuesday and cut by $5,000 on Thursday shows as zero. A deal created and lost in the same week is on neither list, so your lost count misses it. Both live only in the Changelog.

## What to do with the result in the weekly review

The bridge goes at the top of the report. We argued in [the weekly sales report a manager will actually read](https://salesbond.app/blog/weekly-sales-report-what-to-include-and-what-to-cut/) that pipeline numbers come first, and six lines of money plus one count line is the most compact way we know. The [five Insights reports worth building](https://salesbond.app/blog/pipedrive-reports-pipeline-health/) describe the state of the pipeline. The bridge describes its motion.

Read the lines in a fixed order. Won and lost first, briefly. Then slipped out, deal by deal, because every date that left the quarter is a question about whether the deal still exists. Then value changed: an amount that moved without a stage move is usually a discount the rep has not mentioned yet. Then new and pulled in, to check coverage is being refilled and nobody is dragging dates in to make thier numbers look full; put [pipeline coverage ratio](https://salesbond.app/blog/pipeline-coverage-ratio/) beside it. Stage changes last.

One sales leader quoted by Outreach put weekly movement at around 40 percent of the open pipeline ( [Outreach](https://www.outreach.ai/resources/blog/pipeline-movement-forecasting-outreach)). That is one team, not a benchmark. After eight weeks you will have your own number. On Salesforce, the same rule reads as [one report per question on Monday](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/).

A disclosure, since this is the gap our product sits in. 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 that include Forecast and Data, so a pushed date or a quiet value edit reaches the manager the day it happens rather than on Friday’s remainder line. [Check your CRM with SalesBond](https://salesbond.app/) if you want that daily picture.

If you only have twenty minutes this Friday, start with the bridge. It is the only report that can tell you when the others are quietly wrong.