# Workflow Map Template

> **Time:** 20–30 minutes | **Who:** 1 workflow owner + 1 engineer who knows the stand setup
> **Output:** One page showing where a single embedded test workflow flows between tools and people.

---

## Step 1 — Name the workflow

```
Workflow name: [e.g. "ECU variant regression on stand 3"]

Trigger (what starts it): 

Owner (who is accountable):

Reviewer (who signs off):
```

## Step 2 — List the steps

Start from the trigger and walk forward. Include manual steps, tool steps, and evidence steps.

| # | Step | Tool / person | Context passed to next step? |
|---|------|--------------|------------------------------|
| 1 | | | |
| 2 | | | |
| 3 | | | |
| 4 | | | |
| 5 | | | |

*(Add more rows as needed.)*

## Step 3 — Mark the handoff points

Where does context cross between tools or people? At each boundary, note what is passed and how.

```
Handoff 1: [tool/person A] → [tool/person B]
  What is passed: 
  How it is passed: [automatic / manual / not passed]

Handoff 2: … → …
  What is passed: 
  How it is passed: 

Handoff 3: … → …
  What is passed: 
  How it is passed: 
```

## Step 4 — Circle the gaps

Which handoffs create the most rework, ambiguity, or delay? Where does context disappear?

```
Biggest gap: 
  Impact: [rework / re-runs / audit risk / reviewer questions]

Second gap: 
  Impact: 

Third gap: 
  Impact: 
```

## Step 5 — Next step

- [ ] Use the kit and stop — the workflow is clear enough.
- [ ] Share this map in a [workflow review](https://finnegans.tech/workflow-review/).
- [ ] The gaps look worth a diagnostic — [request scope](mailto:hello@finnegans.tech?subject=Diagnostic%20workshop%20scope).

---

*This template is part of the Finnegans diagnostic kit. No confidential test data is required. The output is yours.*