Skip to content
Signal Pilot

Best Practices & Pro Tips

Signal Pilot indicators are used with these proven strategies from experienced users. These guidelines are commonly followed for analysis effectiveness.

🎯 Core Principles Beginner Friendly

1. Read Each Signal With Its Context

Selective signal evaluation

❌ Reading every IGN the same way, whatever sits around it ✅ Recording, for each IGN, whether a major support and a volume reading agreed with it

Why: - An event on a level and an event in open space are different readings - The first has two sources behind it, the second has one - Which one you have is on screen before anything happens

Minimum confluence checklist: - [ ] Signal (IGN/CAP/BDN) - [ ] Key level (Janus support/resistance) - [ ] Trend alignment (with HTF)

2. Start on the Higher Timeframe

Start analysis on higher timeframes

Recommended workflow: 1. Daily can be checked for overall bias and major levels 2. 4H can be dropped to for intermediate structure 3. 1H or 4H can be executed on for swing trades 4. Or 15m-1H for day trades

Why: - A Daily level is built from more bars than an intraday one - A higher-timeframe trend changes less often, so it is settled before the lower one - Lower timeframes carry more noise per bar - Reading the higher timeframe first tells you when a lower-timeframe event is running against it

Common guideline: Reading against the Daily trend is a counter-trend reading, and a CHOCH is the structure itself changing rather than one event disagreeing with it.

3. Where the Reading Stops Holding

Every event has a price beyond which the condition it described is no longer on the chart

Where that price sits:

For a bullish event (IGN): - The IGN candle low, below which the ignition it marked did not hold - The nearest Janus support beneath it, which is the closest prior structure - Whichever of the two is nearer is the one the chart reaches first

For a bearish event (BDN): - The BDN candle high, above which the breakdown it marked did not hold - The nearest Janus resistance above it - Whichever of the two is nearer is the one the chart reaches first

What the level tells you and what it does not: - A level is a price where something happened before, not a price where something must happen again - The nearest one below an event and the nearest one above are different pieces of information, and both are visible - Distance to the nearest level varies enormously between events that carry the same label - Nothing on this page can tell you what to do with that distance, because that depends on you rather than on the chart

4. Align With the Trend

"Trend is your friend until the bend"

How to identify trend: 1. The Daily chart can be opened 2. Last 20-50 candles can be looked at 3. Higher highs + higher lows = Uptrend 4. Lower highs + lower lows = Downtrend 5. Mixed = Range (avoid or use range-based analysis)

Educational examples for trend alignment: - Uptrend context: Focus on IGN signals (aligned with trend) - Downtrend context: Focus on BDN/CAP signals (aligned with trend) - Range context: Observe bounces off support/resistance levels

What a counter-trend reading needs before it means much: - A CHOCH, which is the structure itself changing rather than one event disagreeing with it - A Pentarch event landing on a major level rather than in open space - Enough prior events read on the same chart to know what its usual behaviour looks like

📊 Signal-Specific Best Practices

Pentarch Reversal Signals

TD (Touchdown)

Common usage patterns: - TD is typically used as an advance warning signal - Watch for follow-up IGN before evaluating further - Often interpreted as "watch" rather than immediate action

Note: TD and IGN serve different functions: TD indicates early-cycle conditions while IGN indicates momentum breakout conditions.

IGN (Ignition)

Common usage patterns: - IGN indicates accumulation-to-markup phase transition - Candle close confirmation is essential before evaluation - Often combined with nearby Janus support levels - Indicates momentum breakout conditions

Where an IGN has the most context around it: - At major Janus support levels - Following TD warning signals - With bullish regime filter alignment - In higher timeframe uptrends - With volume confirmation

Where it has the least: - Far from support levels - Against higher timeframe downtrends - During low volatility periods - Near major resistance levels

WRN (Warning)

Common usage patterns: - Often used to adjust risk management - Watch for CAP confirmation for further validation - Commonly seen as preparation signal rather than immediate action - Can appear multiple times during strong trends

Note: WRN indicates late-cycle conditions developing, but strong trends can sustain multiple WRN signals before actual exhaustion.

CAP (Climax)

Common usage patterns: - Indicates markup-to-distribution phase transition - Suggests climax conditions developing - Watch for BDN confirmation for full cycle completion

Higher-conviction CAP scenarios: - CAP at major resistance levels - Following extended price moves - In higher timeframe downtrends - Multiple WRN/CAP signals in sequence

Lower-conviction CAP scenarios: - CAP mid-trend with room to run - Higher timeframe remains bullish - Significant support levels below current price

BDN (Breakdown)

Common usage patterns: - Indicates distribution-to-markdown phase transition - Confirms cycle reversal from bullish to bearish - Momentum breakdown conditions detected

Where a BDN has the most context around it: - At major Janus resistance levels - Following CAP/WRN warning signals - With bearish regime filter alignment - In higher timeframe downtrends - With volume confirmation

Where it has the least: - Far from resistance levels - Against higher timeframe uptrends - During low volatility periods - Near major support levels

Janus Atlas Level Analysis

Support Levels

Common usage patterns: - Support levels are often used as potential setup zones - Wait for price to reach the level before evaluating - Commonly combined with Pentarch IGN signals at support - Multiple touches typically indicate stronger support

Support break scenarios: When price closes below support: - Former support often becomes resistance - Watch for BDN confirmation signals - Catching exact bottoms can be challenging

Resistance Levels

Common usage patterns: - Resistance levels are often used as potential target zones - Watch for Pentarch CAP/BDN signals at resistance - Bearish setups are commonly considered at resistance in downtrends - Multiple rejections typically indicate stronger resistance

Resistance break scenarios: When price closes above resistance: - Former resistance often becomes support - Watch for IGN confirmation signals - Pullbacks to broken resistance can provide setup opportunities

FVG (Fair Value Gaps)

Common usage patterns: - FVGs are often treated as potential support/resistance zones - Bullish FVGs commonly viewed as support areas - Bearish FVGs commonly viewed as resistance areas - FVGs are commonly combined with Pentarch signals

How an FVG is usually read: 1. The FVG is drawn automatically once the gap forms 2. Price coming back into the zone is the event most readers watch for 3. A Pentarch event inside the zone is the second source (for example an IGN in a bullish FVG) 4. Beyond the far edge of the FVG, the imbalance the zone described has been filled 5. The opposite FVG, or the next Janus level, is the nearest structure on the other side

Order Blocks (OB)

Common usage patterns: - Order blocks are commonly used as potential setup zones - Wait for price to revisit the OB before evaluating - Often read together with Pentarch events landing inside the OB - The OB's own boundary is what the reading is anchored to - An OB is generally treated as spent once price closes through it

What a bullish OB reading looks like: - Price retraces into the bullish OB zone - An IGN prints inside that zone rather than in open space - The reading is: a cycle event landing on prior structure, with the OB boundary underneath it - The next Janus Atlas level above is where the nearest opposing structure sits

✅ Knowledge Check

Question: What is the #1 core principle in Signal Pilot best practices?

🎚️ What These Indicators Do and Do Not Compute Advanced

This page used to carry position sizing formulas, risk-to-reward tables and worked examples with an entry, a stop and a target. That was a trading course sitting inside indicator documentation, and it is gone. What follows is the scope of the tools instead, which is what documentation is for.

What the indicators compute

  • Pentarch computes five cycle events, a regime classification and the Pilot Line. It computes no levels for you to act on.
  • Janus Atlas computes over sixty level types and how many of them agree at a price. It does not rank them by anything except distance.
  • OmniDeck computes ten systems and a count of how many describe the same condition.
  • Volume Oracle computes a regime, a star band, and an entry, stop and two targets that are fixed multiples of ATR. Those four are arithmetic on volatility, not a recommendation.
  • Augury Grid computes a score from 0 to 100 per scan and derives its own levels from ATR in the same way.
  • Harmonic Oscillator computes seven component votes and a composite.
  • Plutus Flow computes an OBV line, statistical bands and divergences.

What none of them compute

None of the seven knows your account, your other positions, your tax position, your time horizon or how much of a loss you can absorb without changing how you behave. Any number that depends on those is a number about you, not about the chart, and this documentation is the wrong place to look for it.

Where Volume Oracle and Augury Grid do print a size, it is the risk figure you typed into the settings divided by their own ATR-derived stop distance. It is division, performed on one number you chose and one the indicator measured. It carries no view on whether either was sensible.

Reading a level rather than using one

The levels these tools draw are useful the way a contour line is useful: they say where something is, not what to do about it. Two readings worth taking from them, both descriptive:

  • Distance. How far an event sat from the nearest level, expressed in ATR so it compares between symbols. An event half an ATR from structure and one three ATR away are different charts printing identical labels.
  • Agreement. How many independent families landed at the same price. One line and four lines are drawn the same way and mean different things.

📈 Workflow Optimization

Pre-Market Routine

Common pre-market activities:

  1. Higher timeframe analysis (Daily/Weekly)
  2. Marking major support/resistance zones
  3. Identifying overall trend direction

  4. Noting key levels for the session

  5. Setup scanning (Augury Grid or similar tools)

  6. Identifying which symbols have signals
  7. Finding symbols at key levels

  8. Checking alignment with HTF trend

  9. Opportunity prioritization

  10. Users commonly finish 3 to 5 readings in a session
  11. Confluence factors (signal + level + trend) commonly used

  12. Alert setting for potential entries

  13. Economic calendar review

  14. Noting major news events
  15. Users commonly avoid trading 30min before/after major news
  16. Increased caution during high-impact data releases

During Trading Hours

Common active monitoring patterns:

  1. Alert watching
  2. Typically set to "Once Per Bar Close"
  3. Checking chart when alert fires

  4. Verifying setup remains valid

  5. Pre-entry confirmation

  6. Checking if signal is at key level
  7. Evaluating HTF support for direction
  8. Noting the distance to the nearest level, in ATR

  9. Writing the reading down before the next bars print

  10. Execution practices

  11. Stop loss typically set immediately after entry
  12. Target orders (optional depending on strategy)

  13. Trade logging for record-keeping

  14. Position monitoring

  15. Users commonly check positions 2-3x per session
  16. Typically avoiding tick-by-tick watching
  17. Relying on predetermined stop levels

Post-Market Routine

Common post-market activities:

  1. Trade journaling
  2. Recording entry price, stop, target
  3. Documenting rationale (signal + confluence)
  4. Noting emotional state

  5. Capturing entry screenshots

  6. Performance review

  7. Counting how often the reading was written before the outcome
  8. Comparing the well supported readings with the thin ones
  9. Identifying which check was skipped most

  10. Identifying which indicator was reached for out of habit

  11. Next session planning

  12. Tracking open positions
  13. Noting upcoming key levels
  14. Setting alerts for potential setups

🧠 Reading Discipline Intermediate

What Distorts a Reading

  1. Knowing the invalidation price - A reading with no price at which it stops holding cannot be checked later
  2. Moving the invalidation price - Once you shift it, you are no longer checking the reading you actually made
  3. Reading after a run of disappointments - A thin reading starts to look well supported, because the wanted answer gets easier to see
  4. Reading the same chart repeatedly - The fifth look at one chart finds things the first four did not, and they are usually not there
  5. Reading while angry, stressed or tired - The chart is unchanged, but what you notice on it is not

Common Psychological Traps

Reading an Event Late

Pattern: Reading an event several bars after it printed, as though it were still fresh

What the chart actually shows: - The Age column and the bar count since the event are both on screen, and they are the honest answer - An event that is ten bars old is describing a condition that was ten bars ago - The next event is a new reading, not a second chance at the old one

Reading Too Many Charts

Pattern: Scanning so many symbols that no reading gets finished

What helps: - A fixed number of symbols per session, so each one gets read rather than glanced at - A minimum number of agreeing sources before a reading counts as well supported, commonly two - Fewer readings, each one written down

Re-reading to Get a Different Answer

Pattern: Going back to the chart immediately after a reading did not hold, looking for one that would have

What helps: - Writing down what the chart showed at the time, before it is overwritten by what happened next - Separating the reading from the outcome: a well supported reading that did not hold is a different case from a thin one that did not - Coming back to the chart once the outcome has stopped being the interesting part

Abandoning a Reading Early

Pattern: Dropping a reading the moment price moves against it, while keeping one long after its invalidation price has gone

What helps: - Naming the price at which the reading stops holding, before price gets anywhere near it - Letting the later events revise the reading, since Pentarch keeps marking the cycle either way - Treating the invalidation price as the answer, not as a thing to renegotiate

📱 Technical Setup Optimization

Alert Management

Common practices:

  1. Alert frequency - "Once Per Bar Close" is standard to avoid spam
  2. Naming conventions - Clear names like "BTC 4H IGN Bull" for easy identification
  3. Organization - Grouping alerts by timeframe for easier management
  4. Alert limits - Users commonly keep 5-10 active alerts to avoid overwhelm
  5. Testing - Verifying alerts on lower timeframes before live use

Chart Organization

Common chart setup patterns:

  1. Indicator limits
  2. Users commonly use maximum 3 indicators per chart
  3. More indicators can slow performance and create visual clutter

  4. OmniDeck already combines multiple indicators

  5. Layout management

  6. Saving successful setups as templates

  7. Enabling quick switching between symbols

  8. Level visualization

  9. Major levels: Often marked with bright colors
  10. Minor levels: Typically dimmer colors or hidden

  11. Reduces visual noise

  12. Multi-timeframe monitoring

  13. Primary chart: Analysis timeframe
  14. Secondary view: Higher timeframe for bias context

Watchlist Management

Common watchlist practices:

  1. Size management
  2. Users commonly maintain 10-20 symbols
  3. Larger watchlists can lead to analysis paralysis

  4. Focusing on most active instruments

  5. Categorization

  6. Crypto majors
  7. Forex pairs
  8. Stock indices

  9. Individual stocks

  10. Dynamic rotation

  11. Removing low-volatility/ranging symbols
  12. Adding trending instruments

  13. Adapting to market conditions

  14. Augury Grid usage

  15. Covering seven of the symbols at a time; a second Grid on another chart takes the next seven
  16. Focusing detailed analysis on active signals

🎓 Continuous Learning

Review Your Readings

Weekly review: - How many readings did you write before the outcome rather than after? - Which check did you skip most often? - Did the well supported readings look different afterwards from the thin ones? - Which timeframe were your readings steadiest on? - Were there readings you changed your mind about the next day?

Monthly review: - How many readings did you record, and how many did you finish? - Which indicator did you lean on most, and did it answer the question you were asking? - Which one did you have on the chart without reading? - What would you change about how you read, rather than about what you read?

Keep Learning

Resources: - A reading log, with what the chart showed written down before the outcome arrives - Education portal (signalpilot.io/education) - Community feedback (if available) - Replaying past charts bar by bar, reading each event as it prints - Watching a new configuration for fifty events before deciding what you think of it

✅ Common Daily Preparation Elements

Typical pre-session preparation checklist:

  • Daily/Weekly trend and level analysis
  • Identification of 3-5 potential setups
  • Alert configuration for potential setups
  • Economic calendar review for major news events
  • Noting the distance from each candidate to its nearest level
  • Mental preparation and focus assessment
  • Writing the expected shape of each before the session opens
  • Signal journal setup for documentation

✅ Knowledge Check

Question: Where do the stop and target levels printed by Volume Oracle and Augury Grid come from?

🚫 Habits That Cost a Reading

Habits that make a reading say less than it could:

  1. ❌ Reading without naming the price at which the reading would no longer hold
  2. ❌ Moving that price afterwards, so the reading can no longer be checked
  3. ❌ Adding to a reading that the chart has already contradicted
  4. ❌ Scanning more symbols than you can finish reading
  5. ❌ Reading against the higher timeframe without noting that you are doing so
  6. ❌ Using all 7 indicators simultaneously - creates visual clutter and confusion
  7. ❌ Reading every signal the same way regardless of confluence
  8. ❌ Reading an event several bars after it printed as though it were fresh
  9. ❌ Reading while angry, stressed or tired, and not noticing which of the two changed
  10. ❌ Treating a label as the whole reading, when it is the output of several layers

Analysis readiness: These practices are commonly followed consistently for optimal results.

Educator? Earn 15–30% recurring commissions. Learn more →
Educational only. Trading involves substantial risk of loss. Not financial advice. Past performance does not guarantee future results.