> For the complete documentation index, see [llms.txt](https://size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://size.club/docs/playing-a-trial/how-to-win.md).

# How to win

Winning a Trial that used a Key means finishing #1: the highest score left standing when the fifteen minutes end.

## Win condition

Highest score when the Trial ends. The final elimination lands at 15:00, five survivors place #1 to #5, and the top score takes the Life.

```mermaid
flowchart LR
 Start[10 enter] --> Elims[Eliminations each stage]
 Elims --> Final[5 finish]
 Final --> Win["#1 wins a Life"]
```

## What you get

| Result    | What you get |
| --------- | ------------ |
| #1        | Alpha Life   |
| #2 to #5  | Finalist     |
| #6 to #10 | Eliminated   |

![Finishing #1: the Life award](https://cdn.jsdelivr.net/gh/dropbear-hl/size-docs-assets@master/life-award-ceremony.png)

Life sizes and rules: [Product tiers](/docs/how-size-works/product-tiers-keys-and-lives.md). Feedback after every run: [Your Grading](/docs/playing-a-trial/your-grading.md). Wins also earn [XP](/docs/progress-and-preseason/xp-leveling-and-achievements.md) and [achievements](/docs/progress-and-preseason/achievements.md).

## What scores points

The briefing says it, and it is worth knowing cold. Six habits build your score:

1. **Make money.** Beat what a rated bot would have made in the markets you traded.
2. **Feel the trend.** Be on the right side of the move.
3. **Be selective.** Only take trades you have a reason for.
4. **Keep losses small.** Cut what is failing early.
5. **Do not get greedy.** Size sensibly. Reckless size reads as poor trading even when it works once.
6. **Take profits.** Close winners instead of watching them turn red.

Two examples of what that means in practice:

* Two players finish the same run at the same profit. One took three planned trades, sized them sensibly, and banked the winners. The other clicked twenty times and got bailed out by one lucky hold. Same PnL, very different scores.
* A trade goes against you. Closing it for a small loss scores better than doubling down and clawing back to breakeven, even though the second run "lost nothing."

Full mechanics, including what drags your score down: [How scoring works](/docs/playing-a-trial/how-scoring-works.md).

## Three things that win Trials

1. Stay off the bottom at every elimination. Lowest score is out every three minutes. Timeline: [Minute by minute](/docs/playing-a-trial/a-trial-minute-by-minute.md).
2. Trade better than the bots. [How scoring works](/docs/playing-a-trial/how-scoring-works.md).
3. Read the Stage Boost. [Stage Boosts](/docs/playing-a-trial/stage-boosts-and-missions.md).

## In-run priorities

1. Check your place in the field.
2. Read the active Stage Boost.
3. Cut losers early.
4. Take profits when the boost rewards it.
5. Stay off tilt.

## After you win

Life [auto-equips](/docs/after-you-win/earn-a-life.md) if a slot is free. Then [Trade](/docs/after-you-win/trade-on-your-life.md).

## After you place below #1

1. [Your Grading](/docs/playing-a-trial/your-grading.md)
2. [Practice](/docs/playing-a-trial/practice-trials.md) one fix
3. Another Key from the [Store](/docs/wallet-and-store/the-store.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://size.club/docs/playing-a-trial/how-to-win.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.