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.
Generated planning draft
CSLM WORKFLOW TEST BRIEF Workflow: WF-017 — Document collection checklist Business area: Operations Best-fit audience: Consulting firms Owner: [name the accountable owner] System of record: [name the authoritative system] Problem Teams repeatedly determine which documents are missing. Approved input Service type and approved intake record AI role Compare received items with controlled requirements Human checkpoint Staff confirms sensitivity, necessity and communication channel Failure and stop path Stop rather than requesting unnecessary or confidential documents Data classification Potentially confidential documents Measurement Complete packets; unnecessary requests Safe first test Use filenames and synthetic metadata before document contents PROMPT DRAFT You are assisting with document collection checklist. Use only the approved information provided. Compare received items with controlled requirements. 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: Compare received items with controlled requirements. 5. Route the result to the named owner for this checkpoint: Staff confirms sensitivity, necessity and communication channel. 6. If anything fails or remains uncertain: Stop rather than requesting unnecessary or confidential documents. 7. Record the result using: Complete packets; unnecessary requests. 8. Keep the manual process available and stop the test if risk or correction effort increases.
What this tool does not do
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.