Home
cd ../playbooks
Operations & ComplianceIntermediate

Process Documentation Builder

Document business processes with flowcharts, RACI matrices, and standard operating procedures

10 minutes
By AnthropicSource
#process-docs#sop#raci#flowcharts#documentation
CLAUDE.md Template

Download this file and place it in your project folder to get started.

# Process Documentation Builder

Document a business process as a complete standard operating procedure (SOP).

## How It Works

Walk me through the process — describe it, paste existing docs, or just tell me the name and I'll ask the right questions. I'll produce a complete SOP.

## Output

```markdown
## Process Document: [Process Name]
**Owner:** [Person/Team] | **Last Updated:** [Date] | **Review Cadence:** [Quarterly/Annually]

### Purpose
[Why this process exists and what it accomplishes]

### Scope
[What's included and excluded]

### RACI Matrix
| Step | Responsible | Accountable | Consulted | Informed |
|------|------------|-------------|-----------|----------|
| [Step] | [Who does it] | [Who owns it] | [Who to ask] | [Who to tell] |

### Process Flow
[ASCII flowchart or step-by-step description]

### Detailed Steps

#### Step 1: [Name]
- **Who**: [Role]
- **When**: [Trigger or timing]
- **How**: [Detailed instructions]
- **Output**: [What this step produces]

#### Step 2: [Name]
[Same format]

### Exceptions and Edge Cases
| Scenario | What to Do |
|----------|-----------|
| [Exception] | [How to handle it] |

### Metrics
| Metric | Target | How to Measure |
|--------|--------|----------------|
| [Metric] | [Target] | [Method] |

### Related Documents
- [Link to related process or policy]
```

## Tips

1. **Start messy** — You don't need a perfect description. Tell me how it works today and I'll structure it.
2. **Include the exceptions** — "Usually we do X, but sometimes Y" is the most valuable part to document.
3. **Name the people** — Even if roles change, knowing who does what today helps get the process right.
README.md

What This Does

Turns messy process descriptions into complete standard operating procedures (SOPs). Generates RACI matrices, process flows, detailed step-by-step instructions, exception handling, and metrics — all from a conversation about how work gets done.


Quick Start

Step 1: Download the Template

Click Download above to get the CLAUDE.md file.

Step 2: Set Up Your Project

Create a project folder and place the template inside:

process-docs/
├── CLAUDE.md
├── sops/           # Generated SOPs
└── diagrams/       # Process flow diagrams

Step 3: Start Working

claude

Say: "Document our employee offboarding process"


What Gets Produced

  • Purpose & Scope — Why the process exists and what it covers
  • RACI Matrix — Responsible, Accountable, Consulted, Informed for each step
  • Process Flow — Visual representation of the process
  • Detailed Steps — Who, when, how, and expected output for each step
  • Exceptions — Edge cases and how to handle them
  • Metrics — KPIs with targets and measurement methods

Tips

  • Start messy — You don't need a perfect description. Just explain how it works today
  • Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part
  • Name the people — Knowing who does what today helps get the process right

Example Prompts

"Document our employee offboarding process"
"Create an SOP for our monthly financial close"
"Build a process doc for handling customer refunds"
"Document how we handle vendor onboarding"

$Related Playbooks