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-015 — Invoice intake validation
Business area: Data entry
Best-fit audience: Small finance teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Invoices arrive incomplete or cannot be matched.

Approved input
Approved invoice and purchase reference

AI role
Extract fields and explain missing matches

Human checkpoint
Finance approves coding, amounts and next step

Failure and stop path
Hold unmatched or conflicting invoices; never release payment

Data classification
Financial and vendor information

Measurement
Complete first review; unmatched rate

Safe first test
Use fictional invoices including a duplicate and missing PO

PROMPT DRAFT
You are assisting with invoice intake validation. Use only the approved information provided. Extract fields and explain missing matches. 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 fields and explain missing matches.
5. Route the result to the named owner for this checkpoint: Finance approves coding, amounts and next step.
6. If anything fails or remains uncertain: Hold unmatched or conflicting invoices; never release payment.
7. Record the result using: Complete first review; unmatched rate.
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