Flat weeks tempt stupid upgrades: new pair, wider stop, news gamble, size bump "to make the week count".
Rules I follow when the week is roughly flat by Wednesday:
- No new pairs.
- No increase in size.
- No Tier-1 experimentation.
- Session length stays the same; I do not add NY chase to "find" P&L.
- Journal prompt focuses on process, not on inventing a narrative for the flatness.
Flat is allowed. Flat plus improvisation is how red Fridays start. On prop, a flat week inside limits is a successful week. I try to borrow that definition for personal capital too. The market does not owe me a green Friday because Monday to Thursday were quiet. If flatness bothers me, I schedule extra demo reps or journal review after hours - not extra live risk. The itch to make the week "count" is the risk. Naming it helps. I tell myself flat weeks are inventory of discipline. That framing sounds cheesy and still works better than hunting excitement.
Rules I follow during a flat week
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Rules I follow during a flat week
Roughly flat needs a number, otherwise the rules switch on whenever the week feels disappointing. Mine is anything between minus 1R and plus 1R by Wednesday close, which on my normal trade count is about where noise lives.
Inside that band I also check how the week got flat. A week of six small scratch trades and a week of +3R then -3R both read zero, but the second one usually means a rule broke somewhere and needs looking at.
The flat week with a low ticket count is the one that tempts me most. If there were only two setups by Wednesday, the market was quiet, and adding NY sessions is just hunting for setups that aren't there.
On prop the flat week has one specific trap. If the firm has a minimum trading days rule, people start taking marginal trades just to tick the day off, and I'd rather wait for one clean setup at normal size than force three.
Do your rules change if the flat week is the last week of a challenge? That's the one place I've seen a size bump argued for, and I'm still not convinced.
Inside that band I also check how the week got flat. A week of six small scratch trades and a week of +3R then -3R both read zero, but the second one usually means a rule broke somewhere and needs looking at.
The flat week with a low ticket count is the one that tempts me most. If there were only two setups by Wednesday, the market was quiet, and adding NY sessions is just hunting for setups that aren't there.
On prop the flat week has one specific trap. If the firm has a minimum trading days rule, people start taking marginal trades just to tick the day off, and I'd rather wait for one clean setup at normal size than force three.
Do your rules change if the flat week is the last week of a challenge? That's the one place I've seen a size bump argued for, and I'm still not convinced.
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Rules I follow during a flat week
PropScalpDesk, I would push back gently on the extra demo reps. If the reps are on the same setups that is fine, but on a flat week mine used to drift into testing a new pattern, and that pattern showed up live the following Monday without ever passing a proper sample.
So my rule is demo only for setups already on the sheet, and the demo session is capped at the same ticket count as a live day. For me that is four tickets, which keeps the demo from turning into a slot machine.
The other number I check is the weekly spread of results. My last twelve weeks ran with a standard deviation of roughly 2.5R, so a week sitting at zero by Wednesday is completely ordinary and does not need a story.
Friday afternoon is where the flat week rules get tested hardest. Any ticket after 14:00 London has to be a setup written on the morning sheet, otherwise it is the make the week count trade wearing a disguise.
Do you treat a flat week that follows a red week any differently? That is the combination where I feel the pull to win something back most strongly.
So my rule is demo only for setups already on the sheet, and the demo session is capped at the same ticket count as a live day. For me that is four tickets, which keeps the demo from turning into a slot machine.
The other number I check is the weekly spread of results. My last twelve weeks ran with a standard deviation of roughly 2.5R, so a week sitting at zero by Wednesday is completely ordinary and does not need a story.
Friday afternoon is where the flat week rules get tested hardest. Any ticket after 14:00 London has to be a setup written on the morning sheet, otherwise it is the make the week count trade wearing a disguise.
Do you treat a flat week that follows a red week any differently? That is the combination where I feel the pull to win something back most strongly.
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Rules I follow during a flat week
Memory fades. Six months after building a strategy, the reasons behind its rules, the quirks of its settings and the lessons from its failures are mostly gone. Documentation is a letter to a stranger who happens to be the same person.
A useful set includes: a strategy specification with exact rules and the reasoning behind them. A setup guide for the platform and infrastructure: server details, installed software, configuration. A deployment record with versions and dates. A list of known issues and workarounds. A research log of tests and results. A runbook for emergencies: what to do if the platform crashes, the internet fails or an order goes wrong.
Writing in plain language, with dates, makes later reading easy. Screenshots of configuration screens save hours when rebuilding a machine.
Storing documents in more than one place, and keeping them updated when things change, matters as much as writing them.
The payoff arrives during the first crisis, when a stressed mind can follow a checklist it wrote while calm. It also helps anyone who might need to take over or advise.
A neat way to test documentation is asking someone else, or the same person after a break, to follow the runbook on a spare machine. Every point where they get stuck is a gap to fix. It's an humbling exercise and it works.
What documentation exists for the trading setup, and which gap would hurt the most in an emergency?
A useful set includes: a strategy specification with exact rules and the reasoning behind them. A setup guide for the platform and infrastructure: server details, installed software, configuration. A deployment record with versions and dates. A list of known issues and workarounds. A research log of tests and results. A runbook for emergencies: what to do if the platform crashes, the internet fails or an order goes wrong.
Writing in plain language, with dates, makes later reading easy. Screenshots of configuration screens save hours when rebuilding a machine.
Storing documents in more than one place, and keeping them updated when things change, matters as much as writing them.
The payoff arrives during the first crisis, when a stressed mind can follow a checklist it wrote while calm. It also helps anyone who might need to take over or advise.
A neat way to test documentation is asking someone else, or the same person after a break, to follow the runbook on a spare machine. Every point where they get stuck is a gap to fix. It's an humbling exercise and it works.
What documentation exists for the trading setup, and which gap would hurt the most in an emergency?