<!-- Published by AIMasterz at https://aimasterz.com/docs/templates/02-process-card.md . Part of the Company OS Method: https://aimasterz.com/docs/method -->

# Process Card — <process name>

Stage 2 of the [method](https://aimasterz.com/docs/method). One card per process. Start with the value chain, then write a card for each process that is a candidate for a Digital Employee.

## Value chain (once per function)

Level 1 links in order, for example for marketing: Plan → Create → Publish → Engage → Measure → Learn. Under each link, list its level-2 processes. Each listed process gets a card below.

## Card

| Field | Value |
| --- | --- |
| Process ID and name | e.g. `MKT-PLAN-01 Weekly portfolio review` |
| Value-chain link | Plan / Create / Publish / … |
| Purpose | The job it does, in one sentence |
| Metric it moves | The outcome metric and its source |
| Trigger | Schedule, event, or request; who starts it |
| Inputs | Data and documents, with their system of record |
| Outputs | What it produces, and where it is stored |
| Owner | Accountable person |
| Frequency and volume | e.g. weekly, 11 products |
| Time per run today | Measured or estimated (mark which) |
| Current executor | Person, agent, script, or mix |
| Known failure modes | What goes wrong and how often |

## Steps

Number every step. A decision is a step.

| # | Step | Inputs | Output | Decision? (rule or judgment) | Systems touched | Today done by |
| --- | --- | --- | --- | --- | --- | --- |

## Exceptions

| Exception | How it is detected | What happens today | Who decides |
| --- | --- | --- | --- |

## Gate

- [ ] Trigger, inputs, outputs, owner and metric are filled.
- [ ] Frequency and time per run are real numbers or marked unknown.
- [ ] Every decision point is a numbered step.