> ## 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.

# Quickstart

> Sign in, create a project, add tests or install a pack, run UAT, log findings, and deliver without a spreadsheet.

You already know how to test. This is the shortest path to do it in SimpleUAT instead of a shared sheet and an email thread.

<Steps>
  <Step title="Create or open a project">
    In **Projects**, use **Create First Project** or **Create Client Project**. A project is the job (for example, Acme checkout on staging). Details: [Create a project](/start-here/first-project).
  </Step>

  <Step title="Give it a place to test">
    On **Environments**, add staging (name and `base_url`). That is the URL you used to paste at the top of the spreadsheet. [Environments](/concepts/environments).
  </Step>

  <Step title="Get tests in">
    Fastest: **Test Suite Packs** to a pack such as [E-commerce Checkout](/packs/which-pack) to **Use This Pack** / **Install into project**. Or import Excel/CSV, or write one suite by hand. [Choose a setup](/start-here/choose-setup).
  </Step>

  <Step title="Make a cycle, start a run">
    **Test Cycles** is the testing round (dates, environment, which cases). **Start a run** is you actually executing. You need an active tester on the project. [Cycles vs runs](/concepts/cycles-vs-runs).
  </Step>

  <Step title="Pass, fail, and file issues">
    Mark steps **Pass**, **Fail**, **Blocked**, or **N/A**. A failed step can prompt you to file an issue. Issues live under **Findings** (`/defects` in the URL). Attach screenshots. [Findings](/findings/overview).
  </Step>

  <Step title="Connect the client and deliver">
    On **Deliver UAT**, connect with their Delivery ID (`SUA-XXXX-XXXX`), a connection code, or **Send invitation**. They must approve. Then **Build delivery snapshot** and **Deliver UAT**. [How delivery works](/delivery/how-it-works).
  </Step>
</Steps>

<Note>
  Exports (PDF, Word, Excel, Jira CSV, and the rest) are generated from the work you already recorded. They are plan-gated. You don't rebuild a status deck by hand. See [exports](/delivery/exports).
</Note>

## If you are mid-job

Open the project, install a pack or import the client's sheet, run, log findings, deliver. The [New testing job](/start-here/testing-gig) page is the 10-step version of that.

<Columns cols={2}>
  <Card title="5-minute tour" icon="timer" href="/start-here/five-minutes">
    One example through project, suite, run, finding, delivery.
  </Card>

  <Card title="Coming from a spreadsheet" icon="table" href="/start-here/spreadsheets">
    What each column becomes.
  </Card>
</Columns>