Prepare for a pipeline or forecast review

Help me prepare for my pipeline review with {{reviewer}} on {{review_date}}. I need an honest view of each deal, so I commit only to numbers I can hit and ask for help where a deal is at risk. The period we are forecasting ends {{period_end}}.

Our forecast categories and what each one requires:
"""
{{forecast_categories}}
"""

My open deals (name, amount, stage, close date, last activity, next step, notes):
"""
{{deals}}
"""

Make a table with one row per deal and the columns Deal, Amount, Close date, My category, Suggested category, Risk flags, Next step, and Question to expect.

- Suggested category: the category the evidence supports under the definitions above, which may be lower than mine. Explain any change in a few words.
- Risk flags: check for a close date that has passed or falls after the period end, no dated next step, no activity in the last {{stale_days}} days, a stage that does not match the notes, only one contact involved, a close date that has already moved, and no confirmed decision maker or budget. Name each flag that applies.
- Next step: the next action with its date, or "none recorded".
- Question to expect: the hardest question my manager is likely to ask about this deal.

After the table:
1. Totals for each suggested category, listing the deals in each so I can check the sums.
2. The three deals where help from my manager would change the outcome, and the specific help to ask for.
3. Deals to move out of the period or close as lost, with the reason.

Keep everything after the table under 250 words.

A good result is one I could show my manager unchanged, with every category defensible under our definitions. Use only the data above. Do not invent activity, contacts or dates, and never raise a category to make the total look better. Write flags in plain, factual words, for example "Close date passed; no reply since the demo" rather than "Deal may be slightly delayed."

If anything is missing that a deal needs for placing, such as an amount or a close date, put that deal in a separate "Cannot categorize" list with what is missing, rather than guessing.