The strategy is an example to learn the screens with, not a recommendation. Every number below, from the strikes to the premiums, is a worked example; your screen will show the live values for the day you build it.
Before you start
- A QuantPower account. The strategy builder is free; backtests cost 2 tokens each after 10 free a week.
- A connected broker, because live prices in QuantPower come from your broker account. The getting started tutorial covers connecting one. Without a broker, you can still lay out legs, but the prices and Greeks will not be live.
- A reason for the trade. Know why you are choosing an iron condor: it suits a view that the index will stay inside a range until expiry. Our iron condor strategy guide explains when traders use one and what can go wrong.
The strategy in this tutorial
An iron condor has four legs on the same expiry: a short call and a short put away from the price, each protected by a long option further out.
| Leg | Action | Option | Strike (example, Nifty at 24,000) | Role |
|---|---|---|---|---|
| 1 | Buy | Call | 24,600 | Wing: caps the loss above |
| 2 | Sell | Call | 24,400 | Collects premium |
| 3 | Sell | Put | 23,600 | Collects premium |
| 4 | Buy | Put | 23,400 | Wing: caps the loss below |
The short strikes are 400 points from the price; the wings are 200 points beyond them. One Nifty lot is 65 units.
Part 1: Lay out the position in the strategy builder
Step 1: Open the strategy builder and pick the expiry
- Open Strategy builder from the menu, or from the option chain.
- Choose Nifty and the weekly expiry you want. Since 1 September 2025, NSE's weekly and monthly expiries fall on Tuesday.
- The builder shows the chain for that expiry with the live price of each strike.
Step 2: Add the four legs
- Tap the 24,600 call and set it to Buy. Tap Buy / Sell on a leg to switch it.
- Tap the 24,400 call and set it to Sell.
- Tap the 23,600 put and set it to Sell.
- Tap the 23,400 put and set it to Buy.
- Set each leg to 1 lot.
The legs panel lists the four legs with their strike, side, lots and price.
Step 3: Read the payoff
As soon as the legs are in, the builder draws the payoff and shows the numbers that matter.
Suppose the live premiums are: 24,600 call ₹25, 24,400 call ₹60, 23,600 put ₹70, 23,400 put ₹30.
| Reading | How it is worked out | Example |
|---|---|---|
| Net credit | (60 − 25) + (70 − 30) = 75 points | ₹4,875 for one lot (75 × 65) |
| Max profit | The net credit, if Nifty expires between 23,600 and 24,400 | ₹4,875 |
| Max loss | Wing width minus credit: 200 − 75 = 125 points | ₹8,125 for one lot |
| Upper breakeven | Short call + credit: 24,400 + 75 | 24,475 |
| Lower breakeven | Short put − credit: 23,600 − 75 | 23,525 |
The builder also shows:
- Chance of profit, an estimate from the option prices of how often the index finishes between the breakevens. It is a model figure, not a forecast.
- Net delta, close to zero for a balanced condor: the position gains little or loses little from a small move.
- Gamma, negative for a short condor: the position's delta changes faster as expiry nears, which is why the last day carries the most risk.
- Theta per day, positive: the position earns from time passing if nothing else changes.
- Days to expiry.
- Margin needed (approx.): because the wings cap the loss, an iron condor usually blocks much less margin than selling the same two options without wings.
Move the slider or the date on the chart to see the position's value today, not only at expiry. A condor that looks safe at expiry can show a loss today if the index moves sharply early in the week.
How the builder works out these numbers
The payoff at expiry is simple arithmetic. At each index level on the chart, the builder works out what each option is worth at expiry, which is its intrinsic value, adds up the four legs with their signs and lot size, and adds the credit received. That is why the line is flat between the short strikes, slopes between each short strike and its wing, and is flat again beyond the wings.
The payoff today is different, because the options still have time value. The builder prices each leg with an option pricing model, using the time left and each strike's implied volatility from the live chain, and draws a curved line that moves towards the expiry line as the days pass. When you move the date on the chart, you are asking how that curve will look on a later day if volatility stays the same.
The chance of profit comes from the same model: it estimates how likely the index is to finish between the breakevens, given the volatility the options imply. It is an estimate under the model's assumptions, not a forecast, and it ignores the stops you will set.
The margin needed is an estimate of what the exchange's margin rules would block for these four legs together. Your broker blocks the actual figure when the orders go in, and it can differ, for example on expiry day or when the exchange changes its margin files.
Step 4: Save it and share it if you like
Tap Save strategy and give it a name, such as "Nifty weekly condor 400/200". Share link creates a link to the layout if you want to show it to someone. Saving places no order. A clear name helps later: include the index, the expiry type and the strike distances, so a list of saved layouts reads at a glance. You can reopen a saved layout from the builder at any time, change a leg, and save it again or under a new name to compare two versions side by side.
Why an iron condor behaves the way it does
An iron condor is a bet on a range, paid for by time. Each day that passes without a large move, the four options lose value, and because the trader sold the two that are closer to the price and bought the two further away, the short options lose more than the long ones. That difference is the position's theta, and it is why the builder shows a positive figure for theta per day.
The cost of that steady income is gamma. When the index moves towards a short strike, the short option's delta grows quickly, and the position starts to lose faster than it earned. Gamma is small early in the week and large on expiry day, which is why a move of 150 points on a Monday may cost little while the same move on Tuesday afternoon can take the whole week's credit and more.
Volatility matters too. A condor is short vega: if implied volatility rises after entry, all four options gain value and the position shows a loss even if the index has not moved. This is why many traders avoid opening a condor just before an event that can lift volatility, such as a policy decision or a budget, and why the builder's payoff today can differ from the payoff at expiry.
The wings change the shape of the risk. Without them, the position is a short strangle, and the loss on a large move has no ceiling. With them, the most the condor can lose is the distance between the short and long strikes, less the credit. The builder's max loss line shows this ceiling, and the margin needed falls because the exchange's margin system recognises the cap.
Choosing the strikes
Strike choice is a trade-off between the credit and the chance of keeping it. Closer short strikes collect more but are reached more often; further ones collect less but leave more room.
Suppose, as an example, the live premiums for three choices on the same day look like this:
| Short strikes from the price | Wings beyond | Net credit (points) | Max loss (points) | Credit to max loss |
|---|---|---|---|---|
| 300 | 200 | 110 | 90 | 1.2 to 1 |
| 400 | 200 | 75 | 125 | 0.6 to 1 |
| 500 | 200 | 45 | 155 | 0.3 to 1 |
The closer condor pays more for each rupee of risk but needs the index to stay in a tighter range. The further one pays little for each rupee of risk but is reached less often. None of these is right or wrong; a backtest of each over the same weeks shows how often each range was broken and what that cost after charges.
Two readings on the option chain help. The expected move, worked out from the at-the-money straddle, shows the range the market prices in for the expiry: short strikes inside it are being sold cheaply relative to what the market expects. The delta of each strike gives a rough sense of how far out it is; many traders sell strikes with a delta between 0.10 and 0.20. A rule leg can pick strikes by delta directly, so the distance adjusts to the volatility of the week.
Sizing the position
Size the condor from its max loss, not from its credit.
Take a trader with ₹3,00,000 of capital who will not risk more than 2% of it on one week's condor: ₹6,000. With a max loss of ₹8,125 per lot, one lot already risks more than that if held to the worst case, so the trader either accepts a stop well inside the max loss, such as the ₹6,000 M2M stop in step 9, or narrows the wings to reduce the max loss. Two lots would double every figure: ₹9,750 of credit and ₹16,250 of max loss, and roughly double the margin.
Brokerage is part of the size question. The four legs entered and exited place eight orders; at ₹20 an executed order that is ₹160 in brokerage before STT, exchange charges and GST, about 3% of the ₹4,875 credit for one lot. A stop that fires and re-enters adds more.
What happens during the week
Follow the example condor through a week once it is live.
- Thursday 10:00. The algo picks the strikes from the price at 10:00 using the rule legs, sends the two wings, and once both are filled sends the two short legs. The card shows the four fills and the M2M.
- Friday and Monday. If the index stays near the middle, the M2M rises slowly as theta works. If the lock-and-trail threshold is reached, part of the profit is locked.
- A move towards a short strike. Suppose Nifty rises 300 points by Monday. The short call's premium may double; if it reaches the 100% stop, that leg exits on its own, and with "exit this leg only" the put side stays open. With "re-execute", a new short call is sold at a fresh strike picked from the new price.
- Tuesday, expiry day. Gamma is at its highest. Any whole-strategy stop, target or delta band can still fire. At 15:10 the exit time closes what is left, buying back the short legs first.
The activity log records each of these events in one plain line, and "Copy log" copies the day.
A checklist before you switch it on
- All four legs on the same expiry, wings outside the short strikes.
- Rule legs if the condor should run every week.
- Product set to Overnight if you hold across days.
- A stop on each short leg, a whole-strategy M2M stop, and an exit time.
- A backtest over at least a year, read week by week, with costs.
- Three or four expiries in Forward test.
- A daily loss limit and Smart Exit set for the account.
- One lot to start.
Part 2: Turn the layout into an algo
A saved layout is a plan. To run it with entry and exit rules, turn it into an algo.
Step 5: Run as algo
Tap Run as algo. QuantPower opens the algo builder in Algos → Option bots with the four legs filled in. You could also start from the Iron Condor template in Option bots; a template is an open sample, and once loaded it is your own algo.
Step 6: Choose fixed or rule legs
Each leg can be:
- Fixed: this exact strike and expiry. When the contract expires, the algo stops and says so, and you edit it to move to the next expiry.
- Rule: the strike is picked fresh at each entry, so the algo runs week after week.
For a condor that runs every week, use rule legs. With Nifty's 50-point strike gap, 400 points is 8 strikes and 600 points is 12:
| Leg | Rule |
|---|---|
| Buy call | OTM 12, weekly expiry |
| Sell call | OTM 8, weekly expiry |
| Sell put | OTM 8, weekly expiry |
| Buy put | OTM 12, weekly expiry |
Other strike rules are available: a premium (nearest to, at or above, or at or below a value), a Greek such as delta, a multiple of the at-the-money straddle premium, a share of it, or a percentage from the at-the-money strike. The strike can be counted from spot, futures or a synthetic future. If the prices or Greeks a rule needs are missing at entry, the algo waits and says why; it never guesses a strike.
Step 7: Set the product, the days and the entry
- Product: Intraday or Overnight. A condor held from Thursday to Tuesday needs Overnight.
- Days: every trading day, or the weekdays you pick. Market holidays are skipped. For a weekly condor entered on Thursday, choose Thursday only.
- Entry mode: At the time enters every leg at the entry time. The alternatives are Wait & trade, where each leg waits for a move in its premium or the underlying, and ORB, which enters on a break of the opening range.
- Entry time: for example 10:00, after the opening volatility settles.
- Entry order type per leg: market (the default), limit with a buffer, stop-limit, or modify until filled, which moves an unfilled entry to the last price up to 10 times.
Buy legs always go first, and sell legs go only after the buys are filled, so the wings are in place before the short options. On exit it is the reverse: the short legs are bought back first.
Step 8: Set exits on each leg
Each leg can carry its own target and stop-loss, in points, per cent, underlying points or per cent, or a Greek, counted from the traded price or the price the entry was decided on. For a condor, a common layout is:
- Stop-loss on each short leg: for example 100% of its entry premium, so a short call sold at ₹60 exits if it reaches ₹120.
- On a hit: exit this leg only, so the untested side stays open, or exit all legs.
- Trail SL: for every X the leg moves in your favour, the stop moves Y in your favour, only ever tighter.
- SL to cost: move a leg's stop to its entry price once it is X in profit, or when another leg's stop is hit.
- After a hit: Re-execute to enter the leg again at a fresh strike, or Reverse, 1 to 20 times a day.
Exits are market orders that only reduce the position. They can never open a new one. If an exit order is refused, the algo tries again up to 8 times with a growing gap, and the card shows what is still owed.
Step 9: Set exits for the whole algo
| Setting | Example for this condor |
|---|---|
| Exit time | 15:10 on expiry day, as a next-day exit if entered earlier in the week |
| M2M stop in ₹ | ₹6,000 for the whole condor |
| M2M target in ₹ | ₹3,500, about 70% of the credit |
| Net delta band | Exit if the condor's net delta leaves −0.30 to +0.30 |
| Lock and trail | Once M2M reaches ₹2,500, lock ₹1,500; raise the lock by ₹500 for every ₹500 more |
| What a hit does | Exit all legs |
Choose how often targets and stops are read: on every tick, or once per 1, 3, 5 or 15-minute candle close. The entry time, the exit time and exits already owed are never delayed.
Step 10: Save it, switched off
Tap Save. A new algo is off. Nothing happens until you switch it on, in Forward test or Live, and you can edit every part while it is off. The algo card shows its legs and rules in plain words; read them back once before you test.
Part 3: Test before anything runs
A saved algo has rules but no evidence. Testing gives it evidence in two stages: past data first, then live prices with test money. Each stage can show a problem the other cannot, so skip neither.
Backtest
Open the algo card and run an option strategy backtest over a year or more of Thursdays-to-Tuesdays. The backtest picks the strikes at the entry time each week, fills each leg at its option price with slippage, checks every leg and the whole condor every minute until the exit, and deducts brokerage and every statutory charge. Read the exit reasons, the worst weeks, the longest losing streak and the unseen-days verdict. The tutorial on how to backtest a strategy walks through the report.
Forward test
Switch the algo on in Forward test for three or four expiries. It runs on live prices with test money, with orders and M2M that behave like a broker's book, and nothing reaches your broker. It costs 100 tokens per algo per 28 days. Compare its weeks with the backtest for the same weeks.
Live
Only then switch it on Live, with one lot. Before the first live week, set a daily loss limit and Smart Exit in Algos → M2M.
Switching on runs a set of checks: the broker is connected and signed in, the kill switch is off for F&O, today's loss is inside your limit, the algo has no more than 6 legs, and your tokens cover the charge of 200 tokens per 28 days, pro-rated if the cycle is part-way through. If a check fails, the algo stays off, the reason is shown, and no tokens are taken. An algo that ran in Forward test earlier in the same paid cycle pays only the difference when it goes live.
Mistakes to avoid with a first condor
- Choosing strikes for the credit alone. A rich credit usually means short strikes close to the price. Read the max loss and the breakevens before the credit.
- Holding into expiry afternoon without a plan. Gamma peaks on the last day. Decide in advance whether the algo exits earlier, and set the exit time accordingly.
- Forgetting the wings on one side. Without a wing, that side's loss has no ceiling and the margin jumps. The builder's max loss line shows "unlimited" or a very large figure when a wing is missing.
- Stopping both sides on one move. A stop that exits all legs when one side is tested gives up the untested side's remaining credit. "Exit this leg only" keeps it; choose deliberately.
- Testing only a calm year. A condor tested only on quiet months will look better than it is. Make sure the backtest period includes sharp moves and event weeks.
- Ignoring the cost of adjustments. Each re-entry adds orders and charges. The backtest report shows the charges line; read it.
When to change the plan
Some weeks are not condor weeks. A trader who runs a weekly condor usually decides in advance which conditions pause it: a scheduled event such as the Union Budget or a policy announcement inside the week, implied volatility far below its usual range, or a recent run of losses. QuantPower makes this a one-tap decision: Pause stops new entries while open legs keep their stops and exit time, and Resume new entries undoes it. Writing the pause conditions down before the week starts keeps the decision calm.
Reading the algo card once it runs
Once the condor is switched on, in Forward test or Live, its card becomes the place to watch it. The card shows the algo's state, today's legs with their strikes and fills, the M2M, and one line for anything the algo is waiting on, such as "Sign in to your broker before the entry" or prices it needs before it can pick a strike. The activity log below it records every entry, exit, re-entry, change and refusal in one plain line each.
From the card you can Pause new entries, Stop algo and square off its positions, Stop algo, keep positions (the kept positions are then yours to manage, with no stop or exit time on them), or Restart today, which runs it again in the same place it ran before. Several algos can be paused or stopped together from the list.
Variations to try in the builder
The same steps build other strategies. Lay each out in the builder first and read its payoff.
| Strategy | Legs | When traders use it |
|---|---|---|
| Iron fly | Sell the at-the-money call and put, buy wings either side | A view of very little movement; higher credit, narrower profit zone |
| Short strangle | Sell an out-of-the-money call and put, no wings | Range view without wings; loss is not capped and margin is higher |
| Bull put spread | Sell a put, buy a lower put | A view that the index stays above a level |
| Bear call spread | Sell a call, buy a higher call | A view that the index stays below a level |
| Long straddle | Buy the at-the-money call and put | Expecting a large move either way |
The option strategy builder page lists every template and what the builder shows.
Common problems
| Problem | Likely cause | Fix |
|---|---|---|
| Prices and Greeks are blank | No broker connected, or the broker is signed out | Connect or sign in from Brokers |
| The margin looks too high | A wing is missing or on a different expiry | Check all four legs are on the same expiry |
| The algo will not switch on | Broker signed out, kill switch on, loss limit reached, more than 6 legs, or not enough tokens | Read the reason shown; no tokens are taken for a refused switch-on |
| A fixed leg's algo stopped | The contract expired | Edit the leg to the next expiry, or use rule legs |
| A short leg entered before its wing | It cannot: buy legs go first | If a wing is refused, the algo closes the legs already in and stops with the reason |
Next steps
- Backtest the condor and read the report.
- Learn how to set entry and exit rules in more detail.
- Set up Smart Exit and the daily loss limit before going live.
Start with 500 free tokens
Connect your broker, build a strategy and test it on paper before a single live order goes out.
Frequently asked questions
Can I build futures and stock strategies too?
Yes. Option bots take futures, stocks, stock options, commodity and currency contracts as well as index options, picked by search. An algo with stock legs runs intraday.
Does saving a strategy place orders?
No. Saving a layout in the builder places nothing, and a new algo is saved switched off. Orders go out only when you switch an algo on Live, or when you place an order yourself.
Can I change a strategy after testing it?
Yes, while the algo is off. If it still holds positions, its legs, product and quantity cannot be changed until you square off, but its targets, stops and times can.
Related guides
- How to set entry and exit rules: each setting in detail
- How to backtest a strategy: reading the report
- How to set up an algo bot: switching on, watching and stopping