# Systems & Workflow Map

A department-by-department map of workflows, systems, handoffs and data, showing exactly where work stalls and where Clones can add capacity.

## What this is for

The diagnostic needs a shared picture of how work actually moves: which systems it touches, where people rekey data, where it waits for an approval, and where it breaks. This map is that picture. It turns problem statements into concrete workflows, exposes the systems and data each Clone would need, and gives the scoring rubric the facts it needs for feasibility and data readiness.

## When to use it

During the Weeks 2–3 diagnostic for priority departments, and again in the Discover week of each department rollout. Refresh it when a major system changes.

## Who's involved

- **Business owner:** confirms the map is accurate.
- **Two or three people who do the work:** walk through the real steps.
- **IT lead or system admins:** confirm systems, integrations and data locations.
- **Implementation Engineer and Solutions Architect Clone:** interview, map and draft.

## How to fill it in

1. Start from the department's confirmed problem statements. Map those workflows first.
2. Interview the people who do the work, not just their manager. Ask them to share their screen and walk through one real item.
3. Record each step: who does it, in which system, how long it takes, and what can go wrong.
4. Mark every handoff (person to person, system to system) and every wait.
5. List the data each step needs and where it lives.
6. Tag each step with a Clone fit signal (below). Do not design the solution yet.
7. Review the map with the business owner and IT lead. Fix errors, then confirm.

## The template

### Department summary

| Field | Answer |
|---|---|
| Department | |
| Business owner | |
| Team size and roles | |
| Interviewees | |
| Problem statements covered | PS-___ |
| Date mapped | |

### System inventory (department view)

| System | Used for | Users | Integrations today | API / connector available | Data classification | Admin owner |
|---|---|---|---|---|---|---|
| | | | | | | |
| _ERP_ | _POs, receipts, invoice posting_ | _AP team, buyers_ | _Nightly sync to data warehouse_ | _Yes_ | _Confidential_ | _IT applications_ |

### Workflow map

One table per workflow. Clone fit signals: **R** = repetitive, **K** = knowledge lookup, **X** = cross-system rekeying, **J** = judgment needed, **A** = approval gate, **H** = must stay human.

| Step | Actor | System | Action | Input | Output | Time per item | Wait before next step | Failure modes | Fit signals |
|---|---|---|---|---|---|---|---|---|---|
| 1 | | | | | | | | | |
| _1_ | _AP specialist_ | _Shared inbox_ | _Open supplier invoice email, download PDF_ | _Email_ | _PDF_ | _2 min_ | _0–2 days in inbox_ | _Missed emails, duplicates_ | _R_ |
| _2_ | _AP specialist_ | _ERP_ | _Find PO and goods receipt_ | _PO number on invoice_ | _Matched PO_ | _6 min_ | _None_ | _PO missing or wrong on invoice_ | _K, X_ |
| _3_ | _AP specialist_ | _ERP_ | _Three-way match, key invoice_ | _PDF, PO, receipt_ | _Invoice record_ | _8 min_ | _None_ | _Price or quantity variance_ | _X, J_ |
| _4_ | _AP supervisor_ | _ERP_ | _Approve variances over tolerance_ | _Variance flag_ | _Approval_ | _2 min_ | _1–3 days_ | _Supervisor backlog_ | _A, H_ |

### Handoffs and waits

| From | To | Mechanism (email, ticket, chat, system queue) | Average wait | What gets lost |
|---|---|---|---|---|
| | | | | |
| _AP specialist_ | _Buyer_ | _Email asking for missing PO_ | _2.5 days_ | _Context; follow-ups_ |

### Data and knowledge sources

| Knowledge or data needed | Where it lives | Owner | Quality (Good / Patchy / Poor) | Sensitive? | Notes |
|---|---|---|---|---|---|
| | | | | | |
| _Vendor tolerance rules_ | _Policy PDF in file share_ | _Controller_ | _Patchy: two versions_ | _Internal_ | _Needs one approved version before loading_ |

### Observations

- **Biggest time sink:** _step and minutes_
- **Biggest wait:** _handoff and days_
- **Biggest risk point:** _step and why_
- **Quick fixes that don't need AI:** _e.g. a required PO field on the supplier portal_
- **Candidate Clone opportunities:** _list, each linked to a problem statement_

## Good looks like

- **Mapped from a real item,** watched on screen, not from the process document.
- **Waits are measured.** Most cycle time hides in handoffs, not in the work itself.
- **Data quality is honest.** "Patchy" now saves a failed pilot later.
- **Human steps are named,** with the reason they stay human.
- **Non-AI fixes are captured.** Clone-first, not Clone-only: some answers are a form field or an n8n flow.
- **Common mistake:** mapping the whole department at once. Map the workflows behind the top problem statements first.

## How Clone helps

The **Solutions Architect Clone** joins or reviews the interviews, drafts the workflow tables, flags missing timings and builds the system inventory from the pre-read. The **Implementation Engineer** validates feasibility and connector availability. In the portal, the map is the Systems & Workflow Map deliverable under Opportunity & Roadmap; each candidate opportunity is pushed to the Opportunity Inventory for scoring.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Business owner | | | Accurate / Needs changes |
| IT lead | | | Systems confirmed |

## Related

- [Problem Statement Worksheet](/playbook/templates/problem-statement-worksheet)
- [Opportunity Scoring Rubric](/playbook/templates/opportunity-scoring-rubric)
- [Connections & Permissions Plan](/playbook/templates/connections-permissions-plan)
- [Integration Architecture](/playbook/templates/integration-architecture)
- [Knowledge templates library](https://support.clone.org/libraries/knowledge-templates)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/systems-workflow-map
