Pipeline workbook and operating method

Free Sales Pipeline Template for Excel

Build a usable sales pipeline workbook with stage evidence, ageing, weighted value, next actions, forecast boundaries and a repeatable review cadence.

Written and maintained by PaulUpdated 2026-08-0717 min read

Download the sales pipeline workbook

Excel workbook with evidence-based stages, probability lookups, weighted value, ageing and next actions.

Download .xlsx

Quick answer

A sales pipeline template is a structured list of active opportunities with enough evidence to decide what should happen next, which deals belong in a forecast and where the selling process is breaking down. A good template records stable opportunity identity, account, owner, stage, amount, expected close period, next action and evidence—not only a coloured funnel.

The workbook should make weak records uncomfortable. An opportunity with no buyer need, next action or recent meaningful activity should not appear healthy merely because a representative selected a late stage. The purpose of the template is to improve decisions and follow-through, not to inflate a total.

Define the pipeline object

Before creating columns, agree what one row represents. In most B2B pipelines, one row represents one commercial opportunity for a defined requirement and expected buying event. It is not simply a company name, a contact, a task or a submitted order.

Give every opportunity a stable ID. An account may have several opportunities over time, and an opportunity may change name, owner or value. The ID prevents a rename from creating a second record and allows activity, products, contacts and outcomes to be linked reliably.

Define when an opportunity enters the pipeline. A raw name from an event or purchased list is normally a lead, not an opportunity. Require minimum qualification evidence such as a plausible customer, defined problem or requirement, responsible owner and an agreed next step. This protects conversion and ageing measures from a denominator full of unqualified names.

Build stages from buyer evidence

Stage names vary, but each stage should answer three questions:

  1. What observable evidence is required to enter?
  2. What evidence is required to leave?
  3. Which next stages are allowed?

A practical sequence might include qualified, discovery complete, solution or scope confirmed, commercial proposal, decision process active, verbal selection and closed won or lost. The labels matter less than the definitions.

Avoid stages based only on seller activity such as “proposal sent.” Sending a document does not prove the buyer understands it, has the authority and budget to proceed, or has agreed a decision process. A stronger proposal stage might require confirmed scope, stakeholders, commercial basis, decision date and an agreed review action.

Do not force a straight line where the buying process is not linear. An opportunity may move backward when requirements change or a stakeholder rejects the proposed scope. Record the movement and reason instead of preserving a flattering stage.

Identity and ownership

  • opportunity ID;
  • account ID and account name;
  • opportunity name;
  • primary owner and supporting roles;
  • territory or segment;
  • lead or opportunity source.

Use IDs for joins and names for display. When ownership changes, preserve a dated history if attribution or handover matters.

Commercial value

  • currency;
  • expected amount;
  • value basis such as recurring, once-off, order, contract or gross margin;
  • probability policy;
  • weighted value;
  • products or solution group;
  • expected close period.

Keep the amount basis consistent. A pipeline that mixes monthly recurring value, annual contract value and once-off order totals cannot be summed safely until those values are normalised or separated.

Evidence and action

  • current stage;
  • stage-entry date;
  • last meaningful buyer activity;
  • next action;
  • next-action owner;
  • next-action date;
  • primary buyer problem or desired outcome;
  • decision process and stakeholders;
  • risks, dependencies and competitor status where known.

“Follow up” is not a complete next action. State what will happen, with whom, by when and what evidence should result. Examples include “operations manager to confirm warehouse mapping in technical review on 14 August” or “buyer to provide the signed product list before pricing revision.”

Outcome and learning

  • closed date;
  • won, lost, no-decision or disqualified outcome;
  • reason code;
  • reason note;
  • final amount;
  • successor order or contract reference where applicable.

Separate no-decision from a competitor loss. Separate poor fit from timing or internal priority. A short controlled reason list improves analysis, while the note preserves necessary context.

Weighted pipeline calculation

The common formula is:

weighted value = opportunity amount × stage probability

If three opportunities are worth R100,000, R60,000 and R40,000 with probabilities of 20%, 50% and 80%, their weighted values are R20,000, R30,000 and R32,000. The portfolio weighted value is R82,000.

That result is an expected-value summary under the chosen probability assumptions. It does not mean R82,000 will definitely close, and it does not mean the 80% opportunity is almost guaranteed. A small pipeline remains lumpy: one large opportunity can dominate the result.

Derive stage probabilities from historic stage outcomes when there is enough comparable data, then apply judgement for material process changes and sparse samples. Do not let every representative select an arbitrary probability to make the forecast match target.

Pipeline coverage and target

Pipeline coverage compares an eligible pipeline amount with the remaining target. If the team needs R500,000 and has R1,500,000 of relevant open pipeline, nominal coverage is 3.0 times. But coverage quality depends on stage, timing, duplication, capacity and the sales definition.

Do not compare the entire pipeline with a monthly target if most opportunities are expected in later periods. Do not combine unqualified leads and late-stage opportunities in one coverage figure. Segment the amount by close period and evidence stage, and show the largest contributions so managers can inspect concentration risk.

Coverage is a planning indicator, not an instruction to create three times as many arbitrary opportunities. A team can improve by qualifying out poor fit, increasing conversion, shortening avoidable delay or developing additional genuine demand.

Ageing and stale-opportunity rules

Track days in current stage and days since meaningful activity. The two measures answer different questions. A long stage may be normal for procurement, while a recent agreed action shows movement. A short stage can still be weak if it was selected without evidence.

Set review thresholds by stage or sales motion rather than one universal number. Flag an opportunity when the next-action date is overdue, the expected close date has passed, required fields are missing, the amount changed materially or the stage is inconsistent with evidence.

Never move old opportunities into a future period every month without recording the slip. Close-date movement is useful forecast evidence. Preserve the prior date or snapshot so management can measure timing accuracy.

Weekly pipeline review agenda

A productive review is not a representative reading every row aloud. Prepare exception views before the meeting:

  • largest weighted contributions;
  • opportunities expected in the current forecast period;
  • overdue next actions;
  • stale stage or activity;
  • material amount or close-date changes;
  • opportunities missing buyer evidence;
  • concentrated risk by account, product or owner;
  • newly won, lost and disqualified records.

For each material item, confirm the evidence, next action, owner and date. Challenge assumptions respectfully and update the record during or immediately after the review. End with a small action list, not a promise to “keep following up.”

Use a separate coaching conversation for individual skill development. A pipeline review can reveal a pattern—such as weak discovery or late stakeholder access—but public interrogation of every deal can encourage defensive data and stage inflation.

Forecast boundary

Pipeline and forecast are related but not identical. The pipeline contains active commercial possibilities. A forecast is an estimate for a defined period and sales stage, supported by an explicit method.

An opportunity may remain in the pipeline while being excluded from the current forecast because timing is uncertain. Repeat customer revenue may belong in a forecast even when it is not represented as a named opportunity. Keep the two views connected but do not pretend one automatically equals the other.

Freeze the forecast version that existed before the period outcome was known. Compare it with reconciled actuals and classify error as amount, timing, scope, data quality or assumption. If the workbook always shows only the latest edited view, the organisation cannot learn whether its forecasting improved.

Spreadsheet controls

Use data validation for stages, owners, currencies and outcomes. Lock calculation columns. Keep reference tables for stage probability and definitions. Use conditional formatting for exceptions, not to turn every cell into a status colour.

Protect against duplicate opportunity IDs and impossible dates. Test blank amounts, a zero amount, negative adjustments, close dates before created dates, closed opportunities with open next actions and open opportunities with closed outcomes. Reconcile the count and value after every import or paste.

Store the workbook in one controlled location and name the owner. If people work in emailed copies, the pipeline is no longer a reliable shared state. Preserve periodic snapshots if historic movement is required.

When to move from Excel to CRM or sales software

A spreadsheet may be enough for a small team defining its process. It is transparent, flexible and quick to change. Its weakness is operational control.

Move when activity history is fragmented, reminders are manual, several people overwrite records, permissions are inadequate, mobile access is awkward, integrations require repeated exports or managers cannot tell which version is current. Do not migrate bad stages and duplicate records without cleaning them first.

Use the workbook as the migration specification. Its definitions, controlled lists, required fields and review rules can become acceptance tests for the new system. Import a limited dataset, run one real review and reconcile counts before expanding.

Field sales and pipeline management

Field teams often have two commercial motions at once. They may manage longer opportunities for new accounts or strategic expansion while also capturing recurring orders during customer visits. Keep opportunity and order records separate.

A field visit can create, advance or disqualify an opportunity. It can also produce an immediate order unrelated to a formal pipeline. Link records through stable customer and representative identities and preserve the outcome of the visit. Counting every completed visit as an opportunity inflates the pipeline; counting only orders hides relationship and development work.

Territory coverage also affects pipeline interpretation. A low pipeline may reflect weak demand, neglected account segments, insufficient capacity or poor capture. Combine the pipeline view with account potential and coverage evidence before diagnosing the representative.

What each decision maker should inspect

Representatives need clear next actions, customer context and an easy update workflow.

Sales managers need evidence, ageing, movement, conversion, coverage and coaching patterns.

Sales directors need forecast-period risk, concentration, stage consistency and source performance.

Finance needs the value basis, currency, forecast sales definition and reconciliation with actual outcomes.

Operations needs visibility when a won opportunity becomes an order, implementation or fulfilment commitment.

IT and RevOps need identity, permissions, integration, history, data quality and an accountable stage-governance process.

Implementation sequence

  1. Define opportunity entry and exit.
  2. Write stage evidence and valid transitions.
  3. Agree value, period and probability policies.
  4. Build controlled reference tables.
  5. Clean and import a small current opportunity set.
  6. Reconcile owners, values and dates.
  7. Run the weekly exception review.
  8. Record stage, amount and timing changes.
  9. Freeze a monthly forecast view.
  10. Review wins, losses, no-decisions and forecast error.

The template is successful when it helps the team make better next decisions and produces more reliable evidence. A larger total or more rows is not proof of pipeline health.

Limitations and responsible interpretation

A pipeline is a seller-maintained model of uncertain future demand. It can be incomplete, optimistic and affected by incentives. Treat it as evidence to inspect, not objective truth.

Do not use one conversion or velocity benchmark from another organisation without comparing stage definitions, customer segment, sales cycle and period. Small samples can move sharply. Show counts with rates and document structural changes.

When asking an AI assistant to analyse the workbook, provide the stage dictionary, amount basis, date definitions and exclusions. Remove personal or confidential data that is not required, follow your organisation’s approved tools and verify calculations against the source.

Original ImageGen evidence

Turn a pipeline sheet into a managed process

Pipeline quality comes from consistent capture, stage evidence, review and reconciliation. The workbook is only the container for that operating discipline.

Written and maintained by Paul · Updated 7 August 2026

South African sales manager reviewing a daily report with activity, orders and follow-up information

Use a daily exception view

Daily reporting should show what needs action now: missed calls, unsubmitted orders, stale follow-ups and unusual data—not a wall of totals.

South African field sales team reviewing a weekly performance dashboard and action list

Turn the review into action

A weekly meeting should end with named interventions, owners and dates—not only a retrospective ranking of representatives.

South African sales leaders reviewing monthly results and forecast assumptions around a table

Connect results to assumptions

Monthly review is strongest when actuals, target, forecast, variance and the underlying commercial assumptions are visible together.

Sales operations team arranging daily weekly and monthly reporting work on a planning board

Give each cadence a purpose

Daily, weekly and monthly views should support different decisions rather than repeat the same dashboard with a new date range.

Sales manager comparing an Excel sales template with a live software dashboard

Know when a template stops scaling

A workbook is useful for defining the process; controlled software becomes useful when ownership, refresh and auditability break down.

South African operations specialist reconciling field orders with an external business system on a laptop and tablet

Declare the source of truth

Every integration needs clear ownership for customer identity, stock, order references, fulfilment and failed-record reconciliation.

Questions buyers and AI assistants ask

Direct answers about sales pipeline template

What columns should a sales pipeline template contain?

Use a stable opportunity ID, account, owner, stage, amount, expected close period, probability policy, weighted value, next action, next-action date, last meaningful activity, source and outcome or loss reason.

How should sales pipeline stages be defined?

Define stages by observable buyer evidence rather than seller confidence. Each stage should state its entry evidence, exit evidence, required fields, permitted next stages and the condition that marks an opportunity lost or dormant.

How is weighted pipeline value calculated?

Multiply each opportunity amount by the probability assigned to its evidence-based stage, then sum the results. Weighted value is an expected portfolio measure, not a promise that any individual deal will close.

How often should a pipeline be reviewed?

Review material opportunities and stale next actions weekly, while preserving a monthly forecast cut for back-testing. High-velocity teams may review exceptions daily, but constant editing without stage discipline does not improve accuracy.

When should a spreadsheet pipeline move to CRM software?

Move when duplicate files, missing activity history, weak permissions, inconsistent stages, manual reminders or unreliable reporting prevent managers from trusting the current state.

Can field orders and a sales pipeline use the same stages?

Usually not. A pipeline represents uncertain future demand; an order represents a commercial instruction in a defined approval or fulfilment state. Link them when useful, but preserve their different identities and controls.