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-002 — Lead routing recommendation
Business area: Sales
Best-fit audience: Growing teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Requests wait because ownership is unclear.

Approved input
Validated inquiry, location, service and timing

AI role
Classify ambiguous request text after exact territory rules

Human checkpoint
Approve unclear, sensitive or high-value assignments

Failure and stop path
Leave the request unassigned with a named queue owner

Data classification
Business contact information

Measurement
Time to valid assignment; reassignment rate

Safe first test
Compare recommendations with 15 previously resolved synthetic cases

PROMPT DRAFT
You are assisting with lead routing recommendation. Use only the approved information provided. Classify ambiguous request text after exact territory rules. 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: Classify ambiguous request text after exact territory rules.
5. Route the result to the named owner for this checkpoint: Approve unclear, sensitive or high-value assignments.
6. If anything fails or remains uncertain: Leave the request unassigned with a named queue owner.
7. Record the result using: Time to valid assignment; reassignment 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