Trading journal setup tags: build a consistent review system
By intent: trade · Published
Use setup tags to record the reason for a trade, not whether it won. Start with a small dictionary of observable definitions, keep market context and rule adherence in separate fields, and preserve unknown values. Consistent labels make a journal easier to review without rewriting the story after the outcome.
A setup is not a result or a mood
Labels such as “good trade,” “bad trade” and “winner” mix evaluation with outcome. A planned trade can lose and an unplanned trade can win. If you label only after seeing profit, the category may describe hindsight rather than the decision you made.
Separate four questions: What was the planned setup? What was the context? Did the execution follow your written rules? What was the net result? Record emotional observations separately too. The trading psychology guide covers that dimension; this article focuses on designing the labels themselves.
Build a small dictionary before adding more tags
The following is an illustrative recordkeeping schema, not a recommendation to trade these patterns. Replace the names and definitions with the rules you actually use. Start with a few categories that answer a review question; a large tag list is not inherently better.
| Field | Example values | Definition rule |
|---|---|---|
| Primary setup | range-break, pullback, other, unknown | Use your documented pre-entry criteria. Choose one primary setup per completed trade idea. |
| Session | first-hour, later-session, unknown | Define the market, session start and timezone; derive from entry time where possible. |
| Plan adherence | followed, deviated, not-recorded | Compare the execution with the plan written before entry, not the profit. |
| Evidence | note reference, screenshot reference | Keep the observation supporting the classification; avoid private account details in shared screenshots. |
| Dictionary version | v1, v2 | Record which definitions applied so later revisions do not silently rewrite old data. |
For each setup, write an inclusion rule, an exclusion rule and one ambiguous example. “Range-break” might mean your prewritten range-break criteria were recorded before entry, not simply that price later crossed a line. If your original plan is missing, mark the evidence missing rather than inventing it.
Keep one primary label and separate secondary context
A row with five competing setup labels is hard to interpret. Use a primary setup to answer the first review question, then keep secondary context in separate columns or clearly prefixed notes. If one trade genuinely combines two ideas, define a combined category prospectively or record the ambiguity; do not count the same trade twice in an overall total.
A practical note format is: “setup=range-break; session=first-hour; adherence=followed; dictionary=v1; evidence=entry-note-17.” This is a portable convention you can use in a spreadsheet or notes. It is not a claim that intent: trade automatically parses these prefixes or provides a dedicated filter for every field.
Do not turn missing labels into poor performance
Use “unknown” when you cannot reconstruct the setup from contemporaneous records. Use “other” when the setup is known but deliberately outside your current dictionary. These are different situations. Keep both groups in the overall trade count and disclose how many records are excluded from a category comparison.
Before importing an older journal, map synonyms such as “PB,” “pull back” and “pullback” only if they actually meant the same thing. Keep a mapping table and the original label. Do not bulk-rename ambiguous history just to make a cleaner chart.
Worked review: labels show a question, not an answer
Assume a fictional sample of 20 completed trade ideas, all in USD with net results after recorded costs. Ten are labeled range-break, eight pullback and two unknown. No trade appears in two groups.
| Group | Trades | Total net result | Average net result |
|---|---|---|---|
| Range-break | 10 | 120.00 USD | 12.00 USD |
| Pullback | 8 | -40.00 USD | -5.00 USD |
| Unknown | 2 | -30.00 USD | -15.00 USD |
| All trades | 20 | 50.00 USD | 2.50 USD |
Setup-label coverage is 18 / 20 = 90%. Comparing only the named groups shows 80.00 USD across 18 trades, an average of about 4.44 USD. The complete sample is 50.00 USD across 20 trades, averaging 2.50 USD. Leaving out unknowns changes the summary, so disclose the omission.
This does not prove range-break is better or justify increasing size. Position sizes, instruments, market conditions and rule adherence may differ, and the groups are small. Check individual records and cost treatment before drawing conclusions. There is no universal trade count that makes a setup reliable; no sample removes uncertainty about future performance. NIST’s sample-size guidance ties sample planning to the question, variability and desired precision. That general principle is useful here, but its process examples are not a validation rule for trading strategies.
A weekly maintenance routine
- First reconcile the journal with source records. Labels cannot repair missing or duplicated trades.
- Review unknown and other entries without guessing missing intent.
- Read several examples from each group against the written definition. Record inconsistent assignments.
- Choose one useful review question, such as whether deviations from the plan cluster in a particular session. Treat the observation as a hypothesis, not a causal finding.
- Change definitions prospectively and record the version. If you recode historical records, preserve the previous values, reason and date.
Put the system to work without adding complexity
Use the setup and notes columns in the free CSV trading journal template, adding separate context columns in your own spreadsheet when useful. Spreadsheet formulas, grouping and charts remain your responsibility. The definitions can be useful even without automation.
intent: trade lets you add trade context and search history by instrument, setup or note, as described on the features page. This article does not promise a custom tagging database, automated classification, statistical significance testing or grouping for every example field. Creating, editing, importing or restoring trades requires an active Standard or Grand subscription; account creation does not start a free trial.
Open intent: trade to create an account if the published features fit your workflow. Review the subscription requirements above before adding trades.
Once labels are consistent, use the weekly review checklist and metrics guide to describe the recorded sample. The goal is clearer evidence for your own review, not a promise of better returns.
For recordkeeping and review. Not investment, accounting or tax advice.