Free Ebook cover Technical Analysis Foundations: Charts, Trends, Support/Resistance, and Indicators

Technical Analysis Foundations: Charts, Trends, Support/Resistance, and Indicators

New course

10 pages

Technical Analysis Foundations: Combining Tools into a Simple, Repeatable Signal Process

Capítulo 9

Estimated reading time: 9 minutes

+ Exercise

A simple “layering” workflow (avoid overfitting)

The goal of a repeatable signal process is to make decisions the same way across many charts, without adding so many tools that you can justify any trade. A practical approach is layering: you start with what price is doing (structure and zones), then add only one trend filter and one momentum tool as secondary confirmation. Each layer must answer a different question.

  • Layer 1 (structure): Is the market trending or ranging, and where are the meaningful zones?
  • Layer 2 (trend filter): Is the broader bias aligned with the direction you want to trade?
  • Layer 3 (momentum tool): Is momentum supportive at the moment of entry, or is it fading?
  • Context check (volume): Is participation consistent with the move or does it look like noise?

Overfitting happens when you keep adding conditions until the “perfect” historical setup appears, but the process becomes fragile in live markets. Your workflow should be simple enough that you can apply it quickly and consistently, and strict enough that it tells you when to do nothing.

Confluence vs. redundancy (why fewer tools can be stronger)

Confluence means different tools agree while measuring different aspects of the market. Redundancy is when multiple tools repeat the same information, creating false confidence.

What you addWhat it really measuresRisk if you stack too many
Multiple moving averages (e.g., 20/50/200)Trend direction/slope (same family)Redundant “trend confirmation” that lags; can keep you late
RSI + Stochastic + CCIMomentum/oscillation (same family)Overconfidence from repeated momentum signals; conflicting thresholds
MACD + MA crossover systemTrend-momentum blendDouble-counting trend lag; fewer independent insights
Price zones + one MA + one momentum toolStructure + bias + timingCleaner decision tree; fewer “forced” trades

Rule of thumb: if two tools usually change at the same time and tell you the same story, keep one. Your process is stronger when each component has a distinct job.

The repeatable checklist (the “5-step signal process”)

Use this checklist in order. If you cannot answer a step clearly, you either need more clarity (zoom out, reduce clutter) or you pass.

Continue in our app.

You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.

Or continue reading below...
Download App

Download the app

1) Market regime: trend or range?

Decide the regime first because it changes what “good” looks like. In a trend, you want continuation setups and pullbacks that hold. In a range, you want mean-reversion near boundaries and faster profit-taking. If the chart alternates between mini-trends and sharp reversals with no clean swings, label it noisy/unclear and consider passing.

  • Trend plan: prioritize trades in the direction of the trend; be stricter with countertrend signals.
  • Range plan: prioritize trades from range edges; be skeptical of breakout attempts without participation.

2) Key zones: where must price react?

Mark only the zones that matter for decision-making: the ones price has respected recently and the ones that are obvious on your trading timeframe. Your entry should be at or just after interaction with a zone (rejection, hold, break-and-retest). If you have so many lines that every candle touches something, you have created noise.

Quality filter for zones:

  • Clear reactions (impulsive moves away, repeated tests, clean rejections)
  • Not too close together (avoid “zone soup”)
  • Relevant to your holding period (intraday zones for intraday trades, etc.)

3) Trigger: what is the entry event?

Your trigger is the specific price action or pattern event that turns your bias into an actionable entry. It should be objective enough to describe in one sentence and consistent enough to backtest manually.

  • Trend continuation example triggers: pullback holds a zone and prints a rejection candle; break-and-retest of a prior swing level; tight consolidation then expansion in trend direction.
  • Range example triggers: rejection at range boundary; failed breakout (break above then close back inside); double test with weaker follow-through.

Trigger rule: no trigger, no trade—even if indicators look “perfect.”

4) Confirmation: one indicator + volume context

Confirmation is secondary. It should help you avoid low-quality triggers, not create entries by itself. Keep it to:

  • One trend filter: a moving average you already use (e.g., price above/below and slope direction).
  • One momentum tool: either RSI or MACD (choose one for your plan; don’t require both).
  • Volume context: check whether the move has participation consistent with your trigger (avoid treating every spike as “confirmation”).

How to use confirmation without overfitting:

  • Use it as a veto (block trades that are clearly against the filter), not as a scoring system with 10 points.
  • Define a simple threshold like “momentum is supportive vs. not supportive,” rather than multiple nuanced conditions.
  • If confirmation is mixed, reduce size or pass; don’t add more indicators to “break the tie.”

5) Invalidation and exit logic (define before entry)

Before entering, define what must be true for your idea to remain valid. Your invalidation should be based on price structure and zones, not on an indicator flipping color.

  • Invalidation: the level/zone that, if breached, proves your setup wrong (e.g., below the rejection low, beyond the zone, or beyond the retest level).
  • First target: the next logical opposing zone or prior swing point.
  • Management rule: decide in advance whether you will scale out, trail, or use fixed targets. Keep it consistent.

Exit planning shortcut: if you cannot point to a realistic next target that offers acceptable reward relative to your invalidation distance, pass.

Putting it together: a compact decision tree

Step 1: Regime clear? (trend or range)  → if unclear: PASS
Step 2: At/near key zone?              → if no: WAIT
Step 3: Trigger printed?               → if no: WAIT
Step 4: Confirmation supports?         → if clearly against: PASS
Step 5: Invalidation + target defined? → if not: PASS
Execute → Manage per plan

Practical examples (how the layers interact)

Example A: Trend pullback long (clean confluence)

  • Regime: uptrend.
  • Key zone: prior breakout area aligns with a pullback region.
  • Trigger: price pulls into the zone and prints a clear rejection, then breaks a minor internal level.
  • Confirmation: price is above a rising moving average (trend filter supports). Momentum tool shows supportive momentum (not fading) at the trigger. Volume is not collapsing on the breakout attempt.
  • Invalidation/exit: stop beyond the rejection low/zone; target at next resistance zone; optional trail if price accelerates.

Why this is confluence: structure (trend), location (zone), timing (trigger), and confirmation (filter + momentum + volume context) each add different information.

Example B: Range fade at resistance (avoid trend-tool bias)

  • Regime: range.
  • Key zone: range high/resistance.
  • Trigger: failed breakout (push above resistance then closes back inside the range).
  • Confirmation: momentum tool shows weakening/rollover near the top; volume on the breakout attempt is not convincingly strong (suggesting lack of acceptance).
  • Invalidation/exit: invalidation above the failed-breakout high; target mid-range first, then range low if conditions remain favorable.

Common mistake: forcing a moving-average trend filter to dictate direction inside a range. In ranges, the MA will whipsaw; treat it as lower priority or use it only to avoid chasing mid-range.

Example C: Breakout setup that you should pass (signals conflict)

Price approaches a well-defined resistance zone and breaks above it intraday.

  • Trigger: breakout candle closes above resistance.
  • Trend filter: moving average is flat and price has been crossing it repeatedly (no clear bias).
  • Momentum: momentum tool is diverging or failing to expand with the breakout.
  • Volume context: breakout occurs on average or declining volume relative to prior pushes.

Decision: PASS or wait for a break-and-retest that holds with improved confirmation. The trigger exists, but confirmation is not supportive and the regime is not clean. Taking it anyway is how traders accumulate small losses from false breakouts.

Example D: Chart is too noisy (structure cannot be trusted)

You see overlapping swings, frequent long wicks both directions, and zones stacked tightly with constant minor breaches.

  • Regime: unclear (micro-trends keep failing).
  • Key zones: too many; none produce clean reactions.
  • Indicators: moving average flips slope; momentum oscillates rapidly.

Decision: PASS. No indicator can fix unclear structure. Your edge comes from selecting environments where your process has room to work.

Exercises: choose trade, wait, or pass

Scenario 1: Trend continuation vs. overextended entry

Market is trending up. Price is far above the moving average after a strong impulse and is now approaching a resistance zone.

  • Do you buy immediately because trend is up?
  • Or do you wait for a pullback into a zone and a trigger?

Expected action: WAIT. Trend alone is not an entry. Require location + trigger; avoid chasing extension.

Scenario 2: Great trigger, wrong side of filter

Price forms a clean bullish trigger at a support zone, but price is below a declining moving average and momentum remains weak.

  • Do you take it as a countertrend bounce?
  • Do you pass because it violates the filter?

Expected action: For a rules-based process, PASS unless your plan explicitly includes countertrend trades with different targets and stricter risk. Don’t “make exceptions” ad hoc.

Scenario 3: Indicator agreement but no zone

Momentum tool turns bullish and price crosses above the moving average, but price is in the middle of a recent range with no nearby zone to lean on.

Expected action: WAIT or PASS. Without a key zone, your invalidation is arbitrary and reward/risk is often poor.

Scenario 4: Conflicting confirmation at a key level

At resistance, you get a bearish rejection trigger. Momentum supports the short, but volume expands strongly upward on the rejection candle’s prior push.

Expected action: PASS or reduce risk and require additional proof (e.g., a lower high or a break of a nearby internal support). Strong participation against your idea is a warning that the level may break.

Personalize the process (without adding complexity)

Keep the structure identical, and only swap the momentum tool (RSI or MACD) based on what you read best. Document your rules in a short template you can reuse:

  • Regime rule: I trade only clear trends or clean ranges; otherwise pass.
  • Zone rule: I enter only at pre-marked zones or on retests.
  • Trigger rule: I need a specific price action trigger to enter.
  • Confirmation rule: MA must not contradict; momentum must be supportive; volume must not look like obvious noise.
  • Risk rule: Invalidation beyond the zone; target at next opposing zone; if reward is not acceptable, pass.

Now answer the exercise about the content:

In a simple, repeatable layering workflow, what is the primary role of indicators (trend filter and momentum tool) in the decision process?

You are right! Congratulations, now go to the next page

You missed! Try again.

Indicators are used as secondary confirmation after regime, zones, and a trigger. They should help filter out low-quality setups (a veto), not create entries by themselves or replace price-based invalidation and targets.

Next chapter

Technical Analysis Foundations: Avoiding Common Errors, Overfitting, and Misreading Signals

Arrow Right Icon
Download the app to earn free Certification and listen to the courses in the background, even with the screen off.