> 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/stage-boosts-and-missions.md).

# Stage Boosts

Every Trial has five stages of three minutes, and every stage has a Stage Boost: the habit your score rewards most for those three minutes.

All five boosts appear once in every Trial. The order is random. You always see the active boost on screen before the stage starts, so nothing here is a surprise, only the order is.

Not to be confused with [Daily missions](/docs/compete-and-connect/daily-missions.md), the small everyday tasks in HQ. Boosts live inside Trials.

![The five Stage Boosts](https://cdn.jsdelivr.net/gh/dropbear-hl/size-docs-assets@master/stage-boosts.png)

## The five boosts

| Boost             | On the card                          | What to do                                                                        |
| ----------------- | ------------------------------------ | --------------------------------------------------------------------------------- |
| NAIL YOUR ENTRY   | Get in at a good price. Don't chase. | Wait for your level. Entries at a good price earn extra this stage.               |
| RIDE THE TREND    | Stay on the right side of the move.  | Trade the direction the market is actually going. Skip fighting the tape.         |
| CUT LOSSES FAST   | Close losing trades early.           | Exit what is not working. A small controlled loss earns more than a big recovery. |
| DON'T BET TOO BIG | Keep every trade a sensible size.    | Size down. Sensible position sizing earns extra this stage.                       |
| CATCH THE TURN    | Spot when a move ends and reverses.  | Watch for exhaustion. Being early to the reversal earns extra this stage.         |

## How to use boosts in the moment

Before each stage:

1. Read the boost card on screen.
2. Ask what a good trader would do for three minutes if this were the only thing being graded.
3. Adjust size, frequency, and hold time to match.

During the stage, nudge toward the boost. Skip rebuilding your whole strategy mid-stage.

## Example flow

Stage 1 boost: DON'T BET TOO BIG. You might normally open full size on the first signal. This stage, halve your usual size and take fewer concurrent positions.

Stage 3 boost: RIDE THE TREND. Let winners in the direction of the move run slightly longer and skip counter-trend scalps.

Stage 5 boost: CATCH THE TURN. Watch your losers closely and be quicker to flip when the move exhausts.

## Boosts and eliminations

Boosts do not protect you from eliminations. If you are last on the board at 3:00, 6:00, 9:00, 12:00, or 15:00, you are out whether you matched the boost or not.

Best boost strategy: stay off the bottom.

## Practice boosts for free

Practice Trials use the same boost system. Run Practice to learn how each boost feels before you spend a Key.

## Related

* [How scoring works](/docs/playing-a-trial/how-scoring-works.md)
* [A Trial, minute by minute](/docs/playing-a-trial/a-trial-minute-by-minute.md)
* [How to win](/docs/playing-a-trial/how-to-win.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/stage-boosts-and-missions.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.