Forex Trading Journal: Fields, Sessions, and Review Guide

A forex trading journal should make performance comparable across pairs, sessions, and changing market conditions. Currency markets trade nearly around the clock, spreads vary, and leverage can make small execution differences meaningful. Recording only entry, exit, and P&L misses why a London-session breakout is not the same trade as a late New York entry on the same pair. Structure the journal around the questions you review.

Forex-specific fields to capture

• Pair, direction, entry, exit, stop, size, and timestamps with timezone.
• Session: Asia, London, New York, or an explicitly defined overlap.
• Setup, higher-timeframe context, and market condition.
• Spread, commission, swap, and slippage when relevant.
• Planned risk in account currency and percentage; result in R.
• Chart screenshot, emotion, execution tag, process grade, and lesson.

Keep the pair format and session definitions consistent. EUR/USD and EURUSD should not become separate categories. Decide how you assign trades spanning two sessions and document the rule. Consistency matters more than finding a universally correct taxonomy.

Why sessions belong in the journal

Liquidity and volatility often differ by session, but your journal should test how those differences interact with your own setup rather than repeat general market sayings. Tag the session at entry, then compare trade count, average R, spread cost, and rule adherence for the same setup. If London appears stronger, inspect sample size and screenshots before drawing a conclusion.

Record costs that change the outcome

Spread, commission, financing, and slippage can turn a small theoretical edge into a poor net result. Costs matter especially for frequent trading and tight targets. Record net P&L and use net results for R calculations where practical. For longer holds, note swap or financing separately so the review can distinguish trade movement from carrying cost.

Use R to compare different pairs and stops

Define one R as the amount you intended to lose at the original stop. If account risk was $50 and the trade netted $75, the outcome is +1.5R. If you moved the stop and lost $70, record the planned 1R and actual -1.4R. That gap reveals behavior. Confirm pip value and contract size because they differ across pairs and account currencies.

A simple forex journal example

• EURUSD long; London session; continuation pullback.
• Higher timeframe aligned; no high-impact release inside the planned window.
• Initial stop defined before entry; $50 planned as 1R.
• Spread and commission included; chart captured at decision time.
• Calm entry, no stop movement, partial exit followed plan.
• +1.3R net; lesson: keep the same entry filter for the next sample.

Journal news context without pretending to forecast

Economic releases can change volatility and spread. Record whether a scheduled event was near the trade and whether your plan allowed exposure, but avoid using the journal to assert that one headline caused every move. The useful review question is whether you followed your event-risk rule and whether execution costs changed around those windows.

A beginner learning routine

1. Choose one or two liquid pairs and one defined session.
2. Use demo or risk small enough that execution can be observed calmly.
3. Journal every trade on the same day, including scratches.
4. Keep setup definitions stable for a preselected sample.
5. Review one variable at a time: selection, risk, entry, or exit.
6. Increase complexity or size only under a separate risk plan.

Weekly forex review

First reconcile all trades with broker history and correct timestamps, costs, and size. Then group by setup, pair, and session. Review process grade before outcome, and inspect screenshots behind outliers. Look for repeated overtrading, entries near excluded news, wider-than-planned stops, or session-specific slippage. End with one measured adjustment, not a completely new system.

Spreadsheet, screenshots, and optional OANDA context

A spreadsheet can be a complete free forex journal when it stays current. Screenshot software helps when image storage and tagging create friction. TradeLogger’s optional OANDA API connection supplies connected account performance context; it is not universal broker sync and does not replace setup notes. Screenshot capture remains useful because account statistics cannot show the chart you acted on.

TradeLogger can shorten the manual workflow: upload the pair chart, verify the extracted row, tag pair context, session, and behavior, then review trades on the calendar. Test it with a limited sample and compare completeness with your current journal. The right tool is the one that keeps accurate records available for review.