Discretionary and systematic describe who makes the decision. Manual and automated describe who sends the order. A trader can follow written rules and still click manually; a trader using automated entries can still make discretionary exits.
Use four practical descriptions: discretionary/manual, systematic/manual, semi-automated, and automated. They describe a process, not a ranking. Automation executes your rules; it does not make them profitable or remove responsibility for them.
Part 1 of 8 in From discretionary to automated trading. Previous: series guide. Next: which decisions are ready for rules?
Why are “manual” and “discretionary” different?
A decision is systematic when a written procedure determines the action from the available inputs. Execution is manual when the order needs your action to be sent. Neither description tells you whether the strategy is effective.
Suppose a written condition identifies a bar and your TradingView alert notifies you. If you place the specified order without changing it, the decision can be systematic even though execution is manual. TradingView’s notification options include channels for notifying a person as well as webhooks for sending a message to another service.[1]
What do the four descriptions mean?
| Type | Who decides? | Who sends? |
|---|---|---|
| Discretionary/manual | You judge each setup | You place the order |
| Systematic/manual | Written rules | You place the order |
| Semi-automated | Rules plus human choices | A mix by action |
| Automated | Implemented rules | Software requests the orders |
Semi-automated needs a more precise description. Name the handoff: you approve a signal; software enters but you manage the position; or software runs while you decide when it may operate. A planned, rule-based pause is different from an unrecorded change of mind.
Automated means the defined routine does not require an individual order click. It still needs decisions about its design, deployment and supervision. A broker can reject a request, and receipt of a message is not a confirmed fill.[2]
Algorithmic rules are rules expressed as a procedure, commonly in code. The word “bot” is less precise: ask what produces the signal, what requests the order and what keeps that software running. The execution-routes guide explains how an order can reach a broker.
Who decided and who clicked in your last 20 trades?
Use your last 20 completed trades as an illustrative review window, not a statistical readiness threshold. Include qualifying signals you skipped during that same date range. If you have fewer records, use all available records and write down the count; missing evidence stays “unknown”.
Record the start and end dates, strategy version, account type and any changes during the window. For each question, keep the trade or signal IDs behind the answer:
-
Could another person reproduce the decisions?
Count trades whose entry, exit and size were specified by rules available before the decision: ___ out of ___ reviewed trades. “I can explain it now” does not count as a rule recorded then. -
Did an order require your action?
Count trades with a manual entry, exit or amendment: ___ out of ___ reviewed trades. Record the action separately: entry ___; exit ___; amendment ___. -
Did you override a qualifying signal?
List every skipped, added or resized decision: ___ events in the review window. Include skipped signals even though they never appear in account history. -
Did you change a stop or target by judgment?
Count affected trades: ___ out of ___ reviewed trades. Separate a written management rule from a decision made because the position felt uncomfortable. -
Did you change when the system could run?
Record each intervention, its time and reason: ___ events in the review window. Mark whether a written rule already required it. -
Did size come from a defined formula?
Count trades sized from a written rule: ___ out of ___ reviewed trades. Record every exception and whether the rule used fixed lots, a cash-loss budget or another explicit method.
Scoring key: do not add the six counts into a score. They have different denominators and describe different jobs.
- If every decision is reproducible, size follows the written rule and no discretionary overrides occurred, classify the decision process as systematic.
- If any trade or skipped signal required unwritten judgment, identify that decision as discretionary. The rest of the process can remain systematic.
- If every order requires your action, execution is manual. Combine that with the decision label above.
- If software requests some actions while you approve signals, manage trades or apply discretionary pauses, describe the workflow as semi-automated and name the handoff.
- If implemented rules request the routine entries, management and exits without per-order action, describe that routine as automated. Human supervision still sits outside it.
A result with unknown records is incomplete. Improve the decision log first; do not infer that an unrecorded override never happened.
Which records support those answers?
Use the written rules and decision log for intention, the TradingView alert log for triggered alerts, and PineConnector’s record for received messages. Use MT5 order/deal history and positions for what happened at the broker. TradingView’s simulated trade list is a separate comparison, not account history.[2][3]
Magic Numbers and comments help trace order origin and management scope. The default PineConnector comment can contain the Signal ID; a custom comment can replace that display. An absent default label does not establish that a position was opened manually.[4]
For the reconciliation procedure, use Part 7. The six questions above diagnose your process; they do not certify the execution path.
What do two mixed workflows look like?
Written signals, manual clicks, an unwritten Friday filter
Illustrative example, not a recommendation. A trader follows explicit chart conditions and enters manually, but sometimes skips Friday signals because the market “does not look right”. The signal is systematic; the final entry choice is partly discretionary; execution is manual.
The next task is to record those skipped signals and the reason available at the time. Part 2 helps decide whether to define that filter, accept its removal as a changed strategy, or keep a documented veto.
Automated entries, discretionary stop changes
Illustrative example, not a recommendation. Another trader’s alerts produce order requests through PineConnector, but the trader moves stops when a position feels too exposed. Entry execution is automated; trade management is discretionary. The workflow is semi-automated.
The manual edit does not transfer ownership of the position away from the EA. Later automated management may still target it under the EA’s scope. Specify the handoff before combining manual amendments with automated management, then verify it on demo.[5]
Can manual and automated positions interfere?
Yes. In the self-hosted EA reference, Magic Restriction On limits management to positions whose Magic Number matches the EA. With it off, management can include same-symbol positions opened manually or by other EAs. The docs explicitly warn that a closelong request with restriction off can affect manual buys.[5]
Comments are a separate filter. The multi-strategy guide documents matching-comment selection for closelong, closeshort, cancellong and cancelshort, including MT5 EA support from v2.095. Omitting the comment can broaden a close within the EA’s scope; ordinary close-command support does not establish comment filtering for partial closes.[6]
A label does not create an isolated account. On a netting account, MT5 maintains one position per symbol, so orders from different sources can change that shared position. Verify account type, Magic Restriction, the exact command and the intended remaining exposure together.[7]
PineConnector Edge hosts MT5 with the PineConnector EA, whose settings currently use fixed defaults. Do not apply self-hosted instructions as if those settings were editable on Edge; inspect the displayed configuration and use the Edge information for the hosted path.[8]
What can this classification not tell you?
No category establishes profitability, suitable risk or readiness for real money. A complete written rule can still be wrong. Removing an order click also leaves design choices, monitoring and the decision to intervene with you.
The categories describe the reviewed routine and period. If you change how entries or exits work, classify the new workflow again. For what specific pause controls do to entries, exits and positions, use Part 8.
What should you do next?
Write one sentence naming who decides and who sends each type of order. Then take the unwritten decisions to Part 2’s decision inventory. That is the point where a label becomes a practical specification.
Reviewed 23 September 2026 against the linked primary documentation. Nothing was tested on a trading account, and no Pine Script or MQL5 code was compiled.
Related reading
- Series guide: from discretionary to automated trading
- Part 2: the readiness inventory
- Part 7: verify the demo execution path
- Part 8: pause and resume controls
- TradingView’s broker execution routes
Sources
- TradingView – Introduction to TradingView alerts, accessed 23 September 2026.
- PineConnector – Troubleshoot an alert, accessed 23 September 2026.
- TradingView – Strategies, accessed 23 September 2026.
- PineConnector – Frequently Asked Questions, accessed 23 September 2026.
- PineConnector – EA settings reference, accessed 23 September 2026.
- PineConnector – Keep strategies separate, accessed 23 September 2026.
- MetaQuotes – Basic Principles of Trading, accessed 23 September 2026.
- PineConnector – Connect your MT5 account, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
