Sleep debt and Monday London performance correlation

[LondonScalper]

Sleep debt and Monday London -- a correlation I stopped ignoring.

After short sleep, my journal shows more process tags: early entries, moved stops, "almost" setups taken as if they were A+. P&L can still be green by luck; the tags do not lie. That is the point of tagging behaviour separately from money.

Monday rule when sleep was poor
Half size or observation-only for the first hour. Explicit permission to take zero trades. Coffee is not a strategy and neither is "I will be careful."

I track a simple sleep score (good / ok / poor) next to the day. After a few months the pattern was obvious enough to pre-commit size before the open, not after the first mistake.

Anyone else throttle size off sleep, or do you still treat Monday as full send regardless?

Travel Mondays and clock-change weeks get the same throttle by default. I would rather miss a clean drive than stack sleep debt on top of open volatility. If you share a desk or household, saying "half size Monday" out loud also helps -- social accountability is cheap and effective.

[FTtrader]

Sleep debt and Monday London -- a correlation I stopped ignoring.

After short sleep, my journal shows more process tags: early entries, moved stops, "almost" setups taken as if they were A+. P&L can still be green by luck; the tags do not lie. That is the point of tagging behaviour separately from money.

Monday rule when sleep was poor
Half size or observation-only for the first hour. Explicit permission to take zero trades. Coffee is not a strategy and neither is "I will be careful."

I track a simple sleep score (good / ok / poor) next to the day. After a few months the pattern was obvious enough to pre-commit size before the open, not after the first mistake.

Anyone else throttle size off sleep, or do you still treat Monday as full send regardless?

Travel Mondays and clock-change weeks get the same throttle by default. I would rather miss a clean drive than stack sleep debt on top of open volatility. If you share a desk or household, saying "half size Monday" out loud also helps -- social accountability is cheap and effective.

Hello LondonScalper,

This is an exceptionally mature realization. Separating process tags from P&L outcomes is the exact dividing line between amateur gambling and professional execution. A green P&L on a sleep-deprived Monday can actually be dangerous because it reinforces bad habits; the tags, as you noted, are the true ground truth of your performance.

Here is an extended breakdown of why this happens and how to push this framework even further.

[FTtrader]

The Physiology of the "Almost A+" Setup

When operating on sleep debt, the brain's prefrontal cortex—the area responsible for impulse control, complex pattern recognition, and risk assessment—is significantly impaired. Simultaneously, the amygdala (the emotional center) becomes more reactive.

You aren't taking sub-par setups because you forgot your strategy; you are taking them because your sleep-deprived brain is aggressively seeking the dopamine hit of being in the market, while lacking the executive function to filter out the noise. This is exactly why a "B-" setup suddenly looks like an "A+" setup.

The Monday London Trap

The Monday London open is already a high-variance environment. It is prime time for establishing the weekly narrative and hunting liquidity. Navigating raw price action and waiting for a genuine liquidity sweep on a 15-minute chart requires absolute patience.

If your cognitive bandwidth is compromised, you become the liquidity. You end up entering before the sweep is fully complete, or you start moving stops because you lack the mental resilience to let the market breathe. Stacking sleep debt on top of opening range volatility is mathematically negative-EV.

[FTtrader]

Systematizing the Throttle

"Coffee is not a strategy" is a brilliant operating principle. Willpower is a finite resource, and trying to "just be careful" while sleep-deprived is a losing battle.

Since you rely on custom execution tools and scripts, you can completely remove the human element from this decision:

Hardcode the Permission: Add a simple SleepState parameter (Good/OK/Poor) to the initialization of your execution scripts in MT4/MT5 or cAlgo.

Automated Risk Halving: If the script is initialized with Poor, the risk manager mathematically caps your lot size at 50% and automatically rejects any order placed before a certain timestamp (e.g., forcing you to sit out the first hour entirely).

The Circuit Breaker: By making this a software rule rather than a psychological one, you pre-commit your size at the compiler level before the chart ever opens.

[FTtrader]

Social Accountability at Scale

Your point about vocalizing the throttle is highly effective. Taking it a step further: publishing that daily sleep score/risk reduction to a trading partner or in a community forum creates an external pressure to honor the rule. It shifts the goal from "making money today" to "flawlessly executing the sleep-debt protocol."

Treating your mental capital with the same strict risk management as your financial capital is how longevity is built.

[FTtrader]

Since you spend your days in the .NET ecosystem, implementing this in C# for cTrader (cAlgo) is the cleanest approach. It allows you to leverage strong typing and standard TimeSpan logic to build a strict, unbypassable ruleset before you even look at the charts.

Here is the core logic for a cBot that acts as your execution wrapper. It introduces a SleepScore enum that you must set when dragging the bot onto your chart.

Code: Select all

using System;
using cAlgo.API;
using cAlgo.API.Internals;

namespace cAlgo.Robots
{
    public enum SleepScore
    {
        Good,
        Ok,
        Poor
    }

    [Robot(TimeZone = TimeZones.UTC, AccessRights = AccessRights.None)]
    public class SleepRegulatedExecution : Robot
    {
        [Parameter("Morning Sleep Score", DefaultValue = SleepScore.Good)]
        public SleepScore TodaySleep { get; set; }

        [Parameter("Base Risk Per Trade (%)", DefaultValue = 1.0)]
        public double BaseRiskPercent { get; set; }

        [Parameter("London Open (UTC)", DefaultValue = "07:00:00")]
        public string SessionOpenString { get; set; }
        
        [Parameter("Lockout Duration (Hours)", DefaultValue = 1.0)]
        public double LockoutHours { get; set; }

        private TimeSpan _sessionOpen;
        
        protected override void OnStart()
        {
            if (!TimeSpan.TryParse(SessionOpenString, out _sessionOpen))
            {
                Print("CRITICAL ERROR: Invalid Session Open time format.");
                Stop();
            }
            
            Print($"[INIT] Sleep state: {TodaySleep}. Active Risk: {GetCalculatedRisk()}%");
        }

        // 1. The Circuit Breaker
        private bool IsTradingAllowed()
        {
            if (TodaySleep != SleepScore.Poor) 
                return true;

            TimeSpan currentTime = Server.Time.TimeOfDay;
            TimeSpan sessionEnd = _sessionOpen.Add(TimeSpan.FromHours(LockoutHours));

            // Lockout applies if current time is within the first hour of the session
            if (currentTime >= _sessionOpen && currentTime <= sessionEnd)
            {
                Print($"[REJECTED] Trade blocked. Sleep debt lockout active until {sessionEnd} UTC.");
                return false;
            }

            return true;
        }

        // 2. The Size Throttler
        private double GetCalculatedRisk()
        {
            // Hardcoded 50% penalty for poor sleep
            return TodaySleep == SleepScore.Poor ? (BaseRiskPercent / 2.0) : BaseRiskPercent;
        }

        // 3. The Execution Wrapper (Map your UI buttons or hotkeys to this)
        public void ExecuteTrade(TradeType tradeType, double stopLossPips)
        {
            if (!IsTradingAllowed()) 
                return;

            double riskPercent = GetCalculatedRisk();
            
            // Standard position sizing logic
            double volume = CalculateVolume(riskPercent, stopLossPips);
            
            Print($"[EXECUTE] {tradeType} triggered. Risk bounded to {riskPercent}%.");
            
            // ExecuteMarketOrder(tradeType, SymbolName, volume, "PA_Setup", stopLossPips, null);
        }

        private double CalculateVolume(double riskPercent, double slPips)
        {
            // Replace with your preferred volume calculation
            return 10000; 
        }
    }
}

[FTtrader]

Why this architecture works:

Friction at the Compiler Level: Because TodaySleep is a required parameter, you are forced to make a conscious declaration about your mental state the moment you load the template. You can't just click "Buy" on autopilot.

Automated Journaling: When the bot rejects a trade, it prints [REJECTED] to your cTrader log. This creates an automatic, timestamped audit trail of the exact moments you tried to force a trade while compromised.

MQL Portability: If you need this for your MT4/MT5 setups, the logic maps perfectly to MQL5 using enum, TimeCurrent(), and the MqlDateTime struct to calculate the lockout window.

By offloading the discipline to the machine, you don't have to rely on willpower when your prefrontal cortex is already running on empty. You just let the if statement do its job.