Give your setups a shared language

A tag is a small agreement with your future self. When you label a trade today, you are promising that the label will mean the same thing when you review it later.

That agreement breaks down when a setup name becomes a catch-all, when similar trades receive different names, or when an outcome changes the label after the fact. A simple vocabulary makes your journal easier to read and your comparisons easier to question.

Define the label before using it

Give each setup a short description that states what belongs in the group. Include the conditions you use to identify it and a note about what does not belong.

This is documentation of your own trading plan, not a recommendation to use a particular strategy. The purpose is to remove ambiguity from the record.

For each label, write:

• Name: a short, recognizable term.
• Definition: the conditions that distinguish it from your other labels.
• Boundary: a nearby example that should receive a different label.
• Version date: when this definition began to apply.

If two labels are difficult to tell apart, you may need a clearer boundary or a single shared name. More labels do not automatically produce more useful information.

Separate setup, execution, and context

Avoid asking one tag to describe everything. A setup describes what you intended to trade. An execution note describes how your action related to that plan. Context records something about the situation.

For example, a setup name and a note that you entered before your planned condition was complete answer different questions. Keep both rather than renaming the setup to “bad trade.”

Likewise, do not use profit or loss as a substitute for a setup definition. If the outcome determines the category, a later comparison will partly reflect the way you sorted the trades rather than a distinction that existed before the result.

Give uncertainty a place

Some trades will not fit neatly. Use an explicit unclassified category or leave a note that explains the ambiguity. Forcing an uncertain entry into a familiar bucket makes the record look cleaner while making its meaning less reliable.

Review those entries together. Are they genuinely different, or is a definition missing one useful boundary? Change the vocabulary only when you can explain the change in a sentence.

A useful tag is one you can apply consistently, including when the trade did not go the way you expected.

Change definitions without losing history

When you revise a setup, preserve the old definition and record when the new one takes effect. You can relabel historical entries if you have enough information, but do it consistently and keep a note of the revision.

Do not compare two periods as though nothing changed if their labels now mean different things. A visible break in the record is more honest than a seamless chart built from incompatible categories.

Start with a small vocabulary, then let real review questions justify new detail. Your weekly review is a good place to ask whether a tag helped you understand something or simply added another field to complete.