Free XLSX workbook · Account-free
Weekly Pipeline Review Template: Inspect Evidence, Movement, and Action
A weekly pipeline review workbook for reconciled snapshots, evidence-qualified coverage, change bridges, review queues, and owned actions.
- Method owner
- Anastasiia Krynytska
- Reviewed
- 10 Sep 2026
- Reading
- 9 min read
Practical answer
What this resource does
Use the workbook to inspect material movement and evidence, make explicit portfolio or deal decisions, and write owned actions back to the authoritative record.
- No lead gate. Open, calculate, or download directly.
- Visible method. Definitions, formulas, ownership, and invalid states stay inspectable.
- Human authority. The asset supports a decision; it never owns one.
A weekly pipeline review should decide what to do about material revenue risk. It should not be a tour of every open deal, a forecast recital, or a meeting where the CRM is corrected live without an owner. This workbook creates a reproducible review: the same population rules, evidence standards, movement measures, and decision fields are applied each week.
The asset contains seven linked tabs: Setup, Snapshot, Opportunity Evidence, Changes, Review Queue, Actions, and Decision Log. It is downloadable, account-free, and designed to remain under the user’s control. Formulas operate in the file; the template does not transmit deal data to Luck My Sales.
Gong’s sales pipeline template and Salesforce’s pipeline-review guidance establish useful category patterns. This workbook adds explicit evidence states, qualified-versus-gross coverage, reproducible week-over-week deltas, human authority, and an audit trail. It does not promise forecast accuracy or prescribe one qualification methodology for every sales motion.
01 / Method
Define the population before opening the meeting
The review owner first fixes the as-of timestamp, currency, target period, included teams, included stages, pipeline type, and exclusions. Export or query the same fields each week. If the opportunity population changes, record the change instead of silently rewriting the baseline.
Required setup fields include:
- review ID, week, as-of timestamp, timezone, and currency;
- target period and revenue target;
- source system and extraction time;
- included opportunity types, stages, teams, and owners;
- treatment of renewals, expansions, services, duplicates, and reopened deals;
- qualification method and minimum evidence;
- inactivity threshold and stage-aging thresholds;
- Decision Owner, Operator, Data Owner, and Action Owners.
An open opportunity is not automatically qualified pipeline. Luck My Sales defines pipeline coverage as MEDDPICC-qualified pipeline divided by the target for the same scope and period. Teams using a different method may replace MEDDPICC, but they must name the evidence required and keep gross and qualified values separate. This prevents a coverage ratio from expanding merely because weak records were created.
02 / Method
Build a reconciled snapshot
The Snapshot tab shows counts and values for the declared population. It reports gross open pipeline, qualified pipeline, weighted pipeline if used, target, gross coverage, qualified coverage, new value, advanced value, slipped value, reduced value, lost value, and won value. It also shows data-quality exceptions rather than deleting them from view.
Core formulas are visible:
Gross pipeline = sum of open opportunity value in scope.Qualified pipeline = sum of open opportunity value meeting the declared evidence gate.Qualified coverage = qualified pipeline ÷ target for the same scope and period.Required pipeline = target ÷ win rate, only when the win-rate population is aligned and greater than zero.Weighted pipeline = sum(opportunity value × declared stage or record probability).
Weighted pipeline is a model output, not evidence that a deal is qualified. A probability can be useful when it is versioned and calibrated against comparable historical records. It must not conceal missing buyer evidence. Review the complete metric contracts in Sales KPI formulas.
Coverage has no universal “good” value. A team with long cycles, volatile deal sizes, and low conversion may require more pipeline than a team with short, stable cycles and high conversion. Compare the current ratio with the organization’s own aligned win rate, cycle, slippage, capacity, and target horizon. Do not publish an unlabeled benchmark as a rule.
03 / Method
Inspect opportunity evidence
The Opportunity Evidence tab is one row per material opportunity, with stable IDs rather than display names as keys. It contains account, opportunity, type, owner, stage, value, currency, expected close, created date, last material activity, next step, next-step date, buyer-side owner, seller-side owner, qualification evidence, source links, and review decision.
For a MEDDPICC-based workflow, the workbook treats three fields as mandatory for the owner-specified review:
- Economic Buyer. Name or role, evidence of authority, access state, and the source or date of confirmation.
- Technical Decision Criteria. Stated requirements, constraints, evaluator, validation method, and unresolved gaps.
- Mutual Action Plan. Buyer-agreed events, owners, dates, dependencies, and decision path—not a seller-only task list.
The remaining qualification elements should also be represented where material: Metrics, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, and Competition. The workbook does not convert missing evidence into a zero that can be averaged away. Each element is Confirmed, Partial, Unknown, Contradicted, or Not applicable with reason.
Confirmation requires a traceable record, such as a buyer email, call timestamp, meeting note, shared plan, security request, or approved CRM field with provenance. A generated call summary is a retrieval aid, not self-authenticating buyer evidence. The operator links the underlying record and marks inference separately.
04 / Method
Measure change, not just state
A useful review explains how the pipeline changed since the previous snapshot. The Changes tab joins stable opportunity IDs across weeks and assigns one or more explicit movement types:
- created in scope;
- entered or exited the qualified population;
- stage advanced or regressed;
- value increased or decreased;
- expected close moved into, within, or out of the target period;
- marked won, lost, duplicate, or invalid;
- ownership changed;
- evidence improved, expired, or was contradicted.
For every material delta, store previous value, current value, absolute change, reason, evidence, actor, and timestamp. Do not infer that a moved close date is progression. Slippage is a separate movement and should remain visible even if the opportunity is still open.
Reconcile the bridge from prior snapshot to current snapshot:
Prior open value + new + increases − decreases − won − lost − removed ± scope changes = current open value.When the bridge does not reconcile, show the difference as an exception. Do not bury it in an “other” category without an Action Owner. The Data Owner decides whether the source record, extraction, currency conversion, or scope rule is responsible.
05 / Method
Create the review queue
Not every opportunity deserves equal meeting time. The Review Queue uses transparent flags, not a hidden composite score. A record enters the queue when one or more declared conditions hold:
- high value or high target impact;
- expected close within the review horizon;
- missing or contradicted qualification evidence;
- no dated buyer-agreed next step;
- last material activity older than the configured threshold;
- close-date slippage;
- stage aging beyond the team’s baseline;
- material value change;
- forecast category conflict;
- owner asks for a decision or resource.
The owner specification proposes review or archival for deals inactive more than 45 days. Treat 45 days as a Luck My Sales house control, configurable by motion and stage—not a universal law. “Material activity” should exclude automated email opens, internal tasks, and cosmetic field updates. It should represent a buyer or decision-relevant event.
Sort the queue by decision urgency and potential target effect, then state why each record is present. A seller can challenge a flag with evidence. The Decision Owner resolves the decision; an algorithm does not silently downgrade or remove the opportunity.
06 / Method
Run a 45-minute weekly review
A compact agenda works when preparation is complete:
Minutes 0–5: population and exceptions. Confirm as-of time, target, scope changes, missing extracts, and unreconciled differences. If the data cannot support the intended decision, narrow or postpone that decision.
Minutes 5–12: portfolio movement. Review gross and qualified coverage, the value bridge, creation, progression, slippage, loss, win, and concentration. Ask which change is real, which is administrative, and which requires investigation.
Minutes 12–32: material opportunity decisions. For each queued record, inspect only the evidence needed for a decision. Confirm qualification, buyer path, next event, risk, required help, and forecast implication. Limit status narration.
Minutes 32–40: capacity and interventions. Decide where executive access, technical help, pricing authority, legal/security work, or seller time will change an outcome. Do not allocate resources based only on opportunity size.
Minutes 40–45: commit and close. Read back every action with owner and due date. Record proceed, requalify, resource, reforecast, hold, close, or investigate decisions. Confirm when failed actions return to review.
07 / Method
Record actions that can be audited
The Actions tab contains action ID, linked opportunity or portfolio issue, action, rationale, owner, due date, evidence of completion, status, blocker, escalation owner, and result. A next step requires a date and buyer-side owner when it depends on the buyer. “Follow up” is not an executable action.
Keep the forecast decision distinct from the coaching decision. A deal can remain plausible while its evidence record is weak; the correct action may be to requalify and lower forecast confidence. A seller can need support without being blamed for a system or data failure. The record should make these differences visible.
The Decision Log preserves decisions over time. It stores the options considered, evidence reviewed, Decision Owner, dissent, residual risk, Action Owner, and review date. Do not overwrite a previous week to make the current story appear consistent.
08 / Method
Worked example
This example is illustrative, not a benchmark. Suppose a team has a $500,000 quarterly target, $1,800,000 gross open pipeline, and $1,050,000 that meets its declared qualification gate. Gross coverage is 3.6×; qualified coverage is 2.1×. The difference is not “bad pipeline” by definition. It is a visible evidence gap that the review must classify.
During the week, $200,000 enters scope, $100,000 advances into qualified status, $150,000 slips out of the quarter, $80,000 is won, $40,000 is lost, and $30,000 is removed as duplicate. The bridge and opportunity IDs allow the Data Owner to reconcile the snapshot. The Decision Owner then chooses interventions based on close timing, buyer evidence, concentration, and capacity—not the 3.6× figure alone.
09 / Method
Data quality and governance
No account should remain ownerless under the owner specification. Domain enrichment and deduplication should occur with each relevant webhook or ingestion event, with provenance and exception handling. Regular CRM cleaning matters because duplicate and outdated data can impair decisions; Salesforce provides a useful overview of CRM data cleaning. This citation supports the general control, not a guarantee about any particular cadence or threshold.
Protect sensitive commercial and personal data. Limit workbook access, avoid unnecessary exports, define retention, and use stable internal IDs. If the workbook is distributed, remove confidential fields or provide an empty copy. The template cannot determine legal or security applicability for the user.
10 / Method
Frequently asked questions
Should every open deal appear in the meeting?
It should appear in the population if it is in scope, but only material or flagged records need discussion. Portfolio totals still reconcile to the full declared population.
Is pipeline coverage the same as forecast?
No. Coverage compares pipeline with a target. A forecast estimates an expected outcome using a declared method. Weighted pipeline is also not automatically a forecast.
Can the template work without MEDDPICC?
Yes. Replace the evidence schema with a named method suited to the motion. Preserve the distinction between a stage label and evidence-backed qualification.
What if the source CRM is incomplete?
Mark fields unknown, quantify affected value and count, assign remediation, and limit the decision accordingly. Do not fill missing buyer facts with AI-generated assumptions.
Does Luck My Sales receive the workbook data?
No. The downloadable workbook is intended for local or user-controlled storage. No account or email gate is required.
Method owner: Anastasiia Krynytska, RevOps Architecture Lead. Reviewed 10 September 2026. Thresholds labeled as house controls are configurable; examples are illustrative.
Method & privacy note
Inspect before you act
- The complete approved editorial text is published on this page, not hidden behind the download or interface.
- Calculator inputs stay in browser memory; workbook contents stay wherever the user saves them.
- Unknown, unavailable, contradicted, and not applicable remain distinct states.
- Corrections: corrections@aiinsales.org.