A platform can look great and still get in your way

Begin with the trade ticket, not the chart

Charts sell platforms. Trade tickets reveal whether you can use them safely. Check how the platform expresses size—lots, units, contracts, shares, or notional value—and make sure the unit is obvious every time you place an order. Look for a clear estimate of margin, commission, and potential loss at the chosen stop.

Test market, limit, stop, stop-loss, and take-profit orders. Change a pending order, cancel it, close part of a position, and reverse or hedge only if those actions are part of your intended workflow. Make a deliberate input mistake on demo: enter a size that is too large, a stop that is too close, or an invalid price. The error message should tell you what is wrong without leaving you to guess.

Use demo to learn the workflow

Demo is the right place to learn where settings live, how templates behave, and how quickly you can recover from a mistake. It can expose an awkward mobile ticket, missing order types, confusing contract sizes, or a statement that lacks useful detail. Repeat the same routine until placing, changing, and closing an order feels deliberate rather than improvised.

What demo cannot prove is equally important. It may use simulated liquidity, different fill logic, or simplified funding and verification. It cannot show how a real withdrawal moves, how support handles a live-account dispute, or whether slippage on your small live orders matches the experience you were shown.

Then run a small live test

Test	What to record	What you are learning
Normal market order	Bid and ask, requested price, filled price, size, commission, order ID, and confirmation time.	Your baseline execution and how each cost appears in the platform and statement.
Limit or stop order	Trigger level, fill, partial fill, gap behaviour, and any cancellation or expiry rule.	How pending orders are activated and documented.
Edit and partial close	New stop or target, minimum distance, size remaining, validation messages, and confirmation.	Whether risk controls remain clear when a position is already open.
Disconnect and reconnect	Price recovery, order status, open positions, alerts, and whether the session resumes cleanly.	What happens when your connection or device fails.
Fast market observation	Spread, responsiveness, rejected instructions, slippage, and platform messages.	How conditions change when liquidity is thinner or price is moving quickly.
Statement export	Prices, timestamps, time zone, fees, financing, deposits, withdrawals, balance, and account currency.	Whether the records are complete enough for review, tax preparation, and a support dispute.
Support question	Channel used, response time, answer, ticket number, and whether the answer matches the written policy.	How easy it is to move from a problem to a documented resolution.

Slippage is a data question, not a feeling

Slippage is the difference between the price requested and the price received. It can occur when the market moves before an order is filled, especially during fast conditions or around gaps. Record it rather than relying on memory. Note the direction, size, instrument, order type, timestamp, spread, and market conditions.

Positive and negative slippage are both possible. One poor fill does not establish a pattern, and a market order does not promise a fixed price. Repeated adverse outcomes, unexplained rejections, or fills that do not line up with the broker's own price history deserve a written question and a review of the execution policy. Compare like with like: the same instrument, order type, size, and time of day.

The boring operational details matter most

• Confirm the platform time zone, daily rollover time, weekend schedule, and how financing entries appear.
• Check minimum and maximum order size, size increments, stop-distance rules, and whether those limits change by instrument.
• Learn whether stop-loss and take-profit orders remain attached after a disconnect, restart, or device switch.
• Review contract specifications for tick size, contract value, trading hours, margin, expiration, and any instrument-specific adjustment.
• Test alerts on every device you intend to use. A notification that arrives late or only on desktop is not a reliable emergency tool.
• Find the maintenance calendar and confirm how planned and unplanned outages are communicated.
• Know whether a web platform, dealing desk, or official support channel can help when your primary app is unavailable.

Test the failure modes before you need them

Do this on demo or with no open live risk. Disconnect the internet, close the app, switch devices, and sign back in. Confirm that pending orders and stops still appear correctly. Walk through password recovery and make sure the recovery email or phone number is current. Save the broker's official support details somewhere outside the trading platform.

Think about the less dramatic failures too: a dead phone battery, a lost device, an expired card, a changed number, or an authenticator that was not backed up. A platform is part of an operating system around your trading. The system should still work when one piece is unavailable.

Automation and copy tools need their own checklist

An expert adviser, bot, API connection, copy service, or VPS adds another layer between your decision and the order. Check exactly what the tool can do, how position size is set, whether it can open multiple trades, and what happens when the connection drops. Set a hard maximum size and loss outside the strategy where possible.

Review logs after every update. Remove old API keys and connected apps, keep permissions as narrow as the platform allows, and know how to stop the system without searching through menus. “Automated” should never mean “unmonitored.”

Keep a one-page execution log

You do not need sophisticated analytics to spot a recurring problem. For each test trade, record the instrument, size, order type, requested price, fill, spread, commission, slippage, financing, device, connection quality, and any support ticket. Review the log after a reasonable sample rather than judging the account from the best or worst trade.