# System inventory

Use this to list the systems, spreadsheets, and inboxes behind one workflow. Start with one workflow, not the whole company.

Workflow: ______________________

## Where to look

- [ ] Software license and finance spend list
- [ ] Single sign-on app list
- [ ] Each team: what do you open every day?
- [ ] Each team: which spreadsheet actually runs your work?
- [ ] One piece of work followed end to end, listing every system it touches
- [ ] Exports, shadow spreadsheets, and inbox attachments acting as databases

## Inventory

| System or source | What information it holds | Owner | Has API or export? | Decisions that depend on it | Re-keyed by hand? | Connected? |
|---|---|---|---|---|---|---|
| Example only: Project cost spreadsheet | Example: cost forecasts | Example owner | No | Example: budget approvals | Yes | No |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |

## Rank

For each source, note the following. Start with the top few.

- How many decisions depend on it
- How often people re-key it
- Whether it has an API or export
- Whether anyone owns it

## Next steps

- [ ] Name an owner for each top source
- [ ] Write down what its fields mean and how fresh it should be
- [ ] Decide who and what may read it, with permissions

From tommymagee.com/resources/centralize-data-first
