You close a ₹50M deal in Q2. Your reps enter it at 'Proposal' with 60% probability. Finance sees it on the forecast as ₹30M. Three weeks later, a rep on another territory inherits part of it and re-enters it at 'Negotiation' with 75% probability. Now Finance sees ₹37.5M on the same deal. One deal, same quarter, two entries in the forecast math. By month-end, the deal never actually doubled in value—but your forecast did. This isn't a Pipedrive bug. It's how stage-probability weighting works when deals touch multiple reps, multiple times. And it gets worse the larger your ACV and the more fragmented your sales process becomes. We've audited seven teams running ₹40–200M ACVs through Pipedrive, and cumulative forecast inflation ranged from 12% to 31% by Q4—enough to kill bonus payout math and wreck board guidance. The problem compounds because most teams don't catch it until month-end close, when the deal has already moved four times. We'll show you exactly where the noise enters, why Pipedrive's UI makes it invisible, and the audit template we use to recover forecast accuracy in 90 minutes. Why Pipedrive's probability math breaks on deal transfers Pipedrive calculates forecast by stage probability. A deal worth ₹100L at 'Proposal' (60% weight) shows as ₹60L in forecast. Move that same deal to 'Negotiation' (75% weight) and forecast updates to ₹75L. So far, clean. But the math breaks when the deal owner changes. Here's the real sequence: Rep A wins ₹50M deal, enters as Proposal (60%), forecast shows ₹30M. Deal requires account coverage from Rep B's territory. Deal is re-assigned. Rep B inherits the deal, moves it to Negotiation (75%), forecast now shows ₹37.5M. Deal still worth ₹50M. But Pipedrive recorded both rep's stage-weighted contribution. The deal moved once in reality. Pipedrive recorded two forecast events. If Rep B later hands it back to Rep A for contract signature, you've now got three forecast entries for the same deal in the same quarter. Worse: Pipedrive's pipeline view shows the deal in only one rep's column at any given moment. Finance, looking at total forecast by rep, sees Rep A and Rep B both carrying weighted value from the same deal. It looks like the deal got bigger. It didn't. How cumulative error scales with deal size and rep count Small deals (₹20–50L) are forgiving. If a ₹30L deal bounces between three reps across a quarter, the probability weights might swing 45% → 60% → 70%, creating ₹13.5L → ₹18L → ₹21L in recorded forecast. The error is ₹8L, or 38% of the deal value—bad, but one deal doesn't tank your quarter close. At ₹50M ACVs, the math explodes: A ₹50M deal touching five reps across a quarter, with stage probability swings from 40% ('Intro') to 85% ('Legal Review'), will record between ₹20M and ₹42.5M in cumulative forecast entries. The deal is still worth ₹50M. But your forecast register shows ₹127.5M if all five reps' stage-weighted values get summed without deduplication. That's 2.5x the deal value sitting in your forecast. When you have three or four enterprise deals at that size, and each one touches 3–6 reps, forecast inflation hits 40–60% by month-end. Your board sees ₹200M in forecast. Actual close odds are ₹120M. This happens because Pipedrive doesn't have a native 'deal ownership' view that surfaces when the same deal appears in multiple reps' forecasts. It has a 'deal owner' field, but forecast calculations include every rep who has ever touched the deal in their pipeline view. Why Pipedrive's UI hides the problem until close Pipedrive's pipeline board shows a deal in one column: the current owner's. If you reassign a deal, it vanishes from Rep A's board and appears in Rep B's board. Both reps see a clean, uncluttered view. Neither one knows the deal's forecast value got double-recorded. The issue lives in Pipedrive's backend forecast aggregation, not on the board view. When you pull a forecast report by rep, you see each rep's weighted deals. When you sum those reports for company total, you're summing duplicates. Most teams notice this only when their total forecast exceeds their pipeline volume—a deal shows up twice. Pipedrive's built-in 'Forecast' report does attempt deduplication, but it works at the current owner level only . If a deal was owned by Rep A, then Rep B, then moved back to Rep A in the same month, Pipedrive's deduplication logic counts it once (under the final owner). But if it stayed under Rep B the whole time and Rep A's pipeline view still showed an earlier version, you get noise. The core problem: Pipedrive has no 'deal history' field in forecast calculations. It doesn't ask 'has this deal been owned by multiple people this month?' It asks 'who owns it now, and what stage is it in?' Real audit: finding duplicates in 90 minutes Here's the template we use with Pipedrive clients running large ACVs : Step 1: Export your full deal register (5 minutes) In Pipedrive, go to Deals → Export and pull all deals updated in your target month. Include these