If we had to identify one concept at the foundation of the Xcelerate Trade Strategy, it would be Liquidity.
This does not mean that every market movement happens because price is “searching” for Liquidity, or that every visible high and low must eventually be taken.
It means something much more practical for our strategy: before we look for CHoCH, Displacement, FVG or any of the setup classifications studied so far, we first need a relevant Liquidity context.
Liquidity tells us where to begin looking.
The Confirmations tell us whether there is anything to execute.
This is why identifying Liquidity correctly matters so much.
If the Liquidity reference is poorly selected, the rest of the sequence may look technically correct while being built around the wrong context.
By this stage, however, you also know that Liquidity is not limited to HOD and LOD.
As the strategy expands into different market conditions, we need a clear framework for deciding which Liquidity matters and which should be ignored.
The Four Types of Liquidity
For the purposes of the Xcelerate Trade Strategy, we divide Liquidity into four main categories:
High of the Day and Low of the Day
Major Liquidity, also referred to as External Liquidity
Local Liquidity
Minor Liquidity, also referred to as Internal Liquidity
These categories do not have equal importance and should not be used interchangeably.
A prominent structural extreme that has developed over a larger market movement is not treated the same way as a small internal high formed during a short retracement.
HOD and LOD can also represent prominent external Liquidity in a broader market-structure sense. Within the Xcelerate Trade framework, however, they form a separate category because of their specific operational role in the original tested session model.
This is a practical distinction that creates a clear hierarchy when several Liquidity references are visible at the same time.
This becomes particularly important after Lesson 5 of this chapter.
Once you begin adapting the strategy beyond its original SPX500 environment, more possible Liquidity references become visible.
The solution is not to mark all of them.
The solution is to know which category you are looking at and where it sits within the strategy's hierarchy.
Liquidity Comes Before Confirmation
The analytical order remains consistent:
Filters → Liquidity → CHoCH → required setup structure → Displacement → FVG Configuration → Execution
Do not reverse this sequence.
A common mistake is to notice an attractive FVG or a large candle first and then search backward for a Liquidity event that makes the setup appear valid.
That introduces hindsight and weakens the consistency of the process.
Start with the relevant Liquidity.
Then wait for the strategy to confirm whether that Liquidity event develops into a valid setup.
Before moving further through the algorithm, ask yourself:
Where is the most relevant Liquidity in the current context?
If the answer is unclear, waiting for a cleaner structure is often the better decision.
Major Liquidity - External Liquidity
Major Liquidity is formed around prominent structural highs and lows that stand out clearly within a broader market structure.
These are not small fluctuations close to the current price.
They are significant structural extremes that remain visually relevant even when you step back from the immediate microstructure.
Major Liquidity is the first additional category to learn beyond the original HOD/LOD framework because it is generally easier to identify consistently than smaller Local or Internal Liquidity.
Within the original tested environment, however, HOD and LOD retain first priority.
The objective is not to find as many Major Liquidity levels as possible.
It is to identify the levels that clearly stand apart from the surrounding structure.
Identifying Major Liquidity
There is no mathematical formula that automatically makes a high or low Major Liquidity.
Some judgment is still required.
However, useful characteristics include a level that is:
clearly visible;
well defined within the surrounding structure;
associated with a meaningful previous market movement;
visible without having to magnify a very small section of the chart;
prominent when viewed from a broader structural perspective.
Major Liquidity will often be easier to recognise on higher timeframes such as M15, M30, H1 or above, depending on the instrument and the context being analysed.
The timeframe alone does not make a level major.
A random high on H1 does not automatically become important simply because it appears on H1.
The distinction between Major and Local Liquidity is therefore not determined by timeframe alone.
Major Liquidity stands out within the broader structure being analysed. Local Liquidity belongs to the more immediate structure around current price.
Timeframe can help you see that difference, but it does not define the category by itself.
The practical principle from the previous lesson still applies:
If you have to spend too much time convincing yourself that a high or low is major, it probably is not clear enough to serve as your primary Major Liquidity reference.
Why Major Liquidity Matters
Prominent highs and lows can become areas of concentrated market interest because different types of orders may exist around visible structural extremes.
We do not need to know exactly which participants placed those orders or why every individual order is there.
What matters for the strategy is observable behaviour.
Price approaches a clearly defined structural extreme.
The relevant Liquidity is taken.
Then we observe what happens next.
We do not trade simply because price touches or moves through Major Liquidity.
The Liquidity event provides context.
The algorithm still requires the appropriate CHoCH, required setup structure, qualifying Displacement and FVG Configuration before an Execution can be considered.
Major Liquidity is therefore a starting point for analysis, not an Entry signal.
Risk Around Multiple Major Liquidity Levels
Sometimes two meaningful Major Liquidity areas can exist relatively close to each other.
In this situation, you do not necessarily have to commit the full planned Risk to the first opportunity.
One possible approach is to divide the total planned Risk between the two areas.
For example, if the maximum Risk allocated to the complete idea is 1%, you could allocate 0.50% to one independently valid setup and keep the remaining 0.50% available only if a second independently valid setup later develops around the next Liquidity area.
The presence of two Liquidity levels is not, by itself, a reason to divide Risk.
Each setup must independently satisfy the complete algorithm, and the combined planned Risk must remain within the predefined limit.
Risk is allocated only to independently valid setups according to a rule defined before execution.
This approach is optional. If you decide to use it, define it in your trading algorithm and test it consistently rather than deciding to split or add Risk after seeing how price behaves.
High of the Day and Low of the Day - HOD and LOD
HOD and LOD are among the clearest Liquidity references used in the Xcelerate Trade Strategy.
They played a central role in the original strategy environment because they give us predefined reference levels within a defined session structure.
There is an important detail here.
HOD and LOD are objective only after the data source and session convention have been defined.
Different brokers, data feeds, trading-session definitions or instruments can occasionally produce slightly different daily extremes.
For this reason, use a consistent analysis feed and the same session convention throughout your testing.
Within that defined environment, HOD and LOD provide highly repeatable references.
This is one of the reasons they were used as the foundation for learning the strategy.
Why HOD and LOD Matter
Day extremes are highly visible reference points.
Different market participants may make decisions around them for different reasons, and different order types can be concentrated around visible highs and lows.
For our purposes, we do not need to prove the composition of those orders.
We need to observe how price behaves when the relevant HOD or LOD Liquidity condition occurs.
Again, the level itself is not the trade.
HOD/BSL taken can create potential Sell context.
LOD/SSL taken can create potential Buy context.
The required Confirmations must still follow before an Execution becomes valid.
When to Use HOD and LOD
In the original form of the strategy, HOD and LOD are used within the specific session framework for which the rules were built and tested.
If you are still working within that environment, continue to use them exactly as established in the earlier lessons.
When you begin testing other instruments or other trading windows, HOD and LOD may remain relevant context, but they are not automatically the primary Liquidity reference for every setup.
This is where Major and Local Liquidity can become more useful.
Do not remove HOD and LOD from the chart simply because another Liquidity category is being used.
They may still provide useful broader context or become relevant later in the session.
The key is to distinguish between a level that exists and the Liquidity reference currently driving your setup.
Local Liquidity
Local Liquidity is formed around clear highs and lows within the more immediate market structure.
You were introduced to Local High and Local Low in Lesson 5 because they become particularly useful when adapting the strategy beyond the original HOD/LOD environment.
These levels occur more frequently than Major Liquidity and are usually closer to current price.
That creates both an advantage and a problem.
There are more potential opportunities.
There are also more opportunities to over-interpret insignificant structure.
This is why Local Liquidity should be introduced only after you can consistently identify broader structure and execute the core algorithm.
What Makes Local Liquidity Different?
Local Liquidity belongs to the current structural context.
It can form as the market develops new highs and lows throughout a session.
This is why Lesson 5 required you to reassess structure after meaningful market developments rather than keeping the same Liquidity references all day.
But not every newly formed high or low becomes useful Local Liquidity.
The reference should still be clear enough to identify consistently before the outcome is known.
If you start marking every minor fluctuation as a Local High or Local Low, you have moved away from the purpose of the framework.
More levels do not create a better analysis.
They usually create more discretion.
When to Introduce Local Liquidity
Consider integrating Local Liquidity only after you can:
read the current market structure consistently;
identify a valid CHoCH;
apply the core setup classifications;
follow the complete execution algorithm;
maintain a trading journal;
evaluate your own statistics.
Local Liquidity should expand your ability to recognise relevant context without lowering the quality threshold required for a trade.
It is not a replacement for Major Liquidity.
Major Liquidity can provide a broader structural reference, while Local Liquidity can provide a more immediate reference within that context.
But neither one independently determines direction or guarantees an Entry.
The full algorithm still decides whether the opportunity is executable.
Minor Liquidity - Internal Liquidity
Minor Liquidity, or Internal Liquidity, is the most specific category in this framework.
It develops inside an already established market structure and is most relevant when evaluating continuation rather than looking for a major structural change.
A trending market does not move in a straight line.
It forms impulses and retracements.
Those retracements can create smaller internal highs and lows within the broader directional structure.
Some of those internal levels can become relevant Liquidity references for a continuation setup.
This does not mean every pullback contains a trade.
Minor Liquidity is deliberately lower in our hierarchy because smaller internal structures occur frequently and are easier to over-interpret.
When to Use Minor Liquidity
Minor Liquidity is most useful when the broader market structure is already clear.
If price is moving without a coherent structure, repeatedly changing direction or producing weak impulses, there is little reason to search aggressively for Internal Liquidity setups.
In a clearly established directional structure, however, an internal Liquidity event can provide context for evaluating a possible continuation.
The same algorithm still applies.
The relevant Liquidity must be taken.
A valid CHoCH must develop within the context being evaluated.
In a continuation context, this CHoCH is evaluated within the internal structure of the retracement. It does not mean that the broader trend itself must first reverse.
The broader structure provides the continuation context. The internal structural shift helps confirm that the retracement may be ending before the normal Displacement and FVG requirements are evaluated.
The required setup structure must then be present.
Qualifying Displacement and FVG Configuration must follow.
Only then can an Execution be considered.
Do not turn Internal Liquidity into a shortcut around the normal strategy requirements.
Risk and Minor Liquidity
A practical approach when working with Minor Liquidity is to use 0.50% Risk.
This fits within the established Xcelerate Trade Risk framework, but it should not be interpreted as an automatic rule that every Internal Liquidity trade receives exactly 0.50%.
Your Risk must still remain within the predefined limits of your trading algorithm.
If you decide to differentiate Risk by Liquidity category, that becomes another variable that should be defined in advance and supported by testing.
The important principle is that lower-ranked Liquidity does not justify higher Risk simply because more opportunities appear.
Choosing the Right Liquidity
Once you can recognise all four categories, the natural question is:
Which one should you use when several are visible at the same time?
Do not try to use every Liquidity level on the chart simultaneously.
The purpose of this framework is to simplify the decision process, not to create a reason to trade every high and low.
For the Xcelerate Trade Strategy, use the following hierarchy:
1. High of the Day and Low of the Day
Within the defined trading environment for which the original strategy was built and tested, HOD and LOD have first priority.
They provide the predefined Liquidity references established in the core strategy.
2. Major Liquidity
When HOD or LOD is not the relevant reference for the context being tested, look next to Major Liquidity.
These are prominent structural extremes that provide a broader and generally clearer reference than smaller Local or Internal levels.
3. Local Liquidity
Local Liquidity becomes relevant once you have sufficient experience with the first two categories and are working with the current evolving structure.
It can provide additional valid contexts, particularly when adapting the strategy to other instruments or trading windows.
4. Minor Liquidity
Minor or Internal Liquidity has the lowest priority.
It is used selectively inside a clear broader structure, primarily when evaluating continuation contexts.
It should not become a reason to manufacture additional trades.
The hierarchy is therefore:
HOD / LOD → Major Liquidity → Local Liquidity → Minor Liquidity
This hierarchy gives you a consistent way to decide which reference deserves priority when several Liquidity levels are visible.
When Liquidity Contexts Conflict
The hierarchy becomes particularly important when two Liquidity categories create conflicting contexts.
Do not simply choose the one that supports the trade you already want to take.
Give priority to the higher-ranking Liquidity category.
For example, if a Local Liquidity condition appears to support one context while a higher-ranking HOD/LOD condition within the strategy's defined trading environment supports the opposite context, the HOD/LOD reference takes priority.
The same logic applies throughout the hierarchy:
HOD/LOD has priority over Major Liquidity within the original tested environment.
Major Liquidity has priority over Local Liquidity.
Local Liquidity has priority over Minor Liquidity.
Priority does not mean automatic direction, and it does not mean automatic Execution.
It tells you which Liquidity context governs the analysis.
The normal Confirmation sequence must still follow.
Hierarchy decides the Liquidity context.
Confirmations decide whether that context becomes executable.
Keep the Analysis Simple
Learning more Liquidity categories should make your analysis more precise, not more complicated.
Do not finish this lesson and begin marking every visible high and low with a different label.
Introduce the categories gradually.
Start with HOD and LOD within the original tested environment.
Learn to recognise Major Liquidity.
Add Local Liquidity only when your structure reading and execution are sufficiently consistent.
Use Minor Liquidity selectively and only when the broader context supports it.
The purpose is not to find more trades.
The purpose is to know which Liquidity deserves your attention.
If adding more Liquidity categories causes you to become less consistent, step back to the simpler framework and rebuild from there.
Xcelerate Trade Perspective
Liquidity is the starting context of the Xcelerate Trade Strategy, but not every Liquidity level has the same value.
The more experienced you become, the more highs and lows you will notice on a chart.
Your job is not to trade all of them.
Your job is to classify them, understand their place in the current structure and give priority to the reference that belongs higher in the Xcelerate Trade Liquidity hierarchy.
Within the original tested environment:
HOD / LOD → Major Liquidity → Local Liquidity → Minor Liquidity
When two categories conflict, the higher-ranking Liquidity context takes priority.
Then the strategy continues exactly as it should:
Filters → Liquidity → CHoCH → required setup structure → Displacement → FVG Configuration → Execution
A Liquidity sweep does not create an automatic trade.
A lower-ranked level does not override a higher-ranked context simply because it produces an attractive FVG.
And adding more Liquidity categories should never become an excuse to lower your execution standards.
Start with the clearest references.
Build experience.
Document what you trade.
Use your statistics.
Expand only when the additional category improves your process rather than complicating it.
The objective is not to see more Liquidity.
It is to know which Liquidity matters.