How to Review a Losing Week Without Quitting

Most traders review a losing week by re-reading the chats they were on during the bad trades, calling themselves names, and promising to be more disciplined. That's not a review. That's an emotional ritual that runs after the bad week and produces no actionable change before the next one starts.

A real review separates three things: setup failure, execution failure, and variance. Each one has a different fix. Conflating them produces the worst possible outcome — you adjust the setup when the problem was execution, or you tighten execution when the problem was variance, or you blame variance when the setup was broken to begin with. Five steps gets you out of that loop.

Step 1: Separate setup-failure from execution-failure from variance

Look at every losing trade from the week and put it in one of three buckets.

Setup failure means the trade matched your written criteria for the setup and the setup itself did not work. The signal failed. The pattern broke down in a way you did not anticipate. This is the bucket that signals "this setup may not have the edge I thought it did" and it requires re-examining the setup over a longer window (50-100 trades minimum) before changing anything.

Execution failure means the setup was fine, but you did something wrong. Entered too late. Sized too large. Moved the stop. Got out early. Held past the exit signal. This bucket signals a behavioral problem and it has a behavioral fix.

Variance means everything went right and the trade lost anyway. The setup matched, the execution was clean, the loss was at or under −1R, and the trade just didn't work — which it sometimes won't. This bucket needs no fix. It needs to be left alone.

The hardest part of this step is being honest about which bucket each trade belongs to. Traders default to "variance" for losses they don't want to examine, and to "setup failure" for losses they want to blame on the market. Neither is usually right.

Step 2: Tag everything

If your trades aren't tagged, this review will not work. You need at minimum: the setup name (breakout, pullback, vwap-reclaim, whatever your taxonomy is), the time-of-day bucket (open, mid-morning, lunch, power-hour), and the outcome bucket (winner, −1R, worse-than-−1R, scratch). Three tags per trade. That's enough.

If you're starting from zero tags, Setup Tagging 101 walks through a tag taxonomy you can adopt this weekend. The Tapeboard journal auto-log captures tags on every paper-sim fill automatically; for live trades you tag at the journal-entry step.

Step 3: Isolate the tags that bled

Pull up the week's losses and sort by tag. You're looking for two things: setups that are responsible for an outsized share of the week's losses, and time-of-day buckets that are responsible for an outsized share of the losses.

If 60% of your losers came from one setup tag, the setup is on probation. Run the setup through a longer window — last 50 trades, last 100 trades — and check whether the average R for that tag is positive over the longer window. If it is, this was a bad week for a setup that usually works, and the answer is to keep trading it without changing anything. If it isn't, the setup has been broken for longer than one week and the bad week just exposed it.

If 60% of your losers came from one time-of-day bucket, the discipline problem is time-specific. Maybe you take worse trades after lunch. Maybe you over-trade the close. Maybe you fade-trade the open when you should be standing aside until 10am. Time-of-day failure modes are the most fixable because the fix is a behavioral rule, not a setup change: stop trading during the bad window.

Step 4: Commit to ONE adjustment for next week

This is the step most reviews fail at. Traders generate a list of seven things to fix and end up implementing none of them, because seven simultaneous behavioral changes is impossible.

Pick one. Not two. Not "I'll work on a couple of things." One adjustment, narrowly scoped, that you can enforce as a binary rule.

Examples of one-adjustment rules that actually work:

• "I will not trade between 12:00 PM and 1:30 PM ET for the next two weeks."
• "I will not size above 1% of account on any breakout setup until the breakout tag's average R is positive over the last 30 trades."
• "I will not move a stop after entry. Bracket orders only."
• "I will skip every pre-10am entry signal next week."

Each of those is enforceable as a yes/no rule at the moment of trading. Vague resolutions like "be more disciplined" or "trust the system more" are not adjustments. They are wishes.

Step 5: Journal the adjustment so future-you can audit it

Open the trade journal and add a markdown note to the current week's entry that states the adjustment, the date it starts, and the date you'll review whether it worked. Use the date format Y-W (year-week) so weekly reviews chain together cleanly.

The reason this step matters is that next week, after a few good trades, you will forget the adjustment was a rule. Or you'll remember the adjustment but not the data that produced it, and a single decent trade will convince you the rule isn't needed. Writing it down forces future-you to either follow the rule or explicitly override it with a documented reason. Drift without documentation is how most behavioral fixes die.

What this review is not

This is not a strategy overhaul. A losing week is not enough data to abandon a setup. The average tagged setup needs 50-100 trades before its expectancy is statistically distinguishable from noise. One week's losses, even bad ones, do not justify scrapping the playbook.

This review is also not a confession booth. The point is not to feel bad about the bad trades. The point is to identify which bucket they belong to and apply the right fix to each bucket. Setup failures get a longer-window analysis. Execution failures get a binary behavioral rule. Variance gets ignored.

Most weeks, after running these five steps, you'll find that the losing week was 60% variance, 30% one specific execution failure (usually time-of-day related), and 10% genuine setup question. The 30% has a fix you can apply Monday morning. The 60% has no fix and shouldn't have one. The 10% goes on a watchlist for re-examination in a month.

That's a useful weekly review. The version where you re-read your chat history and feel terrible is not.