A Market-if-touched Order GTT is a conditional trading instruction that waits for a chosen price to be touched and then releases a market order. Traders use it to buy on dips or sell on rebounds without watching the screen constantly. The term combines two ideas: market-if-touched describes the trigger behavior, and GTT describes how long the instruction stays active before that trigger occurs.
1. Term Overview
- Official Term: Market-if-touched Order GTT
- Common Synonyms: MIT GTT, Market-if-touched GTT, Market if touched order, MIT order with GTT validity
- Alternate Spellings / Variants: Market-if-touched Order GTT, Market if touched Order GTT, Market-if-touched-Order-GTT
- Domain / Subdomain: Markets / Order Instructions and Validity
- One-line definition: A Market-if-touched Order GTT is a standing conditional instruction that becomes a market order when a specified favorable trigger price is touched, and remains active until triggered, cancelled, or expired under platform rules.
- Plain-English definition: You set a price you would like the market to reach. If the market touches that level, your broker or trading system sends a market order automatically.
- Why this term matters: It helps traders automate planned entries and exits, especially when they want execution priority after a favorable price is reached but cannot monitor the market continuously.
Important: The combined phrase is often platform or broker terminology, not always a universally standardized exchange order type. The exact trigger method, validity period, and execution rules can differ by broker, product, and jurisdiction.
2. Core Meaning
A Market-if-touched Order GTT is a conditional order instruction.
At a basic level:
- You choose a trigger price.
- The system waits.
- If the market reaches that price, the instruction converts into a market order.
- Because it is a GTT instruction, it can remain pending beyond the current session, subject to broker rules.
What it is
It is an order designed for a favorable trigger direction:
- Buy MIT: typically used below the current market price
- Sell MIT: typically used above the current market price
That is what makes it different from a stop order, which usually triggers in the unfavorable or momentum direction.
Why it exists
It exists because traders often want to:
- buy only if price falls to a preferred level
- sell only if price rises to a preferred level
- automate the trade without being present
- prioritize execution once the market reaches that level
What problem it solves
It solves a practical execution problem:
“I want in or out only if the market reaches my chosen price, and once that happens, I care more about getting filled than about capping the exact price.”
If a trader used a limit order instead, the order might not fill fully or at all after the trigger zone is reached. MIT uses a market order after the trigger, so fill probability is generally higher, though the price is not guaranteed.
Who uses it
Common users include:
- retail swing traders
- active investors
- derivatives traders
- portfolio managers
- wealth managers
- proprietary trading desks
- broker platforms and OMS/EMS users
Where it appears in practice
You may see it in:
- retail brokerage apps under conditional orders or GTT
- professional order management systems
- algorithmic execution workflows
- equity, futures, options, and ETF trading setups
3. Detailed Definition
Formal definition
A Market-if-touched Order GTT is a conditional instruction that remains valid until its trigger event occurs or its validity ends, and upon the market touching a specified favorable price, the instruction submits a market order.
Technical definition
Technically, it combines two layers:
- MIT logic: the order triggers when a reference market price reaches a specified favorable threshold.
- GTT validity: the instruction is stored and monitored until triggered, cancelled, or expired under broker or system policy.
Operational definition
Operationally, the sequence is usually:
- Trader enters symbol, side, quantity, and trigger price.
- The broker or OMS stores the order condition.
- A reference price is monitored, such as last traded price, bid, ask, mark, or another platform-defined field.
- When the trigger condition is met, the system creates a market order.
- The order is routed and executed based on available liquidity and applicable risk controls.
Context-specific definitions
In retail brokerage platforms
“GTT” commonly means Good Till Triggered. The order may sit in the broker’s system rather than on the exchange order book until the trigger occurs.
In institutional OMS/EMS environments
The “MIT” behavior may be supported as part of a broader conditional order framework, while the persistence or validity may be labeled differently from “GTT.”
By geography
- In some markets, “GTT” is a common retail term.
- In others, traders may speak simply of an MIT order or a conditional market order.
- The underlying concept remains similar, but the exact implementation may differ.
4. Etymology / Origin / Historical Background
The term has two parts with different backgrounds.
Origin of “Market-if-touched”
“Market-if-touched” developed from the need to trigger orders only when price reached a desired level. In traditional trading environments, this logic could be handled manually by brokers or floor participants. In electronic markets, it became codified inside order management systems.
The key idea was simple:
- if price touches a favorable level,
- then send a market order immediately.
Origin of “GTT”
“GTT” stands for Good Till Triggered. It is a later platform-oriented expression used to describe how long a conditional order instruction stays alive.
It became especially popular in retail trading interfaces because it explained, in plain terms, that the order would remain stored until the trigger occurred.
Historical development
Important stages include:
- Manual conditional instructions: handled by human brokers or desk workflows.
- Electronic order management: trigger logic moved into OMS/EMS platforms.
- Retail platform adoption: brokers began offering standing conditional orders to app-based traders.
- Platform-specific branding: terms like GTT became more common, sometimes with broker-specific rules and maximum validity windows.
How usage has changed over time
Earlier, MIT was more of a desk and execution concept. Today, it is more visible to retail users through broker platforms. At the same time, the exact phrase “Market-if-touched Order GTT” is often a combined retail-platform label, not a classic universal exchange taxonomy.
5. Conceptual Breakdown
| Component | Meaning | Role | Interaction with Other Components | Practical Importance |
|---|---|---|---|---|
| Trigger Price | The price level that activates the instruction | Defines when the order should fire | Works with the reference price and side of trade | This is the heart of the setup |
| Reference Price | The market value used to test the trigger, such as last price, bid, or ask | Determines whether the condition is met | Can create differences between chart view and actual trigger behavior | Must be verified before placing the order |
| Order Side | Buy or sell | Defines direction of trigger logic | Buy MIT usually triggers below market; sell MIT above market | Misunderstanding this causes wrong order placement |
| MIT Conversion | Once triggered, the order becomes a market order | Prioritizes execution over price control | Directly affects slippage and fill certainty | The main advantage and main risk |
| GTT Validity | The instruction remains alive until triggered, cancelled, or expired | Allows multi-session persistence | Works with broker storage, monitoring, and expiry rules | Useful for traders who cannot watch markets continuously |
| Quantity | Number of shares, units, lots, or contracts | Determines trade size | Interacts with liquidity, margin, and partial fills | Large size can materially worsen execution quality |
| Risk/Margin Checks | Broker risk engine verifies funds, limits, and permissions | Prevents invalid or risky execution | Applies at trigger time, not just entry time | A valid GTT can still fail later if risk checks are not met |
| Market Conditions | Spread, depth, volatility, halts, session timing | Affects execution quality after trigger | Interacts strongly with market-order conversion | A touch does not guarantee a good fill |
| Cancellation/Amendment Rules | Rules for modifying or cancelling the instruction | Controls lifecycle management | Depends on platform design and market status | Important for active portfolio management |
6. Related Terms and Distinctions
| Related Term | Relationship to Main Term | Key Difference | Common Confusion |
|---|---|---|---|
| MIT Order | Core parent concept | MIT describes trigger behavior; GTT adds persistence/validity | People assume MIT automatically means multi-day validity |
| Stop Order | Most commonly confused term | Stop orders usually trigger on unfavorable or breakout direction; MIT triggers on favorable direction | Traders often reverse buy/sell trigger logic |
| Stop-Loss Market Order | Same family of trigger-to-market orders | Stop-loss is mainly risk control after adverse move; MIT is often entry/exit on favorable touch | Both become market orders, but for opposite use cases |
| Limit-if-Touched (LIT) | Closest sibling | LIT sends a limit order after trigger, not a market order | Users think MIT and LIT have the same fill behavior |
| Stop-Limit Order | Another conditional order | Stop-limit triggers on stop logic and then submits a limit order | Confused because both combine trigger plus downstream order type |
| GTT | Validity wrapper | GTT says how long the conditional instruction lives; it does not by itself specify market or limit after trigger | Many users treat GTT as a complete order type |
| GTC (Good Till Cancelled) | Similar long-duration concept | GTC usually refers to an active resting order, while GTT refers to a trigger condition remaining active | Both start with “good till,” but they work differently |
| GTD (Good Till Date) | Time-based validity cousin | GTD expires on a specified date | Traders confuse long-lived GTT with date-expiring orders |
| Bracket Order | Strategy structure | A bracket links entry, target, and stop; MIT GTT may be used for just one leg | Users think MIT GTT automatically manages exits |
| OCO (One Cancels the Other) | Order-linking mechanism | OCO links multiple orders so one cancels the other | GTT can exist inside OCO setups on some platforms, but they are not the same thing |
| Trailing Stop | Dynamic trigger order | Trigger level moves with the market | MIT trigger is typically fixed unless the trader edits it |
7. Where It Is Used
This term is most relevant in trading and execution, not in general accounting or macroeconomics.
Stock market and exchange-traded products
- equities
- ETFs
- listed derivatives in some platforms
- active and swing trading workflows
Brokerage and fintech platforms
- app-based order tickets
- “conditional order” sections
- GTT dashboards
- automated retail execution tools
Institutional trading operations
- order management systems
- execution management systems
- re-entry and tactical execution logic
- portfolio transition and rebalance workflows
Regulation and compliance
- order handling procedures
- best execution review
- trigger methodology disclosures
- risk controls and surveillance
Analytics and research
- execution quality measurement
- slippage analysis
- backtesting conditional entry logic
- market microstructure studies
Contexts where it is not central
- Accounting: not a core accounting concept
- Economics: not a core theoretical economics term
- Corporate reporting: only relevant if discussing trade execution policies or treasury activity
8. Use Cases
| Title | Who is Using It | Objective | How the Term Is Applied | Expected Outcome | Risks / Limitations |
|---|---|---|---|---|---|
| Buy the dip automatically | Retail trader | Enter only if price falls to a preferred level | Sets a buy MIT GTT below current price | Gets into the trade without constant screen watching | Fill may occur above trigger due to rebound or spread |
| Sell into a rebound | Investor reducing position | Exit only if price rises to a better level | Sets a sell MIT GTT above current price | Captures recovery without manually tracking price | Market order after trigger may fill below trigger |
| Re-enter after profit booking | Swing trader | Rebuild position on retracement | Uses buy MIT GTT near support | Systematic re-entry | Support may fail and trade may become poorly timed |
| Portfolio rebalance at target zone | Wealth manager or family office | Trim or add when valuation becomes more attractive | Uses MIT GTT for tactical execution | Cleaner implementation of rebalance plan | Large orders can suffer market impact |
| Options or futures tactical entry | Derivatives trader | Join only after favorable move to target level | Sets MIT GTT on contract or underlying, depending platform design | Timely participation | Derivatives can gap hard and move fast after trigger |
| Multi-session unattended plan | Busy investor or professional | Keep a conditional instruction alive for days | Uses GTT validity rather than day order | Convenience and discipline | Broker-specific expiry, corporate actions, or margin changes may affect outcome |
9. Real-World Scenarios
A. Beginner scenario
- Background: A new investor likes a stock trading at 1,000.
- Problem: The investor wants to buy only if the stock dips to 960 but cannot watch the market all day.
- Application of the term: The investor places a buy Market-if-touched Order GTT with a trigger at 960.
- Decision taken: If price touches 960, the broker submits a market buy order.
- Result: The order triggers, but fills at 962 because price bounced quickly.
- Lesson learned: MIT GTT helps automate entry, but the trigger price is not the guaranteed execution price.
B. Business scenario
- Background: A family office plans to reduce exposure in a stock if it rebounds from current weakness.
- Problem: The desk does not want to place a visible resting sell order far above the market and does not want to monitor intraday constantly.
- Application of the term: It sets a sell MIT GTT above the current price.
- Decision taken: If the rebound level is touched, a market sell order is released.
- Result: The position is partially reduced at acceptable prices.
- Lesson learned: MIT GTT is useful for tactical rebalancing, but size and liquidity still matter.
C. Investor / market scenario
- Background: A swing trader believes a strong stock will retrace briefly before continuing up.
- Problem: A passive limit order may miss execution if the stock only touches the level and bounces immediately.
- Application of the term: The trader uses a buy MIT GTT instead of a limit order.
- Decision taken: Favor execution certainty over strict price cap.
- Result: The order fills slightly above trigger but the trader captures the broader move.
- Lesson learned: MIT GTT is often chosen when getting into the position matters more than getting the exact trigger price.
D. Policy / government / regulatory scenario
- Background: A regulator reviews customer complaints about conditional orders.
- Problem: Customers expected execution exactly at the trigger price and did not understand that the order converted to a market order.
- Application of the term: The broker clarifies disclosures around MIT trigger logic, reference price, execution risk, and platform-side GTT handling.
- Decision taken: Better disclosure and stronger pre-trade explanations are implemented.
- Result: Fewer misunderstandings and stronger compliance posture.
- Lesson learned: With conditional orders, disclosure quality is almost as important as the technology.
E. Advanced professional scenario
- Background: An execution desk compares MIT GTT with limit-if-touched strategies in liquid and illiquid names.
- Problem: The team wants to maximize fill probability while controlling slippage.
- Application of the term: MIT GTT is used in highly liquid securities where speed after trigger matters; LIT or other tactics are used where spread risk is larger.
- Decision taken: The desk adds liquidity and volatility filters before permitting MIT activation.
- Result: Execution quality improves because order type is matched to market conditions.
- Lesson learned: Professional use of MIT GTT depends on microstructure, not just on the trigger level.
10. Worked Examples
Simple conceptual example
- Current market price: 100
- Trader wants to buy only if price drops first
- Trigger price: 95
- Order type: Buy Market-if-touched Order GTT
If the reference price touches 95, the system sends a market buy order.
If the next available sell offers are 95.20 and 95.40, the trade may fill above 95.
Practical business example
A portfolio manager wants to reduce a position in Stock A, currently at 450, but only if it recovers to 470.
- Order placed: Sell MIT GTT at 470
- Reason: the manager wants the order to stay pending for several sessions
- Trigger event: price touches 470
- Action taken: a market sell order is sent
- Outcome: execution occurs quickly, though not necessarily at 470 exactly
Numerical example
A trader places a buy MIT GTT with:
- Trigger price = 480
- Quantity = 300 shares
When the trigger is hit, the market order fills as follows:
- 120 shares at 480.20
- 100 shares at 480.60
- 80 shares at 481.00
Step 1: Compute total cost
- 120 Ă— 480.20 = 57,624
- 100 Ă— 480.60 = 48,060
- 80 Ă— 481.00 = 38,480
Total cost = 57,624 + 48,060 + 38,480 = 144,164
Step 2: Compute average execution price
Average execution price = Total cost / Quantity
- 144,164 / 300 = 480.55 approximately
Step 3: Compute slippage versus trigger
For a buy MIT:
Slippage = Average execution price – Trigger price
- 480.55 – 480.00 = 0.55 per share
Step 4: Compute total adverse slippage cost
- 0.55 Ă— 300 = 165
Result: The order triggered at 480, but the trader effectively paid 165 more than the trigger-based expectation.
Advanced example
A sell-side desk enters a sell MIT GTT for 1,000 shares at a trigger of 525.
After trigger, fills arrive as:
- 400 shares at 524.90
- 350 shares at 524.60
- 250 shares at 523.80
Average execution price
- 400 Ă— 524.90 = 209,960
- 350 Ă— 524.60 = 183,610
- 250 Ă— 523.80 = 130,950
Total proceeds = 524,520
Average execution price = 524,520 / 1,000 = 524.52
Slippage for sell MIT
For a sell MIT:
Slippage = Trigger price – Average execution price
- 525.00 – 524.52 = 0.48 per share
Total slippage = 0.48 Ă— 1,000 = 480
Professional lesson: Even in a moderate-size order, trigger achievement does not guarantee exit at the trigger price.
11. Formula / Model / Methodology
There is no single universal “MIT formula,” but there is a clear trigger-and-execution methodology.
Core trigger logic
Buy MIT trigger condition
Trigger if: R ≤ T
Where:
- R = reference market price used by the platform
- T = trigger price
Sell MIT trigger condition
Trigger if: R ≥ T
Where:
- R = reference market price
- T = trigger price
Execution quality formulas
Buy MIT slippage
Slippage_buy = Pavg – T
Where:
- Pavg = average execution price
- T = trigger price
Interpretation:
- Positive value = worse than trigger
- Negative value = better than trigger
Sell MIT slippage
Slippage_sell = T – Pavg
Interpretation:
- Positive value = worse than trigger
- Negative value = better than trigger
Total slippage cost
Total Slippage = Slippage per unit Ă— Q
Where:
- Q = quantity
Implementation shortfall style view
Sometimes traders compare the fill to the price when the trading idea was first formed.
Buy-side implementation shortfall
IS_buy = (Pavg – D) Ă— Q
Where:
- D = decision price when the trader decided to place the order
A negative value means the trader executed at a better price than the original decision price.
Sample calculation
Suppose:
- Decision price = 500
- Buy MIT trigger = 490
- Average execution price = 491.20
- Quantity = 200
Slippage versus trigger
- 491.20 – 490.00 = 1.20 per share
- Total = 1.20 Ă— 200 = 240
Implementation shortfall versus decision price
- (491.20 – 500.00) Ă— 200 = -8.80 Ă— 200 = -1,760
Interpretation:
- The trader did worse than the trigger by 240
- But better than the original decision price by 1,760
Common mistakes
- Using chart price instead of the broker’s actual reference price
- Forgetting that a market order can gap beyond the trigger
- Measuring only whether the order triggered, not how it executed
- Ignoring partial fills when computing average price
Limitations
- These formulas do not capture opportunity cost from missed or rejected orders
- They do not fully capture market impact in large or illiquid trades
- They assume the platform’s trigger reference is known and stable
12. Algorithms / Analytical Patterns / Decision Logic
MIT GTT is highly relevant to decision logic, even if it does not have a classic valuation formula.
1. Trigger monitoring logic
What it is:
The system checks whether the relevant market price has touched the trigger.
Why it matters:
A different choice of reference price can change whether and when the order triggers.
When to use it:
Always. The trader should know whether the system uses last trade, bid, ask, mark, or another field.
Basic logic:
- For buy MIT: trigger when reference price is at or below trigger
- For sell MIT: trigger when reference price is at or above trigger
Limitations:
- Price feeds can update rapidly
- One print may trigger an order even if displayed chart levels look different
- Trigger timing can vary by system latency and data source
2. Order-type selection framework
What it is:
A decision tree for choosing MIT GTT versus other order types.
Why it matters:
Many mistakes come from using the right idea with the wrong order type.
When to use it:
Before placing a conditional order.
Decision logic:
- Use MIT GTT when:
- you want a favorable trigger
- you care more about execution than exact price after trigger
- the instrument is liquid enough for market execution
- Use LIT / limit GTT when:
- price cap matters more than fill certainty
- Use stop order when:
- you want to trigger on momentum or adverse movement
- Use plain market order when:
- you want immediate execution now
- Use plain limit order when:
- you want price control without waiting for a future trigger
Limitations:
- No framework removes slippage risk
- Market conditions can change between planning and trigger
3. Liquidity and volatility filter
What it is:
A practical screening rule applied before using MIT GTT.
Why it matters:
MIT converts to market, so poor liquidity can create unexpectedly bad fills.
When to use it:
Before placing MIT GTT in small-cap, options, or event-heavy names.
Typical checks:
- bid-ask spread
- average trading volume
- visible depth
- corporate actions or earnings calendar
- opening auction or closing auction conditions
- circuit, halt, or volatility control risk
Limitations:
- Liquidity can disappear suddenly
- Historical liquidity does not guarantee future liquidity
4. Backtesting logic
What it is:
Testing a strategy that uses MIT triggers on historical data.
Why it matters:
Naive backtests often assume perfect fills at the trigger, which is unrealistic.
When to use it:
When evaluating whether MIT GTT improves strategy performance.
Limitations:
- Candle data alone is often insufficient
- Intrabar path, spread, and order book conditions matter
- Trigger touch does not equal fill at trigger
13. Regulatory / Government / Policy Context
This term sits within order handling, market structure, and investor protection.
General regulatory themes
Across many jurisdictions, the main concerns are:
- customer understanding of conditional orders
- best execution obligations
- order handling disclosures
- risk checks before routing
- surveillance and audit trails
- fair treatment during volatility events
United States
In the US, MIT-type conditional orders are relevant to:
- broker-dealer order handling
- best execution obligations
- customer disclosures
- supervisory procedures
- market access and risk controls
- exchange or venue-specific support rules
- volatility protections such as trading halts and price-control mechanisms
Practical point: Some conditional orders may be broker-held until triggered rather than resting on an exchange book. Traders should verify how the broker handles them and whether the trigger is based on last sale, bid/ask, or another reference.
India
In India, GTT terminology is widely recognized in retail trading platforms. In many cases, the GTT instruction is handled by the broker system until the trigger is hit, after which the order is sent to the exchange as a market or limit order, depending on the chosen design.
Relevant considerations often include:
- broker trigger methodology
- exchange product rules
- margin availability at trigger time
- risk management system checks
- price bands, circuit filters, or market conditions
- corporate actions affecting pending instructions
Practical point: The exact behavior should be verified in the broker’s order documentation rather than assumed from the label alone.
EU and UK
In the EU and UK, the main concerns are similar:
- best execution
- customer order handling
- disclosure of conditional order mechanics
- venue support and OMS behavior
- treatment during volatile or halted markets
Terms and interface labels may differ, but the economic logic is the same.
Global / international usage
Globally, the phrase “Market-if-touched Order GTT” is less universal than the underlying ideas. Institutional users may speak of:
- conditional orders
- triggered market orders
- standing trigger instructions
- OMS-held order logic
Taxation angle
There is usually no special tax rule merely because the trade was entered through MIT GTT. Tax treatment generally depends on:
- the instrument traded
- the holding period
- the jurisdiction
- the realized gain or loss
Public policy impact
The public policy importance lies in:
- reducing misunderstandings about automated trading instructions
- ensuring fair disclosures
- preserving auditability and supervision
- protecting investors from assuming that trigger price equals execution price
14. Stakeholder Perspective
| Stakeholder | How They View Market-if-touched Order GTT | Main Concern |
|---|---|---|
| Student | A conditional order type combining trigger logic with persistent validity | Understanding direction and execution behavior |
| Retail trader / investor | A way to automate buying on dips or selling on rebounds | Slippage, gaps, and trigger accuracy |
| Business owner / treasury user | A tactical execution tool for investing surplus funds or adjusting market exposure | Governance, permissions, and unintended execution |
| Accountant | Not a core accounting term, but relevant once trades execute and affect books or valuations | Trade confirmation, valuation date, and audit trail |
| Analyst / researcher | An execution design choice that affects realized returns | Backtest realism and execution measurement |
| Portfolio manager / wealth manager | A tactical order tool for rebalancing and disciplined entry/exit | Market impact and consistency with investment mandate |
| Policymaker / regulator | A conditional order mechanism requiring clear disclosure and supervision | Investor protection and order handling fairness |
15. Benefits, Importance, and Strategic Value
Why it is important
- It helps traders act on a plan instead of emotion.
- It reduces the need for constant monitoring.
- It allows entry or exit only at a more favorable price zone.
- It improves execution certainty relative to a limit-after-trigger design.
Value to decision-making
It forces the trader to decide in advance:
- what level matters
- which direction is intended
- whether execution or price control is the higher priority
Impact on planning
MIT GTT supports:
- pre-planned entries
- tactical exits
- rebalancing workflows
- multi-session trade management
Impact on performance
Used properly, it can:
- improve discipline
- reduce missed opportunities
- help capture desired market moves
But performance gains depend on market conditions, especially liquidity and volatility.
Impact on compliance
For firms and regulated intermediaries, it creates a documented:
- trigger instruction
- audit trail
- execution workflow
- disclosure obligation
Impact on risk management
It can reduce behavioral risk, but it introduces execution risk. That trade-off is central.
16. Risks, Limitations, and Criticisms
Common weaknesses
- Trigger price is not the same as execution price
- Market orders can suffer slippage
- Fast markets can create poor fills
- Gaps can bypass the expected price zone
Practical limitations
- Not all platforms support MIT GTT on all products
- Some brokers limit validity duration even for GTT
- Margin or permissions may change before trigger
- Partial fills can occur
Misuse cases
- Using MIT GTT in illiquid securities
- Using it around major news without understanding gap risk
- Assuming chart price and broker trigger price are identical
- Treating it as “set and forget” with no follow-up
Misleading interpretations
A trader may believe:
- “If price touches 100, I will get 100.”
- “Because it’s GTT, the order is guaranteed to sit safely until execution.”
- “Market order means instant and exact fill.”
All three beliefs can be wrong.
Edge cases
- corporate actions may change price reference context
- symbol changes or expiries may affect pending instructions
- halts or auction-only conditions can delay or distort execution
- exchange or broker risk controls may reject triggered orders
Criticisms by practitioners
Experienced traders sometimes criticize MIT GTT because:
- it hides price risk behind automation
- it can encourage lazy planning
- it may perform poorly in thin markets
- it can look precise while actually being execution-uncertain
17. Common Mistakes and Misconceptions
| Wrong Belief | Why It Is Wrong | Correct Understanding | Memory Tip |
|---|---|---|---|
| “MIT is the same as a limit order.” | MIT becomes a market order after trigger | Limit controls price; MIT prioritizes execution after trigger | MIT = touch, then market |
| “Buy MIT triggers above market.” | That is stop-buy logic, not classic MIT logic | Buy MIT is usually set below current market | MIT seeks a better entry |
| “Sell MIT triggers below market.” | That is closer to stop-loss sell logic | Sell MIT is usually set above current market | Sell MIT wants strength first |
| “Trigger price is guaranteed fill price.” | A market order can fill away from the trigger | Trigger is activation, not a price guarantee | Trigger starts the trade, not fixes the price |
| “GTT means exchange-guaranteed resting order.” | Often the instruction is stored at the broker or platform | Verify where the condition is actually held | GTT may live in the broker’s system |
| “If my chart touched it, the order had to trigger.” | Chart price and broker reference price may differ | Always verify trigger source | Know the reference, not just the chart |
| “MIT removes slippage risk.” | Market conversion can increase slippage risk | MIT improves fill probability, not price certainty | More fill, less price control |
| “It is safe in any instrument.” | Illiquid products can execute badly | Use more caution in wide-spread names | Liquidity decides quality |
| “Once placed, it never needs review.” | Market context, margin, and corporate events can change | Monitor pending GTT instructions | Standing order, not forgotten order |
| “Partial fills cannot happen with market orders.” | Large or thin orders can fill in pieces | Measure average price, not just first fill | Market orders can still fragment |
18. Signals, Indicators, and Red Flags
| Item to Monitor | Positive Signal | Red Flag | Why It Matters |
|---|---|---|---|
| Bid-ask spread | Tight spread | Wide spread | Wide spread increases execution uncertainty after trigger |
| Order book depth | Strong visible depth near trigger zone | Thin book |