How to pass FTMO challenge

1. Start with the correct answer: pass by controlling the path, not chasing the target

The shortest useful answer to how to pass the FTMO Challenge is this: choose a strategy with a demonstrated positive expectancy, risk only a small fraction of the permitted loss on each independent idea, impose your own daily stop well inside FTMO's boundary, and wait for valid setups until the objective is reached. You cannot control whether the next trade wins. You can control position size, entry quality, total exposure, stop placement, operating hours, and the decision to stop. A plan built around controllable inputs survives randomness better than a plan built around earning a fixed amount every day.

Think of the evaluation as a corridor. The profit objective is one end, while daily and overall loss limits form the walls. A trader who tries to sprint reaches a wall quickly when normal variance appears. A trader who advances only when the setup is present gives the edge more attempts to work. This does not mean trading so cautiously that costs consume the edge. It means selecting risk after studying the strategy's losing sequences rather than selecting risk from the largest amount the firm permits. The correct pace is the fastest pace your evidence supports while maintaining a material error buffer.

For example, suppose a hypothetical account begins at 100,000 currency units and your verified strategy risks 0.35 percent per idea. Five full losses would cost about 1,750 before commissions and slippage. If the live product's daily boundary were closer than that, five simultaneous or same-day risks would plainly be unacceptable. The lesson is not that 0.35 percent is universally right. The lesson is to compare planned aggregate loss with the actual published boundary before orders exist. Repeat the calculation with poor fills and correlated trades included.

A pass also needs to be repeatable after the evaluation. If the only way to reach the objective is to use risk you would never accept on a funded account, the evaluation has trained the wrong behavior. Prefer a method that could continue at equal or lower risk after verification. The FTMO EA implementation guide covers automation in more depth, but the same principle applies manually: your execution should be rules based, documented, and boring enough to repeat.

Reject any plan whose central assumption is that you must pass this week, recover the fee immediately, or copy a recent winner. Those pressures convert normal losing variance into oversizing. A suitable plan can state what happens after a loss, after a win, after no setup, and after a technical fault. If one of those answers is simply trade larger, the plan is incomplete.

• Define the strategy in one paragraph without referring to desired profits.
• State the maximum risk for one idea and for one day.
• State what evidence justifies that risk.
• Remove any personal deadline that is not an official current rule.
• Confirm that the same process would be acceptable after passing.

2. Build a dated rule sheet for the exact FTMO product

Do not trade from memory, social media, an old review, or another trader's dashboard. Open FTMO's current official material and record the product name, account denomination, starting reference, profit objective, maximum daily loss definition, maximum overall loss definition, minimum or maximum time conditions if any, required trading days if any, supported platforms, and prohibited practices. Product variants can differ. Promotions and account options can also alter the commercial arrangement without changing every trading rule. Put the retrieval date and official URL beside each item so your notes can be audited.

The wording of a loss rule matters more than its headline percentage. Determine whether the calculation uses balance, equity, or both; whether closed and floating results are included; whether commissions and swaps count; what reference value applies; and exactly when a daily value resets. Write the formula in ordinary language. For instance: current equity minus today's permitted floor equals remaining equity room. Do not use that illustrative formula until you have matched each term to FTMO's live definition. A percentage copied without its reference and reset mechanism is not an operating rule.

Separate evaluation conditions from later account conditions. A practice permitted during a Challenge might be limited during verification or on an FTMO Account, particularly around specified instruments, news, rollover, holding periods, or other operational conditions. The reverse can also occur when products are updated. Passing one stage does not grant a permanent exemption from later terms. Create columns for Challenge, Verification, and post-evaluation conditions, then mark uncertain cells for support confirmation.

Save screenshots or PDFs of material that directly influenced your setup, but never assume a saved copy overrides the agreement. Its purpose is to document good-faith preparation and help identify changes. If a rule is ambiguous, ask support a narrow factual question that includes the product and scenario. Instead of asking whether your strategy is safe, ask whether a pending order opened at a specified time and left through a named event is permitted on that exact stage. Keep the written response with your journal.

Use the FTMO rules and EA compliance article as background, not as a substitute for official material. Any page carrying a year can age. Your rule sheet is complete only when it answers what is measured, from which reference, at what time, on which stage, using which platform records, and what conduct is restricted.

• Record the exact account and product name.
• Copy each objective and its full calculation definition.
• Record reset time in server time and UTC.
• Separate evaluation, verification, and funded-stage conditions.
• Save dated sources and written support clarifications.
• Schedule a final rule review immediately before the first trade.

3. Confirm eligibility, identity, payment, and the complete payout route

A trading plan is useless if you cannot lawfully open, verify, pay for, or receive proceeds from the account. Before purchase, check FTMO's current country and residency restrictions, age and identity requirements, sanctions controls, trader agreement, and accepted customer types. A nationality, present residence, payment-country address, and tax residence are different facts. Provide accurate information and do not use a virtual private network, borrowed address, nominee, or another person's payment instrument to appear eligible. Circumventing access controls can create verification and payout problems even if the trading result is profitable.

Match the account registration name to the documents and payment method as required. Check whether your identity document is current, whether proof of address must meet a date window, and whether a business applicant needs additional records. Transliteration differences, middle names, or recently changed addresses should be resolved before a large time-sensitive payout request. Ask support rather than guessing. Never send documents through an unofficial social account, and enable the security controls offered by the official account portal.

Evaluate the full cost in your local currency. The displayed fee may be denominated differently from your card or bank account. Your issuer, payment processor, or wallet may add foreign-exchange conversion or transaction charges. A refund policy, if offered for the selected product, may have conditions and may return an amount that converts at a different exchange rate. Treat the purchase as risk capital that may be lost. Do not borrow for a Challenge or count a possible fee return as trading profit.

Map the payout route before trading: available methods, identity checks, invoice or contractor documentation, minimum conditions, processing steps, currencies, intermediary fees, and the receiving institution's requirements. All of these can change, so confirm the live process rather than relying on a testimonial. A payout shown in account currency is not necessarily the net amount reaching a local bank. The guide to prop-firm payouts in local currency explains conversion and recordkeeping issues worth considering.

Finally, identify local obligations. Depending on jurisdiction and personal circumstances, evaluation fees, payouts, foreign exchange differences, value-added taxes, self-employment reporting, business registration, or financial-service rules may need attention. FTMO eligibility does not determine your tax treatment or authorize activity under every local law. Keep invoices, agreements, platform statements, payout confirmations, conversion records, and expenses. Consult a qualified local tax or legal professional where necessary rather than treating online trading advice as jurisdiction-specific guidance.

• Verify current residency and age eligibility.
• Use matching, authentic identity and payment information.
• Calculate fee and conversion costs in local currency.
• Confirm the current payout method available in your country.
• Create a folder for invoices, statements, and tax records.
• Resolve compliance questions before paying.

4. Prove the strategy before it touches the Challenge

A strategy is ready only when its rules and risk behavior can be described from evidence. Start with a backtest using realistic spreads, commissions, swaps, trading hours, and order mechanics. Then use unseen data or walk-forward segments to test whether the result survives outside the development period. Finally, forward test on a platform environment reasonably comparable to the evaluation. Each stage answers a different question. A backtest checks historical logic, an out-of-sample test challenges curve fitting, and a forward test exposes execution and operational faults.

Record trade count, time span, net expectancy, win rate, average win, average loss, largest loss, maximum equity drawdown, longest losing run, profit factor, exposure time, and concentration by symbol and month. No single statistic proves robustness. A high win rate can conceal rare destructive losses. A smooth balance curve can omit floating drawdown. Strong annual profit can come from one event. Examine the distribution. If removing the best five trades destroys the outcome, estimate whether the edge is dependable enough for an evaluation.

Expectancy provides a useful baseline. If 45 percent of trades win an average 1.5 risk units and 55 percent lose 1 risk unit, estimated expectancy is 0.45 times 1.5 minus 0.55 times 1, which equals 0.125 risk units per trade before unmodelled costs. At 0.3 percent account risk, the rough expectation is 0.0375 percent per trade. That is not a daily promise. Over ten trades, random ordering can still produce a loss. Use expectancy to compare methods and plan scale, not to demand that reality deliver the average on schedule.

Stress the record. Increase spread assumptions, worsen entries and exits, delay execution, remove favorable trades, and shuffle trade order. Model the largest historical losing sequence plus additional losses. If a modest deterioration changes the system from acceptable to account-threatening, reduce risk or reject it. Read the backtesting versus live trading analysis for the practical reasons simulated fills often look cleaner than deployment.

Manual traders need the same proof. Screenshot and annotate at least a meaningful sample of qualifying setups, including the trades skipped correctly. Define market, timeframe, session, setup, trigger, invalidation, initial stop, management rule, and exit. If discretion changes from one loss to the next, historical statistics do not represent the live method. A Challenge fee should buy access to an evaluation, not serve as the tuition for discovering whether your setup has rules.

• Test with realistic costs and equity drawdown.
• Reserve unseen data for validation.
• Run a comparable forward test.
• Inspect losing streaks and profit concentration.
• Stress spread, slippage, and trade order.
• Reject a method whose rules cannot be written clearly.

5. Convert FTMO loss boundaries into personal safety limits

The firm's boundary is an account failure threshold, not a recommended operating budget. Your internal limits should sit inside it by enough to absorb floating movement, transaction costs, slippage, platform delay, and human error. Begin with the current official daily and overall loss definitions. Subtract a safety reserve that remains untouched. Allocate only part of the remainder to planned trading. This layered design means a normal stop-out does not place equity against the contractual line.

Use a hypothetical illustration, not a claim about current FTMO figures. Suppose a 100,000-unit account has an officially calculated daily floor at 95,000 for the relevant day. If current equity is 98,700, the raw distance is 3,700. A trader might reserve 1,200 for open-position fluctuation, costs, and mistakes, leaving no more than 2,500 as controlled room. If a separate personal daily stop is 1,000, that smaller number governs. Every input must be replaced with the dashboard values and live definitions for your actual account.

Overall room must be checked at the same time. Imagine the applicable overall floor is 90,000 and equity is 96,400. Raw overall room is 6,400. If the plan preserves a 2,000-unit disaster reserve, usable overall room is 4,400. Yet a risk plan should not immediately spend 4,400 merely because it exists. Divide usable room across plausible losing days. If a strategy can experience eight difficult sessions, a 500-unit daily budget leaves more resilience than repeated 1,500-unit attempts.

Closed balance alone can mislead. Three open positions may show a 900 loss, while closing commissions, adverse spread, and fast-market slippage would make the realized result worse. Conversely, an unrealized gain may temporarily alter a rule calculation depending on the live definition. Build the stop process from equity and all account charges that the firm includes. An EA should read account-wide exposure, not only losses under its own magic number. A manual trader should keep the terminal's equity visible and reconcile it with the dashboard.

The prop firm daily drawdown calculator guide can help organize inputs. Still, no generic calculator knows an unpublished product change or guarantees the firm's final calculation. Your own lower stop, the platform, and the dashboard are three controls with different purposes. If they disagree, stop opening risk and investigate.

• Write the official daily and overall floors as account values.
• Reserve room for costs, floating movement, and errors.
• Set a smaller personal daily loss stop.
• Monitor account-wide equity across all orders.
• Recalculate after closed profit, loss, deposits, or rule resets.
• Stop and investigate any platform-dashboard discrepancy.

6. Calculate risk per trade from stop distance and portfolio exposure

Position size comes after stop placement. First choose the price at which the setup is invalid. Then calculate the monetary distance between entry and stop, including the instrument's point or pip value for the account denomination. Position size equals allowed monetary risk divided by loss per unit of volume. Platform contract sizes differ among foreign exchange pairs, metals, indices, energy products, and cryptocurrencies. Use the platform specification and a small test order rather than assuming a familiar pip value applies everywhere.

Consider a hypothetical EUR/USD setup with a 25-pip stop and a verified value of 10 account-currency units per pip for one standard lot. If permitted risk is 300 units, raw size is 300 divided by 250, or 1.2 lots. A conservative trader might size below that to allow for commission and negative slippage. If the stop is widened to 40 pips because volatility increased, keeping 1.2 lots would raise price risk to 480 units. Correct size at the original 300-unit budget would be 0.75 lots before the additional buffer.

Risk belongs to the trade idea, not each ticket. Splitting one setup into three entries does not create three independent budgets. If all entries fail at the same market level, their combined stop loss must fit the idea cap. The same reasoning applies across correlated markets. Long EUR/USD and long GBP/USD may both express broad US dollar weakness. A sudden dollar reversal can stop both together. Either reduce each position, impose a shared currency-factor cap, or choose the cleaner setup.

Open-risk calculations should include orders not yet filled. Two stop orders on opposite sides of a range might appear mutually exclusive, but volatile movement can fill both, especially if cancellation logic is delayed. Decide whether pending orders reserve risk and when the sibling order is cancelled. Count any position without a hard protective stop as potentially much larger than its intended loss. Mental stops and remote EA commands can fail during disconnection.

Use scenario tiers. Under normal conditions, perhaps the plan risks one base unit. Near the personal daily stop, after unusual slippage, during degraded liquidity, or while diagnosing a platform issue, allowable new risk becomes zero. Do not create a recovery tier with larger size. The prop-firm EA lot-sizing guide provides additional instrument examples, while the drawdown and lot-size calculator guide connects sizing with account limits.

• Place the technical stop before calculating size.
• Verify tick value and contract size for the exact symbol.
• Include commission and slippage allowance.
• Cap combined risk for split entries.
• Group correlated positions under one exposure ceiling.
• Count pending orders when reserving risk.

7. Choose a pace based on expectancy and drawdown, not excitement

A realistic pace begins with how often your valid setup occurs. If a method historically produces six trades per month, an evaluation cannot safely turn it into twenty by lowering standards. Estimate the number of opportunities, expectancy, and expected variance. Then compare the approximate path to any live time condition. If the current product does not impose a short deadline, use that flexibility. If a time rule does apply to your selected account, decide before purchase whether your normal strategy can meet it without distortion.

Suppose a tested method takes twelve trades per month, expects 0.18 risk units per trade after costs, and risks 0.35 percent per idea. Its arithmetic expectation is roughly 12 times 0.18 times 0.35 percent, or 0.756 percent per month. That average may be too slow for a trader's preference, but increasing risk sixfold does not improve the edge. It magnifies both return and drawdown and can make ordinary variance incompatible with the boundary. A different account or a stronger method is a better answer than pretending leverage changes quality.

Now consider a method expecting 0.3 risk units over thirty monthly trades at 0.25 percent risk. Its rough monthly expectation is 2.25 percent before live deviations. Even here, outcomes will cluster around a wide range. A month with ten losses early can happen despite positive expectancy. Evaluate probability through trade-sequence simulations or conservative historical blocks, and size for unfavorable ordering. Never divide the profit objective by calendar days and force that amount from the market.

Profit milestones can be useful if they reduce risk rather than create pressure. At the first meaningful gain, keep risk constant or trim it. Near the objective, calculate the amount still required and the amount that could be surrendered. If only a small gain remains, full baseline risk may be irrational. Reduce size so a normal losing streak cannot erase weeks of progress. Do not remove stops or close healthy trades prematurely merely to protect an exact round number.

A no-trade day is successful when conditions do not meet the plan. Minimum-day conditions, if currently applicable, must be satisfied through legitimate qualifying activity under the firm's definition, not through sham or token transactions designed to manufacture compliance. Confirm what counts as a trading day and plan normal low-risk opportunities. If the setup never appears, accept delay rather than inventing a trade.

8. Define a strategy playbook with objective permission to trade

Your playbook should state when trading is allowed and when it is forbidden. Include instruments, timeframes, active sessions, trend or range conditions, volatility limits, setup structure, trigger, initial stop, profit management, maximum holding period, and cancellation criteria. Add examples of near misses that do not qualify. The purpose is not to eliminate all judgment. It is to prevent standards from changing because the account is up, down, or close to the target.

A breakout trader might require a defined opening range, above-average but not extreme liquidity, a close beyond the range, and a retest that holds. The stop sits beyond structural invalidation, not at an arbitrary cash distance. The trader rejects a breakout occurring immediately before a restricted event, after a large unplanned gap, or when spread exceeds the tested ceiling. This creates an observable yes-or-no sequence. If one condition fails, there is no trade, even if the chart later runs in the predicted direction.

A mean-reversion trader needs different controls. The playbook may require price displacement from a reference, evidence that liquidity remains orderly, and a target before the opposite boundary. It should prohibit averaging into an unlimited adverse move. If scaling is tested and permitted, every entry, maximum aggregate size, common invalidation level, and worst-case loss must be defined before the first order. Calling an unbounded grid a flexible exit plan does not make its risk finite.

A systematic trader should produce a settings manifest: software version, strategy file checksum if available, symbols, timeframes, risk input, maximum positions, spread threshold, slippage handling, session filter, event filter, and emergency equity stop. A manual intervention policy should say exactly when intervention is authorized. Appropriate reasons include a verified software malfunction, duplicated order, breached internal stop, or rule conflict. Fear after a normal losing trade is not a malfunction.

Use a decision gate before every new idea: Is the account eligible to trade now? Is the setup valid? Is liquidity within tested conditions? Is an event or rollover restriction relevant? Is total open risk below the cap? Is the remaining daily budget enough for the buffered loss? Is the stop accepted by the platform? If any answer is no or unknown, do not enter. A checklist works only when an unknown is treated as a stop signal rather than as permission.

• Define allowed markets, sessions, and setup conditions.
• Specify entry, invalidation, management, and exit.
• Document examples that must be rejected.
• Write scaling rules and maximum aggregate exposure.
• Create an automation settings manifest where relevant.
• Require every pre-trade gate to be yes.

9. Handle UTC, server time, reset boundaries, news, and rollover

Time errors can violate a correct strategy. Maintain three clocks: UTC as the stable global reference, the trading server's displayed time, and your local time. Record the offset between server time and UTC when the account starts. Check it after daylight-saving transitions, platform maintenance, or server changes. Your local clock is convenient for daily life, but it should not drive rule-critical automation unless conversion is tested. A laptop timezone change while travelling must not shift an EA's event window unexpectedly.

Identify the official daily-loss reset precisely from current FTMO material. Convert it into UTC and server time, noting the date. Do not assume midnight means local midnight or that the offset remains constant all year. Around the reset, avoid opening fresh risk until balances, equity references, and the dashboard are reconciled. A position carried across a boundary can influence two daily calculations in ways that depend on the live rule. Model both sides rather than assuming the reset erases economic loss.

For example, suppose server time is UTC plus two hours on the date checked. A 14:30 UTC economic release appears at 16:30 server time. If an internal pause begins thirty minutes before and ends thirty minutes after, the EA window would be 16:00 through 17:00 server time. When the server later moves to UTC plus three, hard-coded 16:00 logic becomes wrong. Store event timestamps in UTC and perform a verified conversion, or update a documented offset under change control.

News policy must be checked separately for the exact stage and instrument. Determine whether restrictions concern opening, closing, pending-order activation, modification, or holding; which events and affected currencies count; and what time buffer applies. Do not infer permission from the platform accepting an order. Technical acceptance and contractual compliance are different. The news trading with a forex EA guide explains why spread, slippage, and order gaps remain risks even where a trade is permitted.

Rollover can widen spreads, reduce depth, add financing charges, and delay execution. Weekend holds introduce gap risk and potential symbol reopening differences. Compare these periods with both current rules and tested strategy behavior. If they are not essential to the edge, flatten or block entries early enough to account for illiquidity. If holding is essential and permitted, size for a discontinuous gap rather than trusting a stop to fill at its requested price.

• Record UTC, server, and local-time relationships.
• Verify the official reset for the actual account.
• Recheck offsets after seasonal clock changes.
• Map every news event from UTC into server time.
• Confirm event restrictions separately for each stage.
• Model rollover and weekend gaps beyond the stop price.

10. Set up platform, EA, VPS, and account access safely

Install only the platform version and credentials supplied or approved for the account. Confirm symbol names, suffixes, contract specifications, minimum volume, volume step, stop distance, trading sessions, and whether the strategy's instruments are offered. A strategy designed for one broker symbol may calculate size incorrectly on another if tick value or contract size differs. Test with the smallest sensible non-Challenge environment first, then inspect the platform's calculated profit and loss against your independent estimate.

If using automation, choose infrastructure for reliability rather than secrecy. A VPS near the trade server can reduce network variability, but it does not eliminate execution risk. Document provider, region, operating system, platform build, restart policy, access method, and backups. Use a unique strong password and multi-factor authentication where available. Do not give credentials to an EA seller, passing service, friend, or remote operator. Third-party account access can create security, ownership, and compliance concerns regardless of trading performance.

Ask FTMO about current VPS or access expectations if your situation is unusual, such as international travel, migration between regions, corporate networks, or several legitimate devices. Keep an access log with UTC timestamp, device, approximate location, reason, and relevant support ticket. The FTMO IP and VPS guide discusses legitimate access consistency. Never attempt to disguise shared operation or coordinate accounts in a way that conflicts with current terms.

Configure recovery deliberately. The platform should start with the correct account, charts, strategy version, and automated-trading state, but an uncontrolled auto-start can be dangerous after maintenance. Decide whether the safest recovery is to manage existing positions only, remain disabled pending inspection, or resume fully. Ensure duplicate protection recognizes positions opened before restart. A heartbeat alert should report loss of terminal connectivity, stale price feeds, rejected orders, and disabled automation.

Keep an independent emergency path. Know how to access the official platform from a secure device, close positions, cancel pending orders, and disable automation. Test alerts without placing risky orders. Do not rely on a single messaging app whose notifications may be muted. For detailed operating choices, consult the forex EA VPS guide, then verify that every recommendation fits FTMO's current terms and your account platform.

• Verify every symbol and contract specification.
• Use unique credentials and secure official access.
• Document VPS region, build, and restart behavior.
• Test duplicate-order protection after restart.
• Alert on disconnection, rejection, and stale data.
• Practice emergency closure on a non-evaluation account.

11. Use a controlled first-week launch

The first trades should verify the environment, not prove your talent. Begin below planned baseline risk, perhaps at one-half of the eventual size if your testing supports that step. The fraction is a process example, not a universal recommendation. Observe spread, commission, slippage, server timestamps, stop placement, dashboard updates, and alerts. Increase only after several correctly processed trades and a written review. If execution differs materially from testing, remain reduced or stop.

Before the first order, capture starting balance and equity, official floors, current server-to-UTC offset, software version, settings, open charts, and the day's event calendar. Confirm there are no inherited positions or pending orders. Place a harmless platform notification test. For an EA, watch the initial signal live if practical without interfering. Verify that one logical signal produces one order with the intended stop, size, identifier, and comment.

Imagine the first trade loses normally, the second is skipped because spread exceeds the ceiling, and the third wins. This is a strong operational start even if net profit is small. The loss proves the stop and size worked. The skipped trade proves the filter is active. The winner is only one sample. By contrast, a lucky oversized winner with a missing stop is a failed launch because the process exposed the account to uncontrolled loss.

Set a first-week change freeze. Do not optimize entries, switch symbols, add a second strategy, or double risk based on three outcomes. Correct only genuine implementation defects, and document the old setting, new setting, reason, time, and validation. Strategy changes should return to testing rather than being improvised on the Challenge. A version-controlled process protects you from hindsight, where every recent loss appears to demand a new parameter.

Finish each session by reconciling platform history with the dashboard. Check balance, equity, closed result, floating result, charges, open positions, pending orders, and remaining personal budgets. Export records periodically. If the day ends near a reset boundary or with an open position, write the next action before stepping away. The account should never depend on remembering an unstated intention the following morning.

• Launch below baseline size.
• Capture starting account and settings evidence.
• Verify the first complete order lifecycle.
• Treat correct filters and stops as success.
• Freeze nonessential strategy changes.
• Reconcile the platform and dashboard every session.

12. Manage winning periods and the approach to the objective

Profit creates a different failure risk: confidence expands faster than the evidence. Do not increase size simply because the account can now absorb it. A winning sequence does not change the probability distribution established by the strategy unless market conditions or the method changed. Maintain baseline risk or reduce it as the remaining objective shrinks. Protecting progress is not the same as moving a stop irrationally; it is controlling the size of future independent bets.

Use a lock-in framework. Divide accumulated profit into a protected portion and a working portion. For example, on a hypothetical account that is 6,000 units above its start, you might decide that no more than 1,500 of that gain can be exposed before pausing for review. This is an internal rule, not an FTMO requirement. If a normal losing sequence could consume more than the working portion, lower risk. Keep the official daily and overall calculations separate because internal profit protection does not replace them.

As the objective nears, calculate remaining distance after all realized costs, not from an intraday peak. If 700 units remain and normal per-trade risk is 350, two full losses would move the account away significantly. Reducing risk to 150 may allow several valid attempts while preserving progress. Conversely, taking a huge position to capture the final 700 turns a nearly complete evaluation into a binary gamble. The market does not know that your dashboard is close to a milestone.

Avoid target fixation. A valid trade may have an exit beyond the exact objective, while a premature close can damage expectancy. Yet continuing to hold excessive risk after the objective is securely met may be unnecessary. Understand when FTMO measures completion and whether positions must be closed or conditions satisfied. Follow the current dashboard instructions. Do not assume a floating gain, a brief equity touch, or a screenshot completes a stage.

Stop opening new trades once current official objectives are satisfied and all required conditions appear complete, unless FTMO's current process explicitly requires something further. Review open orders, minimum trading conditions, and verification steps. Save platform records and wait for official confirmation. Extra trading offers no prize for style and can convert completion into a breach.

13. Respond to drawdown without revenge trading or strategy drift

Drawdown is expected if the strategy takes risk. Before launch, define response levels based on account loss and process quality. A small drawdown with perfect execution may require no change. A moderate drawdown may reduce size and trigger a review. A process breach, unexplained order, or technical discrepancy requires an immediate halt even if the account is profitable. The cause matters. Treating every loss as evidence of failure leads to constant strategy switching, while ignoring operational errors invites a breach.

Suppose five consecutive trades each risked 0.3 percent and lost as planned. Ignoring small cost differences, drawdown is about 1.5 percent. If the historical record contains several five-loss runs, this sequence is uncomfortable but not surprising. Doubling to 0.6 percent to recover would expose the next five-loss run to roughly another 3 percent and alter the tested distribution precisely when discipline is weakest. Keep size unchanged or apply the prewritten reduction rule. Never let emotion invent a new risk regime.

Use a drawdown review with four questions. Were all trades valid? Were sizes and stops correct? Did execution remain within tested tolerances? Has the market regime moved outside the strategy's scope? If validity failed, fix behavior. If sizing failed, disable trading until the calculation is corrected. If execution degraded, investigate infrastructure or liquidity. If all processes passed and the sequence fits expected variance, either continue at planned size or follow the predetermined reduction threshold.

A pause should have an exit condition. Waiting until you feel confident makes emotion the restart signal. Instead, require a full reconciliation, error resolution, rule reread, and one or more clean demo executions if a technical issue occurred. For market-regime pauses, define observable return conditions such as spread normalization or volatility returning within tested bounds. Do not use the pause to shop impulsively for a new strategy that happens to have won last week.

If remaining room becomes too small for the strategy's minimum safe size, stop. Trying to rescue a severely reduced buffer often requires a risk profile that makes breach more likely. An evaluation fee already paid is a sunk cost. Preserving decision quality, records, and capital for a future properly prepared attempt may be superior to a low-quality final gamble. This is risk management, not surrender.

• Classify the issue as variance, behavior, execution, or regime.
• Never raise risk to recover losses.
• Compare the sequence with historical losing runs.
• Pause immediately for unexplained orders or calculations.
• Define objective restart conditions.
• Stop if safe minimum sizing no longer fits the buffer.

14. Monitor without sabotaging valid trades

Monitoring should detect exceptions, not provide a constant invitation to interfere. Create alerts for account equity thresholds, personal daily stop, missing stop losses, excessive spread, rejected orders, connection loss, duplicate positions, unexpected volume, and trading outside permitted hours. Then decide the response to each alert in advance. An alert without a procedure merely transfers automation anxiety to a phone.

Separate three intervention classes. Class one is immediate protection: close or reduce risk when an order lacks its required stop, total exposure exceeds the hard cap, or the personal account stop is reached. Class two is controlled diagnosis: disable new entries while preserving managed exits after a data, VPS, or settings discrepancy. Class three is observation only: a normal losing trade, ordinary pullback, or valid signal that feels uncomfortable. This classification prevents manual overrides from destroying tested expectancy.

Manual traders also need distance. If watching each tick causes early exits, use platform alerts at structural levels and review only at planned intervals. Do not move a stop farther to avoid realizing a loss. Do not cancel a target because the account is close to the objective unless that behavior is part of the tested plan. The evaluation measures disciplined risk under uncertainty, not the ability to make every trade look pleasant.

Journal decisions in UTC and server time. For each trade, record setup, planned risk, actual volume, stop, target or exit method, event context, screenshots, execution differences, and whether intervention occurred. Add maximum favorable and adverse excursion when available. Weekly review should compare actual behavior against the playbook, not merely total profit. A profitable rule violation is more dangerous than a valid loss because it rewards behavior that can later breach the account.

Use the journal to calculate leading indicators: percentage of valid setups taken, rejected trades correctly skipped, average planned versus actual risk, correlated exposure incidents, stop modifications, and technical alerts. These measures are actionable before account-level profit becomes statistically meaningful. Profit is an outcome; process adherence is the operating system that gives the outcome a chance.

15. Avoid the failure patterns that most often destroy a sound plan

Overtrading is not simply taking many trades. It is taking trades beyond the tested opportunity set, after the daily stop, outside approved hours, or without sufficient remaining risk. A high-frequency strategy can be disciplined if its frequency is tested and permitted. A swing trader taking one impulsive extra position can be overtrading. Count deviations, not just tickets. Set a hard platform or EA entry lock after the daily budget or trade cap is reached.

Correlation hiding is another common failure. Traders label positions by symbol and miss that they share a macro factor. Long several equity indices, short a safe-haven currency, and long a risk-sensitive currency pair may all lose in the same risk-off move. Create factor groups and cap them. During major events, correlations can rise toward one precisely when diversification is expected to help. Stress the portfolio as a single position.

Stop manipulation appears in several forms: widening the stop, removing it before news, replacing it with an EA running on an unstable connection, or opening an offsetting position without reducing gross risk. A hedge can change directional exposure while adding spread, financing, margin, and execution complexity. It is not automatically a loss stop. Use only methods that are tested, transparent, and permitted under current terms.

Strategy shopping after losses produces a portfolio of recent marketing claims rather than a coherent edge. Warning signs include guaranteed-pass language, hidden entry logic, enormous backtest returns with no equity curve, tiny average wins beside rare catastrophic losses, broker-specific fills, and requests for account credentials. Evaluate any tool through the FTMO EA review framework. You remain responsible for every order placed on your account.

Rule assumptions are equally dangerous. Platform acceptance does not prove contractual permission. Another trader's payout does not prove your method is compliant. A support answer about one product may not apply to another. A previous successful Challenge does not freeze terms. Recheck live rules after account changes, software updates, or long pauses.

Finally, avoid life-pressure trading. Rent, debt payments, promised returns, and public pass deadlines create incentives to force trades. Use money whose loss does not threaten essential obligations. Keep evaluation activity separate from emergency savings. If emotional intensity makes you unable to follow the stop, close exposure safely and step away. No objective is worth turning a controlled evaluation into an uncontrolled financial problem.

• Lock new entries after the daily budget is used.
• Aggregate markets by common risk factor.
• Never widen a stop to escape a valid loss.
• Reject guarantees and credential-sharing requests.
• Recheck rules after any product or setup change.
• Use only genuinely disposable evaluation capital.

16. Complete the pass, verification, and funded transition carefully

When the dashboard indicates the objective is reached, stop celebrating long enough to verify the record. Confirm required trading conditions, closed and floating positions, pending orders, balance, equity, charges, and absence of rule warnings. Cancel orders that are no longer part of the plan. Export statements and save screenshots. Follow the official completion workflow rather than relying on an email arriving immediately. Processing times and steps can vary.

If another evaluation or verification phase follows under the selected product, build a fresh rule sheet for it. Do not copy settings automatically. Confirm objectives, risk calculations, permitted practices, server, credentials, and time conditions again. Start reduced while validating the new environment. The desire to finish quickly is often strongest after an initial success, which makes this transition a high-risk moment for unnecessary sizing.

Before accepting a later agreement, read it fully. Check identity and know-your-customer requirements, payout eligibility, invoicing, profit split, loss rules, restricted trading windows, scaling conditions, inactivity terms, account access, and intellectual-property provisions that concern your strategy. Current conditions may differ from those in the Challenge. Ask written questions before placing trades if any term conflicts with the method used to pass.

Reduce risk on the funded-stage account until its execution and calculations are observed. The purpose now changes from reaching a one-time objective to preserving access while generating repeatable eligible profits. A modest first payout can validate the operational chain from platform to local receiving method. Do not immediately multiply exposure across accounts, copy trades, or introduce third-party tools without checking both compliance and aggregate risk.

Plan payouts with business discipline. Verify the request window and method, keep sufficient equity buffer under the current rules, save invoices and confirmations, and account for processing and currency conversion. Never advertise an expected payout as received income. When funds arrive, retain records for local reporting and reserve any amount advised for taxes or other obligations. Profit split headlines are less important than net, compliant, documented proceeds.

A passed Challenge is evidence that one path met the conditions once. It is not proof of permanent edge, immunity from drawdown, or guaranteed future payout. Keep testing, journaling, and reviewing the live rules. The habits that protected the evaluation should become stricter, not looser, when the commercial stakes increase.

• Confirm all completion conditions in the dashboard.
• Close or cancel unintended residual exposure.
• Export statements and preserve account records.
• Build a new rule sheet for each later stage.
• Validate funded-stage execution at reduced risk.
• Document payout, conversion, and local reporting.

17. Final FTMO Challenge execution plan and conclusion

Here is the complete decision framework. Before purchase, verify eligibility, product rules, costs, payment, identity, and payout access. Before launch, prove one strategy, calculate account floors, reserve safety buffers, configure time and event controls, secure access, and test recovery. Before every trade, require a valid setup, known stop, correct size, acceptable costs, sufficient daily room, and compliant timing. After every trade, reconcile equity and journal execution. At predefined loss or fault thresholds, stop. Near the objective, reduce exposure and wait for official completion.

A practical daily sequence is equally concise. At session start, compare platform and dashboard, update events in UTC and server time, inspect spreads, calculate remaining personal and official room, and confirm settings. During the session, take only playbook entries while aggregating correlated exposure. When the daily budget is spent, disable new risk. At session end, reconcile orders, charges, floating results, pending orders, access records, and the next reset. This routine converts broad discipline into observable actions.

The central warning is that no checklist can make trading certain. Even a robust strategy can fail an individual evaluation through ordinary variance, and an apparently weak method can pass through luck. Judge the plan by whether it limits damage, follows current rules, and can be repeated. Never respond to uncertainty by buying more attempts than you can afford or using greater leverage. A failed evaluation with complete process adherence can provide useful evidence; a lucky pass built on uncontrolled risk provides a fragile foundation.

So, how do you pass the FTMO Challenge? You pass by knowing the current contract better than your assumptions, risking less than the published maximum, trading only a validated edge, accounting for all open and correlated loss, respecting time and operational details, and refusing to chase. There is no guaranteed route. There is a high-quality process that keeps mistakes from deciding the result and gives statistical edge enough time to appear.

Treat the conclusion as a final go or no-go test. Proceed only if every hard rule has an owner and control, the strategy has relevant evidence, one normal losing sequence fits comfortably inside your internal limits, your access is legitimate, and a technical failure can be contained. If any answer is no, return to preparation. Patience before launch is cheaper than urgency after a breach.

• Every current rule is sourced, dated, and translated into a control.
• The strategy has out-of-sample and forward evidence.
• Normal adverse variance fits inside internal limits.
• UTC, server time, news, and reset controls are verified.
• Identity, payment, payout, and local obligations are understood.
• Emergency actions have been tested.
• The final decision is no-go if any critical answer is unknown.