CheckAI playbook

The standing instructions your CheckAI teammate follows. Configure the org-wide voice and per-event-type defaults so every gig starts from your best practice.

Concept — not yet in the real product

No CheckAI playbook UI exists in the real product yet — the backend holds a free-text Organization.agentPlaybook field and a structured EventTypePlaybook model. Per checkai.md, event-type playbooks are described as CheckAI's moat. This page is a deliberate spec, not a mirror — CheckAI is a "digital worker, not a copilot", so this should feel like configuring a teammate's standing instructions, not toggling app settings.

Org-wide playbook

Voice

Tone

FormalCasual

Proactivity

ReactiveProactive

Brevity

DetailedTerse

Tool approvals

Consequential tools go through the MCP confirmation gate — a Change Card you approve or reject. Auto-approved tools run silently.

Send message to crew or client

SMS, email, or in-app.

AutoApproval

Settle a gig

Double-gated: payout gate + closeout gate.

AutoApproval

Commit a file-import change card

Applies schedule / crew / expense / venue mutations.

AutoApproval

Invite crew (draft → send)

Flips NOT_SENT drafts to SENT.

AutoApproval

Record a payment / mark paid

Writes SUCCEEDED transactions.

AutoApproval

Create a new gig

From a lead, template, or intake form.

AutoApproval

Read gig details

Roster, timeline, files, activity.

AutoApproval

Read financial reports

Ledger, invoices, payouts.

AutoApproval

Propose a schedule / run-of-show

Drafts only, never commits.

AutoApproval

Org guidance

Free-text standing instructions. Backs the real Organization.agentPlaybook field.

Event-type playbooks

— the moat.

How each event type runs, so CheckAI drafts each gig from your best practice. Pre-filled examples for Wedding, Festival, and Corporate.