Skip to content

TradingView assessment

Tool access does not establish a firm's permission to use an external strategy.

Public-document research checked 8 October 2026. Examples are fictional; no challenge, pass, payout or paid account test is claimed.

Charting and alert tooling

Practice Task

A chart can support rule observation and decision journalling. Identify the data feed, timestamp convention and selected platform's compatibility with the evaluation.

Permission Boundary

An alert is not an accepted firm order. No platform connection or external-signal authorisation was tested. Obtain the account's own policy before planning any integration.

Primary Sources

Compare categories and evidence limits

Chart conditions and account rule versions

For a chart notification, preserve the condition version, quote convention, observation time and subscriber arrival before linking it to an account event. A later setting change should not silently rewrite the instruction available earlier. Keep the selected strategy's native exit policy separate from an evaluation reference reset.

The new tools do not fetch chart history or infer a fill from a plotted level. They accept supplied account states and daily results. A hypothetical comparison can ask whether those source relationships are inspectable for the intended route, while leaving the original profile intact. It does not claim to test every author, authenticate a programme account or confer holding permission.

An invented chart-version boundary

Suppose an educational record has a chart condition saved before entry, a later changed setting and a notification near a programme boundary. Preserve the original version, quote convention, notification source and effective change. A screenshot of the later chart should not silently replace the condition that existed at the earlier decision time.

The account request and execution still need their own records. A plotted level cannot supply filled quantity, commission or the programme's permission. The new replay does not fetch chart bars or parse alert conditions; it compares supplied account measures only. This case adds an operational source question around the original profile, not an empirical claim about a platform author, measured notification delay or a paid evaluation path. Keep actual source precision and any uncertainty beside the account join.

A chart event is not a daily account category

Several notifications can concern one open position or never produce an entry. A qualifying positive day also needs the applicable accounting window, costs and definition. A chart event count cannot replace those fields. The daily ledger deliberately starts from supplied closed-net rows, while the loss replay starts from marked account observations.

A genuine review can link condition, notification, decision and account state when the underlying records are available. That link remains separate from account permissions and administrative approval. The additions do not modify the original profile or invent a universal evaluation-compatible alert. They ask how the intended workflow can preserve version ownership and actual economic events without treating a later favourable chart, an altered setting or a numerical worksheet output as proof that a real account satisfied its programme.

Worked evaluation records