# Automation Discovery Worksheet

Before the first conversation, document one workflow that consumes the most attention. You do not need a technical solution—just describe the real work clearly.

## 1. Current workflow

- Workflow name:
- Business outcome:
- Who performs it:
- Runs per day/week:
- Average time per run:
- Dashboards, spreadsheets, or messaging tools involved:

## 2. Operating steps

List each step in the order it happens:

1.
2.
3.
4.
5.

## 3. Decision rules

- Which conditions allow the process to continue?
- Which cases should be skipped?
- Which decisions must stay with a person?
- Do rules differ by store, product, or operator?

## 4. Common failures

- Step most likely to fail:
- Status most likely to be missed:
- Current response to page, data, or network errors:
- How failures are detected and recovered:

## 5. Desired outcome

- Actions the system should handle:
- Judgments that should remain human:
- Time you expect to save:
- Errors you expect to reduce:

## 6. Acceptance criteria

- Normal path must complete:
- Failure path must report:
- Pause/resume required:
- Diagnostic log required:
- Export or synchronization required:

## 7. Materials to prepare

- A screen recording of the current operation
- Screenshots of pages or spreadsheets
- Sample data with sensitive information removed
- Existing SOPs or message templates
- One actual operator who knows the workflow

---

LongpinCubic - Turn repetitive work into a reliable execution system.