# UpScalp Trading Principles

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

Use these principles before acting on any UpScalp signal. They are designed to keep the decision anchored to structure, risk, and timing instead of urgency.

## A signal is not the trade

An UpScalp signal gives you a structured setup to evaluate.

Before entry, the setup still needs to pass:

1. Correct symbol and direction.
2. Current price still near the entry zone.
3. Stop loss defined before order entry.
4. Position size that fits your max-loss rule.
5. Take-profit levels that still justify the downside.
6. Market context that has not invalidated the idea.

If those checks fail, the signal has not become a trade.

## Structure before prediction

Do not start with "will this pump?" or "will this dump?"

Start with:

1. Where is entry valid?
2. Where is the trade wrong?
3. What is the planned first exit?
4. What market condition would make the setup worse?

Prediction without structure usually turns into chasing.

## Context can cancel a clean-looking chart

A chart can look clean while the trade is still poor.

Context can veto the setup when:

1. The move already happened.
2. The market is moving too fast for clean execution.
3. Confirmation is weaker than the chart shape suggests.
4. The trade requires a stop loss wider than your risk plan.
5. News, volatility, or liquidity makes the setup harder to manage.

When context is unclear, waiting is a valid action.

## Skipping is part of the process

UpScalp users should expect to skip signals.

Skip when:

1. Entry is late.
2. Stop-loss distance is too wide.
3. You are sizing up to recover a loss.
4. You cannot explain the setup in one sentence.
5. You need to change your rules to make the trade acceptable.

The next clean setup is more useful than forcing the current one.

## Risk comes before confidence

A strong-looking signal does not justify unlimited size.

Before any order:

1. Decide the amount you can lose.
2. Calculate size from entry to stop loss.
3. Confirm leverage is within your written rules.
4. Decide where partial exits or review points belong.
5. Accept that the trade may still lose.

Confidence is not a replacement for position sizing.

## Apply the rule after entry

The same discipline applies after the order is open.

| If this happens                     | Do this instead of improvising                                                            |
| ----------------------------------- | ----------------------------------------------------------------------------------------- |
| Price moves toward the stop loss    | Accept the planned invalidation instead of widening the stop.                             |
| Price moves quickly toward TP1      | Follow the planned exit or review rule instead of adding size late.                       |
| The market changes after entry      | Reduce exposure or exit according to the plan. Do not wait for hope to become a strategy. |
| You missed the entry                | Wait for another setup. A missed trade is not a reason to chase.                          |
| You feel pressure to recover a loss | Stop trading until the next calm, planned decision.                                       |

## Related

1. [How to Read UpScalp Signals Correctly](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-how-to-read-signals)
2. [UpScalp Risk Management Guide](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-risk-and-safety)
3. [When to Skip an UpScalp Signal](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-when-to-skip-a-signal)
4. [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate)


---

# 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/trading-principles/upscalp-trading-principles.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.