1. Scope and schedule
- Plan name
- Demo process rehearsal — illustrative only
- Product type
- OTC forex
- Instrument and venue
- EUR/USD on a fictional demo feed. No real broker or live account is represented.
- Observation timeframe
- Record observations on a 15-minute chart. This is a documentation example, not a tested trading timeframe.
- Trading window
- Weekdays 14:00–16:00 in the named zone. Plan to end the rehearsal with no open positions or pending orders.
- Named time zone
- Europe/London
2. Entry, skip and exit rules
- Entry criteria
- Refer to your separately documented playbook, identified here by the fictional label DEMO-A, and record its version and observed condition before a rehearsal. If DEMO-A has no precise entry trigger, skip the trade. This example intentionally supplies no entry strategy.
- Skip criteria
- Skip if the setup definition is missing, the quote is stale, order status is uncertain, required event checks are incomplete or the chosen session limit has been reached.
- Exit procedure
- Use the exit procedure recorded in DEMO-A; do not improvise a wider planned loss. Record actual execution and costs. A stop order may execute at a different price; the chosen amount is a planning limit, not a guaranteed maximum loss.
- Setup invalidation
- If a required DEMO-A condition ceases to hold before entry, cancel the pending request only after checking its actual status. Record the reason; do not relabel the setup after the outcome.
3. Planned limit per trade
- Chosen per-trade amount
- 0.5
- Per-trade unit
- Percent
- Per-trade currency
- USD — the currency of the illustrative denominator
- Percentage basis
- Fictional demo equity: 10,000 USD. This is an arbitrary teaching amount.
- Basis snapshot timing
- Take the demo-equity snapshot at 14:00 Europe/London at the start of this rehearsal; keep that denominator fixed for this session.
- What this limit measures
- Planned loss per new rehearsal trade, including estimated explicit fees. 0.5% × 10,000 USD = 50 USD for this fictional snapshot. This is not a recommended risk level; gaps, execution and costs can make actual loss greater.
4. Aggregate limit and reset
- Chosen aggregate amount
- 100
- Aggregate unit
- Money
- Aggregate currency
- USD
- Aggregate percentage basis
- Not applicable: this illustrative aggregate limit is a money amount, not a percentage.
- Aggregate basis timing
- Not applicable to the money unit; measurement starts at the session boundary defined below.
- What accumulates
- Net loss for the defined demo session across all rehearsal positions. Profits offset losses in this particular definition. This differs from adding only losing trades.
- Measurement period and scope
- All positions in the fictional demo exercise, weekdays 14:00–16:00 Europe/London. Do not combine this record with a live account.
- Reset rule
- Begin a new record at 14:00 Europe/London only after reconciling prior positions, orders and costs. Do not erase an unresolved open loss or unsettled cost by starting a new session.
- P&L counted
- Count realized P&L booked during the session plus the change in open P&L since its opening snapshot, marked at the demo platform’s executable close-side quote. Exclude deposits and withdrawals from trading P&L; record them separately. The starting equity denominator remains fixed.
- Costs counted
- Include commissions and financing attributable to the session; reconcile estimates against recorded charges. Spread already reflected in execution prices/P&L is not subtracted again.
- Action at the limit
- At the chosen session limit, stop new entries and check/cancel unfilled entry orders. Handle existing positions under the recorded exit/incident procedure. Reconcile the record and review before the next rehearsal; the limit may be exceeded by execution or open-position changes.
5. Operating procedures
- News and event rules
- Before the session, check the chosen official event sources for EUR and USD. Record the event and the separately defined exclusion window in DEMO-A. If the window has not been defined, skip the affected rehearsal rather than inventing it during the event.
- Overnight and weekend rules
- This example permits no planned overnight or weekend holding. Check that positions and pending orders are resolved at the end of the rehearsal; use the incident procedure if closure cannot be confirmed.
- Technical-incident procedure
- Stop sending new requests after a connection failure or uncertain response. Inspect open orders, positions and history through the provider’s supported channel. Do not resend an order until its status is known. Record times and the incident; never share credentials in the journal.
- Session checklist
- Confirm product and demo environment. Confirm time zone, session window and relevant events. Read the current DEMO-A rules and this plan version. Reconcile positions, pending orders, costs and chosen limits. After the rehearsal, record facts and unresolved issues in the journal.
6. Version and review
- Plan version
- DEMO 1.0
- Effective date
- 2026-10-23
- Review date
- 2026-10-30
- Reasons to review or revise
- Review after the scheduled rehearsal block, an execution incident, a change to product/cost terms, or an instruction that cannot be followed. Record the evidence and reason before issuing a new version; preserve the previous version.
- Journal reference
- DEMO-JOURNAL / session identifier / plan version DEMO 1.0
- Additional notes
- All figures, rules and dates are illustrative. A filled-in plan does not establish profitability, suitability or readiness for live trading. The referenced playbook is a placeholder, not a strategy provided by this guide.