What to ask a signal provider before subscribing
A detailed evidence request before subscribing.
Educational explanations, fictional scenarios and personal worksheets. No live calls, paid-account test or provider performance certification.
A provider may show a genuine winning alert while leaving the result of the whole service unclear. Start by asking for a defined evidence pack: original calls, their revisions, the full outcome ledger and the method used to produce the headline statistics. A well-organised reply makes it possible to examine the claim. A vague reply leaves a specific question unresolved; it does not by itself prove fraud.
Define the product and period first
Ask which model, channel, strategy version and subscription tier produced the record. Establish the start and end dates, timezone, whether results are hypothetical or funded, and whether the figures refer to the provider's own account or subscribers' executions. An audited personal account and a simulated signal ledger describe different things, even if the same trader operates both.
The SEC performance-claims bulletin discusses the distinction between actual and hypothetical results, the effect of expenses and the importance of the period shown. Apply those questions to the particular claim being made rather than treating the word “verified” as a complete answer.
The evidence request, claim by claim
| Claim | Ask for | Still unresolved |
|---|---|---|
| The call existed before the move | Original alert, exact included fields and independently checkable publication evidence | Whether an order filled or made money |
| The stop and target were fixed | First-version levels and a dated correction history covering those levels | Whether the intended exit was achievable |
| The reported win rate is complete | All calls in the stated period, inclusion rules and outcome classifications | Average gain, average loss and portfolio drawdown |
| The result represents trading performance | Fill convention or broker records, quantities, costs and return formula | Whether a subscriber could reproduce the same fills |
| An outside review supports it | Reviewer identity, the inspected records, dates, scope and limitations | Claims outside the actual review scope |
Publication evidence has a field boundary
A dated message archive, retained first-version alerts, an independent publication system or a cryptographic receipt may provide different levels of chronology evidence. Ask what can be independently checked and which fields the mechanism covers. A seller does not have to use Bitcoin to supply a useful record; the important question is whether the evidence supports the specific timing claim.
For the VR2 example used in this primer, the preimage is VR2|salt|family|ticker|direction|grade|entry|signal_time. Reconstruct the exact digest and verify the Bitcoin anchor against the outcome time. The preimage omits stop, target, fills and performance. A receipt that matches the entry therefore cannot establish that a displayed stop was unchanged. The verification lesson works through that boundary.
Ask how every alert enters the denominator
Consider a hypothetical ledger of 100 alerts. Ten are cancelled before any entry, 20 never fill under the declared fill rule, and 70 become completed trades. Of the completed trades, 40 win and 30 lose. The trade win rate is 40 / 70, or about 57.14%. Calling it 40 / 100 answers a different question: winning completed trades as a share of all alerts. Neither figure should be presented without its definition.
Keep cancellations and unfilled alerts visible. Decide their treatment before outcomes are inspected. If losing calls can be relabelled “cancelled” only after the market turns, the denominator no longer follows a fixed rule. If a target is touched before the entry condition is met, it also cannot become a winning filled trade under a rule requiring entry first.
Ask for a stable ID per alert and a status such as open, cancelled before entry, expired unfilled, partially filled or completed. Retain open calls at the period end. The ledger should make clear which rows are used for the published win rate and which are used for return calculations.
Separate level arithmetic from funded returns
A list of price changes does not automatically give a portfolio return. Reproducing a funded result requires quantities or risk weights, the treatment of simultaneous positions, cash flows, leverage, costs and open exposure. Ask whether percentages are added, compounded on a common equity base, or calculated independently for each signal. Those methods can produce different numbers from the same trades.
For a broker-based claim, ask what record connects each published call to its fills and account result. For a hypothetical record, ask for the exact entry and exit convention, latency assumptions and treatment of ambiguous bars. A subscriber entering later may face a different price even when the provider's own record is accurate. The SEC execution explainer describes why execution is a distinct step.
A short request you can adapt
Keep each request, reply and reconciliation note separate in the evidence worksheet. Its statuses are a reader's working assessment, not an outside verification or a provider rating.
Download the blank evidence-request checklist (text). Record the reply, supporting source and unresolved question for each claim. The checklist is a review aid, not a certification of any provider.
Please identify the model version and continuous period behind the advertised record. Could you provide the original alerts and correction history, a complete outcome ledger including cancellations and unfilled calls, the fill and cost assumptions, and the calculation used for returns and drawdown? Where a timestamp or audit is cited, please state the fields, period and claims it covers.
Personal or subscriber data may need redaction. The remaining record should still preserve the information needed for the claim under review. If full data cannot be shared, ask what an independent reviewer inspected and which conclusions can be supported without the private fields.
Compare replies consistently
Use the same review period, outcome definitions and cost basis where the records allow it. Record missing information as unknown. A provider with a higher headline return but an unclear denominator cannot be ranked confidently against a complete lower-return record. A timestamp match establishes a chronology result; an execution reconciliation establishes a fill result; the full ledger establishes whether aggregate statistics can be reproduced.
Finish with a list of supported claims and open questions. That is more useful than a single invented star score. Practise the distinction in the evidence exercise, then use the track-record checklist on a real service.
A filled packet can make a missing source more specific
The new journal completes one structural teaching packet: original events, versions, parents, comparable clocks and exact notes. It deliberately does not complete authentic message, account-return, calibrated-grade or outside-audit evidence. There are fourteen declared events and three fictional signals, not an observed provider population. A reviewer receiving such a packet should record which object arrived and which requested evidence is still absent.
Use the preserved personal notebook to keep requested, received and reconciled-by-you states separate. Its new filled teaching draft is not an actual vendor verdict. Invalid imports preserve that notebook's existing notes, while the journal inspector clears an invalid calculation. Current access terms and publisher relationships are separate sources from performance. A complete format, correct CSV grammar or matching digest cannot make missing economic validation or broker fills appear. The original full evidence-pack protocol and downloads remain.