# Workflow Acceptance Worksheet

Version 1.0 | 13 November 2026 | Toronto, Ontario, Canada

This is an evaluation aid, not a certification or a statement of deployment readiness.

## 1. Task and ownership
- Business task, intended user, workflow owner and decision owner.
- Normal completion, per-item results, partial completion and unknown outcomes.
- Software versions, actual tool APIs, environments and reversible scope.

## 2. Boundaries
- Requesting subject, service identity, recipient, content/version and purpose.
- Authority source, expiry, revocation and who may stop new work.
- Final resource enforcement, credentials and any path around the adapter.
- Resource idempotency, business uniqueness, condition/version checks and lookup.
- Distinguish same-transaction protection from independent SaaS calls.

## 3. Fixed cases
- Normal multi-step completion and permitted variations.
- Content, destination, plan or tool-version change after approval.
- Authority withdrawn before dispatch, between check and commit, and after commit.
- Intermediate exposure followed by a private final state.
- Lost acknowledgement, caller restart, same-ID and new-ID duplicate attempts.
- Shared-budget competition, partial completion and unavailable result lookup.

## 4. Evidence and comparison
- Freeze versions, source/input hashes, baseline configurations and expected results before the confirmatory run.
- Retain actual resource events independently of model statements and callback status.
- Compare existing native capabilities, complete conventional controls and the proposed integration under equivalent obligations.
- Record all failures, unattempted cases, exclusions, fixes and fresh-run identifiers.

## 5. Customer value
- Normal tasks completed; prohibited effects; manual interruptions per agreed task count.
- Cold installation, online checks, approval waiting, storage and readback costs.
- Operator recovery steps and time; new tool/version and second-consumer maintenance.
- Report observed human effort separately from author or agent-assisted work.
- Include software, infrastructure, support, migration and exit costs; do not assume savings.

## 6. Deployment and exit
- Data flows, retention, deletion, access, key ownership and incident responsibilities.
- Qualify provider ACLs, backups, restore and failure behavior for the actual environment.
- Define acceptance thresholds, unresolved limitations, rollback and manual handoff.
- Start observation-first where supported, then explicitly authorize a limited write scope.
- Record participant consent and separately agree whether any results can be published.