# Workflow intake sheet

Use this to walk one real analysis from raw data to delivery. Fill in one row per step, ideally with a statistician and someone from QA in the room. The gaps you find are the work to scope. Nothing here is a regulatory requirement; adapt it to your own SOPs.

**Analysis or study (no confidential details needed):**
**Date / people present:**

## 1. The workflow, step by step

| Step | What happens here | What record would a reviewer ask to see? | Does it exist today, and where? | Could it be replayed, or only trusted? | Who is accountable? |
|---|---|---|---|---|---|
| 1. Data in (source, version, who touches it) | | | | | |
| 2. Preparation (derivations, exclusions) | | | | | |
| 3. Analysis (code, environment, packages) | | | | | |
| 4. Review (who checks the output, how) | | | | | |
| 5. Change (plan, data or code changes) | | | | | |
| 6. Delivery (what supports what is delivered) | | | | | |

## 2. Where does AI enter?

| Question | Answer |
|---|---|
| Is an AI assistant used anywhere in this workflow (officially or informally)? | |
| For what: drafting code, summarising output, writing text, other? | |
| Is its use recorded anywhere? | |
| Who reviews what it produces, and is that review recorded? | |
| Is there a written context of use for the tool? | |

## 3. Existing controls

| Question | Answer |
|---|---|
| Which SOPs already cover this work? | |
| Is the R (or SAS, Python) environment qualified or locked? How? | |
| How are changes to code and data controlled? | |
| What did the last audit or inspection ask for? | |

## 4. Gaps and next step

| Gap found | Why it matters | Smallest useful next step | Owner |
|---|---|---|---|
| | | | |

Pick one workflow, one gap and one deliverable for a first piece of work. A short, fixed time box with a clear stopping point is usually better than a programme.