Setting Up Cycle Analysis on NinjaTrader 8

You can set up a NinjaTrader 8 chart for cycle analysis with nothing but a daily price panel, a volume panel, and three built-in drawing tools — vertical lines for timing, trend lines for structure, horizontal lines for levels. No custom indicator is required, and no indicator can do the one part that matters: the count is still yours.

That answer disappoints people, so let me say it again in a different way. The software's job is to mark and to measure. Your job is to decide. Everything below is about drawing the line between those two jobs correctly, because most traders who come to cycle work put the line in the wrong place — they expect the platform to find the cycles for them, and it can't. What it can do is make the cycles far easier to see, and that turns out to be worth a lot.

What does a cycle chart actually need?

Less than you think. Cycle work is about the timing of lows and the structure between them, so the chart has to show you clean price history, honest volume, and enough room to draw. That's the whole list. Here's the layout I'd give a trader starting from a blank NinjaTrader 8 workspace:

Two panels are enough. Three is the ceiling. If your chart has five stacked studies, you're not doing cycle analysis — you're doing indicator archaeology, and the lows get lost in it.

On the data itself: give the chart enough history to see the rhythm repeat several times. A cycle you've watched complete once is a guess. A cycle you've watched complete again and again across the visible history is a working read. Load the chart with room to scroll back, because the whole point of this style of analysis is that the past instances of the rhythm inform the current one.

How do I lay out the chart in NinjaTrader 8?

Conceptually, the setup is four moves. NinjaTrader calls its panes "panels," and its chart settings live in the Data Series and chart-properties dialogs — but I'm going to describe this at the level of what you're building, not which menu to click, because the menus change and the structure doesn't.

1. Open a daily chart of the instrument and stretch the price panel tall. Cycle troughs are read off daily bars first. Intraday charts come later, after the daily map exists — never instead of it.
2. Add volume in its own panel below price. Keep it plain. You're reading relative height at the lows, not decorating.
3. Strip the chart. Kill the gridlines you don't need, drop the default studies you didn't choose, pick a background you can stare at for hours. This sounds cosmetic. It isn't — fatigue is a real cost in this work, and a noisy chart taxes you on every glance.
4. Save the layout as a chart template. NinjaTrader lets you save a chart's whole configuration and apply it to any instrument. Build the setup once, name the template, and every new symbol opens ready for cycle work. This is the single biggest time-saver in the platform for this style of analysis.

That's the whole build. First-time configuration is honestly the hardest part of getting started — not because any step is difficult, but because a blank platform offers you a hundred options and cycle work needs about six of them. Set it up once, template it, and stop touching it.

Which drawing tools do the cycle work?

Three built-in tools carry almost all of it. They're stock NinjaTrader 8 drawing objects — nothing custom, nothing imported.

Notice what's not on the list: no oscillator that "finds" cycles, no adaptive anything. The drawing tools force you to make each judgment yourself and leave a visible record of it. That record is what you review later — a journal built as a dataset does for your trades what marked-up charts do for your counts.

Do I need cycle software or a custom indicator?

No. You can do this entirely by hand — mark the lows, measure the spacing, draw the structure. I want that stated plainly before anything else, because the hand-built version is not a lesser version. It's the same analysis at a slower speed, and slower has teaching value when you're learning.

That said: I use cycle-charting software in my own trading, and the charts in my book were made with it — because I needed to communicate the ideas clearly across many assets and many years, not just one index. Software earns its keep in three specific ways. It computes the displaced lines and projections for you instead of you doing arithmetic by hand. It turns you into a visual learner — you see the structure instantly instead of assembling it in your head. And it cuts the daily time cost of tracking the cycles, which keeps you fresher and keeps your psychology in better shape. Fatigue is a position risk nobody puts on their risk report. Software reduces it.

What I won't do is publish our indicator code or the scan logic behind it, here or anywhere. That's a boundary, and I'd rather say it out loud than pretend it's an oversight. The concepts are teachable and I teach them. The computed output is the business.

So the honest hierarchy is: hand-drawn is fully sufficient, software is a genuine convenience, and neither one is the analysis. The analysis is the judgment layered on top.

What does the software see that I don't?

Software beats you at exactly the things machines are good at, and it's worth naming them so you use it for those and nothing else.

It's consistent — it measures the same way on the thousandth chart as the first, while your eye drifts with mood and fatigue. It's fast — checking a structure across forty instruments by hand is an afternoon; software does it before your coffee cools. And it's broad — it lets one person keep a cycle map current across many assets and many years of history, which is how you learn that the rhythm you found isn't a one-chart accident.

What does the software not see?

This is the section that matters, so I'll be specific.

It doesn't know which lows are real. A cycle count is a judgment about which troughs belong to which rhythm. Software can propose candidates; it cannot confirm them, because confirmation depends on context — spacing, structure, volume, what the larger rhythm is doing — that has to be weighed, not computed. If you feed a tool a wrong count, it will extend that wrong count forever, beautifully, with total confidence. I've written a full walkthrough of what a valid low actually looks like in how to identify a cycle low on a daily chart.

It doesn't know the news. A scheduled announcement that will land in the middle of your timing window is invisible to a price chart until it hits. The calendar is part of the analysis and no chart setup carries it for you.

It doesn't grade the setup. The platform will render a mediocre situation with the same crisp lines as a great one. Selectivity is yours.

And it doesn't make the read. This is the one traders most want to outsource and the one that can't be outsourced. Here's what that looks like in practice, from my own public record — logged before the outcome, scored after:

2026-07-09 — COST, graded a miss. On the 4PM show I read Costco falling through the prior day's level as a breakdown — the kind that keeps going. The chart was drawn correctly: the level was right there, the break was clean on the screen. Price bottomed near the call instead and bounced about 3% over the following week. The ledger scored it a miss. The software displayed everything perfectly. The read was mine, and it was wrong.

That's the division of labor in one entry. The platform did its whole job. The error lived in the layer no platform touches.

Questions traders ask

Do I need NinjaTrader specifically for cycle analysis?

No. Everything in this article — panels, drawing tools, saved templates, deep history — exists in every serious charting platform. I've framed it for NinjaTrader 8 because that's a common desk setup and its chart templates make the one-time configuration reusable, but the method doesn't care what renders the bars. If your current platform shows clean daily bars, honest volume, and lets you draw vertical lines, trend lines, and horizontal lines, you have what you need.

Can an indicator find the cycle lows for me?

It can propose them; it can't confirm them. Detection tools are pattern matchers, and market rhythm is regular enough to be useful but not regular enough to be mechanical. Every count I trust has a human judgment in it — usually several. Treat any auto-detected low as a candidate awaiting your confirmation, never as an answer.

How much history should I load on the chart?

Enough to watch the longest rhythm you track complete several times, not once. One completion is an anecdote. Several completions, with spacing you've measured yourself, is the beginning of evidence. Practically that means erring on the side of more history than looks necessary, and actually scrolling back through it rather than letting it sit off-screen as decoration.

Should I set this up on intraday charts too?

After the daily map exists, not before. The daily chart carries the primary count; intraday charts inherit context from it. A trader with a beautiful five-minute setup and no daily map is navigating with a street map and no idea which city they're in.

Where does the chart setup end and the method begin?

Everything above is scaffolding — necessary, one-time, and honestly the easy part. The method is what you do on top of it: the counting itself, which I've kept generic here because it deserves its own articles. If you want the substance, start with the 80-day cycle — the workhorse rhythm this whole approach is built around — and then the FLD, the displaced line of past price that turns a cycle read into something you can act on, in what is a Future Line of Demarcation. The full framework, including how the pieces fit together and how we score our own public reads, is laid out in the methodology hub. The chart takes an afternoon to set up. The method is the actual work.

Tools our own desk actually runs. No vendor pays to be listed, and no link here earns us a commission.

Keep reading