Performance evidence needs context
A trading result is meaningful only when its period, account type, broker conditions, costs, deposits, withdrawals, leverage, settings, and demo-or-live status are clear. A balance screenshot or selected list of winning trades does not provide that context.
Look for a complete, dated record that includes losing periods and changes to the system. If material details are missing, treat the result as unverified rather than estimating what happened.
Review drawdown and losing periods
Drawdown describes a decline from a previous account peak. Review both its size and duration, including how much exposure was active and whether the account recovered without deposits, setting changes, or increased risk.
A system can have many winning trades and still create an unacceptable loss if its losing trades, open exposure, or recovery behaviour are large.
- Maximum balance and equity drawdown
- Longest losing sequence and recovery period
- Largest individual loss and combined open exposure
- Results after spreads, commission, swaps, and other relevant costs
Separate demo results from live results
Demo results can help verify installation and rule behaviour, but they may not reproduce live liquidity, slippage, latency, rejection, or account restrictions. Evidence should label the environment clearly.
Do not accept a demo label as proof of future live returns, and do not accept an unlabeled result as live.
Check broker and setting dependence
Ask which market symbol, price feed, account type, leverage, trading hours, spread assumptions, and risk settings were used. Different conditions may alter entries, exits, position size, and order handling.
Compatibility should be confirmed for the current version rather than inferred from an old video, third-party message, or another user’s setup.
Inspect the operating and failure states
A credible evaluation includes what happens when connectivity drops, prices stop updating, an order is rejected, spreads widen, the software is updated, or the trading environment restarts.
The ability to pause, remove, monitor, and recover the system is part of the risk assessment, not a secondary technical detail.
Watch for common red flags
Guaranteed returns, fixed monthly-income claims, urgency, secret recovery methods, unexplained screenshots, hidden terms, and requests for credentials are warning signs.
- Only profitable periods are shown.
- The account, date range, or demo/live status is hidden.
- Risk is described only with a win rate.
- Access terms or recurring costs are not explained before installation.
- You are asked for a password, one-time code, deposit, or remote access.
Make a documented decision
Write down what has been verified, what remains unknown, and what would make you stop testing. Use a demo environment and exposure limits that do not depend on recovering a previous loss.
If the evidence cannot be explained clearly, do not treat complexity as proof of quality.