What is Edge Audit?
Reviewed by Karthikeyan Anbarasan (Founder, TradeLyser) · Updated 19 Oct 2026 · Editorial policy
Running the audit
- Pull every closed trade for the period and group it by setup tag. Use net P&L after brokerage, STT and other charges.
- Check the sample. Under 30 trades a setup is "not enough data"; around 100 the numbers become dependable.
- For each setup, work out expectancy in R, win rate, average win and loss, profit factor and maximum drawdown.
- Compare with the last audit and with the most recent 20 or 30 trades, as in Figure 1, to see the direction of travel.
- Check rule adherence on the setup’s trades. If adherence was low, the audit is measuring execution, not the edge.
- Write a decision for each setup, keep, resize or pause, with the date, and review it at the next audit.
Worked example: three setups
| Setup | Trades | Expectancy | Net P&L (1R = ₹2,000) | Decision |
|---|---|---|---|---|
| Opening range breakout | 84 | +0.32R | +₹53,760 | Keep at current size |
| VWAP reclaim | 41 | +0.11R | +₹9,020 | Keep; recheck next audit |
| Expiry-day scalps | 63 | −0.18R | −₹22,680 | Pause; paper trade only |
Illustrative. At ₹2,000 per R, +0.32R is ₹640 per trade, so 84 trades make ₹53,760; +0.11R is ₹220 per trade, ₹9,020 over 41 trades; −0.18R is −₹360 per trade, −₹22,680 over 63 trades. The account made +₹40,100 overall; without the scalps it would have made +₹62,780. Note the sample sizes as well: the VWAP reclaim has 41 trades, enough for a rough read but not a confident one, so it stays at current size rather than being scaled up.
Edge problem or execution problem
Edge decay
Execution leak
A quick test is to filter the setup’s trades by execution grade. If the A-grade trades alone are still positive and the C-grade trades drag the total down, the setup is fine and the leak is execution. If even the A trades have turned negative over 30 or more trades, the edge itself has weakened. The mistakes below make either answer harder to read.
- Auditing setups with 10 or 15 trades and treating the result as final.
- Using gross P&L. A setup with a thin edge can turn negative after charges.
- Mixing two setups under one tag, so a good one and a bad one average out.
- Changing the setup’s rules halfway through the period, so the audit measures two different things.
Reference guide
| Context | Value | Reading |
|---|---|---|
| Per-setup numbers, net of charges, 30+ trades each | Meaningful audit | Enough data to separate a working setup from a lucky run |
| One account-level number for all trades | Hides the answer | A strong setup can carry a losing one for months; split by setup tag |
| Setup paused after five losses in a row | Premature | Losing streaks are normal; judge on expectancy over a full sample |
Questions
What is an edge audit in trading?
A scheduled review of each setup’s results, net of charges, to check that it still has positive expectancy. It ends with a keep, resize or pause decision for each setup.
How often should I audit my trading edge?
Monthly for active intraday or F&O traders, quarterly for slower swing traders. What matters is that each setup has enough new trades between audits to say something.
How many trades do I need for an edge audit?
At least 30 per setup for a rough read, and closer to 100 before trusting the numbers. With fewer, record the result as "not enough data" rather than acting on it.
What is a good expectancy in an edge audit?
There is no universal figure. It should be positive after charges, hold up over 30 or more trades and stay roughly stable between audits. A small positive expectancy over many trades can be worth more than a large one over a few.
What should I do if a setup has lost its edge?
First check adherence; if the rules were not followed, fix execution before judging the setup. If they were, reduce size or pause it, paper trade it, and only bring it back if a fresh sample is positive.