Risk management best practices for automated trading
Automating a strategy doesn't remove the risk. It removes your hand from the trigger, which means whatever risk rules you had in your head need to live in the command instead. Autoview places exactly what the command says, at the size and stop it's told, with no judgment layered on top. That's the whole point of automation, and it's also why a sloppy command is a sloppy trade, just faster.
Autoview doesn't manage risk. Your command does.
This is worth stating plainly, because people sometimes assume the platform is doing something protective in the background. It isn't. Autoview reads a symbol, a side, a size, and whatever stop or target you attached, and sends exactly that. If the command has no stop, none gets placed. If the size is too large for the account, it trades too large. The risk management is whatever you wrote into the alert, nothing more and nothing less.
That puts the actual practice back where it belongs: a consistent plan for how much you risk per trade, applied the same way every time an alert fires. A few things make that plan hold up once it's automated rather than manual.
Size the position before you worry about anything else
Position size decides how much a single bad trade can cost you, and it's usually the first control worth getting right. Autoview's quantity parameter can be set as a percentage of your account balance rather than a fixed number, so the same command scales automatically as your balance changes. Keeping that percentage small on any individual trade, rather than sizing for a best case, is the single biggest lever most traders have. The exact parameter and its accepted values are on the command reference.
Leverage compounds this. A larger position moves the same dollar amount faster in both directions, so a size that felt reasonable unlevered can be a very different bet once leverage is applied. If you use leverage at all, size around the leveraged exposure, not the margin you put up.
Attach a stop to the command, not to your memory
A stop-loss you plan to add manually after the trade fires is a stop-loss that depends on you being at your screen, which defeats the reason you automated in the first place. Autoview supports stop parameters as part of the same command that opens the trade, either as a distance from your fill or as a fixed price, along with a take-profit on the other side. Both are documented on the command reference, and both travel with the order from the moment it opens.
A trailing stop is worth knowing about for the same reason: it follows the market in your favor rather than sitting at one fixed level, which matters for a strategy meant to run without you watching every candle. Whether a given exchange supports it varies, so check the command reference and that exchange's own guide before assuming it's available.
One trade at a time, sized against the account, not the plan in your head
A percentage-based quantity is measured against your account balance when you're opening a position, not against some target you're mentally building toward. If your plan calls for growing into a larger position over several alerts, work out the size you actually want at each step and send that number, rather than assuming the percentages will stack the way they would on paper. The command reference covers exactly how sizing behaves on opens versus closes.
Diversifying across uncorrelated symbols, and capping how many positions can be open across a strategy at once, are plan-level decisions Autoview doesn't make for you either. They belong in whatever generates your alerts, encoded the same way your entries are.
A worksheet, not just a mindset
Everything above is easier to hold onto as a plan once it's written down against actual numbers rather than kept as a general intention. Fill this in for one account before you turn a strategy loose on it, and revisit it whenever your balance or leverage changes materially.
| Item | What to write down |
|---|---|
| Notional exposure | Position size x price, per trade and summed across every open position. This is what's actually at risk in the market, not the margin you posted. |
| Max loss per trade | The dollar amount your stop-loss represents at your planned size. If you don't know this number before the trade opens, the stop isn't doing its job yet. |
| Leverage | The multiple between notional exposure and your posted margin. Write down the number, not just "I use leverage," since sizing decisions should scale with it explicitly. |
| Margin | How much of your account balance is committed as margin right now, and how much stays free. A margin call happens when this runs out, not when your strategy decides it should. |
| Spread and slippage | An estimate, from your own log or the venue's own data, of how far your actual fill lands from the price your alert fired at. Wider on illiquid symbols and during volatility; a plan sized for a tight spread can be wrong on a wide one. |
| Correlation | Whether your open positions move together. Five "different" trades that are all long crypto against USD are one concentrated bet, not five diversified ones. |
| Daily stop | A dollar or percentage loss for the day at which you stop taking new signals, decided in advance, not renegotiated in the moment. |
| Kill switch | See below -- Autoview doesn't have a built-in one, so write down the actual steps you'd take. |
| Outage response | What happens to your open positions if Autoview, your alert source, or the exchange itself goes down mid-trade. Decide this before it happens, not during. |
There is no kill switch inside Autoview
Worth stating plainly rather than implying: Autoview has no built-in kill switch, no daily-loss auto-halt, and no panic button that stops trading for you. If you need to stop everything immediately, the real levers are outside Autoview's own parameters: revoke or disable the exchange API key Autoview is using (this is why read-only/trade-only keys without withdrawal access matter so much elsewhere on this site), pause or delete the alert or webhook that's sending commands, and use whatever emergency controls the exchange itself offers, if any. None of those are instant the way a dedicated kill switch would be, so build your daily stop as a discipline you act on, not a feature you can flip.
Outage response, decided ahead of time
An outage anywhere in the chain, TradingView, your alert source, Autoview's own platform, or the exchange, doesn't pause your open positions; a stop-loss that's already live on the exchange side keeps working, but a new signal simply can't reach you until the outage clears. The status page shows whether Autoview's own platform is the problem. Decide in advance what you'll do if an outage hits while you have open risk: whether you close manually from the exchange's own interface, whether your stops are already wide enough to hold without intervention, and who's watching for the alert that the outage even happened.
Venue-specific limitations
Not every protection is available on every exchange. Trailing stops, reduce-only orders, and one-cancels-other brackets vary by venue, some support all of them, some support none; the command reference and each exchange's own guide say what's actually available before you build a worksheet control around a feature that particular venue doesn't have. A risk plan that assumes a trailing stop exists everywhere is a plan with a silent gap on the exchanges where it doesn't.
Prove the plan before you fund it
None of the above is worth anything if the command doesn't actually do what you think it does. Add the dry-run flag to a command and Autoview parses it, computes the size and stops it would have used, and reports that back without sending an order. Read the output. Does the size match your risk plan? Does the stop sit where you expected? Only once that checks out should you drop the flag and let it trade for real. What is Autoview walks through the dry-run step in the context of a first trade end to end.
A note on what this page is and isn't. This is general risk-management practice, not investment advice, and Autoview doesn't evaluate or guarantee the outcome of any sizing or stop-loss approach you choose. It executes what the command tells it to, precisely and the same way every time. The judgment about how much to risk stays yours. See our disclosures.