---
name: pipeline-review
description: "Prepare coverage, aging, conversion and risk review. Use for this workflow with supplied business information."
---

# Pipeline review

## Inputs and purpose

Use this workflow to prepare: Coverage, aging, conversion and risk review.

Start with: Pipeline export, stage definitions, quota and historical snapshots.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Confirm the observation date, stages, target period and opportunity counting rules. Reconcile totals and remove confirmed duplicates from the analysis.

2. Examine coverage, stage aging, conversion history, close-date movement and concentration using consistent definitions.

3. Identify the deals and process gaps that materially affect the objective, distinguishing data-quality problems from commercial risk.

4. Return a pipeline review and action list. Explain assumptions behind coverage or probability measures and avoid counting nominal value as guaranteed revenue.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).