The shortlist Tips What we check Method FAQ Compare

External Signals and Prop-Account Restrictions

Check exact external-signal permissions, instruction identity, expiry and overlapping exposure before claiming prop-account compatibility.

Rulebook desk research checked 8 October 2026. No evaluation purchase, enforcement test or payout verification is represented.

Guide revision and linked reference check: 10 October 2026. Examples are fictional; no paid-account test.

Ask whether the intended arrangement is permitted

Identify the exact activity: manually considering an outside alert, automatically copying orders, sharing account access or running a personal algorithm. These are not interchangeable permissions. Read the governing product and phase rules, then request written clarification when the intended arrangement is not covered clearly. Retain the question as well as the answer so a broad support reply cannot be stretched beyond what was asked. A signal vendor statement does not bind the evaluation firm.

Do not disguise trade origin, bypass restrictions or treat a public forum workaround as authorisation. If the arrangement is prohibited or unresolved, the consumer decision can be not to purchase. The FTMO source provides a current policy reference for that firm scope, not universal permission across evaluations. This publication has not run a paid challenge with a listed signal product. A documented feature, instrument list or attractive historical result does not establish acceptance under an account contract.

Count actionable instructions rather than messages

Separate originals, amendments, commentary and duplicate delivery. A notification count can be much larger than the number of distinct instructions. Preserve stable identifiers and the relationship between a correction and its original. If an original expires, a later discussion of its result does not automatically reactivate it. Keep source publication, subscriber receipt and the decision you actually make as distinct clocks. Do not fabricate a timely receipt from an old screenshot.

An invented stream contains sixteen messages: ten originals, three amendments, two commentaries and one duplicate delivery. There are ten original instructions under this example, not sixteen independent opportunities. If six originals expire without an authorised action and four proceed to consideration, retain both sets. Neither the message count nor the consideration count is a pass-rate denominator. The exercise has no real provider dataset. It shows why a journal should retain instruction identity before discussing frequency, overtrading or the outcome of any evaluation attempt.

Keep expiry and amendment decisions visible

Record the instruction validity window, the time you received it and whether an amendment changed its actionable terms. A late receipt may be genuine but no longer usable under the rules stated by the source. Do not widen a stop, chase a changed entry or silently extend an observation window to preserve a favourable historical comparison. The authorised research-fill convention and an actual account fill are separate evidence objects.

For a fictional instruction expiring at 14:55 UTC, receipt at 14:55:05 is later than its declared expiry. That arithmetic alone does not say how a real vendor defines equality or whether a later amendment exists. It certainly does not demonstrate that an evaluation firm approves the trade. Preserve the unresolved state and the actual source terms. The record should explain why an instruction was acted on, skipped or left unknown without pretending that every delivered alert had an executable price or a compliant account action.

Review the exposure shared across instructions

List current filled positions and pending orders before assessing another instruction. Two alerts can express the same underlying market risk despite different symbols or identifiers. A pair of leaders or signal families does not automatically diversify an account. Use a clearly labelled stress scenario where a real covariance estimate is unavailable; do not invent a correlation score to make the comparison look quantitative. Keep direction and instrument units explicit.

A hypothetical shared move produces losses of forty, fifty and sixty dollars across three considered exposures, a combined one hundred fifty. The sum is accounting under entered scenarios, not a forecast or a sizing recommendation. An unrelated gain cannot be assumed to occur simultaneously to offset it. Compare the scenario with correctly established account boundaries only if their metric and observation clocks align. Stops, reserves and nominal trade counts do not guarantee that actual joint losses remain inside a contract limit during gaps or partial execution.

Reconcile routing and permitted account action

Map the original instruction to any authorised account request, acknowledgement and fill. A sent webhook is not an executed order. An unknown submission should remain unknown until reconciled, because repeating it can create duplicate exposure. A cancellation might remove an unfilled remainder while leaving a position open. Record operating failures as states in the journal rather than deleting them from a performance summary. Do not connect a live account to test this article.

Keep operational compatibility separate from historical model evidence. A signal might have a genuine dated record and still use instruments, holding patterns or automation that the account prohibits. Conversely, a permitted routing mechanism says nothing about the predictor accuracy. A hash receipt covers specified bytes and limited chronology, not firm authorisation or subscriber profit. This publication cannot approve copied activity on behalf of the contract owner, and its local software checks are not independent strategy-validation or production reliability evidence.

Use a permission-first decision record

Conclude with the exact arrangement, authoritative permission reference, unresolved restrictions and observed operating scope. A seller general compatible badge should not become this publication blanket certification. If a contract answer is unavailable, record the gap and do not replace it with a favourable score. Recheck when product terms, phase, instruments or execution behaviour change. Preserve previous versions so a later policy is not applied retrospectively to an older attempt.

The blank CSV supports private organisation of source links and instruction states. It contains no approved account, completed evaluation or real signal run. Do not publish account credentials or other personal identifiers in a review. A consumer may choose a different permitted arrangement or decline the purchase altogether. More alerts are not evidence of more value, and fewer alerts are not evidence of lower risk. The useful distinction is between documented permission, distinct valid instructions and the exposure that actually exists in the account.

Review checkpoints

Evidence requests, not observed strategy results
ObjectPreserveDo not infer
PermissionExact programme rule and written clarificationSeller compatibility binds the firm
InstructionOriginal, amendment, expiry and receipt clocksEvery notification is a new trade
ExposureOpen, pending and shared-risk positionsSeparate IDs are independent risks

Download blank research record (CSV)

Headers only. No trades, account outcomes or operating receipts are supplied.

Primary Sources

Prop Account Headroom Worksheet

Related research

Received alerts are not a required activity quota

An alert stream is a research population, not an instruction to execute every item on an evaluation account. Keep proposed workflow, permission and actual observed actions separate. This addition does not recommend a new size, entry filter or exit change. It explains why a preparation record should preserve skipped and revised alerts rather than selecting only favorable examples. A strategy's native policy and its independent validation remain outside this publication's event tool. An unchanged alert can lead to different account observations under different timing, mapping or costs. Those differences require evidence rather than a broad guarantee attached to a provider name.

Keep the original source relationship

Attach the cited source to the precise field it supports. A rule URL supports its observed wording; an account record supports an observed event; a cash record supports its supplied payment status. None of those records establishes the others automatically. The publication's practice packet is deliberately authored, with no participant population. Use it to inspect the relationship between input and output rather than as evidence that a programme, provider or trading method achieved the displayed result. Missing fields remain unresolved, and the responsible account process owns any real eligibility decision.

A worked contrast to investigate

In the invented packet a close at an entered window endpoint changes classification when the endpoint operator changes. In the separate cash journal a pending refund changes the balance only after the status is changed to posted. These controlled contrasts do not prove a named firm's policy. They show why the record needs an explicit operator or status. Export the supplied inputs with the result, retain the applicable product card separately and preserve uncertainty about missing events. A precise calculation is useful when its scope remains visible; it is misleading when presented as an account approval or a measured participant outcome.

Preparation records