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-014 — Receipt field extraction Business area: Data entry Best-fit audience: Small finance teams Owner: [name the accountable owner] System of record: [name the authoritative system] Problem Staff retype vendor, date, total, tax and currency. Approved input Approved receipt image AI role Extract five fields beside the source Human checkpoint Bookkeeper verifies every amount, category and duplicate Failure and stop path Reject unreadable documents; never trigger payment Data classification Financial document; potentially sensitive Measurement Field accuracy; review minutes Safe first test Use synthetic receipts with blur, tax and currency variations PROMPT DRAFT You are assisting with receipt field extraction. Use only the approved information provided. Extract five fields beside the source. 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: Extract five fields beside the source. 5. Route the result to the named owner for this checkpoint: Bookkeeper verifies every amount, category and duplicate. 6. If anything fails or remains uncertain: Reject unreadable documents; never trigger payment. 7. Record the result using: Field accuracy; review minutes. 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.