Use Claude or Codex to review deal stage, probability, close date, next action, risk, and forecast category before publishing a pipeline forecast in Sanka.
Last updated: May 16, 2026
This guide shows how to build a pipeline forecast in Sanka with AI review. Start by asking Claude or Codex to inspect open deals and explain risk, then confirm forecast categories before publishing the forecast.
Claude/Codex
Review this quarter's open pipeline. Check stage, probability, amount, close date, next action, activity history, risk, and forecast category. Prepare a forecast draft only; do not publish it yet.
Preparing pipeline forecast draftI prepared a forecast draft grouped by commit, best case, pipeline, and risk. Please review stale deals, missing next actions, and close date changes before publishing.
Ask for another forecast check...
Before you start
Check that you have the following ready.
Deals and stages are available in Sanka
Owners, close dates, amounts, probabilities, and next actions are up to date
Your team has forecast categories such as commit, best case, pipeline, and omitted
Activity history or notes are available if you want AI to explain risk
You have permission to view and publish pipeline reports
Ask AI to review the forecast inputs
Ask Claude or Codex to review the pipeline before publishing. The goal is to find deals that are stale, over-weighted, missing next actions, or sitting in the wrong forecast category.
Sample prompt
/sanka Review open deals for this quarter. For each deal, show amount, owner, stage, probability, close date, latest activity, next action, risk, and forecast category. Explain any category changes you recommend.
Ask the AI to flag:
Close dates that moved multiple times
Deals with no recent activity
High-probability deals without a next action
Amount changes that affect forecast confidence
Deals assigned to the wrong owner or stage
Adjust forecast categories
After the review, adjust categories with evidence. Do not move a deal to commit only because the stage probability is high; confirm the next action, buyer signal, and operational readiness.
Sample prompt
/sanka Recommend forecast category changes for these deals. Use buyer activity, next action, close date confidence, quote status, and operational blockers. Keep all category changes pending for review.
Common categories:
Commit: strong buyer signal, clear next step, and close date confidence
Best case: possible this period, but with unresolved risk
Pipeline: active but not ready for forecast pressure
Omitted: stale, duplicate, unqualified, or pushed out
Publish and monitor changes
When the sales owner or manager approves the forecast, publish it to reports. Review changes weekly so stale deals and close-date slips do not hide in the forecast.
Checkpoints
Use Sanka logs and reports to confirm who changed forecast categories, what reason was recorded, and how the forecast moved by owner or segment.
Search Sanka...
Review pipeline forecast activity
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
4Forecast published2026/05/12 17:00Q2 pipeline forecastPublished reviewed forecast by ownerSales manager
3Category changed2026/05/12 16:25Castem expansion / DealMoved from best case to pipeline due to missing next actionSales manager
2Forecast draft reviewed2026/05/12 15:45Q2 pipeline forecastChecked stale deals and close date changesClaude / Codex
1Forecast draft created2026/05/12 15:20Q2 pipeline forecastGrouped open deals by forecast categoryClaude / Codex
You can also confirm forecast category, amount, close date, owner, and risk notes from the deal table.
