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-001 — New inquiry completeness check
Business area: Sales
Best-fit audience: Local services
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Incomplete inquiries delay estimates and assignment.

Approved input
Approved form fields and service request

AI role
Summarize free text and identify missing details

Human checkpoint
Confirm identity, scope, destination and any commitment

Failure and stop path
Hold incomplete or conflicting requests in a visible queue

Data classification
Contact information; avoid sensitive attachments

Measurement
Complete requests at first review; correction rate

Safe first test
Run 10 synthetic inquiries including missing and conflicting fields

PROMPT DRAFT
You are assisting with new inquiry completeness check. Use only the approved information provided. Summarize free text and identify missing details. 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: Summarize free text and identify missing details.
5. Route the result to the named owner for this checkpoint: Confirm identity, scope, destination and any commitment.
6. If anything fails or remains uncertain: Hold incomplete or conflicting requests in a visible queue.
7. Record the result using: Complete requests at first review; correction 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