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

Problem
Duplicate contacts fragment history and ownership.

Approved input
Stable IDs, contact fields and dates

AI role
Rank likely duplicate pairs

Human checkpoint
Authorized owner decides whether any records merge

Failure and stop path
Leave both records unchanged when evidence is weak

Data classification
Contact information

Measurement
Precision of candidates; incorrect merge count

Safe first test
Plant five duplicates among 30 synthetic records

PROMPT DRAFT
You are assisting with duplicate-record candidate list. Use only the approved information provided. Rank likely duplicate pairs. 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: Rank likely duplicate pairs.
5. Route the result to the named owner for this checkpoint: Authorized owner decides whether any records merge.
6. If anything fails or remains uncertain: Leave both records unchanged when evidence is weak.
7. Record the result using: Precision of candidates; incorrect merge count.
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