# Workflow design worksheet

Fictional examples only. Keep credentials and sensitive records out of shared copies.
This is a planning document, not an IFS import file.

## Requirement
- Business outcome:
- Why workflow is suitable:
- Owner and reviewer:
- Target release / installed components:
- Expected volume per run / simultaneous triggers:
- Maximum acceptable duration:

## Entry point
- Process key and proposed version:
- Trigger: projection / event / command
- Exact API, entity set, operation or call signature:
- Logical unit / event and explicit attributes, if applicable:
- Workflow type:
- Timing:
- Input identity and data types:
- How the real payload was observed:

## Tasks and dependencies
| Step | Task type | Input | Output | API/configuration | Grant |
| --- | --- | --- | --- | --- | --- |
| 1 | | | | | |

## Transaction and repeat behavior
- Commits before/after user forms:
- REST or autonomous side effects:
- Possible cascading triggers:
- Expected outcome on failure:
- Retry/idempotency/reconciliation approach:
- Timestamp meanings and server/site context:

## Delivery
- BPMN version:
- ACP and included triggers:
- Page command/context:
- Target REST configuration completion:
- Grant review:
- Queued async version compatibility:
- Deployment checks:
- Rollback and business-data repair plan:

## Verification
- Test matrix and actual evidence:
- Real trigger tested under intended role:
- Denied role checked:
- Target-environment import checked:
- Performance evidence:
- Remaining limitations:
- Reviewer / date / verified release: