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-019 — Weekly operations summary
Business area: Operations
Best-fit audience: Growing teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Reports take hours and causal claims are hard to verify.

Approved input
Defined fields from approved systems

AI role
Draft a narrative after exact calculations

Human checkpoint
Report owner verifies every number and causal statement

Failure and stop path
Show missing data and source failures explicitly

Data classification
Internal operational data

Measurement
Preparation time; corrections; missing-source rate

Safe first test
Build from a synthetic weekly export with one missing source

PROMPT DRAFT
You are assisting with weekly operations summary. Use only the approved information provided. Draft a narrative after exact calculations. 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 a narrative after exact calculations.
5. Route the result to the named owner for this checkpoint: Report owner verifies every number and causal statement.
6. If anything fails or remains uncertain: Show missing data and source failures explicitly.
7. Record the result using: Preparation time; corrections; missing-source rate.
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