BDS / Intraday usability
Trade Ideas: Intraday Workflow and Evidence
Candidate discovery. Source-linked desk research, not a verified subscriber-performance ranking.
An alert window is not one managed account
The user guide documents alert windows, top-list windows and price alerts as parts of the platform. The meaningful test is a saved configuration operating under a specific session and universe, not a universal Trade Ideas win rate. Decide which event qualifies for action before reviewing the subsequent price path.
Preserve the scan identity
Record the alert type, filters, symbols, data entitlement and version. A hypothetical scan that flags a breakout supplies a discovery event; your strategy must still define the entry, initial risk and exit. Changing a liquidity filter after observing losses creates a different rule. Do not combine those revised results with the initial test as though the configuration never changed.
Measure what the platform supplies
Evaluate whether qualifying events arrive, can be reviewed and contain the fields you need. Maintain a separate record of orders, partial fills and rejected entries. If a simulated execution module is used, label its results simulated and identify its assumptions rather than treating them as broker-confirmed trades. This review did not measure feed latency or reproduce an AI strategy's live result.
Fit decision
Shortlist for self-directed intraday discovery when you can own the trading rules and monitoring workload. Confirm current feature access with the plan documentation. A saved scan and a complete prospective event log are stronger foundations for evaluation than a curated list of stocks that happened to move.
Intraday Evidence Packet
| Question | Required record |
|---|---|
| What is purchased? | Candidate discovery |
| What remains to inspect? | Active scan identity and the reader's rules |
| Which test was not done? | Paid access, routing latency and funded subscriber execution. |
Check the selected product, actual instrument mapping and original session policy. A platform mechanism can be documented while a private plan or source account remains untested. Do not fill those gaps from a brand reputation.
Keep the session evidence record / Product compatibility questions
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.