Forecast notes for pipeline review

Create a consistent forecast note for every opportunity being reviewed. Use this workflow when you need to turn CRM fields, call notes and recent deal activity into a position that a sales representative and forecast owner can challenge quickly.

The output is not a deal summary. It is a short record of what is known, what is blocked, what happens next and why the current forecast confidence is justified.

1. Set the review scope

Start with the opportunity list for the review. Export or copy only the records that need a forecast note. For each opportunity, collect the same inputs before asking the model to draft anything.

Use these inputs:

• Opportunity name, account name and owner
• Stage, amount, target close date and forecast category from the CRM
• Last activity date and the two or three most recent logged activities
• Call notes from the latest customer conversation
• Email or meeting outcomes that change timing, scope, stakeholders or competition
• The agreed next step, its owner and due date, if one exists
• Previous forecast note, if it exists
• Known risks, including procurement, security review, budget approval, legal review or missing stakeholder access

Keep the source material with each opportunity. Do not combine notes from different deals into one unlabelled block. If you use an AI workspace or API, check the current data handling and product details in the xAI documentation overview before supplying customer information. Available features and controls are version-dependent.

2. Normalise the source record

Make a compact input record before drafting the forecast note. This stops a long call transcript from outweighing the CRM record or an older, more relevant decision.

For each opportunity, arrange facts under these labels:

Field	What to record	Example standard
Deal position	Current stage and the event needed to progress	Proposal sent; buyer review meeting still needed
Evidence	Dated facts that support the position	14 Aug: operations lead confirmed evaluation criteria
Change since last review	New information only	Security review added to process
Blockers	Named unresolved conditions	Budget holder has not joined a call
Next action	One action, one owner, one date	Rep to book budget call by Friday
Confidence	Your stated confidence and its basis	Medium, technical fit confirmed but commercial approval open

Use absolute dates in the source record. Replace next week, soon and after the holiday with the actual date where it is known. If the date is not known, write date not agreed.

Separate fact from interpretation. For example:

• Fact: The procurement manager requested the supplier form on 12 Aug.
• Interpretation: Procurement is now active, but no approval timeline has been confirmed.

This distinction matters during a pipeline review. Facts can be checked. Interpretations can be debated.

3. Draft the note with a fixed instruction

Use one prompt structure for every opportunity. Paste the normalised record beneath it. Do not ask for a generic summary.

Draft a forecast note for a pipeline review using only the source record.

Return these headings:
1. Deal position
2. Evidence
3. Blockers
4. Next action
5. Forecast confidence

Rules:
- State facts separately from judgement.
- Include dates for evidence and next actions where supplied.
- Do not invent buyer intent, approvals, dates, stakeholders or competition.
- If evidence is missing, say "not evidenced in source record".
- Keep each heading to one or two sentences.
- Describe forecast confidence as High, Medium or Low, then give the reason.

Source record:
[PASTE ONE OPPORTUNITY HERE]

Run one opportunity at a time when call notes are detailed or deal histories conflict. This makes it easier to compare the output with the source record. For a large review, use the same fields in a structured sheet, then draft notes in batches only after each row has been checked for complete inputs.

4. Check the draft against the record

Read the note beside the source record. Check every sentence that makes a claim about the customer, timing or likelihood of close. The model can make a fluent sentence from incomplete evidence. Fluency is not verification.

Use this check before saving the note:

1. Find each named stakeholder. Confirm that person appears in a source item.
2. Find each date. Confirm it is either in the record or clearly marked as unconfirmed.
3. Check the stage. Does the stated next action match the event required to leave that stage?
4. Check the blocker. Is it unresolved, material and specific to this opportunity?
5. Check the confidence reason. Does it cite both supporting evidence and any material uncertainty?
6. Remove claims such as on track, strong deal or likely to close unless the note explains why.

Use this table to correct common failures.

If you see this	It usually means	Do this
Customer is committed	Intent was inferred from a positive call	Replace it with the customer action or mark commitment unconfirmed
A close date with no event tied to it	The CRM date was copied without testing it	State the required event and whether it is scheduled
Follow up with customer	The next action has no accountable outcome	Name the owner, action, customer contact and date
High confidence with open approval	Risk was omitted	Lower confidence or explain why approval is no longer material
A long evidence section	Notes were summarised rather than selected	Keep only facts that affect stage, timing, scope or probability

5. Save and hand over the review pack

Paste the checked note into the opportunity's forecast-note field, review document or agreed CRM activity format. Put the review date at the top if your team uses a separate document. Keep the wording stable between reviews so changes are visible.

During the review, hand over three things for each opportunity:

• The current forecast note
• The source links or CRM activity references used to support it
• A list of actions due before the next review, with owners and dates

After the meeting, update only the fields that the review changed. If the group changes confidence, record the evidence behind that change. Do not overwrite the prior note without preserving what changed, otherwise you lose the audit trail for missed dates and repeated blockers.

When the workflow does not work

Stop and return to the source record if the draft contains claims you cannot verify, conflicting dates or an unclear next step. Ask the opportunity owner for the missing fact, rather than asking the model to make the note sound more certain.

If most notes need major rewriting, tighten the input record first. Missing call outcomes, vague next actions and stale CRM stages are source-data problems. Fix those fields, then rerun the draft using the same structure.