# Sales pipeline review
Turn supplied pipeline data into an evidence-bounded operating review. Preserve the distinction between a reported stage and the evidence that supports it.
When supplied notes, calls, or messages need to be turned into pipeline data, extract only proposed activities, stage changes, dates, owners, and next steps. Resolve the opportunity or contact from explicit evidence, preserve ambiguity, and normalize dates only when their meaning is clear. Return proposed record changes for approval; this method never writes them.
Workflow
1. Establish the as-of date, stage definitions, currency, and value type for each opportunity. Keep recurring, one-time, booked, open, and forecast value separate. 2. Normalize the supplied records without overwriting conflicting information. Flag missing owner, next action, next date, value, or source evidence. 3. Report pipeline by stage and value type. Include the denominator for every conversion or activity rate, and do not infer trends from one snapshot. 4. Identify overdue follow-ups, stalled deals, stage-evidence conflicts, concentration risk, and decisions needed. 5. Provide a ranked action queue with the owner, evidence, and next action. Draft proposed record corrections separately for the host record owner.
Review method
Classify the supplied material as a snapshot, period comparison, or incomplete history. For each stage show count, value type, denominator, as-of date, and source coverage. Separate pipeline hygiene from activity logging or record capture, and preserve conflicting buyer evidence beside the reported stage. Identify stale next actions, missing owners/dates, duplicate records, stage definition gaps, concentration, and dependencies. Rank remediation by impact and evidence, then return proposed updates for review rather than applying them.
Forecast discipline
Do not invent win probabilities, a committed forecast, or a growth rate. A reported Won stage that conflicts with a buyer's stated condition remains a conflict to resolve, not a 100% forecast.
Output
Return an as-of statement, stage and value summary, hygiene findings, risk register, action queue, and clearly labeled proposed updates.
Boundaries
This method is read-only. It does not update a CRM, send follow-ups, or alter an opportunity stage. It does not infer missing probabilities, dates, or trends from a single snapshot.