# Workflow QA Checklist

Use this checklist before publishing, selling, or handing off an automation workflow.

## Minimum standard

A workflow is not ready because it runs once on your machine. It is ready when another operator can understand the use case, import the workflow, connect credentials, test sample data, and know what output should look like.

## Checklist

| Check | Pass condition | Score 1-5 | Notes |
| --- | --- | --- | --- |
| Use case | The workflow solves one clear business job with a named buyer and trigger. |  |  |
| Inputs | Required fields, files, credentials, and sample payloads are documented. |  |  |
| Outputs | The user can see exactly what should be created, updated, sent, or logged. |  |  |
| Failure path | The workflow explains what happens when an API fails, data is missing, or a rate limit is hit. |  |  |
| Setup time | A new user can complete setup in under 30 minutes for a simple workflow. |  |  |
| Test data | At least one safe sample input is included so users can test before going live. |  |  |
| Maintenance | Known dependencies, API limits, and credentials are listed. |  |  |
| Commercial claim | The product page states what it helps with without promising impossible outcomes. |  |  |

## Scorecard

Score each workflow from 1 to 5 on clarity, setup speed, output reliability, failure handling, and business value.

Do not publish paid workflows below 20/25 unless the page clearly marks them as experimental.