Weekly pipeline snapshot

Most pipeline reports show the total this week next to the total last week, and nobody can explain the difference. A total that stayed flat can hide 600,000 of new pipeline and 600,000 of pushed deals. This snapshot breaks the change into its movements and reconciles them, so if the bridge does not add up, you know the data is wrong before anyone presents it.

Category:: Pipeline & Forecasting
Formats:: CSV + web view
Sections:: 5
Updated:: September 24, 2026

What you get

A weekly bridge from starting to ending pipeline across created, pulled in, pushed, lost, won, and amount changes
A reconciliation formula that must equal zero every week
A deal-level movement log that explains each number in the bridge
Stage advancement tracked separately, since it moves value between stages without changing the total
A checklist for taking the snapshot the same way every week

Who it's for

RevOps analysts who build the weekly pipeline report
Sales leaders who need to explain pipeline changes before the forecast call
Finance partners who track pipeline trends against plan

What's inside

1
Weekly pipeline bridge
11 columns, 3 worked example rows
2
Formulas
3 columns, 4 worked example rows
3
Deal-level movement log
11 columns, 5 worked example rows
4
How to classify movements
Guidance notes
5
Snapshot hygiene checklist
9-point checklist

Preview of section 1

Weekly pipeline bridge

Scope: open pipeline with a close date in the current quarter. Worked example for three weeks; each week's ending is the next week's starting.

Week	Starting pipeline	Created	Pulled in	Pushed	Lost	Won	Net amount change	Ending pipeline	Check (must be 0)	Advanced (value moved to a later stage, info only)
1	5,000,000	400,000	150,000	300,000	200,000	250,000	-50,000	4,750,000	0	600,000
2	4,750,000	350,000	0	450,000	150,000	300,000	25,000	4,225,000	0	800,000

The preview shows part of section 1. The full template has all 5 sections (4 not previewed here), with blank rows ready to fill in. Download the full template

How to use it

1
Define the scope once
Pick one scope, for example open pipeline with a close date in the current quarter, and keep it. Pulled in and pushed only exist because of that scope: they are deals moving across the quarter boundary.
2
Take the snapshot at the same time every week
Use a scheduled report or a CRM snapshot at a fixed time, such as Monday 6am. Taking it by hand at different times turns rep activity timing into apparent pipeline movement.
3
Compare deal by deal, not total by total
Join this week's snapshot to last week's on opportunity ID and classify every difference as one movement type. The totals in the bridge are sums of the deal-level log.
4
Stop if the check is not zero
Ending - (Starting + Created + Pulled in - Pushed - Won - Lost + Net amount change) must be zero. If it is not, a deal was missed or double classified. Fix the log before sharing the numbers.

Frequently asked questions

What is a pipeline snapshot report?

A report that captures open pipeline at a fixed point each week and explains the change since the last snapshot as movements: created, pulled in, pushed, won, lost, and amount changes.

How do you reconcile week-over-week pipeline?

Ending = Starting + Created + Pulled in - Pushed - Won - Lost + Net amount change. Build the numbers from a deal-level comparison of the two snapshots and confirm the check equals zero.

What is the difference between pushed and lost pipeline?

Pushed deals are still open but their close date moved outside the reporting period. Lost deals were closed lost. Both reduce this quarter's pipeline, but pushed deals may return, so track them separately.

How often should you snapshot the pipeline?

Weekly is the common cadence for forecast purposes, taken at a fixed time before the forecast call. Daily snapshots are useful for analysis but too noisy to present.