Updated 2026 prop firm news trading guide covering evaluation vs funded rules, CFD vs futures, pending orders, server time, event risk, prohibited strategies and compliant setups.
Akash Mane is the Founder and CEO of Prop Firm Bridge, where he leads the company’s vision, platform growth, and long term strategic direction. He oversees operations across research, marketing, content systems, SEO, and product positioning while driving the platform’s mission of becoming a trusted authority in the prop firm industry. At Prop Firm Bridge, Akash plays a direct role in shaping educational frameworks, comparison systems, and trader focused resources designed to help users make informed decisions with transparency and confidence. His work focuses on building scalable organic growth systems, improving platform authority, and strengthening trust through accurate, structured, and search optimized content. In addition to leadership responsibilities, he actively manages growth strategy, social media marketing, search visibility, and brand development to expand the platform’s reach across global trading audiences.
Manoj Gholap is responsible for content accuracy, compliance, and factual integrity at Prop Firm Bridge. He acts as the final verification layer for all published content, ensuring that prop firm reviews, rules, and comparisons are clear, accurate, and aligned with transparency standards. Manoj plays a key role in maintaining trust and credibility across the platform.
News trading in prop firms has become harder to summarize with one sentence. “News trading is allowed” can be true during an evaluation and incomplete after funding. “News trading is restricted” can apply only to one account type, one product or one short window around selected events. A futures program can use a completely different policy from the same brand's CFD program. A firm can allow news but prohibit bracketing, latency exploitation or concentrated event-only behavior.
That is why a serious 2026 prop firm trader needs an action-level rulebook rather than a yes/no list. The important questions are: Can you open? Can you close? Can you hold? Can a pending order trigger? Can a stop loss or take profit execute? Which instruments are targeted? Which events count? Which clock governs the restriction? Does the rule change after you pass? Does the futures product follow the same logic as the CFD product?
Current official rules show how different these answers can be. FTMO's current CFD FAQ says its Evaluation Process does not apply the selected-news restriction, while Standard FTMO Accounts do restrict opening or closing targeted instruments from two minutes before until two minutes after selected releases; Swing accounts are exempt. FTMO Futures currently says news trading is allowed in any phase, subject to its Forbidden Trading Practices. The5ers' current news FAQ says Hyper-Growth and Bootcamp allow news except bracket strategies, while High Stakes permits holding through high-impact news but limits new order execution in a defined server-time window. These examples are not an all-industry table. They are proof that product, stage and action matter.
Author credibility: This guide is written by Akash Mane, Founder and CEO of Prop Firm Bridge. It combines current 2026 official rule research, event calendars, server-time mechanics, execution risk, drawdown mathematics and practical evaluation workflows. Manoj Gholap is the fact checker.
Table of Contents
Quick answer: There is no universal prop firm news-trading rule in 2026. Verify the exact product, account type and stage. Convert every selected event to the governing server time. Treat opening, closing, holding and pending-order activation as separate actions. Even when trading is allowed, cap event risk for spread, slippage and correlation. When direct release execution does not fit the account, use post-news technical structure instead.
A broad label hides the details that decide compliance. A program can allow traders to hold positions but restrict new entries. Another can permit all news activity during evaluation but use a funded-stage restriction. A futures product can allow release-time trading while its CFD product uses a targeted instrument rule.
When traders copy a one-line summary from a review, forum or social post, they often miss the action that matters. The trade itself can be technically sound and still be incompatible with the current account.
Build rules from the source at the account level, not from the brand level alone.
Use product + account type + stage + action + event + instrument + time. For example: “CFD Standard funded account, FOMC, targeted USD pair, new entry, current server time.” That is specific enough to answer.
“Does Firm X allow news?” is usually too broad.
Store the answer with a last-verified date because terms and infrastructure can change.
A strict rule can be easy to follow when the event list, action and time window are explicit. A flexible rule can still be dangerous if the trader cannot tell whether a pending order, stop or stage is covered.
Clarity reduces operational risk. If a strategy depends on time-sensitive execution, documentation quality is part of account fit.
Ambiguity should lower risk rather than encourage a loophole search.
Prop Firm Bridge research note: The correct 2026 question is not “Is news allowed?” but “What exactly is permitted on this account, at this stage, for this action?”
Book insight: Atul Gawande's checklist philosophy fits because complex rules become safer when converted into small, explicit decisions.
FTMO's current CFD FAQ provides a clear example. It states that the selected-news restriction does not apply during its Evaluation Process for Standard or Swing account types, provided forbidden practices are avoided. Once a trader reaches an FTMO Account, Standard accounts must follow selected-news restrictions, while Swing accounts remain exempt.
This means a strategy can be fully usable in the evaluation and require adaptation after funding.
The lesson is broader than one firm: every stage transition deserves a fresh rule audit.
Passing creates confidence and familiarity. The trader assumes the funded environment is simply the evaluation with payouts. That assumption can be wrong. News rules, consistency conditions, holding rules or payout mechanics can change.
Before the first funded trade, re-read the current news policy and risk formula. Do not rely on what worked during Phase 1 or Phase 2.
Success should trigger verification, not complacency.
Move entries outside the restricted window, use post-news consolidation or next-session setups, or choose a product/account type designed for the holding style. Preserve the technical logic where possible.
If the edge disappears when the restricted minutes are removed, the account may be structurally incompatible with the strategy.
Do not change the rule through interpretation; change the execution model through testing.
Prop Firm Bridge research note: Evaluation success does not prove funded-stage rule compatibility.
Book insight: Morgan Housel's preservation principle applies because access to a valuable account should usually reduce unnecessary operational variance.
Holding means an eligible position already exists before the event. Opening creates new exposure. A current rule can permit one and restrict the other. The5ers' current High Stakes material, for example, allows holding through high-impact news while restricting new order execution within a defined two-minute window around relevant events.
A trader who sees “holding allowed” should not interpret that as “adding allowed.”
Write a separate rule for every action.
A pending order can trigger while the trader believes the account is inactive. Current FTMO Standard funded-account rules explicitly include pending-order execution inside the selected-news restriction. Current The5ers High Stakes guidance likewise focuses on when an entry order actually executes, not merely when it was placed.
Before every major event, review buy stops, sell stops, limits and automated entry instructions.
Flat open positions do not equal zero future exposure.
Rules can distinguish protective exit behavior. Current FTMO guidance says that on targeted Standard FTMO Account instruments, stop-loss or take-profit execution inside the selected two-minute window counts as closing activity and can breach the agreement. Other programs may treat exits differently.
Do not generalize that rule to every firm. Record the exact current treatment for the account.
Never remove protection merely to avoid a rule unless the strategy and terms clearly support another risk method.
Prop Firm Bridge research note: The most preventable news mistakes usually come from actions traders forgot to classify.
Book insight: Checklist thinking is especially valuable for pending orders because memory degrades when attention shifts to the event.
CFD prop programs and futures prop programs can use different platforms, exchanges, session structures and risk frameworks. The same brand can therefore publish different news rules for each product.
Current FTMO Futures guidance says news trading is allowed during any phase without special news restrictions, provided the trader avoids Forbidden Trading Practices. That differs materially from the selected-news restriction on Standard funded CFD accounts.
Product identity matters before brand identity.
News permission does not mean every event-focused behavior is acceptable. FTMO Futures' current prohibited-practice material includes a concept called News-Event Concentration, targeting patterns of trading concentrated around scheduled economic events in a way inconsistent with broader sustainable trading activity.
The important lesson is not to infer a universal ban from that example. The lesson is that “news allowed” can coexist with rules about how a strategy behaves.
Read the product's prohibited-strategy section separately.
The5ers' current material says Instant Funding/Hyper-Growth and Bootcamp allow news trading except for bracket strategies. Its High Stakes guidance allows holding through high-impact news but limits new order execution around the event. The5ers Futures currently states that news trading is allowed as long as risk and account rules are followed.
This is a strong demonstration of why a brand-level one-word label is not enough.
Always identify the exact program first.
Prop Firm Bridge research note: 2026 news due diligence must be product-specific: CFD, futures and program structure can produce different rules under one brand.
Book insight: Howard Marks' contextual thinking applies because identical labels can hide materially different risk structures.
The event can be published in Eastern, London or another local timezone while the prop rule uses platform server time. If the trader compares the event to a phone clock instead of the governing server, the window can be shifted.
Daylight saving makes this worse because offsets can change during the year.
Use UTC as the conversion bridge and verify the live platform offset for the exact date.
Account, product, platform, observed UTC offset, date verified, daily reset, news-rule source and any seasonal offset change. Add the formal event window and personal buffer.
Do not write only “server 15:30.” Write “15:30 server, UTC+3, verified September 2026,” or the appropriate current value.
This makes the record auditable after daylight-saving changes.
A small additional buffer can protect against clock mismatch, slow order cancellation and last-second execution. It also reduces the temptation to enter at the first legal second while spreads remain abnormal.
Keep personal rules clearly labelled so they are not later misreported as the firm's rule.
Compliance is the minimum boundary; strategy can be more conservative.
Prop Firm Bridge research note: Time conversion is an operational control, not a minor calendar detail.
Book insight: James Clear's systems thinking is useful because server-time verification should be automatic routine rather than memory.
Both are scheduled U.S. releases, but they contain different information and can produce different spread, slippage and price paths. Employment Situation includes payrolls, unemployment, wage data and revisions. CPI includes headline and core inflation components.
A strategy profitable after CPI does not automatically have edge after NFP.
Tag event type separately in the journal.
FOMC can include a statement, projections at selected meetings and a press conference. ECB decisions can be followed by a press conference and additional projections. The first market direction can reverse as the information sequence develops.
Map every scheduled stage before calling the market “post-news.”
Use wider personal event zones when the strategy does not want intermediate exposure.
OPEC-related production decisions can emerge from a meeting window rather than one universally fixed release second. Geopolitical headlines can be unscheduled altogether. A prop firm's named-event list may or may not treat these the same as CPI or FOMC.
Market-risk controls still apply even when a compliance rule does not explicitly name the event.
Use a wider elevated-risk state when exact headline timing is uncertain.
Prop Firm Bridge research note: Event classification has two layers: what the account restricts and what the market makes risky.
Book insight: Taleb's uncertainty framework is useful because scheduled time does not eliminate outcome or execution uncertainty.
Permission answers compliance. It does not guarantee normal spreads, stop fills or liquidity. A firm can allow news while a trader's own data shows direct-release execution has negative expectancy after costs.
Use a personal market-readiness filter even on unrestricted accounts.
The trader can voluntarily wait for post-news structure.
Calculate the structural stop, then add a severe but realistic event fill based on historical live samples. Position size should remain comfortably inside daily and maximum drawdown under that stress case.
Do not size exactly to the formal limit.
If one ordinary event fill can breach the account, leverage is too high.
Dollar pairs, gold, indices and rates can move together around Fed or U.S. inflation data. Euro assets can correlate around ECB policy. Oil and energy-sensitive instruments can correlate around OPEC developments.
Several individually small trades can become one large macro exposure.
Use one event cash-risk cap across the correlated cluster.
Prop Firm Bridge research note: Compliance risk can be zero while market risk remains high.
Book insight: Morgan Housel's room-for-error principle applies because realized loss can exceed the ideal stop during fast markets.
Bracketing commonly means placing opposing pending orders around price before a release so whichever direction moves first creates an entry. Current The5ers material explicitly disallows bracket strategies in programs that otherwise allow news trading.
The strategy can depend more on event-speed mechanics than on ordinary market structure.
Never interpret “news allowed” as “all pending-order methods allowed.”
Latency strategies attempt to profit from temporary delay between a reference market and the account's price. The edge depends on infrastructure mismatch rather than sustainable price risk.
Many prop environments prohibit arbitrage or exploitation of price discrepancies and glitches.
A robust strategy should survive realistic synchronized pricing.
A futures program can permit news while still expecting a broader sustainable trading pattern. FTMO Futures' current material explicitly warns against concentrating trading around scheduled economic events in a pattern inconsistent with broader activity.
The key idea is strategy sustainability. A trader should not assume one giant event bet demonstrates the same risk profile as a repeatable approach.
Read the exact forbidden-practice language for the product.
Prop Firm Bridge research note: News permission and prohibited-strategy rules must always be read together.
Book insight: The professional risk lesson is that an edge dependent on a temporary infrastructure condition is different from repeatable market skill.
A $100,000 evaluation can have only a small fraction of that balance available as maximum loss. After drawdown, the remaining room is smaller. Risking 1% of nominal balance can therefore consume a large percentage of actual survival capital.
Use the tighter of remaining daily and maximum room as the reference.
Firm limits are breach lines, not recommended trading budgets.
It is the maximum severe cash loss allowed across all attempts and correlated positions associated with one event. If the first trade loses most of the cap, later setups receive less risk or are unavailable.
Switching from fade to continuation does not reset the cap.
This prevents event-day overtrading from bypassing the daily plan.
Use target-zone and drawdown-zone multipliers. Near completion, optional high-variance event exposure can shrink because the downside creates more recovery work than the upside adds evaluation value. Near the maximum floor, risk should shrink because the account has fewer samples left.
The technical setup can remain unchanged while size changes.
Account state is part of position sizing.
Prop Firm Bridge research note: Event risk should be expressed as a percentage of remaining account life, not only nominal balance.
Book insight: Van K. Tharp's position-sizing framework is central because exposure determines whether normal variance can survive the account rules.
Waiting can improve stop definition and execution. The event impulse can create a new range, trend or failed breakout that becomes tradeable once spreads normalize.
The trader gives up the first part of the move in exchange for more information.
This can be attractive on both restricted and unrestricted accounts.
Breakout and retest of a stable post-news range, failed breakout and return into value, volatility compression, trend pullback and next-session continuation. Tag each separately.
Do not call every late event trade “post-news” and combine them into one statistic.
The setup needs a clear invalidation and target.
A U.S. release can create levels Asia or London trades later. An ECB event can shape New York price action. The trader uses information indirectly without competing in the fastest execution window.
Check the new session's calendar before entry.
News can be context without being the execution trigger.
Prop Firm Bridge research note: The information does not expire when the restriction ends; it can create technical structure for later sessions.
Book insight: Mark Douglas' acceptance of missed opportunities supports waiting for a cleaner setup instead of chasing the release.
Exact product, stage structure, news actions, holding rules, pending-order treatment, platform, server-time logic, daily reset, drawdown method, prohibited strategies and funded-stage changes. Compare these fields with the strategy's normal behavior.
If direct news execution is a core edge, rule compatibility is a primary purchase criterion.
Do not choose only on price, discount or nominal balance.
Start with the firm's current official FAQ, help center, terms and dashboard information. Use third-party reviews as navigation and explanation, not as a substitute for the account agreement.
Date every rule record. If an old article and live documentation conflict, investigate the current product rather than averaging the answers.
When material ambiguity remains, ask support narrowly.
Live server time, actual platform behavior, new credentials, account stage and any program-specific notices. Recheck again after daylight-saving changes and phase transitions.
A pre-purchase rule can be correct while the trader's server assumption is wrong.
Due diligence continues after checkout.
Prop Firm Bridge research note: Current official source + live account verification is stronger than any static all-firm table.
Book insight: Atul Gawande's checklist idea turns research into a repeatable pre-trade control instead of a one-time reading exercise.
Refresh major official event dates. Verify account rules and server offset. Map selected events to server and local time. Calculate current drawdown and target distance. Review open swing positions and upcoming weekend risk.
Rank events by relevance to the instruments actually traded.
Write personal buffers and event caps before the market becomes volatile.
Recheck the official time, pending orders, correlated exposure and severe cash-loss estimate. Enter the restriction with the account in the intended state. Do not improvise around a blocked setup.
During the event, obey the current action-level rule. If direct trading is allowed, the strategy still needs normal risk controls.
Unknown rule state means no new event-sensitive trade.
Wait for account eligibility and market readiness. Recalculate drawdown. Trade only tested structure. Journal actual server time, spread, slippage, action, event type and process quality.
Review monthly by product, event and setup. Remove behavior that does not contribute positive risk-adjusted expectancy.
The operating system should become simpler as evidence improves.
Prop Firm Bridge research note: The complete sequence is verify → convert → classify actions → size → respect the window → wait for readiness → execute → review.
Book insight: A checklist closes the loop because the uncertain variable should be price, not whether the trader remembered the account rules.
Deep case study: evaluation rule changes after funding. A trader uses release-time entries successfully during a CFD evaluation where the selected-news restriction does not apply. After passing, the funded Standard account introduces a two-minute selected-news restriction on targeted instruments.
The trader does not assume the old strategy remains eligible. The release-time model is moved to a Swing-compatible or post-news structure where appropriate. Stage transition becomes a formal research checkpoint.
Deep case study: Swing account behaves differently from Standard. Two traders use the same technical swing strategy. One selects a Standard funded account and another uses a current Swing account type where news restrictions differ.
The account wrapper changes execution permissions even though the market signal is identical. This is why strategy logic and account logic should be separate layers.
Deep case study: FTMO Futures differs from CFD funded rules. A trader familiar with Standard CFD funded restrictions starts a futures product and assumes the same selected-news window applies. Current futures guidance instead says news trading is allowed during any phase, subject to forbidden practices.
The trader still studies the futures prohibited-strategy rules, including event-concentration behavior. Product change triggers full due diligence.
Deep case study: The5ers Bootcamp news allowed but bracket strategy prohibited. A trader sees “news allowed” and plans opposing pending orders around CPI. The detailed program rule disallows bracketing.
The trader switches to directional post-news structure. One permitted category does not make every execution method legal.
Deep case study: The5ers High Stakes holding versus new execution. An existing position is open before high-impact news. Holding is permitted, but a new pending entry would execute inside the restricted window.
The trader separates the two actions. The existing trade follows the holding plan; the new order is cancelled or delayed according to the rule.
Deep case study: pending order placed early triggers late. A trader places a buy stop thirty minutes before a selected event and forgets it. The order activates inside the restricted window.
The error came from execution time, not order-placement time. The pre-event checklist adds a hard pending-order review.
Deep case study: stop loss triggers inside a restricted funded window. A trader assumes a protective stop is always exempt. The current account's written rule treats that stop execution as a prohibited close during the targeted period.
The lesson is not to remove stops. It is to understand the exact rule before choosing to hold the position through the event.
Deep case study: unrestricted futures account still avoids first-tick trading. News trading is allowed, but the trader's live data shows poor fills in the first thirty seconds.
A personal spread and slippage filter keeps the system flat until execution normalizes. Freedom does not require aggressive participation.
Deep case study: event concentration creates a sustainability issue. A futures trader takes almost no trades except large positions on scheduled economic events. The product's current forbidden-practice framework treats concentrated event behavior as a risk concern.
The trader should not assume “news allowed” means an event-only pattern is automatically acceptable. Broader strategy behavior matters.
Deep case study: CPI is allowed but correlated risk is too large. The account permits the trade. EUR/USD, gold and an index all signal the same dollar move.
The trader calculates one combined severe loss and chooses the cleanest setup rather than three full-size entries.
Deep case study: FOMC statement and press conference produce opposite moves. The trader enters after the first statement because the formal restriction has ended. The press conference is still ahead and reverses price.
The personal event map expands beyond the minimum rule to include the full information sequence when the strategy requires stability.
Deep case study: ECB decision is followed by projections. A euro trader sees a post-press-conference range but another scheduled projection release remains.
The strategy stays in event mode until the final mapped information stage is complete.
Deep case study: OPEC meeting has uncertain headline timing. Oil trader cannot identify one precise release second. The account rule does not clearly name OPEC.
The trader uses an elevated market-risk state for the meeting window, smaller size and a post-headline range requirement. Compliance uncertainty and market uncertainty are treated separately.
Deep case study: DST creates a one-hour server error. The trader's saved NFP server time comes from a prior season. The platform has shifted offset.
A live-server check catches the change. The formal event arithmetic is rebuilt from UTC rather than memory.
Deep case study: local phone alarm is correct but server calculation is wrong. CPI is correctly set on the trader's local phone. The account rule uses server time and the saved offset is stale.
The event card requires both local alert and server timestamp, preventing one correct clock from hiding another incorrect one.
Deep case study: no restriction, severe slippage. A trader risks the normal technical amount on a permitted release. Stop slippage increases the realized loss by 50%.
Future event size uses a severe-fill estimate. Compliance and risk are independent gates.
Deep case study: one event consumes the daily plan through multiple attempts. A fade loses, then a continuation loses, then a second fade appears.
The event cap is already used. The third trade is blocked even though the setup is valid.
Deep case study: target-zone account skips a legal event. Phase 2 needs only 0.4% more. The event strategy's severe loss is 0.8%.
The target-zone rule disables optional event risk. The trader finishes later through a normal setup.
Deep case study: drawdown-zone account reduces a good setup. Only $1,000 of practical maximum room remains. A normal event position risks $300 under severe fill.
The risk multiplier reduces size or removes the trade. High setup quality does not create more account capacity.
Deep case study: a blocked winner creates post-window FOMO. The restricted period contains a large move. After the window, price is already extended.
The no-chase rule blocks entry. A rule-compliant trade can still be a bad trade if timing and geometry are poor.
Deep case study: next-session entry preserves the edge. U.S. data creates a strong trend but no compliant entry. Asia builds a range, and London later breaks it in the event direction.
The trader participates under normal spread with a technical stop. News created context, not the release-time execution.
Deep case study: current official rule conflicts with an old review. A trader finds a cached article saying a program has one policy, while the current official FAQ says another.
The current official source and live account govern the trade. Historical content is treated as history, not current instruction.
Deep case study: support answer is vague. The trader asks “Can I trade news?” and receives a broad response. The strategy actually needs to know whether a pending stop can trigger inside the window.
The follow-up question names the product, stage, event, instrument and action. Better questions create better compliance records.
Deep case study: a rule breach wins money. The trader accidentally enters in a prohibited minute and earns 2R.
The journal marks the process as failed. Profit does not validate the action. The workflow is corrected before the next event.
Deep case study: a legal trade loses. The setup is compliant, market-ready and properly sized, but price reverses.
The trade remains a valid statistical sample. Loss alone does not prove the news strategy is wrong.
Operational principle: never store a brand as “news yes/no.” Store product, stage and action.
Operational principle: pending orders belong in the event checklist. An old order can create new exposure automatically.
Operational principle: server time is part of the rule. A timezone mistake can be larger than the entire restriction.
Operational principle: firm permission never replaces personal risk control. Spread and slippage can still make a legal trade unattractive.
Operational principle: one event gets one cash-risk cap. Multiple symbols and attempts share it.
Operational principle: every phase transition gets a fresh audit. Do not transfer evaluation assumptions to funding.
Operational principle: every product transition gets a fresh audit. CFD and futures can differ under the same brand.
Operational principle: prohibited methods are separate from news permission. Bracketing, latency or event concentration can matter even when news is allowed.
Operational principle: blocked winners are opportunity loss, not account drawdown. Do not revenge trade them.
Operational principle: a no-trade event is a successful process outcome. The calendar creates opportunities, not obligations.
Advanced framework: build a seven-column rule matrix. Product, stage, action, event, instrument, timezone and consequence. This format forces specificity.
Advanced framework: version-control rules. Keep old and new effective dates rather than overwriting history. Historical trade review becomes accurate.
Advanced framework: create a source-confidence score. Current official terms and live dashboard rank above old blogs, search snippets and community comments.
Advanced framework: maintain a rule-uncertainty state. If a material action is unclear, the strategy cannot enter until clarified.
Advanced framework: use destination-specific policy objects in copy trading. Each account decides whether one source signal may execute.
Advanced framework: separate event-state and market-state logic. The account can be legally open while the spread filter keeps the strategy closed.
Advanced framework: use UTC as the canonical event timestamp. Generate server and local times from one source value.
Advanced framework: stress-test normal losing streaks plus event slippage. Size should survive both, not just average conditions.
Advanced framework: calculate return per unit of drawdown by event type. High raw profit can hide poor prop-account suitability.
Advanced framework: track blocked setups separately from executed setups. This reveals account-strategy mismatch without contaminating strategy expectancy.
Advanced framework: track direct, post-news and next-session trades separately. The best execution window may differ from the most exciting one.
Advanced framework: use an event-tier system. Normal, elevated and high-risk events can carry different maximum position multipliers.
Advanced framework: add target-zone and drawdown-zone multipliers. Account state can override normal event size.
Advanced framework: perform a monthly rules refresh for active programs. Fast-changing products deserve current verification, especially before major event weeks.
Advanced framework: evaluate documentation quality in account selection. Clear rules reduce hidden operating cost.
Advanced framework: test whether a stricter personal filter improves expectancy. A trader does not have to use every legal minute.
Advanced framework: define when event mode ends. After the final information stage and normalization, return to ordinary technical rules.
Advanced framework: make the one-page event card auditable. Include official event source, server time, rule, action matrix, event cap, pending orders and re-enable conditions.
Advanced framework: design the evaluation strategy to resemble funded behavior. Sustainable risk is more valuable than a fast pass built on event variance.
Advanced framework: review each breach or near-miss by root cause. Classify timing, rule interpretation, pending order, spread, slippage, correlation, sizing or deliberate override. Each cause needs a different fix.
The article's frequently asked questions are stored in the structured FAQ field so this body keeps one clickable FAQ heading without duplicating the same Q&A text.
About the Author: Akash Mane
Akash Mane is the Founder and CEO of Prop Firm Bridge. His work focuses on verified prop firm research, evaluation rules, news trading, drawdown mechanics and practical trader education. Connect with Akash Mane on LinkedIn.
Final Take: In 2026, News Trading Is an Account-Specific Operating Problem
Stop asking only whether a prop firm “allows news.” Ask what your exact product allows, at your exact stage, for the exact action you intend to take. Current official examples make the point clearly: evaluation and funded rules can differ, CFD and futures rules can differ, and a program can allow news while prohibiting specific execution behaviors.
Verify current rules. Convert the event to the governing server time. Treat opening, closing, holding, pending orders and protective exits separately. Size from severe cash loss and remaining drawdown. When direct release trading does not fit, use post-news or next-session structure instead.
Prop Firm Bridge helps traders understand current prop firm rules, news restrictions, server time, drawdown and evaluation mechanics. Always verify the live terms for the exact account and use propfirmbridge.com as part of your wider research process.
There is no universal rule. Policies vary by firm, product, account type and stage. Some evaluations allow news trading while funded accounts add restrictions, and some futures programs use different rules from CFD programs.
Yes. Current FTMO rules, for example, allow macro news trading during its CFD Evaluation Process but restrict selected news activity on Standard FTMO Accounts while Swing accounts are exempt.
Yes. When a rule restricts order execution around news, a pending order that activates during the restricted window can count as new exposure even if it was placed earlier.
It depends on the exact account. Some programs allow holding while limiting new execution, and others may use different conditions. Verify the current rule and stage.
No. Current official examples show product-level differences. FTMO Futures currently allows news trading in any phase subject to forbidden-practice rules, while FTMO CFD Standard funded accounts have selected-news restrictions.
A firm can permit ordinary directional news exposure while prohibiting strategies that depend on simultaneous opposing pending orders, latency, abnormal pricing, or unsustainable concentration around scheduled releases.
Use the actual structural stop plus a realistic slippage stress, then compare the severe cash loss with remaining daily and maximum drawdown. One event should have one total risk cap across correlated positions.
Verify the current account rule and official event time, convert to the governing server clock, manage pending orders, calculate event risk, respect the restriction, wait for normal execution, and trade only a tested setup.
