Direct answer
Signal Provider Due Diligence uses inputs that describe (1) what the provider claims they do, (2) what actually happened in the historical record, and (3) what operational factors could make results differ going forward. In practice, these inputs fall into categories such as provider identity and rule disclosure, performance history with enough context to interpret it, execution and cost assumptions, risk controls (if any), and operational dependencies (for example, whether trading continues under outages).
Because the inputs can vary by platform and provider, the most useful way to understand the process is to list the data fields and assumptions a due diligence reviewer needs in order to independently check whether the provider’s claims are coherent with the record.
Mechanism and definition: what “inputs” means
Due diligence is not a single score; it is a repeatable check against specific inputs. A reviewer typically builds a verification dataset from:
- Provider documentation inputs
- Stated strategy description, rules, and any risk constraints (for example, position sizing rules or maximum exposure).
- Change history: whether the provider states they alter parameters, rules, or instruments over time.
- Operational details: availability targets, downtime handling, and whether signals are generated by a model or manual method.
- Historical record inputs
- Time period covered and whether there are missing intervals.
- Reported trading activity: instrument coverage, trade frequency, and holding durations (when available).
- Performance metrics shown with consistent methodology (for example, how fees and spreads were treated, if at all).
- Execution and cost dependency inputs
- Assumptions about transaction costs: spreads, commissions, swaps/financing (when applicable), and slippage.
- Execution model assumptions: whether fills are estimated or based on live execution, and whether the record includes latency or only end-of-period values.
- Risk and failure-mode inputs
- Evidence of drawdowns and recovery characteristics, interpreted with the knowledge that historical relationships do not prove future outcomes.
- Clear identification of limitations: for example, whether backtests or forward results are mixed, or whether performance depends on periods that are not representative.
A key distinction is between stable mechanics (the provider’s stated rules and risk constraints) and variable conditions (market regime, execution quality, and costs). Due diligence inputs are designed to test whether the stable mechanics plausibly explain the observed record under realistic dependencies.
Evidence or example: a “checklist” of verifiable inputs
To make this concrete, consider what a reviewer would need to independently verify a provider’s due diligence claims without using real-time data.
- Strategy disclosure vs observed behavior: If the provider claims a rules-based approach, the reviewer checks whether the historical record shows consistent instrument selection, risk exposure patterns, and behavior under different market conditions.
- Costs and methodology: If performance is presented as net results, the reviewer looks for documentation describing how spreads/fees/slippage were handled. If methodology is unclear, the reviewer treats performance comparisons as uncertain.
- Data completeness: The reviewer checks that the covered timeline is contiguous (or understands gaps). Missing periods can change risk estimates even if headline metrics look similar.
- Rule changes: If the provider indicates parameter updates, the reviewer checks whether the performance record shows regime shifts aligned with those changes, rather than treating the full history as stationary.
This checklist is about inputs, not conclusions: it helps a reader explain what was used, what assumptions were required, and what can be verified from provided documentation.
Limitations and risks
Several material limitations affect which inputs matter and how conclusions should be interpreted.
- Market dependency: Outcomes vary with market conditions. Even if inputs are accurate, the future may not resemble the historical environment.
- Cost and execution uncertainty: If the record relies on estimated fills or ignores certain transaction costs, the apparent performance can be misleading.
- Survivorship and selection bias: If only providers with strong outcomes are documented, historical results may overstate typical experience.
- Incomplete or changing rules: Providers can change methods or risk controls. When inputs do not capture rule changes, comparisons across time become unreliable.
- Jurisdiction and operational constraints: Real trading can be constrained by account rules, platform behavior, or execution limits. Due diligence inputs that omit these dependencies leave key uncertainty.
One practical failure mode is treating historical performance metrics as a standalone proxy for future quality.