HomeResources › Prop Firm Evaluation Mistakes

7 Prop Firm Evaluation Mistakes That Blow Accounts

Updated May 2026 · ~10 min read

Most prop firm evaluations aren't failed because traders lack a working strategy. They're failed because traders take a working strategy and deploy it in ways that violate the specific mechanical rules of the evaluation. If you've failed two or more evaluations with the same general approach, one of these seven mistakes is almost certainly the cause.

Mistake #1: Backtesting without prop firm constraints

A strategy that returns 80% annual in a standard TradingView backtest might fail an eval in its first week. Why? Because the standard backtest doesn't model trailing drawdown, session restrictions, or minimum trading day requirements. You're optimizing for a different objective than the eval requires. See our full guide on passing the Apex evaluation for a step-by-step on adding drawdown constraints to backtests before paying an eval fee.

The fix: Add prop firm parameters to every backtest:

A strategy that backtests perfectly without these constraints is not prop firm tested. It's just backtested. These are different things.

Mistake #2: Trading the full-size contract on eval

Every major futures contract has a micro version: MES (not ES), MNQ (not NQ), MCL (not CL), MGC (not GC). Trading the full-size contract on a prop firm evaluation account increases your per-tick dollar exposure by 10x compared to the micro. Understanding drawdown rules in terms of dollar-per-tick exposure is the first step toward correct contract sizing.

On an Apex 50k eval with a $2,500 trailing drawdown: one 25-point NQ stop-out costs $500 (1 MNQ) or $5,000 (1 NQ — instant fail). There's no situation where the full-size contract is justified during an evaluation phase.

Mistake #3: No daily loss kill switch

Algo strategies can chain losses. A strategy with a 55% win rate will statistically produce runs of 5-7 consecutive losers — it's not malfunction, it's normal variance. Without a daily loss limit, that sequence plays out fully and takes your trailing drawdown with it.

The fix: Build a kill switch into every strategy:

On a $2,500 Apex trail, this means a $1,000 daily cap. That's 6-7 MNQ losing trades with a standard 30-tick stop — enough to cover normal losing runs without threatening the account.

Mistake #4: Trading during news events

CPI, NFP, FOMC, PPI, jobless claims — these releases move ES and NQ 30-100 points in seconds. An algorithmic strategy has no edge during these events; it's pure noise. But more importantly for prop firm traders: a news-triggered loss can be large enough to violate your trailing drawdown in a single candle.

Scheduled high-impact news times for US futures traders:

The fix: Hard-code a news blackout. Your Pine Script strategy should have a variable that blocks entries starting 5 minutes before and 15 minutes after any scheduled high-impact release. Use an economic calendar service to define which days/times require the blackout.

Mistake #5: Using a strategy built for a different market structure

A trend-following strategy performs well in trending conditions. A mean-reversion strategy performs well in ranging conditions. Prop firm evaluations run in real-time — and real markets alternate between trending and ranging regimes unpredictably.

Traders who paste a strategy from a trending-month backtest onto an eval that starts during a ranging period will consistently underperform until the market regime matches again. By then, they've often already failed on drawdown.

The fix: Test your strategy across multiple market regimes. Include at least one strongly trending period (2020-2021, 2022 bear, 2023 recovery), one choppy period (mid-2015, mid-2019), and a period of macro volatility (2022 rate hike cycle). If the strategy only passes in one type of market, it's not ready for eval.

Mistake #6: Ignoring slippage in the backtest

TradingView backtests default to zero slippage — fills execute at exactly the signal price. In live trading on futures, you will experience slippage. On MES and MNQ, this is typically 1-2 ticks per trade. On CL or GC, it can be 2-5 ticks on fast-moving bars.

For a strategy with 100 trades per month, 2 ticks of slippage on MNQ is $1.00 per trade = $100/month slippage cost. This sounds small but it's not: on a strategy with a $200/trade average profit, you're losing 50% of edge to slippage. Many strategies that look great in backtests are marginally profitable in live trading once slippage is accounted for.

The fix: In TradingView's strategy settings, set slippage to at least 2-3 ticks per trade. Re-evaluate your backtest results with this realistic fill assumption before running on any evaluation account.

Mistake #7: Scaling up contract count before proving the strategy live

The most common reason traders fail funded accounts (not just evals) is scaling up contract count before the strategy has demonstrated live edge. A backtest proves hypothetical edge. 10-20 live trades proves real-world edge. 50+ live trades starts to give statistical significance.

The temptation is to run 5 or 10 MNQ contracts immediately after getting funded — the math says you can afford it with the account size. But you haven't accounted for the fact that live performance always differs from backtest performance in ways you can't fully predict in advance.

The fix: Start funded accounts at the minimum contract count that makes the strategy meaningful. Scale up by 1-2 contracts every 10 profitable live trades. This gives the strategy time to prove its live edge before you're risking full position size on it.

Strategies with daily kill switches, news filters, and slippage-tested sizing.

Built around prop firm drawdown rules. Skip the mistakes — get funded faster.

View Plans