Quick definition — A trade screenshot is a dated visual record, linked to the journal, of what a chart or interface displayed at a declared stage of the decision.
A screenshot supplements the trading journal: it preserves the visible context before an order, after execution, or at closing. It does not replace order history, fills, the entry reason, or the plan. An image shows only the selected window, with a specific data feed, time zone, zoom level, and set of indicators.
Knowledge of an outcome can alter how a past decision is reconstructed. A pre-trade capture should therefore be preserved separately from annotations added during review. A screenshot does not eliminate hindsight bias, but it makes at least part of the information available at that time verifiable.
From context to review
When to capture
The stages are not interchangeable:
| Stage | What it documents | Limitation |
|---|---|---|
| Pre-entry | Visible information and levels already planned before the order | Does not contain the actual fill |
| Post-fill | The newly executed position and any difference between plan and execution | The first price movement may already influence it |
| Management | Changes, partial exits, or new information during the trade | Must remain separate from the initial thesis |
| Closing | Exit context and the final situation | Cannot reconstruct by itself what was known at entry |
If only one image is available, the journal should at least identify its stage and time. A chart recreated after closing should be labeled reconstruction, not presented as a capture contemporaneous with the decision.
Minimum contents
The capture should allow a reviewer to identify:
- instrument, venue or contract and, when relevant, expiry;
- date, market time, and time zone;
- timeframe, chart type, scale, and displayed window;
- feed or session when differences in data and hours can change interpretation;
- levels and indicators actually used in the decision, with readable labels;
- position stage and an identifier linking the image, note, and execution record.
Drawn entry, stop, or target levels are elements of the plan, not evidence that an order was submitted or filled at those prices. Quantities, average prices, commissions, and fills must come from intermediary or platform records, not from pixels.
Integrity and annotations
Preserve the original capture without arrows or comments added later. If review requires highlighting, create a distinctly named copy, for example:
2026-08-11T13-28Z_ID123_pre_original.png
2026-08-11T13-28Z_ID123_review_v1.png
The name is only an organizational example. A date in the filename or a checksum may help detect changes, but neither proves by itself when or why an image was acquired. If software generates the chart automatically, still record the data origin, displayed interval, and generation time.
How to use it in review
Compare separately:
- what the trading plan stated;
- the reason recorded before the order;
- what the image made visible;
- the actual orders and fills;
- annotations written after the outcome.
A winning trade may come from a decision that breached the plan, while a losing trade may come from one that followed it. The screenshot helps verify documentary consistency; it does not justify inferring process quality from P&L alone.
Illustrative example — A pre-entry note cites a level and timeframe; the original capture shows both, while the order record reveals a fill different from the intended price. The review can separate documentation quality, decision, and execution without redrawing the chart after the outcome.
Privacy and sharing
A screenshot may contain a name, account number, balance, order ID, notification, or third-party information. Before sharing it, create a publication copy, remove unnecessary data, and verify that redaction is not reversible or hidden in editable layers. Keep the original in access-controlled storage.
Limitations
- cropping can omit information that contradicts the thesis;
- different feeds, sessions, scales, and time zones can produce different images;
- a static image does not show latency, order queue, or the full event sequence;
- later annotations can be mistaken for elements present originally;
- a selected collection of only winners or only losers is not a representative sample;
- no screenshot proves causality, edge, or future profitability by itself.
Essential procedure
- Capture the pre-entry stage before order submission when the workflow permits.
- Record stage, timestamp, time zone, instrument, and timeframe.
- Link the image to the same ID used by the journal and execution records.
- Preserve the original; annotate a separate copy.
- During review, compare plan, reason, image, and fills without changing ex-ante data.
- Before sharing, redact a copy and recheck visible and hidden information.
Sources
- CME Group — Keep a Trade Log — advises recording why a trade was made alongside targets, entries and exits, times, levels, and indicators.
- Fischhoff (1975) — Hindsight is not equal to foresight — peer-reviewed study of how outcome knowledge affects retrospective judgments; it does not specifically study trading.
- Information Commissioner's Office — Disclosing documents to the public securely — official guidance on checking hidden information and redacting material before disclosure.