Map the work before you automate it.

Make the handoffs, judgment calls, and failure points visible before a tool makes them expensive. Everything autosaves in this browser.

Workflow canvas

Move left to right. Loop back when new information changes the path.

Swipe the canvas left to see all five stages →

1Trigger

See completed example

A new client inquiry is submitted through the website contact form.

2Inputs

See completed example

Name and email Project description Budget range Lead source Existing CRM record

3Decisions

See completed example

Is this a good-fit client? Which service path is best? Do we have capacity? What needs human review?

4Actions

See completed example

Send acknowledgement Create CRM record Assign an owner Draft follow-up Set response deadline

5Human checkpoints

See completed example

Fit decision Pricing exception Sensitive reply Low-confidence output No response after 3 days

Name the exact event.

Avoid vague triggers such as “when needed.”

Capture every dependency.

Include data, files, context, and access.

Make judgment explicit.

Write the rule or the question a person answers.

Use concrete verbs.

Send, update, assign, create, route, or stop.

Define the stop points.

Name the reviewer, threshold, and escalation.

What a useful map includes

  • A precise start signal and a clear finish state.
  • The system of record for every important input.
  • Rules separated from judgment and uncertainty.
  • Human review where empathy, risk, or exceptions matter.