Weekend preparation is a chance to check scheduled events, chart scenarios and the previous week’s journal before the next sessions begin. Set aside a workable block of time and record what you will review again during the week. Preparation can reduce avoidable surprises, but it cannot remove unscheduled news or guarantee calm decisions.

What weekend preparation actually covers

Begin with the account: open positions, pending orders, available equity and any execution problem. Record exposure held overnight or over a weekend and times when you can actually operate the strategy. Then review the journal, scheduled releases and the relevant charts. Separate net outcomes from rule adherence: a planned loss is not automatically an error and profit after breaching a limit does not validate the process. Resolve an outage or uncontrolled exposure before another session rather than waiting for the weekly review.

Define conditions to monitor, action when they occur and reasons to cancel or wait. No entry can be a correct result. A reminder or alert is not an order; check which exit rules are broker-held and which require a running local programme. For further tools see the trader’s workshop.

The macro calendar — what really deserves a mark

Open the calendar in weekly view and filter for the currencies relevant to your positions and scenarios. A high-impact label is a vendor classification, not a guarantee of a price move. Tools: economic calendar tools; method: how to use the economic calendar. Select the events you will monitor, then confirm their official schedule and time zone.

Check the published schedules for US employment and inflation, euro-area inflation and central-bank decisions. The US Employment Situation is often released on a Friday, but the official calendar includes exceptions; do not infer the date from a first-Friday rule. Consult the relevant central bank for scheduled speeches and meetings. Their market effects can vary in size and direction, so no fixed fifty-to-one-hundred-pip response should be assumed.

For each selected event, record its data period, release stage, date, stated time zone, converted local time, forecast source and previous value. Decision, statement and conference can have separate times. Recheck the schedule and daylight-saving relationship for that date. Also inspect the actual broker instrument’s holidays, shortened sessions, breaks and financing terms; one country’s holiday does not close every market. Retain original server time rather than copying a fixed conversion from a previous week.

Daily and weekly chart work on the majors

As an example, review EUR/USD, GBP/USD, USD/JPY, AUD/USD and USD/CAD, plus gold quoted as XAU/USD. Gold is not a currency pair. Start with the weekly chart, then inspect the daily chart and mark a manageable set of reference levels. The time needed depends on your process; a level is a reference for a scenario, not a guaranteed future reaction.

Own hypothetical Monday example: EUR/USD has risen from 1.0680 over three months; Friday closes just below 1.1020 and the daily range has been 1.0950–1.1020 for two weeks. Those assigned observations do not predict the next move. A plan may investigate a break of 1.1020 or a pullback to 1.0950, but “confirmed” and “demand reaction” require explicit price, timing and cancellation rules. Neither a third scenario nor rejecting every scenario is automatically wrong; the method determines which conditions qualify.

Two or three setups to watch

Select a manageable number of setups to monitor. For each, record the instrument, direction, entry condition, invalidation level and target assumption. Two or three is a possible checklist size, not evidence that a longer list necessarily causes overtrading. Leave room to reject all candidates if their conditions do not occur.

Record entry, stop, target and an explicit risk budget. Recalculate with current equity, stop distance, pip value, account currency, costs and available margin before entry. Ordinary stops do not guarantee their fill price. Own simplified USD model: equity $10,000, assigned budget 0.5% = $50, EUR/USD pip value $10 per standard lot, with costs and slippage excluded. A twenty-five-pip stop gives 50 / (25 × 10) = 0.20 lot. Moving the stop to forty pips while retaining 0.20 lot plans $80 of price loss. Recalculation gives 0.125 lot; with a 0.01-lot step, rounding down to 0.12 lot plans $48. Costs included in the same budget reduce the amount available for price movement. Do not round up solely to meet a broker’s minimum.

The percentage is an example policy, not a universal rule or realised-loss ceiling. Check total account exposure: several dollar-related positions may respond to the same news, and different symbols are not automatically independent. Summing planned stop losses does not capture every gap or dependence.

Calendar week and five sessions are different counters

In this hypothetical example, closed net results are: Wednesday PLN 0, Thursday PLN 0, Friday − PLN 30, Monday − PLN 30 and Tuesday − PLN 30. Two example rules compare total losses with a PLN 60 threshold using different windows. A counts the current week from Monday; B counts the last five completed sessions.

Calendar window and the last five sessionsFive completed sessions have losses of zero, zero, thirty, thirty and thirty zloty. The current week includes Monday and Tuesday, giving sixty zloty. The last five sessions also include Friday and give ninety zloty. Only the second window is above the example threshold of sixty.Closed net results [PLN]Wed.Thu.Fri.Mon.Tue.00−30−30−30Five sessions: 30 + 30 + 30 = 90 PLNCurrent week: 30 + 30 = 60 PLNRule A: 60 ≤ 60 — at the thresholdRule B: 90 > 60 — above the threshold
Negative bars share one scale. The upper bracket covers five sessions; the lower bracket covers Monday and Tuesday.

Before resetting the counter, record its start, end and condition for exceeding the limit. Here the end is Tuesday’s close; only rule A excludes the previous Friday. The label “weekly limit” alone does not identify your rule. Do not change the window after seeing losses to obtain a more comfortable result.

Assumptions: Fictional completed sessions on one schedule. PLN 60 is an example parameter. Both rules add the positive loss amounts from closed net results; there are no gains or open positions here. Exceeding means strictly more than PLN 60. These are two explicitly different windows, not a recommended risk policy or a claim about protective-order effectiveness.

An honest journal review of the previous week

Review a clearly defined journal period. Compare the pre-decision plan, actual action and evidence of execution, separating observations from possible explanations. Several trades after a loss do not establish loss chasing without their signals, timing and rules. Likewise, one weak afternoon sample does not establish that the session should be removed. Keep method changes as hypotheses for separate assessment. Templates: how to keep a trading journal and trader journal template.

If the journal shows three trades in thirty minutes after a large loss, review their reasons and whether they followed the plan. A temporary two-trades-per-day cap is one possible process rule to test, not a diagnosis or a proven cure. Compare morning and afternoon records using a defined sample before removing a session solely because its recent results were weaker.

Update the plan without rewriting the past

Decide beforehand how a release affects new entries, existing positions and pending orders. No universal fifteen-minute or one-hour buffer is established. Widening a stop without resizing increases planned price loss; tightening it changes the exit rule and does not guarantee a price. Own scheduling example: a rule blocks new entries from fifteen minutes before until fifteen minutes after each of two fictional events at 14:30 and 14:45 in one time zone, including endpoints. Its windows are 14:15–14:45 and 14:30–15:00. Each is thirty minutes, but they overlap for fifteen: the union is forty-five minutes, not sixty, with no free gap between events. Merge overlapping intervals and state separately what happens to already accepted orders and positions. This is arithmetic for an assigned rule, not an optimal news-trading buffer.

Recheck schedules and positions before each session. Record the time and reason for a change, retaining the previous version so later review can reconstruct what was actually known. New information can justify an update; a profitable outcome does not justify replacing the old rationale afterwards. Adapt preparation time to the method and responsibilities. If a necessary risk check or fault cannot be resolved, waiting or reducing activity may be part of the plan. See trader morning routine for a related daily checklist.

A preparation checklist to adapt

  1. Open your chosen economic calendar in weekly view, filter for high-impact releases on the currencies you currently trade, and write down two or three of the most significant events in a notebook with date, local time, the market consensus forecast, and the previous value.
  2. Review the instruments you actually trade, including any gold exposure separately from currency pairs. Begin with the weekly chart, then mark a manageable set of daily reference levels for scenarios.
  3. Select a manageable set of scenarios and record instrument, direction, entry condition, stop assumption, target and chosen risk budget. Calculate a preliminary size and verify it again against current equity, prices and exposure before placing an order.
  4. Define the journal window, then compare planned conditions with recorded decisions, fills and costs. Record a possible process problem without diagnosing it from a short result streak or automatically imposing a two-trades-per-day cap. Fix material execution or exposure faults before continuing.
  5. Create calendar reminders, for example twenty minutes before selected scheduled events, and platform price alerts for your setup levels. Test notifications and recheck the official schedule during the week; the reminder does not freeze the plan for five days.