Alert Systems

ORB Trading Alerts

Alerts treated as infrastructure around the opening range boundary: where to place them, why an overgrown alert list stops being heard at all, and the gap that has to stay open between a notification and an order.

What We Cover

Alerts Are Plumbing, and Plumbing Deserves Design

An alert is a small piece of infrastructure sitting between a level on a chart and a person who needs to know when price reaches it. Most traders set them casually, one at a time, in response to whatever is happening that morning, and end up with a system nobody designed. That system then shapes behaviour, because what you get notified about is what you pay attention to. Treating alerts as a built thing, with rules about what gets one and what does not, is a modest amount of work with a disproportionate effect.

The Boundary Is the Natural Place for One

An opening range produces two specific numbers at a known time, which makes it unusually well suited to alerting. There is no interpretation required and no ambiguity about the level. Once the formation period closes, the high and the low can be handed to the platform and the screen can be left alone. This replaces continuous watching with a defined trigger, and continuous watching is not a neutral activity. It generates opinions, and opinions generated while waiting tend to arrive in the form of early entries.

Too Many Alarms Is the Same as None

The failure mode of any notification system is volume. An alert that fires several times a session, most often for something that needs no response, teaches the person receiving it to ignore it. That learning is not a choice and it cannot be undone by resolving to take them more seriously. The only real defence is scarcity, which means deleting alerts that have expired, refusing to set them for levels that do not change any decision, and keeping the number small enough that each one still means something.

Notification and Execution Are Different Things

An alert tells you price touched a number. That is all it tells you. It does not tell you the break was supported, that the range was worth trading, or that your rules were satisfied, and it certainly does not constitute a decision to enter. Alerts that arrive on a phone are especially prone to being answered with a reflex, because the interface is designed for a quick response. Keeping the gap between the notification and the order explicit, with the checks that belong in it, is the difference between an alert that helps and one that simply speeds up mistakes.

Wiring Up the Alerts

The articles here treat alerting as a subject in its own right rather than as a platform feature. One covers setting alerts at the range boundary and what that buys you compared to watching. One covers alert fatigue, how it develops and what actually reduces it. One covers the gap between a notification and an order, why it collapses so easily, and how to keep it open.

Latest Guides

Alert Fatigue and the Alarm You Stop Hearing

Detailed view of a financial chart displaying a bearish trend with red and green candlesticks.

The first alert of the morning gets full attention. By the sixth, the phone is picked up, glanced at and put down without the chart being opened. Nothing was decided. No rule was broken. The notification simply stopped carrying information, because most of the previous ones did not require a response and the brain adjusted accordingly. This happens to careful people with well intentioned setups, and it happens gradually enough that it is rarely noticed while it is underway.

The Adjustment Is Automatic

Stock market data chart showing trends in red and green. Perfect for financial and business themes.

Ignoring a repetitive signal that usually means nothing is not a discipline failure. It is a sensible adaptation, and it operates below the level of choice. A sound that has been followed by nothing important on most of its recent occurrences stops registering as urgent, whatever the person hearing it intends.

Which is why the common remedy fails. Deciding to take alerts more seriously addresses the wrong layer. The response is being calibrated by the actual history of what those alerts have meant, and that history is not changed by an intention. Fix the population of alerts and the response corrects itself, without any effort being required.

How the List Grows

Close-up of a digital market analysis display showing Bitcoin and cryptocurrency price trends.

Nobody builds a noisy alert setup deliberately. It accumulates. A level from a session two weeks ago that was never cleared. An alert set at a round number out of curiosity. Duplicates on the same level across two devices. Alerts on instruments no longer traded, left behind from a period of experimenting.

Each addition looked harmless on its own. Together they generate a stream of notifications with no consistent meaning, and it only takes a modest number of irrelevant ones to dilute the few that matter. The problem is structural rather than a matter of any single bad alert.

Scarcity Is the Only Real Fix

The workable rule is that an alert exists only if its firing would change a decision. Applied honestly this removes a great deal. An alert on a level you would not trade fails the test. An alert on an instrument you are not going to act on today fails it. An alert set because a level looks interesting, with no defined response attached, fails it clearly.

What survives is a small set, often just the two boundaries of the current session's range. A short list is not a cosmetic improvement. It is what makes each remaining notification meaningful, because meaning here is entirely a function of how often the thing fires without needing anything.

Different Sounds for Different Jobs

Where a platform allows it, separating alert types by sound or channel preserves attention better than a single undifferentiated stream. A trigger level that demands an immediate look should not arrive in the same form as a background note about an instrument being tracked casually.

The value is that fatigue then develops only in the channel that earns it. The routine notifications can be safely tuned out without dulling the response to the one that matters. This works only while the separation is respected, and the temptation to promote something borderline into the urgent channel is the thing that erodes it.

A Regular Clear Out

Fatigue is best treated as maintenance rather than as a problem to be solved once. Reviewing the full list at a fixed interval, weekly is usually enough, and deleting anything whose purpose is no longer obvious keeps the population honest.

The useful test during that review is whether you can say, for each alert, what you would do if it fired right now. Anything without a clear answer is contributing noise and nothing else. Removing it costs nothing, since an alert with no attached response was never going to produce an action anyway. It was only ever going to produce one more notification, teaching you a little more thoroughly to disregard the next one.

An Alert Is Not an Order

Close-up of stock market trading screen displaying financial growth and charts.

The alert fires. Within a few seconds an order has been placed. Described that way it sounds efficient, and sometimes it is, but the sequence has skipped something. An alert reports a single fact, that price touched a specified number. Everything else that should stand between that fact and a live position, the checks, the conditions, the question of whether this session was one to trade at all, has been compressed into the moment it took to reach for the screen.

What the Notification Contains

Detailed view of a stock report displaying a market performance graph with data trends.

It is worth being literal about this. The alert knows one level and one crossing. It has no view on how price arrived there, whether the move carried any participation, how tall the range was relative to normal, or whether the crossing was a sustained push or a single spike that immediately withdrew.

Every one of those is part of deciding whether the break is worth taking, and none of them are in the notification. The alert is a prompt to look. Treating it as a conclusion is not an aggressive interpretation of the tool, it is a straightforward misreading of what the tool reports.

Why the Gap Closes

Financial candlestick chart showing market trends and data visualization.

Two forces squeeze it. The first is urgency, some of it real. A break can move quickly, and the belief that hesitation is expensive encourages skipping straight to the order. The second is the design of the device the alert usually lands on. A phone notification is built to be answered immediately, in one gesture, and the surrounding interface offers a route from notification to order with very little in between.

This combination is why the collapse happens even to traders who have a perfectly good checklist. The checklist lives somewhere else, on paper or in a routine performed at a desk, and the notification arrives in a context that has no room for it.

What Belongs in the Gap

The content varies by strategy, but the shape is consistent. Whether the range height falls inside the acceptable band. Whether the crossing came with any expansion in participation. Whether this session was already assessed as one to skip. Whether the stop level implied by the setup produces a position size within the day's limit.

Most of these can be answered in well under a minute by someone looking at a chart. The problem is never that they take too long. It is that they do not get asked, because the alert did not ask them and nothing else in the sequence prompted them either.

Building the Gap Into the Process

Intention alone will not hold a gap open under time pressure. Structure will. The most direct arrangement is to route alerts somewhere that cannot place an order, so the notification necessarily leads to a chart rather than a ticket. The additional step is small and its whole purpose is to exist.

A written checklist visible from the trading position works on the same principle, as does the habit of speaking the checks aloud, which is slower than thinking them and therefore harder to skip. None of this is sophisticated. It is a deliberate piece of friction placed exactly where the process is known to fail.

The Legitimate Automated Case

There is a version of alert to order that is entirely defensible, and the distinction is worth drawing clearly. A resting order placed in advance at the range boundary, with size and stop already determined, is not a reflex. Every check happened before the order existed, and the execution is simply the mechanical consequence of a decision already made.

That is the opposite of answering a notification with a manual order in the moment. The first case front loads the judgement and automates only the execution. The second automates the execution and hopes the judgement will keep up, which under time pressure it reliably does not. If the intention is to act instantly on a boundary being crossed, the honest way to do it is to place the order beforehand, not to try to reproduce a considered decision in the seconds after an alarm goes off.

Setting Alerts at the Boundary Rather Than Watching

Close-up of a cryptocurrency market graph focusing on BNB price and volume trends over time.

Once the formation period closes, the session has produced two numbers that will not change. They are known, they are unambiguous, and nothing about them requires interpretation. That combination makes them close to ideal material for an alert, and yet a great many traders still spend the following period staring at a chart, waiting for price to reach a level a machine could watch for them without getting bored.

What Watching Actually Costs

A close-up view of a cryptocurrency trading chart displayed on a monitor, showcasing market trends.

The cost is not attention in the abstract. It is the specific tendency of a watched chart to generate opinions. Twenty minutes spent observing price approach a level produces a view about whether it will get there, and that view was not part of the plan. It arrives with a feeling of insight because it was formed by looking rather than guessing, which makes it more persuasive than it deserves to be.

Those views turn into the familiar errors. Entering slightly early because the move looks certain. Deciding the level will not be reached and walking away just before it is. Adjusting the level itself because price has been hovering nearby and a slightly different number now seems more sensible. None of these require poor discipline. They require nothing more than sustained exposure to a moving chart.

Where to Put Them

Vibrant candlestick chart showcasing cryptocurrency trends with space for copy in Valencia, Spain.

The obvious placement is at the range high and the range low, exactly. That is the level the rules refer to, and any offset from it introduces a second decision that then has to be justified.

Some traders prefer an alert set slightly inside the boundary so the notification arrives while price is approaching rather than after it has crossed. This is a reasonable trade and it should be made knowingly. It buys warning time and it costs precision, because price frequently comes close to an edge without touching it. Setting both, an approach alert and a boundary alert, is a third option that works if and only if the discipline exists to treat the first one as information and not as a trigger.

Set Them Once, at a Known Time

The mechanical advantage of an opening range is that the moment to set the alerts is fixed. The period ends, the two numbers exist, the alerts go on. It is a repeatable step that takes very little time and can be done identically every session.

That repeatability is worth more than it sounds. A routine performed at the same point every day is far harder to skip than one performed whenever it occurs to you, and skipping is the main failure mode. An alert not set is not a small error. It is the difference between a trigger arriving as a notification and a trigger arriving as something noticed late, from a chart glanced at while doing something else.

Clearing Them Is Part of the Job

An alert that has fired, or that belongs to a session which is finished, should be removed. Otherwise the list accumulates until it contains levels from days ago that mean nothing, and the whole arrangement starts producing notifications that are not worth reading.

The tidy version is a short routine at the end of the session that clears everything set that morning. Since opening range levels are only relevant to the session that produced them, nothing needs to survive to the next day, which makes the clearing rule simple. Anything left over is stale by definition.

What Alerts Cannot Do

An alert reports that a number was touched. It has no view about how the number was touched, and that distinction is the whole subject of whether the break is worth taking. A level tagged by a single fast spike and a level crossed by steady sustained trade produce the same notification.

There is also the question of what happens in the gap between the alert firing and the chart being looked at. On a fast move that gap can be expensive, and no alerting arrangement removes it. What alerts genuinely provide is freedom from continuous watching and a reliable prompt at the moment something relevant occurs. That is a real benefit and a limited one, and expecting more of it than that is how people end up trusting a notification with a decision it was never capable of making.

↑