forex-scalping.com

Documentation habit for when execution goes wrong -- before you need it.

I do not enjoy disputes. I do enjoy having a folder ready so I am not reconstructing a bad fill from memory three weeks later.

Minimum pack I keep

• Screenshot of order ticket / reject dialogue with platform time
• Journal row: symbol, side, size, order type, intended price, fill, spread at click
• Account statement export for that day
• Short note: what I did next (resubmit, cancel, flat elsewhere)

Filename pattern with date and symbol. One folder per month. If I ever switch accounts, the same pack shows whether the problem was my timing, the session, or a pattern worth raising calmly with support.

This is not about picking fights. It is about not arguing anecdotes. Most "broker issues" in my history were me clicking into thin tape -- and the folder made that obvious.

What do you archive on a messy fill day so Sunday-you is not guessing?

Execution folder before you need a dispute

I do not enjoy broker disputes. I do enjoy having a pack ready so I am not reconstructing a bad fill from memory. Minimum from this desk: ticket/reject screenshot with platform time, journal row (symbol, side, size, intended vs filled), and periodic deal-history exports.

Rule: after any weird fill or reject cluster, capture immediately — not after the session when the UI has moved on. That habit also informs account-switch decisions with evidence instead of anger.

Prop platforms deserve the same logging; eligibility arguments go better with timestamps.

I store the pack outside the trading VPS as well. When the machine is the problem, evidence trapped on the machine is not evidence you can use.

Monthly I verify I can actually open the archive quickly. A folder you cannot find during a dispute is decorative.

What is the one field you still forget to capture in the moment — server time, or the partial-fill residual?