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-010 — CRM completeness check
Business area: CRM
Best-fit audience: Growing teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Incomplete records create reporting and follow-up gaps.

Approved input
CRM fields and controlled validation rules

AI role
Explain missing context and suggest a next-action note

Human checkpoint
Record owner approves additions; AI never fabricates a value

Failure and stop path
Create an exception without overwriting the original record

Data classification
Business contact and activity history

Measurement
Required-field completeness; invented-value incidents

Safe first test
Test a copied synthetic dataset with deliberate gaps

PROMPT DRAFT
You are assisting with crm completeness check. Use only the approved information provided. Explain missing context and suggest a next-action note. 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: Explain missing context and suggest a next-action note.
5. Route the result to the named owner for this checkpoint: Record owner approves additions; AI never fabricates a value.
6. If anything fails or remains uncertain: Create an exception without overwriting the original record.
7. Record the result using: Required-field completeness; invented-value incidents.
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