Journal fields that match the reading sequence
If your journal starts with entry price, you are recording the last step first. Here is the field order we teach.
A journal that opens with “entry / stop / target” skips the decisions that actually failed. Our template forces higher-timeframe context onto the page first.
Required fields (in order)
- Weekly context — range, trend, or break; one sentence.
- Daily bias — one sentence referencing the weekly.
- Zone — where confluence justified interest.
- Trigger — what the execution timeframe had to print.
- Pass or take — with a reason code (e.g.
WT_CONFLICT,ZONE_MISS,TRIGGER_OK). - Result — only after the above; R-multiple or scratch.
Codes we use in the study circle
| Code | Meaning |
|---|---|
| WT_CONFLICT | Lower timeframe disagreed with weekly |
| ZONE_MISS | Entry taken outside pre-marked zone |
| TRIGGER_OK | Confirmation printed as planned |
| NEWS_SKIP | Session skipped due to scheduled event |
Habit tip
Fill fields 1–3 before the session opens. If you cannot, you are not prepared to take a trigger that day. That empty journal page is still useful evidence.
The intensive includes the template as a printable sheet; alumni in the Weekly Study Circle compare reason codes each month.