AI SOP Library
Six departmental procedures. Defined inputs, named approval roles, and evidence required before use.
Untested general-purpose draft. All procedure steps, quality checks, and acceptance tests are not run.
Jump to section tap to open
Department templates
-
Sales SOP: Call to reviewed CRM handoff
Prepare a timestamped account note, proposed CRM changes, and an unsent follow-up from approved call evidence.
Approval role: Designated sales reviewer
-
Marketing SOP: Source-checked content review
Prepare a claim register, proposed edits, and an editorial review packet without publishing or inventing evidence.
Approval role: Managing editor
-
Operations SOP: Decision-oriented intelligence brief
Compare approved dated sources with the previous reviewed state and propose decisions only when a verified change matters.
Approval role: Operations lead
-
Customer Success SOP: Evidence-backed escalation handoff
Separate reported symptoms, observed behavior, and hypotheses in a redacted escalation packet with an unsent response.
Approval role: Customer success lead
-
Recruiting SOP: Role-based interview question pack
Draft task-linked questions and an unfilled evidence sheet from a role brief. No applicant analysis, scores, or hiring decisions.
Approval role: Hiring manager and designated people reviewer
-
AI Agent SOP: Bounded trial and recovery specification
Specify a synthetic read-only trial, permission boundaries, failure cases, and recovery evidence without running an agent.
Approval role: Agent owner and recovery owner
Review boundaries
These are proposed templates, not actual Belkins SOPs or hands-on test reports. No external actions, sends, model calls, or schedules are performed or configured. No action is preapproved.
Role labels are placeholders, not assigned approvers. Before operational use, identify specific people, clear the input data, resolve conflicting requirements, and design a controlled synthetic trial. Expected results are not observed results.
Recruiting is limited to role-based questions and an unfilled evidence sheet. Applicant analysis, scoring, ranking, profiling, and hiring decisions are outside its scope.
The workflow planner assembles an editable specification. It does not validate the procedure or run its checks. The sales, marketing, and operations SOPs start from the closest existing planner presets; their fields are starting values: replace the owner, approver, trigger, and inputs with the SOP's, and reconcile the rest. Outbound campaign QA remains a separate planning template.
Chapter 11: Build a Skill connects a reviewed procedure to reusable instructions. Chapter 25: Evals covers the evidence needed to judge an implementation.