# Risk Management for UpScalp Signals

**Last reviewed:** 2026-05-22.

Decide how much you can lose before the signal arrives. If the signal does not fit that number, skip it.

UpScalp can help you find setups. It cannot remove volatility, leverage, execution risk, or emotional decision-making.

## Before opening the exchange

Write the answer to each question before placing a trade:

| Question                                                                | If the answer is unclear        |
| ----------------------------------------------------------------------- | ------------------------------- |
| What is the exact invalidation price?                                   | Do not enter.                   |
| How much can this trade lose in account terms?                          | Size is not ready.              |
| Where is the first realistic take-profit level after fees and slippage? | Reward is not clear enough.     |
| What market condition would make the setup stale?                       | Context has not been checked.   |
| What rule stops trading for the day?                                    | Session risk is not controlled. |

## Set the loss first

Before using any signal, write down:

1. Maximum loss for one trade.
2. Maximum loss for one day.
3. Maximum number of trades for one session.
4. What makes you stop trading for the day.

Do this before a Telegram alert appears. Rules written during a fast move are usually too generous.

## Measure entry to stop loss before size

The stop-loss distance decides whether the trade fits your account.

1. Start with the signal entry zone.
2. Measure from planned entry to stop loss.
3. Calculate position size from that distance and your max-loss rule.
4. Reduce size or skip if the trade is too large.

Never choose size first and then move the stop loss to make it fit.

## Use leverage only after the risk is already acceptable

Leverage changes how fast your account moves. It does not improve the signal.

Stand down when:

1. A normal move toward the stop would feel unacceptable.
2. You need high leverage to make the trade feel worth taking.
3. Fees and slippage make the first target too small.
4. You would be tempted to remove the stop if price moves against you.

## Rules that do not move

These rules apply to Lite, Premium, and approved beta workflows:

1. Stop loss is defined before entry.
2. Position size is based on the stop loss.
3. Losing trades are not repaired by adding size.
4. Premium context does not cancel a stop.
5. A skipped setup is better than an oversized trade.

## When to stop for the day

Stop trading and review later when:

1. Daily max loss is hit.
2. You break your entry or stop-loss rule.
3. You take a trade mainly to recover a loss.
4. You feel rushed because several signals appeared close together.
5. You cannot clearly explain why the next setup is different from the last failed one.

The safest next action after broken rules is usually no action.

## If the calculation fails

Do not repair a bad calculation by widening the stop, increasing leverage, or removing take-profit discipline. Use one of these actions instead:

| Problem                                            | Safer action                                    |
| -------------------------------------------------- | ----------------------------------------------- |
| Stop-loss distance is too large.                   | Skip or wait for a better entry.                |
| Position size is too small to feel worth it.       | Skip; the trade does not fit the account today. |
| First target is too close after fees and slippage. | Wait for a cleaner setup.                       |
| You need to move the stop to make the idea work.   | Treat the setup as invalid.                     |

## Lite and Premium risk difference

| Path             | Risk focus                                                                                                                        |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Lite             | Keep the workflow simple and prove you can skip unclear setups.                                                                   |
| Premium          | Use extra context to filter harder, not to increase size.                                                                         |
| Private Beta API | Treat beta access as a controlled validation path; keep manual risk rules unless an approved beta flow explicitly says otherwise. |

## Related

1. [How to Read an UpScalp Signal Before You Trade](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals)
2. [When to Skip an UpScalp Signal](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-when-to-skip-a-signal)
3. [UpScalp Legal Notice and Trading Risk Disclosure](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-legal-and-risk-notice)
4. [How to Protect Your UpScalp and Exchange Accounts](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-security-and-account-protection)


---

# Agent Instructions: 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:

```
GET https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.