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-009 — Appointment reminder preparation
Business area: Support
Best-fit audience: Local services
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Reminder preparation is repetitive and errors damage trust.

Approved input
Confirmed appointment and contact preference

AI role
Prepare an approved reminder draft

Human checkpoint
Staff controls recipient, time zone, cancellation and accommodations

Failure and stop path
Do not prepare a message when status or consent is unclear

Data classification
Contact and scheduling information

Measurement
On-time reviewed reminders; contact errors

Safe first test
Use 10 synthetic appointments across two time zones

PROMPT DRAFT
You are assisting with appointment reminder preparation. Use only the approved information provided. Prepare an approved reminder draft. 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: Prepare an approved reminder draft.
5. Route the result to the named owner for this checkpoint: Staff controls recipient, time zone, cancellation and accommodations.
6. If anything fails or remains uncertain: Do not prepare a message when status or consent is unclear.
7. Record the result using: On-time reviewed reminders; contact errors.
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