Every IDX trader eventually discovers that the most expensive thing in their portfolio is not a bad stock — it is a good trade executed without a plan attached to it.

The Wreckage of Unlogged Trades

The typical retail trader on IDX runs their positions from a brokerage app, their watchlist from a Telegram channel, and their trade rationale from memory. When BBCA drops 4% the week after they averaged down, they cannot tell you whether that average was part of a BoB continuation play with a defined SL, or an emotional averaging that was never logged as a plan at all. The distinction matters enormously — not just for ego, but for actually improving.

Without a structured journal, you cannot audit your strategy performance by type. You cannot tell if your BoW speculative setups have a positive expectancy over forty trades. You cannot see that your WnS entries tend to work in trending months and bleed in sideways markets. You are just a person with opinions about stocks and no data to sharpen those opinions against.

Inside a Well-Structured Plan Record

The "Strategy" field is where this template earns its keep. Instead of a free-text note saying "I think this will bounce," the trader must commit to one of five structured strategy types: BoB continuation, BoB reversal, BoW pullback, BoW speculative, or BoW sideways. This taxonomy is the entire backbone of a retroactive performance audit.

The "Action" field — BoW, WnS, BoB, Haka — pairs with Strategy to give each plan a complete directional and contextual label. The TradingView button, which dynamically populates with the ticker code from the "Code" field using the IDX prefix, launches the chart directly from the record. The "Entry Chart" image field is where you screenshot the setup at the time you wrote the plan — not after the trade closed, not after the stock moved. At the time you committed. That screenshot is the single most valuable piece of data in the entire record, because it is the only thing that cannot be revised with hindsight.

The SL and TP fields are integers — price levels, not percentages. This keeps the data clean and calculable. The linked "Trade" sub-library handles the actual execution: date, code, lot count, average price, and a calculated Amount field that runs -lot * avg / 10 to give you the position value in IDR units. The Amount and Lot rollup fields on the parent record aggregate these across all linked trade entries, so you always see your blended exposure at a glance.

The Forty-Trade Review

A single trade entry takes thirty seconds to log. The value does not appear until entry forty.

At forty entries with consistent Strategy labeling, you run a filter: BoW speculative only, then sort by outcome. The pattern that emerges — which months worked, which ticker segments cooperated, whether your BoB continuation trades outperform your reversals — is not something you could have seen any other way. The "Note" field on each plan record captures the pre-trade thesis; the Note on each individual Trade entry captures what actually happened. Reading those two fields side by side on a closed position, months later, is the closest thing to genuine trading education that retail traders have access to.