> ## Documentation Index
> Fetch the complete documentation index at: https://docs.simpleuat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cycles vs runs

> A cycle is the testing round (scope, dates, environment). A run is one execution of those cases.

Spreadsheet people used one tab named "UAT round 2" and colored the result column. SimpleUAT splits that:

## Cycle (the round)

Status: `draft` | `active` | `in_progress` | `completed` | `archived`.

Also: title, description, environment, dates, `case_ids`.

**Create First Cycle** when you know the scope. Draft = planning. Active = we're supposed to be testing. Completed/archived = don't keep adding results to it.

## Run (the execution)

Status: `in_progress` | `completed` | `aborted`.

**Start a run** from a cycle (you need an active tester). Each case gets `passed` | `failed` | `blocked` | `skipped` | `in_progress`. You can have more than one run in a cycle (retest after they deploy).

Old run results stay. That's why this beats overwriting cells.

[How to run](/running/runs), [Statuses](/concepts/statuses)

<Columns cols={2}>
  <Card title="Start a run" icon="play" href="/running/runs">
    Prerequisites and buttons.
  </Card>

  <Card title="Can't start?" icon="circle-alert" href="/troubleshooting/cant-start">
    Tester, environment, cases, cycle.
  </Card>
</Columns>