Most traders review their losing trades and move on. The ones who compound their edge over time do something different: they review the entire month as a system, not a collection of individual outcomes.
A monthly performance review is where patterns that are invisible in daily or weekly snapshots become undeniable. Here is the exact process to run one.
Step 1: Pull the Raw Numbers First
Before drawing any conclusions, gather your core metrics for the month. These are non-negotiable:
- Total trades taken
- Win rate (winning trades / total trades)
- Average winner vs. average loser (in pips and R)
- Profit factor (gross profit / gross loss)
- Maximum drawdown (peak-to-trough in the month, as a percentage of account)
- Net pips and net P&L
A profit factor below 1.0 means you lost money. Between 1.0 and 1.3 means you’re grinding with thin edge. Above 1.5 is where sustainable growth typically lives. If your profit factor was 1.8 last month and 0.9 this month, the data will tell you exactly where the divergence came from — but only if you dig into the breakdown below.
For context: if your account is $5,000 and your maximum drawdown hit $600 (12%) this month while your average monthly gain has been 4-5%, something structural changed. That’s what you’re hunting for.
Step 2: Break Performance Down by Session and Day
A monthly aggregate hides the most useful information. Slice it further:
By session: London open, New York open, Asian session, London/NY overlap. Most retail forex traders are significantly more profitable during one session and actively lose money during another. If your EUR/USD trades taken during the Asian session show a 35% win rate versus 58% during London, that is a 5-minute fix: stop trading that pair during that session.
By day of week: Pull your win rate and average R for each day — Monday through Friday. Many traders discover Friday afternoon trades (after 4:00 PM EST) drag their monthly numbers significantly due to low liquidity and position squaring. A single rule like “no new trades after 3 PM EST on Fridays” can add 15-20 pips to a monthly average.
Example: If you took 12 trades on Tuesdays with a 67% win rate and 1.8R average, but 14 trades on Thursdays with a 38% win rate and 0.9R average, Thursday has a measurable problem worth investigating before next month begins.
Step 3: Audit Your Setup Performance
Every trade belongs to a setup category — breakout, pullback to structure, session open range, news fade, etc. Group your trades and calculate win rate and average R per setup type.
This step consistently exposes one of two problems:
-
A setup that used to work has stopped working. Markets shift. A supply/demand zone setup that had a 65% win rate in Q1 may have dropped to 44% in Q2 as the pair entered a strong trend regime. The data will tell you this before your account does.
-
You are over-trading low-probability setups. Traders who feel pressured to trade every session often fill gaps with B-grade setups. If your A-grade setups (clearly defined structure, high confluence) show 2.1R average but your total month average is 0.8R, the gap is coming from setups you should not have taken.
Track this in your trading journal with setup tags on every entry. Without that metadata, this entire step becomes guesswork.
Step 4: Identify Behavioral Patterns in the Data
Numbers reveal behavior. Here are three behavioral signals hidden in monthly data:
Revenge trading signature: Look at trades taken within 30 minutes of a stop-out. Calculate the win rate on those trades separately. If it is below 30%, you have a documented revenge trading problem. If it is near your average, the behavior is not hurting you — yet.
Position sizing drift: Calculate your average lot size for trades 1-10 versus trades 11-20 versus trades 21+ in the month. Traders under drawdown pressure often unconsciously increase size mid-month to “make it back,” which inflates losses on already-bad weeks. A consistent lot size across the month is a discipline indicator.
Winner-cutting / loser-holding: Compare your planned R:R at entry versus your actual R:R at exit. If you planned 1:2 on average but exited at 1:1.1 actual, you are cutting winners short. If your planned stop was 25 pips but your average realized stop was 38 pips, you are moving stops — and that compounds monthly losses significantly.
Understanding emotional trading patterns in your data is harder than tracking pips, but it is where most improvement actually comes from.
Step 5: Set Three Specific Rules for Next Month
A review is worthless without commitments. But “trade better” is not a commitment — it is a wish. Set three rules that are specific, measurable, and tied directly to what the data showed:
-
Bad: “I will be more disciplined.”
-
Good: “I will not trade EUR/USD during the Asian session. If I do, I will flag the trade as a rules violation.”
-
Bad: “I will cut losers faster.”
-
Good: “My maximum stop loss on GBP/USD is 30 pips. Any trade where I move the stop wider than 30 pips counts as a risk management failure, regardless of outcome.”
Three rules maximum. More than that and compliance drops. Write them down at the top of next month’s journal before placing a single trade.
Review your forex risk management rules alongside this step — your monthly data should be informing those rules, not the other way around.
How to Structure the Review Document
Keep it simple. A monthly review should have five sections:
- Metrics summary — the raw numbers from Step 1
- Session and day breakdown — where you made and lost money
- Setup breakdown — win rate and average R per setup type
- Behavioral observations — what the data reveals about your decision-making
- Rules for next month — three specific, measurable commitments
The whole thing should fit on one page. If it is longer than one page, you are over-analyzing the wrong things. Clarity beats comprehensiveness in a monthly review.
Key Takeaways
- Pull profit factor, win rate, average R, and max drawdown before drawing any conclusions — in that order.
- Break monthly performance by session and day of week; most traders have one session that silently drains their account.
- Tag every trade by setup type so you can isolate which setups are working and which are costing you.
- Look for behavioral signatures in the data: revenge trades, sizing drift, and actual versus planned R:R.
- Commit to exactly three specific, measurable rules for next month — no more, no fewer.
PipJournal automatically tags your trades by session, day, and setup type, then surfaces these breakdowns in a monthly analytics dashboard — so the data-gathering part of this review takes minutes instead of hours. For traders serious about building edge through review, the $179 one-time license pays for itself in the first month you catch a pattern you would have otherwise missed.
People Also Ask
How long should a monthly trading review take?
A thorough monthly review takes 60-90 minutes. Rushing it below 45 minutes usually means skipping the qualitative analysis that produces the most actionable insights.
What metrics should I review every month?
At minimum, review win rate, average R:R, profit factor, maximum drawdown, best and worst sessions by day/time, and your most and least profitable setups. These six data points catch the majority of fixable problems.
What is a good profit factor for a forex trader?
A profit factor above 1.5 is considered solid for an active forex trader. Below 1.2 suggests your winners are barely covering your losers and the edge is thin. Above 2.0 is excellent but rare without a very selective entry approach.
How do I identify emotional trading in my monthly data?
Look for clusters of trades taken within 30 minutes of a stop-out. If your win rate on those revenge trades is below 30%, you have a measurable emotional trading problem — not just a suspicion.
Should I review winning months differently than losing months?
Yes. In a winning month, the priority is understanding which setups and sessions drove the gains so you can replicate them. In a losing month, the priority is isolating whether the loss came from one bad week, a specific setup failure, or a systematic sizing error.
