What a screenshot contributes
A screenshot can show a zone, entry example, exit or interface issue that is difficult to describe. It supplies the visual context that is visible in that image. It does not include full history, hidden settings or trading costs.
Use it to start a description, compare your intention with a rule or explain a problem. Testing still requires precise conditions and suitable market data.
Prepare a useful image
- Choose a clear view with readable candles and levels.
- Keep the symbol, timeframe and relevant dates in the frame.
- Include indicator labels when needed for the question.
- Hide personal details, balances, identifiers and unnecessary keys.
- Add a sentence identifying exactly what to inspect.
A very tight crop can remove the context of a move. A full desktop screenshot may make the signal too small to read. Prefer a relevant chart area with some candles before and after the event.
Explain what you want to observe
Inspect the marked area in this EURUSD M15 screenshot.
First describe only what is visible.
I want to formalise a return inside the zone, rather than a breakout.
Suggest a measurable signal and invalidation condition.
List information missing from the image. Do not infer performance.Explain whether the lines are manual annotations, indicator output or a proposal to discuss. If you selected a level manually, say so: an automated rule needs a repeatable way to select that level.
Resolve ambiguous descriptions
| Visual description | Question before testing |
|---|---|
| Price touches the zone | Wick, body or close? Which boundary? |
| The trend is strong | Which measure, horizon and threshold? |
| The level is rejected | Which close or move confirms rejection? |
| The signal is too late | What time or candle limit applies? |
| The stop is behind the level | What distance and unit? |
These questions help two readers interpret the same example consistently. They do not require adding unnecessary complexity.
Review the rule in the product
Inspect conditions and parameters in Flow. Compare chart marks with the event you intended to describe. If the symbol or period differs from the screenshot, correct that context before concluding that the signal is wrong.
Use screenshots for support
For an interface issue, show the control and its immediate surroundings. Describe the preceding action, expected result and actual behaviour. For a report issue, include its title, period and relevant metric while excluding unrelated account details.
Continue with Choose conditions to build the rule, or Read a backtest to inspect an historical signal.