# AI Workflow Report Template

## Recommended stack

Summarize the smallest recommended set of tools, the role of each, why the combination wins, review date, and important assumptions.

## Project frame

| Item | Status | Detail |
|---|---|---|
| Outcome | Confirmed/assumed/unknown | |
| Acceptance criteria | | |
| Volume and frequency | | |
| Budget | | |
| Privacy/rights constraints | | |
| Existing tools and skills | | |

## End-to-end workflow

| Step | Owner/tool | Input | Action | Output/format | Acceptance gate | Next handoff |
|---:|---|---|---|---|---|---|

## Tool decisions

| Stage | Primary | Why | Fallback | Rejected/not needed | Evidence/confidence |
|---|---|---|---|---|---|

Include the weighted comparison only where multiple candidates are genuinely viable.

## Handoff contracts

Define the material transitions using the structure in `handoff-contracts.md`.

## Human control and safety

| Checkpoint | Reviewer | Trigger | Evidence required | Failure action |
|---|---|---|---|---|

## Cost, speed, and capacity

State assumptions, ranges, subscription versus usage cost, human review time, bottlenecks, and what was not verified.

## Implementation plan

1. Minimum pilot
2. Measurement and acceptance criteria
3. Tool/account configuration
4. Prompt, schema, and folder setup
5. Integration and error handling
6. Review and approval setup
7. Controlled rollout
8. Monitoring and improvement

## Ready-to-use assets

Provide only those needed now: canonical brief, prompts, schemas, naming conventions, checklists, or test cases.

## Risks and fallbacks

| Risk | Likelihood | Impact | Prevention | Fallback/owner |
|---|---|---|---|---|

## Open decisions

List only decisions that materially change the workflow, with a recommended default.

## Final recommendation

State what to implement now, what to test first, what to defer, and what should deliberately remain manual.