# Proof-of-Concept Scope Outline Template

> **Use this after the workflow map and gap scorecard.** Turn the diagnostic into a narrow, testable proof scope.

---

## 1. Target workflow

```
Workflow: [same as workflow map]

Stand: [which stand / environment]

One success metric: [what must be true for the PoC to be worth it?]
```

## 2. Current state (from gap scorecard)

```
Weakest category: [from evidence gap scorecard]

Biggest handoff gap: [from toolchain handoff map]

Estimated rework per release: [hours / days lost]
```

## 3. Proposed scope

```
What we would change: [one concrete intervention — not a platform migration]

What stays the same: [existing tools continue to work]

Duration: [weeks, typically 1-2]

People involved: [minimum — workflow owner + one engineer]
```

## 4. Success criteria

- [ ] Evidence chain visible: setup context → run data → review decision
- [ ] One handoff gap closed or measurably reduced
- [ ] Before/after metric captured (time, rework instances, reviewer questions)
- [ ] Recommendation: go / no-go for production pilot

## 5. Known risks & assumptions

```
Risk 1: 
Risk 2: 

Assumption 1: 
Assumption 2: 
```

## 6. Deliverables

- [ ] Annotated workflow map (before/after)
- [ ] Updated gap scorecard
- [ ] Evidence pack sample (one run, fully traced)
- [ ] Written recommendation (go/no-go + rationale)

---

*This template is part of the Finnegans diagnostic kit. It does not require confidential data and does not commit to any implementation.*