Required context
- RFP question
- Approved answer examples
- Product boundaries
- Legal/commercial notes
Playbook example · Sales ops
RFP response draft
Question class → approved source pattern → drafted answer → owner 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
Owner reviews source coverage before an answer is promoted.
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
RFP response draft
What was reviewed
RFP response draft playbook
Visible context/evidence
RFP question, Approved answer examples
Review gate
Owner reviews source coverage before an answer is promoted.
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.