The weekend is where the next week gets decided
Posted: Sat Oct 31, 2026 8:46 am
Between Friday's close and Sunday's open there is no price to react to, which makes it the most useful time of the week for a scalper. A short fixed routine does more than another hour of chart staring.
Saturday morning: export the week's history and fill any missing journal fields while memory is fresh. Tag every rule violation. Calculate cost per trade and expectancy by session, then compare against the previous four weeks. One week is noise, but a sliding window shows trend.
Saturday later or Sunday: check the calendar for central bank meetings, major data and holidays, and mark the pairs that will be thin or event-heavy. Decide which sessions will be traded and which skipped, and write it down.
Sunday evening is for technical hygiene. Restart the machine, check for pending platform updates but do not install anything new right before the open, confirm the backup of the journal ran, and make sure the VPS or internet connection is behaving. Updates belong in a quiet window with time to test them.
The test is simple: if Monday begins with a plan and a clean setup, mistakes in the first hour should visibly drop.
Is there a weekend step you used to skip that turned out to matter more than expected?
Saturday morning: export the week's history and fill any missing journal fields while memory is fresh. Tag every rule violation. Calculate cost per trade and expectancy by session, then compare against the previous four weeks. One week is noise, but a sliding window shows trend.
Saturday later or Sunday: check the calendar for central bank meetings, major data and holidays, and mark the pairs that will be thin or event-heavy. Decide which sessions will be traded and which skipped, and write it down.
Sunday evening is for technical hygiene. Restart the machine, check for pending platform updates but do not install anything new right before the open, confirm the backup of the journal ran, and make sure the VPS or internet connection is behaving. Updates belong in a quiet window with time to test them.
The test is simple: if Monday begins with a plan and a clean setup, mistakes in the first hour should visibly drop.
Is there a weekend step you used to skip that turned out to matter more than expected?