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-016 — Spreadsheet category suggestions
Business area: Data entry
Best-fit audience: Growing teams
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Manual categorization varies between employees.

Approved input
Copy of a spreadsheet with stable row IDs

AI role
Suggest categories in a new column

Human checkpoint
Data owner approves changes and verifies formulas

Failure and stop path
Preserve source file and reject unknown categories

Data classification
Depends on spreadsheet contents

Measurement
Accepted categories; formula damage

Safe first test
Use a synthetic copy with known expected categories

PROMPT DRAFT
You are assisting with spreadsheet category suggestions. Use only the approved information provided. Suggest categories in a new column. 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: Suggest categories in a new column.
5. Route the result to the named owner for this checkpoint: Data owner approves changes and verifies formulas.
6. If anything fails or remains uncertain: Preserve source file and reject unknown categories.
7. Record the result using: Accepted categories; formula damage.
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