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-024 — Customer-question content outline
Business area: Marketing
Best-fit audience: Local services
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Useful customer questions are not reflected in website content.

Approved input
Anonymized question themes and verified service facts

AI role
Cluster intent and propose a useful outline

Human checkpoint
Owner confirms demand, facts, privacy and cannibalization risk

Failure and stop path
Reject thin location variants and unsupported claims

Data classification
Anonymized themes

Measurement
Validated topics; impressions and clicks

Safe first test
Use ten non-identifying questions to outline one service page

PROMPT DRAFT
You are assisting with customer-question content outline. Use only the approved information provided. Cluster intent and propose a useful outline. 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: Cluster intent and propose a useful outline.
5. Route the result to the named owner for this checkpoint: Owner confirms demand, facts, privacy and cannibalization risk.
6. If anything fails or remains uncertain: Reject thin location variants and unsupported claims.
7. Record the result using: Validated topics; impressions and clicks.
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