Most retail traders in India who explore algo trading assume it is exclusively an intraday game — high-frequency entries, 15-minute candles, square-off by 3:20 PM. That assumption leaves one of the most trader-friendly strategy types almost entirely unexplored in the automation space: positional trading.
If you hold trades for days to weeks, rely on end-of-day signals, and have a day job that makes it impossible to monitor screens during market hours — positional algo trading was built for you. This guide covers what it is, which strategies work best when automated, and how to set one up on AlgoBulls without writing code.
What Is Positional Trading? (And Why It's Different from Intraday)
Positional trading means holding a trade open for more than one session — typically anywhere from two days to several weeks. Unlike intraday trading, where every position is squared off before market close, positional traders ride medium-term trends and are willing to hold through short-term noise.
In the Indian market context, positional trading most commonly happens in:
- Nifty Futures and Bank Nifty Futures — for index-level directional bets
- Large-cap equity futures — Reliance, HDFC Bank, Infosys, TCS
- Currency futures — USD/INR for macro-driven positional plays
The appeal for retail traders is straightforward. Positional strategies do not require you to watch a screen all day. Signals typically fire at or near market close — 3:15 to 3:30 PM — based on end-of-day (EOD) price data. A salaried professional can theoretically run a positional strategy with five minutes of attention per day: glance at the signal, confirm the order was placed, move on.
The reality, however, is that manual positional trading still fails most retail traders — just for different reasons than intraday trading does. More on that shortly.
Why Positional Traders Are Moving to Automation in 2026
Manual positional trading sounds manageable until you encounter its three structural failure points.
Missing the EOD signal window. Most positional strategies generate signals based on the closing price or the last 15-minute candle of the session. That means the entry decision happens between 3:15 and 3:30 PM — precisely when most salaried traders are wrapping up meetings, commuting, or unavailable. Miss the signal window and you either enter the next day at a worse price or skip the trade entirely. Over time, this inconsistency significantly degrades real-world performance versus backtest results.
Emotional exits during drawdowns. A positional trade designed to be held for eight to ten days will almost always experience at least one adverse session in between. Manually, that adverse session triggers doubt — "what if the trend has reversed?" — and traders exit early, missing the eventual move they set up the trade for in the first place.
Inconsistent re-entry after stop-loss. When a positional stop-loss is hit, the correct response is often to wait for the next signal and re-enter systematically. Manual traders frequently either re-enter too early (revenge trading) or stay out too long (loss aversion). Neither is systematic.
Automation addresses all three. An EOD algo monitors closing prices, fires the entry order in the 3:15–3:30 PM window without human intervention, holds the position through noise according to pre-defined rules, and exits only when the strategy conditions are met — not when the trader's emotions are.
Three Proven Positional Strategies That Work Well When Automated
Strategy 1: 20-Day EMA Crossover on Nifty Futures
The logic: Enter long when the 9-day EMA crosses above the 20-day EMA on the daily chart. Enter short when the 9-day EMA crosses below the 20-day EMA. Exit when the opposite crossover occurs or when a trailing stop-loss is hit.
Why it works when automated: EMA crossovers on daily charts are simple in theory but operationally difficult to manage manually. The crossover is confirmed only at the day's close — meaning the entry order needs to be placed in the final minutes of the session. An automated system does this precisely; a manual trader often hesitates, enters the next morning at a gap, and immediately distorts the strategy's entry price assumptions.
Backtest summary on AlgoBulls: A 3-year backtest of this strategy on Nifty Futures (2021–2024) shows reasonable trend-capture characteristics during directional markets and expected drawdowns during sideways, choppy periods — particularly in mid-2022 and late-2023. The strategy performs best when a minimum holding period filter (e.g., no exit before day 3) is added to reduce whipsaw exits.
Position size: Risk no more than 1% of total capital per trade. With ₹5 lakh capital, your maximum acceptable loss per position is ₹5,000 — set your stop-loss distance accordingly at the time of entry.
Strategy 2: Weekly Breakout on Bank Nifty Futures
The logic: Record the high and low of Bank Nifty Futures over the previous week (Friday's closing range). On Monday, if price breaks above last week's high, enter long. If price breaks below last week's low, enter short. Hold for three to five trading days with a trailing stop-loss.
Why it works when automated: The entry trigger on Monday morning is time-sensitive. A breakout above last week's high in the first 15 minutes of trading requires an alert, a decision, and an execution — all happening simultaneously during one of the most volatile windows of the trading week. Manual traders either miss the entry or enter impulsively without confirmation. An automated system has the breakout level pre-configured and fires the order the moment the condition is met, without delay or second-guessing.
Note: Bank Nifty no longer has a weekly options expiry following SEBI's 2024 rationalisation, but Bank Nifty Futures remain available for positional trades and are well-suited to this weekly breakout framework.
Strategy 3: RSI Mean Reversion on Large-Cap Equity Futures
The logic: On the weekly chart, when RSI drops below 30, enter long — the stock is oversold relative to its recent history and statistically likely to revert. When RSI rises above 70, enter short. Hold for five to ten trading days. Exit when RSI crosses back to neutral (45–55 range) or when stop-loss is hit.
Why it works when automated: RSI signals on weekly charts are infrequent — which is actually an advantage for a positional system. When a signal fires, it carries more statistical weight than an RSI signal on a 5-minute chart. The challenge manually is tracking RSI levels across multiple large-cap futures simultaneously. An automated system monitors the entire universe of instruments you define and flags — or enters — the moment any of them breach your threshold.
Best instruments: Reliance Industries Futures, HDFC Bank Futures, Infosys Futures, and TCS Futures tend to show reliable mean reversion characteristics on weekly RSI due to their high liquidity and strong institutional participation.
How to Automate a Positional Strategy on AlgoBulls (EOD Signal Execution)
End-of-day signal execution is technically distinct from intraday algo execution, and it is worth understanding why.
Intraday algos run continuously throughout the session, monitoring live price feeds and firing orders the moment intraday conditions are met. EOD algos, by contrast, evaluate closing price data — a clean, settled value — and place orders either in the last few minutes of the current session or at the open of the next session, depending on your configuration.
AlgoBulls Phoenix handles EOD execution around the market close window on NSE. When you configure a positional strategy, you define whether the signal is evaluated on the closing candle of the day, with the resulting order typically placed as a limit order at the next session's open for cleaner execution and tighter price control.
Building your positional algo on AlgoBulls Phoenix:
Depending on your background, AlgoBulls offers three paths to build and deploy a positional strategy:
Phoenix Copilot is the recommended starting point for most retail traders. Describe your positional logic in plain English — "Enter long on Nifty Futures when 9 EMA crosses above 20 EMA on the daily chart, exit on the opposite crossover or 1.5% trailing stop-loss" — and Copilot converts it into a fully deployable strategy. Supports India VIX filters and EOD signal conditions.
Phoenix Pro Build is the right choice if you have a specific, well-defined positional strategy but prefer to have AlgoBulls' expert team build, test, and deploy it for you. VIX-based entry filters and gap-risk parameters can be fully incorporated at this level.
Phoenix Python Build is for traders with coding experience who want complete programmatic control. Write your EOD signal logic in Python, define gap-risk exit conditions, incorporate India VIX as an entry filter, and automate the full positional workflow — including walk-forward parameter updates — without any platform constraints.
Once live, the platform monitors market data, evaluates your EOD signal at close, and places the order — without you needing to be at a screen.
Overnight Gap Risk: The India-Specific Problem Every Positional Algo Must Solve
This is the section most positional trading guides in India ignore completely. It is also one of the most operationally important risks for any automated positional strategy.
When you hold a Nifty Futures or equity futures position overnight, you are exposed to gap risk — the possibility that the next session opens significantly higher or lower than the previous close, bypassing your stop-loss entirely. Your stop-loss order exists in the exchange's system, but if the market opens on the other side of it, your order fills at the opening price — not your stop-loss price.
This is not a hypothetical. Indian markets have seen significant overnight gaps driven by:
- Geopolitical events — Nifty gapped down over 300 points on the morning Russia's Ukraine invasion began, February 24, 2022
- US Fed decisions — unexpected rate decisions announced after Indian market close regularly drive 100–200 point gaps at the next open
- Domestic political events — election results, budget announcements, or sudden policy shifts
- Global market crashes — US or Asian market sell-offs overnight translate to Indian gap-downs at open
A well-configured positional algo on AlgoBulls can address gap risk through two parameters:
Gap percentage exit trigger. Configure your strategy to evaluate the opening price versus the previous close on each session. If the gap at open exceeds a defined threshold — say, 1.5% against your position — the system triggers an immediate market exit at the opening price, rather than waiting for your original stop-loss level to be hit intraday. This limits your loss to the gap, rather than compounding it through an intraday continuation.
For example: You are holding a long Nifty Futures position from 24,000. Overnight, geopolitical news breaks. Nifty opens at 23,600 — a gap down of 400 points (approximately 1.67%). Your original stop-loss was set at 23,800. With a gap exit trigger configured at 1.5%, the algo recognises the gap exceeds your threshold the moment the market opens and exits immediately at 23,600, rather than waiting to see if 23,800 is breached intraday. This is disciplined loss containment — the kind that is structurally impossible to execute manually if the gap happens before you have seen the opening price.
Position sizing as the first line of defence. Gap risk also reinforces why maximum 1% capital risk per trade is the correct position sizing discipline for positional algos. If a severe gap event occurs and your exit is delayed, the damage is contained by size — not by hope.
Backtesting Your Positional Strategy: What Data Period to Use
Before deploying any positional strategy live, backtesting on AlgoBulls is non-negotiable. A few principles specific to positional strategies:
Use a minimum of three years of data. Positional strategies generate far fewer trades than intraday strategies — a weekly breakout system might produce 40–60 signals per year. A one-year backtest gives you a statistically thin sample. Three years captures at least one trending market, one sideways market, and one high-volatility event — the minimum range needed to assess whether a strategy is genuinely robust or just lucky in a particular market regime.
Include 2022 in your backtest window. The 2022 period — combining the Russia-Ukraine shock, sustained US Fed rate hikes, and Indian market volatility — was one of the most challenging environments for positional trend-following strategies in recent years. If your strategy survives 2022 with an acceptable drawdown, it is built on something real.
Avoid overfitting. Overfitting means tuning your parameters — EMA periods, RSI thresholds, stop-loss percentages — so precisely to historical data that the strategy performs perfectly in backtest and fails immediately in live trading. The warning signs: suspiciously high win rates (above 70% for trend-following), very tight parameter ranges that work, or performance that collapses when you shift the backtest window by even three months. Keep your parameters intuitive and round — 20-day EMA, not 17-day. RSI 30/70, not 28/73.
Walk-forward testing. After running your initial backtest, take the last six months of your data period completely out of the sample. Optimise your parameters on the earlier data only, then test those parameters on the held-out six months without adjustment. If performance holds reasonably well, you have a strategy with genuine out-of-sample validity.
Risk Management for Automated Positional Strategies
A few non-negotiable rules for any live positional algo:
1% capital risk per trade. With ₹5 lakh capital, maximum loss per trade is ₹5,000. Set your stop-loss distance at entry to reflect this. As your capital grows through compounding, recalculate position size periodically — do not lock in a fixed lot count and forget it.
Maximum simultaneous positions. Define an upper limit — typically two to three open positions at any given time for a retail capital base. An automated system will keep firing signals if conditions are met; without a position cap, you can find yourself holding five correlated long positions during a market downturn.
Circuit breaker handling. Indian markets have upper and lower circuit limits for individual stocks and indices. If a stock hits its circuit limit, your stop-loss order may not execute because there are no matching buyers or sellers. Configure your strategy to monitor for this scenario and flag it for manual review — it is one of the few situations where human intervention in an otherwise automated system is appropriate.
Monthly strategy review. Positional algos do not require daily supervision, but they do require periodic review. Once a month, check whether your strategy's live performance is broadly consistent with its backtest expectations. A significant divergence — particularly a sustained drawdown that did not appear in the backtest — is a signal to pause and investigate before continuing.
Getting Started: Your First Positional Algo on AlgoBulls
If you have a positional strategy in mind — even a simple one like the 20-day EMA crossover — the fastest path to testing it is:
- Sign up on AlgoBulls
- Choose your build path — Copilot if you want to describe your strategy in plain English, Pro Build if you want expert help, or Python Build if you are comfortable with code
- Configure your strategy using daily candles and EOD signal execution
- Run a backtest over a minimum three-year window and review results honestly — including drawdown periods
- If results are satisfactory, deploy live with minimum position size while you build confidence in the system's behaviour
Alternatively, if you have a more complex positional logic — multi-condition entries, VIX filters, gap-risk parameters — Altogether much more experience in coding, then Python Build is the best for you. Phoenix Copilot can convert your plain-English description into a deployable strategy, or Phoenix Pro Build connects you with AlgoBulls' expert team to build it properly from the start.
Explore solutions for retail traders or check current pricing to find the plan that fits where you are today.
Positional trading was always the most accessible form of systematic trading for retail investors with day jobs. Automation simply removes the last remaining manual bottleneck — the 3:15 PM signal window — and makes the whole thing genuinely hands-off.