Required context
- Opportunity list
- Stage rules
- Risk criteria
- Follow-up owners
Playbook example · RevOps
Pipeline review prep
Evidence → risk → next step → owner → follow-up → manager review.
The anatomy
What this playbook carries.
A playbook is not a prompt template. It is the working method: the inputs, steps, review gate, visible evidence, review record, and version history around recurring AI-assisted work.
Review gate
Manager reviews stalled-deal reasons and next steps.
Review record
Each record holds what was reviewed, the evidence it was built from, where a human signed off, and the version it proposes.
The record one run leaves behind.
Every reviewed run leaves the same record: what was reviewed, the evidence it was built from, where a human signed off, and the version the next run inherits.
Review record
Pipeline review prep
What was reviewed
Pipeline review prep playbook
Visible context/evidence
Opportunity list, Stage rules
Review gate
Manager reviews stalled-deal reasons and next steps.
Next version
Version proposed for the next run
Start with one workflow.
Bring this workflow, or one your team already repeats, and shape it into a shared, reviewable playbook with the steps, the review gate, and the version built in.