# Pipedrive forecast view: one drag-and-drop moves the expected close date

https://salesbond.app/blog/pipedrive-forecast-view-dragging-deal-date/
Published: 2026-10-03 · Updated: 2026-10-25

Pipedrive’s forecast view projects revenue by each deal’s expected close date, and dragging a deal from one column to another changes that date ( [Pipedrive: the deal forecast view](https://support.pipedrive.com/en/article/the-forecast-view-revenue-projection)). The screen you use to read the forecast is also a screen that edits it. So our rule for the weekly review is short: look, don’t drag. A deal moves to another month only after the buyer has given you a reason, and the reason goes on the deal before the card goes anywhere.

## The Friday drag

A made-up scene, but we have sat in this meeting more than once.

A Friday in early October, half past four. The team runs its weekly review on the forecast view, columns by month. The October column header shows open deals at $96,000 and won deals at $41,000, so $137,000 if everything lands. November shows $22,000 open. The manager looks at the two columns and says what everyone is thinking: October is never going to be ninety-six, and November looks empty.

Two cards get dragged. An $18,000 deal where the rep said “they’re waiting on their board” and a $9,500 deal nobody has heard from in two weeks. Both land in November. October now reads $68,500 open, $41,000 won, $109,500 combined. November reads $49,500. The columns look balanced, the call ends on time.

Here is what else happened. Both deals now carry an expected close date in November that no rep chose and no buyer confirmed. There is no note on either deal. On Monday the rep who owns the $18,000 deal opens it, sees a November date, and assumes somebody knows something she doesn’t. The following Friday, the October column is smaller and looks more believable, and nobody remembers that the the improvement was a mouse movement.

## What the forecast view actually sums

The forecast view sits under the Deals tab, behind the third View button, and shows your deals as a kanban board with date-based columns ( [Pipedrive help](https://support.pipedrive.com/en/article/the-forecast-view-revenue-projection)). By default, an open deal goes into the column that matches its expected close date. A deal marked WON is placed by its won date instead, not by whatever expected close date it had while it was open.

Each column header carries three figures: the total value of open deals in that period, the total value of won deals in that period, and the combined revenue of the two, which is what the column would bring in if every open deal were won. The gear icon lets you change what the columns are: “Show by” decides which columns deals are sorted into, “Arrange by” decides the order of deals inside a column. The green status bar on each card shows how far along the pipeline the deal is. Separately, deals are ordered by their current pipeline stage and when they were last changed, so the ones furthest along sit at the top ( [Pipedrive: how deals are ordered](https://support.pipedrive.com/en/article/how-are-deals-ordered-in-the-forecast-view)).

Two consequences follow from the won-date rule, and both bite at month end. A deal you expected in September that was marked won on October 1 adds to October, not September. And a column’s won total usually only grows during the month, while its open total shrinks every time a deal is won, lost, or dragged out. So a column that “went down” since last Friday is not news on its own. You have to know which of the three movements caused it.

![One forecast column with open, won and combined totals in the header and deal cards ordered by stage](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-forecast-view-expected-close-date-2.png)

## Drag-and-drop is an edit, not a view change

Pipedrive is clear about this: you can drag a deal from one column to another, and doing so updates the deal’s expected close date ( [Pipedrive help](https://support.pipedrive.com/en/article/the-forecast-view-revenue-projection)). It is a feature, and in the right hands a useful one. A rep who just got off a call where the buyer named a date can move the card and be done.

The problem is that the gesture carries no weight. On the pipeline board dragging a card to the next stage feels like a decision, because everyone understands a stage change as progress. On the forecast view the same gesture changes a plan, and it feels like tidying up. The field does get edited, exactly as if someone had opened the deal and typed a new date, but there is no moment where a person has to say why.

Why care? Because the history of the date is the signal. A deal whose close date has moved twice is a different deal from one that was set for November on day one, and we wrote about how to count those moves in [the close date you keep pushing](https://salesbond.app/blog/pushed-close-dates-pipedrive/). A drag in a meeting adds a push to that history without anyone noticing it was a push. That push does leave a line in the [Changelog](https://salesbond.app/blog/pipedrive-deal-changelog-close-date-audit/) of the deal, which is where you can check when the date moved.

It also resets the baseline. Last Friday’s October becomes this Friday’s starting point, and the gap between what you forecast at the start of the month and what landed is quietly erased. And the rep stops owning the date. A date the manager set in a meeting is a date the rep no longer defends, and a forecast nobody defends is a spreadsheet.

So we treat the two cases differently. A rep moving their own deal after a buyer conversation: fine, and write one line on the deal saying what the buyer said. A manager moving someone else’s deal during a review: no. Ask the question, let the rep make the change after the call, and if there is no buyer reason, the card stays where it is and becomes an action item.

## When to use a different date field

The expected close date is when you expect the deal to be marked won or lost ( [Pipedrive help](https://support.pipedrive.com/en/article/the-forecast-view-revenue-projection)). For many small teams that is close enough to when the money arrives. Not always. Equipment with a lead time, an implementation project, a subscription that starts on a go-live date: the signature lands in October and the money lands in December. Before anyone drags deals around for December, [ask one budget question in November](https://salesbond.app/blog/year-end-budget-deadline-deals-pipedrive/) and store the answer in a field, so the date reflects the buyer and not the board.

Pipedrive’s answer is a custom date field. The help article’s own example is “delivery date.” Create the field, fill it on the deals where it differs from the close date, and the forecast view can use it to project revenue instead of the expected close date.

Pick one field per question and say out loud which is which. Bookings, meaning when deals will be won, go on the expected close date. Cash or recognized revenue, meaning when the customer gets what they paid for, goes on a delivery date field. Otherwise you get the same argument every month about why the number is “wrong,” when two people are reading two different questions off one column.

There is a second reason to keep them apart. A close date that moves because teh buyer’s decision slipped is a sales signal. A delivery date that moves because your own team is late is an operations signal. One date for both hides both.

## Reading a column: open, won, weighted

The header’s third figure, the combined value if you win every open deal, is the easiest number to read and the worst one to report. We call it the ceiling. It tells you whether the plan is still reachable at all. It does not tell you what will happen.

The won figure is the floor. It is already in.

The weighted figure is the expectation, and it depends on a setting. If you have set custom probability on deals or stages, the forecast view presents the weighted value ( [Pipedrive help](https://support.pipedrive.com/en/article/the-forecast-view-revenue-projection)). In the October scene above, imagine the $18,000 deal sits in a stage with a 40% probability. It contributes $7,200 to the weighted figure, not $18,000. The arithmetic is simple, the hard part is whether the probabilities are honest, and that is a separate article: [weighted pipeline forecast](https://salesbond.app/blog/weighted-pipeline-forecast/).

So read a column as three lines, in this order. Won: what has landed. Weighted: what we expect. Combined: the most that could land. Compare plan against the middle line. Use the top line to check that the gap is closable. And if your team already splits the pipeline into commit and best case, the mapping is close: commit lives near the weighted figure, best case near the ceiling, and we covered how to set those categories in [commit vs best case forecast](https://salesbond.app/blog/commit-vs-best-case-forecast/).

One habit kills this reading: looking at the combined figure, seeing that it is above plan, and moving on. Say the October plan in our scene was $120,000. The combined figure cleared it at $137,000. A fifth of that was two deals: one waiting on a board meeting, one with a buyer who had gone quiet.

## A rule for the weekly review: look first, move only with a reason

Here is how we run it, and it fits inside the [15-minute weekly pipeline review](https://salesbond.app/blog/weekly-pipeline-review-15-minutes/) without adding a step.

Open the forecast view with columns by month. Start with the current month and walk the column from the top, because deals are ordered by pipeline stage, furthest along at the top ( [Pipedrive: how deals are ordered](https://support.pipedrive.com/en/article/how-are-deals-ordered-in-the-forecast-view)), and those are the ones whose dates matter most this week. For each open deal whose expected close date has already passed, or falls within the next seven days, one question to the rep: what did the buyer say, and when? Not “is this still October,” which invites a yes. A buyer’s words and a buyer’s date.

Three outcomes, and only three.

The buyer gave a later date. The rep changes the expected close date after the meeting, from the deal, with a one-line note quoting the buyer. Not during the call, and not by drag.

The buyer gave no date. The deal stays in its column, and the rep’s next activity is to get one. The forecast is allowed to look ugly for a week. Ugly and true beats smooth and edited.

The buyer is gone. Mark it lost. A dead deal dragged into next month is the most expensive card on the board, because it will be dragged again.

Nobody drags during the meeting. That is the entire rule. The forecast view is good at what it was built for, showing you the plan by date, and dangerous at what it also happens to do, which is letting you change the plan with no record. We would rather the manager ask one more question than fix one more column.

A disclosure, since this sits in our territory: 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, shows the specific violations and recommends what to do about each. That gets a manager to the right cards before the Friday call instead of during it. It will not tell you whether a date deserved to move; the buyer’s answer does that. If you want to see your pipeline against those rules, [check your CRM with SalesBond](https://salesbond.app/).

This Friday, try it once. Open the forecast view, walk the current month from the top, and keep your hand off the mouse until the meeting ends. Write down every card someone wanted to drag and the reason they gave. That list is a better read on your forecast than the column totals, and it is most of what [forecast accuracy for small teams](https://salesbond.app/blog/sales-forecast-accuracy-small-teams/) comes down to.