The Forex trader's workflow: daily plan, pre-market, end of day and journal

A trader's daily work includes preparing for the session, observing the market, executing planned decisions and reviewing the results. A defined workflow establishes what to do before trading, what deserves attention during the session and how to close the day. This lesson connects the daily plan with a weekly review and regular evaluation of your work. It provides example schedules and checklists to adapt to your trading style and available time, including variants for fatigue, illness and travel. An essential part of the plan is deciding when to reduce activity or refrain from trading.

1. Three workflow scales: weekly, daily and monthly

Trading work includes regime assessment, preparation, end-of-day reconciliation, retrospectives and playbook review. Order execution is only one part. After two to four hours of continuous chart watching, a trader may start rationalizing a desire to act rather than analyzing a valid opportunity; this example offers no population study establishing that this happens to most retail traders at a particular hour. In the journal, look for entries outside the time window, incomplete checklists and orders prompted by “nothing is happening.” A useful routine restricts decision windows and includes periods when you leave the entry platform alone, while continuing any required management of existing exposure. Unnecessary clicking is a process risk; the article does not establish it as the cause of most account failures.

Three scales, three purposes

What happens when a scale is missing?

No weekly review: the same playbook remains active across every regime. In the example's illustrative progression, a trend-following strategy keeps signaling after the market becomes range-bound; results deteriorate over three to four weeks and the trader abandons the strategy without investigating regime fit. The adaptive markets hypothesis discusses changing conditions for strategies,^[5] but does not prove that a particular strategy has lost its edge or that a regime filter would have saved it.

No daily preparation or end-of-day review: the trader does not know today's releases, yesterday's final account state or why a trade was closed early. Each decision begins from scratch because the information needed for continuity was never recorded.

No monthly review: the last three weeks may feel better without producing better measured execution or outcomes. A B setup may warrant investigation if its estimated expectancy falls, but two different averages alone prove little without sample sizes, a method and uncertainty intervals; see 15.9, journal and metrics. The monthly review supplies the instruments needed to assess performance instead of navigating by mood.

Workflow stages: start condition, output and stop condition

Return to this table whenever it is unclear whether the next stage is permitted. Every stage has a start condition, a required output and a stop condition that ends the activity regardless of unused time. Durations illustrate a day trader's routine. Other styles change the windows rather than removing the sequence.

The table also identifies vulnerable points: the unsupervised break and end-of-day review after a difficult session may receive less attention than actual entry decisions. The example emphasizes stages 4 and 6 as practical failure points; it supplies no measured ranking of failure rates.

The monthly scale: specific work

Reserve two to three hours on the first weekend of the month. This article describes this as often neglected by retail traders and formalized in professional settings, without providing comparative prevalence data. The concrete tasks are:

1. Full P&L attribution — forty minutes. Total R, account-currency cash — PLN in this example — and account percentage. Break down results by A+/B/C class, pair and setup. Identify which setup contributed the largest gain and loss. A month may depend on one or two setups, while a supposedly profitable idea contributes losses through poor execution; investigate rather than assume that explanation.
2. Risk-exposure audit — thirty minutes. Monthly maximum drawdown, worst daily drawdown and days exceeding the daily loss limit. Was position sizing appropriate to the declared market conditions? Was a required high-volatility size reduction applied or forgotten?
3. Playbook evidence review — sixty minutes. Collect the weekly signals identifying setups that behave differently from their cards or require separate monitoring. The rhythm is weekly collection, monthly organization, quarterly decisions. Demotion, promotion and deactivation criteria, with sample size, method and intervals, belong to 15.10, strategy audit. Organize evidence monthly; do not change the rules ad hoc.
4. Quarterly-goal review — twenty minutes. Compare progress with the goals established at quarter-start. Financial goals, such as the example's illustrative 100R per quarter, are not return forecasts or reasons to force trades. Include process goals such as 100% end-of-day completion and zero entries outside planned hours. These are more directly controllable than P&L.
5. Next month's plan — fifteen minutes. Choose at most two or three priorities: specific behavioral repairs, a proposed new setup only after testing and review, or a justified exclusion from the observation universe.

The listed tasks total 165 minutes, within the two-to-three-hour budget. Against 25–35 hours of market work per week ×4.33 weeks, or approximately 108–152 monthly hours, a two-to-three-hour review uses roughly 1.3–2.8% of that time. Its value is an opportunity to detect a problem in the records before it becomes a larger balance loss. How early depends on trade frequency, evidence quality and sample size; a review cannot guarantee advance detection.

2. Sunday evening: assess the market regime in forty-five minutes

Choose a 45-minute slot on Sunday, for example between 19:00 and 22:00 Europe/Warsaw. Without a weekly plan, Monday can begin with a fresh chart and unchanged habits. Much of the later preparation, session work and review implements the playbook decision made during this assessment, while updating it for new information through predeclared rules.

The purpose of regime assessment

Answer four questions:

1. What is the volatility regime? High, normal or low, using recorded measurements rather than an impression.
2. Is the market trending or ranging? Check D1 ADX and the structure of the last twenty completed daily candles.
3. Which high-impact events occur this week? Record the actual schedule rather than “something on Wednesday.”
4. Which playbook is eligible? Trend following, mean reversion, breakout or a separately tested news strategy: one whose documented evidence and conditions fit the regime. If none qualifies, select no new trading.

The Sunday procedure, minute by minute

The blocks total forty-five minutes. If the review takes ninety, investigate an oversized watch universe or time spent debating individual setups. This example's four-to-six-pair universe is a practical workflow choice. Sunday chooses the framework; current entry setups are validated during the relevant trading day's preparation and session.

The regime decision tree

3. Before the session: the pre-market routine in fifteen to thirty minutes

Pre-market preparation connects Sunday's regime assessment to today's session. It updates information from Friday or Sunday with overnight developments. In fifteen to thirty minutes, move from ordinary daily activity into an operational state with current context and a recorded assessment of readiness.

The full variant: 08:30–09:00 Polish time before the London window

Keep one convention explicit throughout. Operator states A/B/C differ from setup classes A+/B/C, whose required conditions and sizing belong to 15.2, trading plan and playbook. The example operator-based per-trade caps are A →1%, B →0.5%, C →0%, calculated from start-of-day equity and kept on that fixed base throughout the day: two full 1% losses then equal exactly 2% of opening equity. A lower setup, portfolio or remaining-budget cap takes precedence; the percentages are ceilings, not entitlement. “Maximum risk today” in the templates denotes a single-trade cap, while daily loss-budget headroom is separate and checked before every entry. The cited example plan uses a 2% daily limit, 4% weekly limit, monthly −5% trigger for half size and −8% stop for the rest of the month. These are illustrative scenario rules owned by the plan, not market standards or locally adjustable workflow numbers. State the reference base for each period in that plan. Section 10 uses the same distinction.

The shortened variant: fifteen minutes when thirty are unavailable

Keep three written lines at minimum: active playbook, operator state and maximum per-trade risk plus remaining daily headroom. A full comparison is not needed if no additional exposure is being considered. Before adding a candidate alongside even one open position, the correlation check remains necessary. With no open exposure, record that the comparison is not applicable. Calendar, account-state and other hard evidence checks cannot be replaced by memory. This variant can accommodate a later start — 08:15 instead of 08:00 in the example — but if the required preparation does not fit before the window, defer entry.

The operator check is an operational control

This example's sleep literature discusses changes in decision-making and risk preference under sleep deprivation,^[2] but provides no measured effect size for traders. Treat it as a rationale for a declared operating rule, not a coefficient predicting trading losses. A trader after four hours of sleep may misclassify a poor setup as A+. The check aims to block new trading when decision quality is compromised, even if confidence remains high. Less than six hours of sleep fails the selected checklist; severe distress or illness can independently block entry. These are declared operating rules, not medical fitness criteria or a promise of safety above the threshold. Manage confirmed existing exposure only according to the plan or incident procedure, and defer new opportunities.

4. The session: execution windows and the time between trades

The session has a narrow task: execute eligible setups from the active playbook during the permitted windows, without impulsive departures. It may occupy many hours, but involves fewer types of decision than preparation and review. An executed fill cannot be undone; closing it is another transaction. Unplanned activity commonly takes the form of an off-card entry, excessive size or an unjustified stop adjustment.

Active session windows in Polish time

Operating rules during the session

Remove distractions. Close Slack, Telegram, YouTube and podcasts. Use Do Not Disturb with exceptions for broker alerts and emergency contacts. Keep Discord, X/Twitter and trading-community feeds out of the execution window if they prompt comparison or FOMO. The working screen contains the platform, journal and calendar, with only the information required by the declared setup.

Complete the checklist before entry. This example's thirty-second shorthand cannot replace the full fifteen-point procedure in 15.6, whose illustrative budget is 60–90 seconds. Each answer is YES, NO or unknown, with no “probably.” A hard NO or unknown blocks entry; the three auxiliary context criteria affect class and cannot compensate for a hard failure. Do not misread an auxiliary NO as automatically identical to a hard veto. Article 15.6 defines the calendar window, correlation limits, evidence and ticket checks. The workflow ensures that the complete check occurs before submission and that every rejection leaves a dated reason in the journal.

Take sizing from both the setup and operator limits. The setup-class cap comes from 15.2; the example operator cap is A →1%, B →0.5%, C →0%. Use the lower value. A highest-class setup in state B remains capped at half a percent; state C produces a rejection, not an entry. If the week's predeclared defensive variant applies, multiply that result by 0.5, giving 0.25% for a 0.5% B cap. The fixed sequence is setup cap → operator cap → weekly regime reduction, followed by portfolio and remaining-budget checks. It never bypasses a failed hard condition.

What to do between trades

The 09:00–10:30 London window may produce no signal or only one. That can leave more than an hour in which it is tempting to invent opportunities. Wait for the defined setup instead of searching for a reason to trade. Suitable activities include:

• Update the journal: finish legitimately deferred details from earlier trades. Repeated unfinished end-of-day records indicate a workflow problem rather than normal housekeeping.
• Read planned material: a trading book, economic report or BIS Quarterly Review, rather than a continuously stimulating social/news feed. Do not let reading interfere with required position monitoring.
• Take microbreaks: stand up approximately every 45–60 minutes and step away for three to five minutes after ensuring exposure is protected and monitoring arrangements permit it. Ninety minutes of continuous staring is not evidence of better concentration.

Waiting tests whether a defined opportunity exists or whether the trader merely wants action. The example highlights boredom and outside messages — a friend's setup, profit screenshot or breakout alert — as possible triggers for impulsive entries. It supplies no dataset proving that they account for most mistakes or that switching them off eliminates a particular proportion. Keep trading-community Telegram, Discord and Twitter feeds closed during the execution window if that is the declared control, and measure the resulting behavior in the journal.

A zero-entry day: a session can still produce complete work

A day with no new position is often left undocumented because it feels unproductive. It can demonstrate adherence to the admission process, although zero trades alone does not prove the filter improves expectancy. The example below follows a session with no entries and a record at every stage. The example includes a pending-order mistake, so complete entry records do not make every part of the process correct.

Illustrative example, not historical performance.

A zero-entry day is completed work when every stage leaves its required output. Check four records: daily plan, contemporaneous rejection reasons, final pending-order state and a completed end-of-day entry with a trade count of zero. If one is missing, the work is unfinished even when realized P&L is zero. A later winning move does not change whether a rejection complied with the rules. In the retrospective, two documented no-entry days and three compliant trades are more interpretable than eight trades containing three boredom entries. A complete record can also reveal a process error, as the pending-order example does.

The in-session journal

Record decisions as they occur. The minimum entry record is:

• Time, HH:MM with timezone — Europe/Warsaw in this example.
• Pair, direction and position size.
• Setup class A+/B/C and a one-sentence rationale; a rejected C candidate is recorded without an order.
• Planned entry, stop, TP1 and TP2.
• Order type — market, limit or stop — followed by actual execution confirmation, fill price and difference from the planned reference.
• The plan/playbook version used for the decision.
• Emotional-state rating on the example's one-to-five scale: 1 calm, 5 noticeable excitement or fear. This descriptive field cannot override hard behavioral limits.

The example budgets approximately thirty seconds for a brief record, with planned fields written before submission and fill fields added only when confirmed. It preserves the information needed to investigate why a trade that once showed 2.5R eventually closed at break-even, rather than relying on a vague memory that “something happened.”

A day trader's session, hour by hour

This example covers London and New York activity in Polish summer time, with the normal six-hour New York offset. Recalculate for mismatch weeks:

The two active-attention blocks total five hours: 1.5 hours plus 3.5 hours. The rest is preparation, waiting, administration or monitoring. Five hours of availability does not mean five hours of continuously permitted entries. Trying to remain intensely focused for eight uninterrupted hours can undermine the second window; treat breaks as part of the operating plan rather than assuming unlimited attention.

5. End of day: close the day in fifteen minutes

End of day (EOD) creates the evidence needed to ask where outcomes or execution depart from the plan. A month of impressions without reconcilable records cannot answer that question. Reserve approximately fifteen minutes after your own session ends, often somewhere between 17:30 and 22:00 Polish time depending on style. Leave the account operationally understood instead of beginning tomorrow by reconstructing positions, stop levels and exit reasons from memory.

The five EOD steps

1. Complete the journal — five minutes. Each closed trade needs opening/closing time, entry/exit fills, size, class, P&L in pips and R, account-currency cash — PLN in this example — and a short execution note. Did the stop and take profit follow the plan? Were they changed, and why?
2. Calculate daily P&L — two minutes. Sum cash and individual-trade R, with week-to-date and month-to-date totals. Check loss-budget compliance. In the example, −1.7% against a 2% daily limit leaves only 0.3% of that fixed daily base before other exposure and costs. A reduced next-day starting size applies only if a prewritten drawdown rule requires it; do not invent a new “kill switch” after seeing the result or confuse today's remaining budget with tomorrow's reset.
3. Assess execution quality — three minutes. Separate it from P&L. Did each trade fit the playbook? Was an entry forced by FOMO or frustration? Was the stop changed without a valid trigger? Was a position closed early? The example labels are good for full compliance, mixed for one or two minor deviations, and poor for three or more deviations or one major error. A profitable breach remains a breach.
4. Review open positions and pending orders for tomorrow — two minutes. Check every swing/position trade's accepted SL/TP and overnight or next-day events that trigger predefined management. Separately inspect pending-order trigger price, attached protection, expiry — day, GTC or a specific date — and whether the order may remain active overnight. An overlooked GTC can open a position during an excluded release while the trader sleeps. Prevent or cancel prohibited activation and verify the resulting broker state; a past checklist does not authorize indefinitely changed conditions.
5. Write tomorrow's plan — three minutes. Record watched pairs, playbook setups worth monitoring based on today's observations and tomorrow's events. These are candidates, not forecasts. Tomorrow's pre-market starts by updating that plan rather than starting from nothing.

EOD is not a reward for a pleasant day

After three losses in a row, it is tempting to write “bad day, tomorrow will be better” and stop. Review can reveal deviations such as treating B as A+, increasing size after a loss or entering outside planned hours. It can also confirm three compliant losses; do not presume every losing streak contains an operator error. Without the record, neither explanation can be assessed and a repeated mistake may remain unidentified.

The five-minute minimum EOD

When exhausted after a late window, for example ending at 22:00, retain these essentials:

• Check every open position and pending order: accepted protection, known expiry and no unaddressed overnight event requiring action — approximately one minute if the account is simple.
• For closed trades, record R, execution quality — good/mixed/poor — and one sentence of learning. If there were no entries, record zero and the rejection reasons. Approximately two minutes.
• Review tomorrow's calendar and confirm dated high-impact alerts — approximately one minute.
• Write one sentence for tomorrow's plan — approximately one minute.

The target is five minutes, not a reason to leave an unresolved position unchecked. Minimum means a reduced but complete essential record, never zero review. Defer only nonessential detail and record what remains to be completed.

Common EOD traps

Trap 1: reducing EOD to “good day / bad day.” Green P&L produces happiness, red produces frustration, and neither produces analysis. Keep the record neutral: numbers, execution quality and the next plan. Set a fixed EOD alarm, for example 22:15 Europe/Warsaw after a personally chosen evening entry window closes. The example New York FX session continues to approximately 23:00 under the normal offset; your EOD follows your planned work window, not an assumed universal market close.

Trap 2: reading PLN without R. A PLN 180 gain against PLN 600 of initial trade risk equals +0.3R. A PLN 660 loss against the same denominator equals −1.1R. The ratio describes magnitude; it does not by itself prove good management or that a worse-than-stop loss was within the plan. Investigate costs, slippage and deviations separately. Fix the denominator for each trade before submission. Sum individual R-multiples for the day; do not divide total cash by an averaged risk denominator. A 1%-risk trade and a 0.5%-risk trade have different initial cash-risk units. R is the analytical unit; PLN is the accounting currency in this example. Risk-multiple analysis was popularized in trading-system literature.^[4] Keep both currencies and R, and never alter a pre-entry denominator after seeing the result. Where initial risk was not defined, report cash and equity percentage rather than inventing R.

What EOD hands to the next stage

EOD supplies evidence for weekly/monthly statistics and quarterly setup review. Expectancy, profit factor, R distributions, MAE/MFE, drawdown, denominators, intervals and field definitions belong to 15.9; retain/change/disable decisions belong to 15.10. The workflow's narrower duty is complete contemporaneous data. Expectancy computed from a journal missing losing days is selection-biased, regardless of arithmetic precision. Rejected candidates do not enter executed-trade expectancy, but their separate records and consistently modeled hypothetical outcomes are needed to evaluate what the filter excluded. Execution-cost modeling for tests is covered in 15.4.

Trap 3: EOD without a deviation list. “Three trades, P&L +1.2R” is data, not the complete review. Were all three eligible under their actual classes? Was any entry forced? Was a stop modified? Without that assessment, recurring deviations cannot appear in the weekly retrospective because they were never categorized.

6. The weekly retrospective: thirty minutes at the weekend

Choose a consistent weekend slot of thirty to forty-five minutes. The retrospective does not redesign the system every Friday. It marks deviations and collects evidence, adapting the familiar plan–do–check–adjust process loop^[3] to a trading week. Repair execution while keeping rule changes under review. The overall rhythm is weekly collection, monthly organization, quarterly decisions. Without a recurring review, each week's P&L becomes an isolated event rather than part of an interpretable record.

The retrospective procedure

1. Weekly P&L in R and account currency — three minutes. Total R, cash — PLN in this example — and account percentage. Compare with the previous three weeks. Describe the pattern without treating four weekly observations as proof of a stable trend.
2. Weekly trade statistics — five minutes. Trade count, win rate, average win and loss in R, and expectancy, broken down by setup class A+/B/C. A C trade is a recorded breach under a card that excludes C, not a newly permitted category.
3. Deviations from the plan — ten minutes. Read each day's EOD record for FOMO, increased size after a loss, out-of-window entries or unjustified stop changes. Write “increased size after a loss twice,” rather than “undisciplined.”
4. Regime review — five minutes. Compare Sunday's assessment with what subsequently occurred. If the week ranged after a trend-following plan, distinguish a missed available input from a genuinely later regime change. Do not grade Sunday using information that did not yet exist.
5. Playbook observations — five minutes. Record setups whose behavior differs from the card or warrants separate monitoring. These are observations, not immediate promotions, demotions or deactivations. Apply the audit's sample, method and interval criteria in 15.10.
6. Next week's behavioral repair — two minutes. Choose one or two measurable actions that restore existing rules, such as obeying a declared Friday-after-18:00 ban or the established EUR/USD FOMC exclusion. If a ban does not already exist, adding it is a proposed filter change requiring a new version and validation.

The six-step retrospective template

Keep the retrospective operational

Market complaints, unsupported claims of manipulation and promises to “focus harder next week” do not produce an actionable review. Emotional observations belong in the daily record and may help explain behavior, but the retrospective turns evidence into specific execution repairs. Its output is an operational document, not a motivational verdict on the trader.

What one week cannot justify changing

After five to ten losing trades, the trader may begin adjusting everything: wider stops in week two, a new ATR filter in week five, no Wednesday entries in week nine. This article calls this intervention bias as a working description of reacting to noisy results. The label does not establish a formal statistical diagnosis; the problem is repeated rule selection from an insufficient and repeatedly reused sample.

• Do not redesign a setup from a handful of weekly trades. The retrospective collects evidence. Whether it resolves a decision depends on uncertainty relative to the threshold, outcome dispersion, signal frequency and the number of variants tried. There is no magic trade count. See 15.10.
• Do not validate a rule change on the same week that suggested it. Specify a comparison using separate held-out data and appropriate regime controls, rather than admiring a few new trades on an equity curve. A naive different-period before/after comparison can also confound regime and filter effects. Methods are in 15.4.
• A weekly correction restores an existing behavioral rule. Obeying an already declared Friday-after-18:00 restriction is different from introducing a new time filter. Changing stop distance from 1.5×ATR to 1.8×ATR changes the system and belongs in the versioned audit process.

The boundary of the retrospective

The weekly review repairs execution timing, checklist completion, state-based sizing and record quality. Diagnosing whether a deterioration comes from strategy rules, regime, costs or the operator requires the separate sequence in 15.10: trustworthy data and execution, costs and regime, then the edge. Each quantitative decision needs its sample, method and uncertainty interval.

Stopping new trading because a loss limit or execution fault is reached never requires waiting for statistical significance. A small sample can prevent a justified strategy redesign; it does not prevent a predeclared stop protocol. “I cannot do anything until enough trades accumulate” is not a reason to continue through a known operational failure.

7. What to omit during fatigue, illness or travel

A workflow is tested on the difficult Wednesday after five hours of sleep and a call from a child's school, not only on an ideal Monday. Flu, business travel, a sick child, work stress, a wedding weekend or a flight across eight timezones all require a predetermined reduced routine. Travel arrangements and position-sizing controls are separate parts of preparation. Define the variant before the difficult day, when improvisation is least reliable.

Three workflow variants: full, reduced and minimum

When to use each variant

Full: the default example assumes at least seven hours of sleep, no illness and a familiar working location. Whether that describes most days is individual; measure your own pattern rather than importing a prevalence claim.

Reduced: this example uses at least six but less than seven hours of sleep, a mild cold or headache, same-timezone business travel and significant family demands. Those examples describe workload reduction, not automatic entry eligibility. With the current 15.6 checklist, less than six hours of sleep blocks new trades; a reduced administrative routine can still be used. Six hours alone does not prove fitness, and illness, medication effects or other hard conditions can still require no trading.

Minimum: this example gives less than six hours of sleep, fever, jet lag, severe outside stress or holiday as examples. There is no new active trading; manage existing confirmed exposure according to the plan. If this state persists beyond three days, the example plan calls for winding down exposure and taking a break. Carry out any closure only with confirmed account state and available execution; if monitoring cannot be sustained, use the predefined incident procedure rather than waiting mechanically for day four.

A worked week with poor sleep

The synthetic week runs from 7.5 hours of sleep on Monday to 4.5 after a party on Tuesday, five interrupted hours while caring for a child on Wednesday, eight hours on Thursday and seven on Friday. Preserve the example's schedule while applying the governing admission conditions:

The retrospective records two reduced-workflow days and fewer possible trades. Following the declared controls is a process success, even if there are fewer profit opportunities; it does not guarantee the account cannot lose on existing exposure. A trader without variants might instead use full size after 4.5 hours of sleep. No evidence is supplied here of measured financial cost of that choice, so the example illustrates an executable rule rather than a promised return improvement.

Rules for moving between variants

• Choose the variant during pre-market. Do not promote a morning B assessment to A mid-session because you feel warmed up. A hard no-entry condition remains binding.
• Downgrade when conditions worsen. Increasing fatigue or frustration can move B to C and end new trading. A same-session upward reassessment by the same impaired operator is not a reliable override.
• After three or more minimum-variant days, perform a full readiness review. Decide whether recovery is sufficient or a longer break and exposure reduction are required. Managing positions for two weeks while unable to resume the routine can itself consume recovery capacity.

The minimum variant still needs reliable infrastructure

Three prerequisites remain: protective stop instructions submitted with the entry request and then confirmed server-side, rather than deliberately opening an unprotected position and promising to add a stop; a tested, logged-in broker mobile app; and a recorded support/dealing contact with the account identifier. A server-side stop does not guarantee its fill price, but it avoids dependence on the local computer remaining online. The example budgets a brief weekly verification of these arrangements; a failure discovered on any day must be resolved before relying on them.

Backup power, a second connection, terminal redundancy, configuration backups and failover drills are covered in 15.1. Actions during a live outage, including the need to confirm account state before sending another instruction, belong to 15.8. A minimum routine without reliable protection and access is not an operationally complete variant.

8. Workflow by trading style: scalping, day, swing and position trading

The workflow changes with style while retaining periodic review, preparation, execution control and reconciliation, together with reduced and no-entry variants. Window length, review frequency and active hours change. Fit the workflow to the chosen style and actual availability.

Workflow by style

The Polish schedule and how to localize it

This example uses Poland as its reference location. Use a named zone, Europe/Warsaw, for these examples and convert actual dates to your working location. Do not label a daylight-saving-aware schedule simply “GMT” or “EST” throughout the year. The standard reference times are:

Do not hard-code remembered offsets into an expert adviser or playbook without dated timezone handling. Check the broker calendar around March and October/November clock changes, and set alarms for a specific date and release time rather than assuming a weekly recurring event.

The scalper's workflow: compressed time

The example scalper uses M1–M5 and holds positions for approximately two to fifteen minutes. Compress the process without deleting necessary controls:

• Ten-minute pre-market: inspect today's calendar, readiness, data and any open exposure or pending orders. An eight-pip spread around news can overwhelm a small scalp target. Preconfigured real-time inputs can save collection time; they do not remove calendar or behavioral checks.
• A 90–150-minute active window: for example 09:00–10:30 around London or 14:00–15:30 around the 08:00 ET New York FX convention. A 14:30 US release is a data event, not the session opening. The governing calendar rule can exclude this entire candidate window on that day. This example's ninety-minute attention warning is a workflow heuristic, not a measured universal failure threshold.
• Twenty-to-thirty-minute EOD: eight to twenty-five trades at thirty to sixty seconds per record require four to twenty-five minutes of recording alone, followed by daily totals and the next plan. These illustrative counts are not a trading target. Preserve a record for every execution.
• Sixty-minute retrospective: more trades create more material, not automatically stronger evidence. Splitting by hour, weekday and setup creates smaller subgroups and more comparisons; describe the week and leave validated system decisions to the audit.

The swing trader's workflow: calendar exposure across days

The example swing trader uses H4–D1, holds positions for two to ten days and sets aside thirty to sixty minutes for planned daily review. Distinctive elements include:

• An extended Sunday assessment of sixty to seventy-five minutes: add the central-bank hiking/cutting cycle, seasonal hypotheses tested on your own data, and relevant futures positioning. The CFTC's Commitments of Traders reports describe reportable positioning categories in covered markets, not every large participant's complete global FX book. This example's usual schedule is Friday publication of Tuesday positions; check holiday exceptions and use only information available at the decision time.
• 08:00–08:30 Poland-local preparation: inspect the previous completed D1 candle, whose boundary is defined by the broker's server convention. This example mentions 23:00 Poland-local or midnight implementations; verify your account rather than assuming all daily candles are identical. Review exposure, upcoming events and any valid new daily-chart candidate.
• Mostly passive monitoring: price and calendar alerts supplement planned checks. The example proposes four to six checks of five minutes each, adding twenty to thirty minutes to the stated review workload. If work duties prevent a complete admission check, the alert does not authorize an immediate new entry. Pending orders need valid expiry and pre-activation controls.
• Ten-minute EOD: review open exposure and tomorrow's plan, which may simply be “hold under the existing rules.” A profitable day alone does not justify moving the stop; use the card's actual trailing or invalidation trigger.

The position trader's workflow: the monthly scale dominates

The example position trader uses weekly charts and holds positions for four to twelve weeks. The review rhythm shifts towards longer horizons:

• Monthly regime assessment: ninety to 120 minutes on the first weekend, focused on central banks, inflation and the economic cycle. Technical inputs remain whatever the declared strategy requires.
• Weekly preparation: approximately thirty minutes on Sunday to inspect completed weekly charts, the coming calendar and confirmed exposure.
• Several fifteen-minute reviews during the week: avoid unnecessary continuous chart watching, but retain the account, margin, event and incident monitoring required by the instruments. A long intended holding period does not make daily risks disappear.
• Weekly EOD-style review: approximately thirty minutes on Friday for position state, fundamentals and whether the thesis still meets the card. Do not wait for a broker's Friday closure to send a required order that cannot execute after the market shuts.
• Quarterly retrospective: two to three hours, plus the shorter ninety-minute monthly review. With perhaps one or two entries per week or none, a weekly performance conclusion may lack evidence; a weekly operational check still has value.

9. Common workflow mistakes

Mistake 1: keeping the workflow only in your head

The trader “knows what to do” but records neither preparation, EOD nor the retrospective. Three months later, last quarter's conclusions are unavailable. The workflow must exist in writing. That does not mean it must be long: a text file, Notion page, Excel sheet or paper record can provide external memory, provided it is complete and retrievable.

Mistake 2: skipping EOD after a good day

A profitable day still raises the question of whether execution followed the strategy or benefited from chance despite a breach. EOD can assess compliance; one day's record cannot establish a persistent edge. Apply the same review regardless of P&L, with the five-minute minimum as the lower-bound essential procedure rather than an exemption.

Mistake 3: judging the regime by eye alone

Five minutes on a chart followed by “probably a trend” is an impression vulnerable to recency. Use the section 2 procedure: four to six pairs with recorded ATR, ADX, structure and calendar context. Qualitative structure still needs defined criteria; writing a table does not make an ambiguous judgment objective.

Mistake 4: omitting or falsifying the operator check

“I am fine” after four hours of sleep is not evidence that the admission rule passes. This article cites sleep research^[2] and literature on fast intuitive judgments^[6] as reasons to record concrete inputs. Use sleep duration, known caffeine intake where relevant, and a one-to-five condition rating with a short note. A mood score remains subjective, and milligrams are only as accurate as the available product information. None of those fields can override a hard no-entry condition.

Mistake 5: a weekly workflow without the calendar

A purely technical review discovers releases only on the morning they occur, after swing exposure or pending orders have already been left in place. Include all relevant high-impact events and selected medium-impact events in the weekly assessment, with dated times and the plan's response. Update the calendar daily because the weekly snapshot is not final.

Mistake 6: only one workflow variant

An elaborate full routine can collapse during the first week of illness or poor sleep. Write the reduced and no-entry variants in advance and keep them immediately accessible. A shorter routine changes workload, not whether a hard admission condition can be ignored.

Mistake 7: turning the retrospective into a complaint session

Thirty minutes of “terrible week,” “strange market” or unsupported claims that algorithms targeted a stop do not produce an operational repair. Use numbers, concrete deviations and one or two measurable corrections. Emotional notes may remain in the daily record; the retrospective must identify actions and evidence.

Mistake 8: treating the first workflow version as permanent

Review the workflow itself at least every six months in this example, using recorded evidence. Give every version a number and date so each day's record identifies the procedure used. This example supplies three illustrative review triggers: (a) more than 20% of trading days contain a recorded deviation in each of four consecutive weeks; investigate whether format, hours or operator state caused noncompliance; (b) a style change, such as day trading to swing, requires different preparation and EOD timing; and (c) a life change permanently shifts availability by more than ninety minutes per day, such as a new job, a child's birth or regular business travel. That may require redesigned B/C variants rather than cosmetic edits. These are review thresholds, not proven universal cutoffs or automatic strategy-change permissions.

Mistake 9: copying a YouTube routine unchanged

A “top trader's morning routine” may fail within two weeks because it fits someone else's style, job, family duties and sleep pattern. A person starting at 05:30 and ending at 17:00 needs a different schedule from someone working 12:00–22:00. Start with a template and refine its logistics during the first two weeks, recording versions where the actual operating rules change. Keep validated strategy conditions intact while adapting presentation and timing; a simpler consistently completed routine is more useful than an elaborate unused one.

Mistake 10: no boundary between trading and life

Fourteen-hour platform days, price checks during meals and overnight browsing can become exhausting. This example's three- and six-month burnout narrative is illustrative, not a measured timetable. Define when entry work ends: after the planned EOD for the day trader, after the evening review for the swing trader, and outside scheduled macro/review slots for the position trader. The example proposes airplane mode after 22:00 for swing trading, but silencing every channel is incompatible with exposure that requires urgent alerts. Disable discretionary browsing while retaining necessary broker and emergency notifications, or reduce exposure through the plan before going offline. Boundaries should protect recovery without abandoning required account monitoring.

10. Copyable templates: build a workflow in sixty minutes

Copy and adapt the following framework during a weekend. Fill each section with your actual pairs, dated local times and versioned rules. Sixty minutes is an initial setup estimate for someone who already has a journal, not the time required to validate a trading strategy.

Part 1: Sunday template, forty-five minutes, for example 21:00–21:45

SUNDAY REGIME ASSESSMENT — WEEK [date]
Plan/playbook version: ______ (number + change date)
Working timezone: ______ (Europe/Warsaw in the example)

A. PAIR METRICS — approximately 2 minutes per pair:
   EUR/USD: ATR(14) D1 ___ pips; /mean of 90 earlier completed ATR values ___×; ADX ___; trend/range ___
   GBP/USD: ATR(14) D1 ___ pips; /mean of 90 earlier completed ATR values ___×; ADX ___; trend/range ___
   USD/JPY: ATR(14) D1 ___ pips; /mean of 90 earlier completed ATR values ___×; ADX ___; trend/range ___
   AUD/USD: ATR(14) D1 ___ pips; /mean of 90 earlier completed ATR values ___×; ADX ___; trend/range ___
   Use completed observations and record the data convention.

B. MACRO CONTEXT:
   VIX: ___   DXY trend/range: ___   Global context: ____________

C. WEEKLY CALENDAR — dated times in the stated zone:
   MON __:__ ____________ (high / relevant medium impact)
   TUE __:__ ____________
   WED __:__ ____________
   THU __:__ ____________
   FRI __:__ ____________
   High-impact event count: ___
   Exclusion windows for both currencies: __________________

D. ACTIVE WEEKLY PLAYBOOK:
   [ ] Trend following — assess eligible A+ candidates
   [ ] Mean reversion
   [ ] Breakout
   [ ] Predeclared defensive variant — half size
   [ ] No eligible playbook — no new trading
   One-sentence rationale: ____________________________________

E. OPEN POSITIONS — REVIEW:
   1. ______ SL ___ TP ___ weekly event? ____ planned action ____
   2. ______ SL ___ TP ___ weekly event? ____ planned action ____
   Pending orders, expiry and required cancellations: ___________

F. WEEKLY PLAN — maximum 2 sentences: ___________________________

Part 2: daily pre-market template, approximately fifteen minutes

PRE-MARKET — [date, weekday]
Plan/playbook version: ______   Timezone: ______

1. OVERNIGHT SUMMARY:
   Live feed and account-state confirmation: _______________
   Asian range formed since Tokyo opened: __________________
   (Example Tokyo session ends 10:00 PL winter / 11:00 summer.)
   Relevant overnight moves: _______________________________

2. TODAY'S CALENDAR:
   __:__ ___________ (high / relevant medium impact)
   __:__ ___________
   No-new-entry window: ___ to ___
   Check BOTH currencies; ±2h if using the 15.6 card.

3. EACH OPEN POSITION AND PENDING ORDER:
   Position 1: __________ SL ____ TP ____
   Position 2: __________ SL ____ TP ____
   Pending order 1: ______ trigger ____ attached SL ____ TP ____
   Expiry: day / GTC / date ____
   Cancel before release? YES / NO
   Required action and broker confirmation: _________________
   Correlation before adding any exposure: value ___ window ___

4. OPERATOR CHECK:
   Sleep ___ hours; quality 1/2/3/4/5
   Known caffeine intake ___ mg; mood 1/2/3/4/5
   Illness/fatigue YES/NO; outside stress YES/NO
   OPERATOR STATE A / B / C — separate from setup class
   All hard behavioral checks pass? YES / NO / UNKNOWN
   Maximum SINGLE-TRADE risk ___%
   Example operator caps: A=1%, B=0.5%, C=0%
   Base: start-of-day equity; lower setup/portfolio cap governs.
   Five hours of sleep does NOT pass a six-hour admission minimum.
   Daily loss budget from plan: example 2%
   Used ___%; open-risk commitments ___%; available headroom ___%
   If one full planned loss cannot fit, no new entry.

5. DAILY PLAN:
   Watched pairs: __________________
   Specific candidate setups, subject to complete admission checks:
   - Example: GBP/USD breakout of the Asian range formed by 09:00,
     in the 09:00–10:30 window, SL below that defined range.
   - Example: fade a London-opening extreme on EUR/USD only under
     its own card, including M5 ATR >1.3× the declared reference mean.
   - Your versioned setup: __________________________________

Part 3: daily EOD template, fifteen minutes after the session

END OF DAY — [date]
Plan/playbook version: ______   Timezone: ______

A. EVERY TRADE:
   #1: time __:__ pair ____ long/short ____ size ____
       planned/actual entry ____ exit ____ initial R0 ____
       result ____R; setup class A+/B/C; note _________________
   #2:...

B. DAILY RESULTS:
   Entry count ___ (zero is valid)
   Rejected candidates and contemporaneous reasons: __________
   Pips by instrument ___; sum of trade R ___
   Account-currency cash ___ (PLN in this example); account % ___
   Week to date ___; month to date ___
   Floating P&L / equity / financing recorded separately: _____

C. EXECUTION QUALITY: good / mixed / poor
   Specific deviations: _____________________________________

D. POSITIONS AND PENDING ORDERS FOR TOMORROW:
   Position 1 ___ SL ___ TP ___ overnight/tomorrow event? ___
   Pending order 1 ___ trigger ___ attached SL ___ TP ___
   Expiry day / GTC / date ___
   Decision: retain under valid conditions / cancel before ___
   Broker-confirmed resulting state: ________________________

E. TOMORROW'S PLAN:
   Pairs ___; candidate setups ___; events ___

Part 4: weekly retrospective, thirty minutes on a fixed weekend day

WEEKLY RETROSPECTIVE [date range]
Plan/playbook version: ______

1. Weekly P&L: R ___; account cash ___ (example: PLN); % ___
   Four weekly observations: ___ → ___ → ___ → ___

2. Trade statistics:
   Count ___; WR ___%; average win ___R; average loss ___R
   Expectancy ___R; uncertainty / sample limitations __________
   A+ / B / C breakdown: ___ / ___ / ___

3. Specific deviations:
   - _________________
   - _________________

4. Regime review:
   Planned playbook ___; observed regime ___; assessment _____
   What was knowable then versus learned later? ______________

5. Playbook observations for quarterly review:
   _________________________________________________________
   These observations are not immediate rule changes.

6. NEXT WEEK'S EXECUTION REPAIR — maximum two:
   1. _______________________________
   2. _______________________________

These four forms are the framework. A complete workflow also needs actual broker data, execution costs, a deviation record, technical contingencies and explicit no-action conditions. If a journal already exists, an hour may suffice to configure the forms. After four weeks, compare record completion and execution behavior with your prior records; do not intentionally omit preparation to create a control group. Differences in regime, workload and sample composition mean an uncontrolled comparison cannot establish the routine's causal financial benefit.

Tools: what supports each stage?

On a fixed monthly date, export the journal history and reconcile it to the broker account report. 15.9 explains normal and abnormal differences and the reconciliation procedure. The workflow's duty is to reserve the review date and record the outcome, including unresolved discrepancies.

Limits and STOP: where the numbers come from

The workflow executes limits defined in the trading plan. This example's illustrative set is 1% per highest-class trade, 0.5% for a permitted lower class, 2% daily loss limit, 4% weekly limit, monthly −5% → half size, and −8% → stop for the rest of the month and audit. Two full 1% losses equal 2% only under the fixed opening-equity convention used here, before any excess execution loss. These are scenario assumptions, not universal limits across every strategy or recommendations for the reader. Definitions and restart conditions belong to 15.2; incident handling belongs to 15.8. EOD calculates cumulative results, checks thresholds and records the result even when none was reached.

Two distinctions matter. First, if the proposed full trade risk exceeds remaining daily headroom, that entry cannot fit the plan; reduce it only if the card explicitly permits the smaller valid size, otherwise do not enter. A daily cap smaller than an ordinary full loss is not intrinsically impossible — it means that ordinary size is ineligible. Second, a return to full size depends on predetermined process and readiness conditions, such as a documented period without deviations, not on winning back the loss. For a Polish tax example, annual history exports can support PIT-38; the Polish tax article explains that local filing context. Readers elsewhere need their jurisdiction's rules. The journal supplies records; it is not itself a tax calculation.

A practical minimum for someone working 09:00–17:00

The full example requires 45 daily preparation/review minutes, 75–90 weekend minutes and separate session availability. Employment status alone does not determine whether it fits; actual obligations do. For a person unavailable during a 09:00–17:00 job, this example proposes:

• Twenty morning minutes, 07:00–07:20: today's calendar, operator check, existing swing positions and any D1/H4 pending orders prepared earlier, with validity and event exposure rechecked.
• Ten evening minutes, 22:00–22:10: account and order state, R and cash P&L — PLN in this example — a brief learning note and tomorrow's plan.
• Sixty minutes at the weekend: a thirty-minute regime review and thirty-minute retrospective in one planned session.
• No day-trading entries during unavailable work hours. Brief phone access between duties is not equivalent to a complete, undistracted admission process.

For five working days, 30 ×5 +60 =210 minutes, or 3.5 weekly hours of workflow. Any evening trading session is additional. Two to six weekly D1/H4 trades are an illustrative workload, not a target or guarantee of fit. A separately tested 17:30–22:00 Poland-local New York-session variant can be considered only if energy and availability support its full checks.