Free browser-based planning tool

Turn one workflow idea into a test brief, prompt, and SOP.

Choose one of 25 CSLM workflow designs. Add an owner and system of record, then download a planning draft. Your entries stay in this browser and are not submitted to CSLM.

Use safe inputs

Do not enter customer records, credentials, payment data, regulated information, or confidential files here. CSLM does not receive these fields.

CSLM WORKFLOW TEST BRIEF

Workflow: WF-021 — SOP first draft
Business area: Knowledge
Best-fit audience: Consulting firms
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Repeatable work depends on one person's memory.

Approved input
Interview notes and approved examples

AI role
Draft trigger, steps, checks, owner and exception path

Human checkpoint
Process owner validates every instruction in a dry run

Failure and stop path
Label unknown steps and keep the current process available

Data classification
Internal process knowledge

Measurement
Dry-run corrections; completion consistency

Safe first test
Draft one low-risk internal SOP and run it with sample data

PROMPT DRAFT
You are assisting with sop first draft. Use only the approved information provided. Draft trigger, steps, checks, owner and exception path. Identify missing or conflicting information instead of guessing. Do not send, publish, pay, delete, merge, approve, or make a commitment. Return: (1) proposed result, (2) source fields used, (3) uncertainties, and (4) items for the human reviewer.

SOP DRAFT
1. Confirm the request is in scope and the input is approved.
2. Preserve the original source and stable record identifier.
3. Run exact validation rules before the AI step.
4. Use AI only for: Draft trigger, steps, checks, owner and exception path.
5. Route the result to the named owner for this checkpoint: Process owner validates every instruction in a dry run.
6. If anything fails or remains uncertain: Label unknown steps and keep the current process available.
7. Record the result using: Dry-run corrections; completion consistency.
8. Keep the manual process available and stop the test if risk or correction effort increases.

A plan is not a production implementation.

Verify requirements with the people who perform the work. Test with synthetic or specifically approved data, review permissions, confirm vendor terms, exercise failure cases, and keep consequential actions under accountable human approval.

← Return to the 25-workflow atlas