DupliTrade assessment
Assess the broker route and selected strategy rather than assigning one return to the platform.
Automated strategy replication
Advertised Role
DupliTrade presents automated replication of strategy activity into brokerage accounts. That describes an execution arrangement, not one uniform strategy. A platform profile cannot be converted into a verified result for every leader or follower.
What to Request
Identify the supported broker and account arrangement available to you, the selected strategy, allocation controls and stopping process. Inspect the history's definitions before treating a displayed drawdown as comparable to another platform's metric.
Research Boundary
We did not connect a broker, run a funded copy test or independently audit a strategy ledger. Platform descriptions are primary product evidence only. Current eligibility, fees and replication outcomes remain account-specific questions.
Primary Sources
A described service is not a measured follower path
DupliTrade's public site is a reference for its described copying service, not a record of a private integration tested by this publication. Keep the original assessment and the actual account relationship separate. A source strategy description cannot authenticate a particular follower fill or determine the full fee scope. The new journals do not connect to a provider or broker. They preserve supplied intentions, observations and costs under declared units. A precise authored example should not be relabelled as proof that a platform delivered the same economic history as a source account.
An authored follower-record question
Suppose a fictional intended row Q2 is 300 valuation units and its observed fill is 180. That is a partial comparison under the exercise definition. The cause remains a separate source question: mapping, eligibility, timing or an omitted observation could require different records. This is not a DupliTrade participant case or error finding. Keep the source event, accepted policy, instrument reference and authoritative follower observation together. The ledger's below-target amount can locate the question while broker reconciliation and strategy validation remain null.
A specific record check
An authored partial row has intended amount 300 and observed 180, leaving 120 below the entered target. The arithmetic does not identify why. Keep the mapping, source event, actual account and applicable policy with the question. This is not a DupliTrade account test. A later complete fill would be a new observation, not proof that the earlier partial never existed. The tool cannot reconstruct that lifecycle. The buyer should preserve the actual source population rather than turn one matched row into a platform success statistic or use a missing record to invent a failure.
Keep the record boundary
The authored journals are not empirical provider tests. A valid decimal result can still use an incomplete population or incompatible product definition. Keep the account card, mapping, period and source coverage with the interpretation. The tool cannot authenticate an observation, discover omitted events or choose a causal explanation for divergence. Original personal and provider claims remain unchanged. No new participant result or user-review aggregate is invented to make the comparison look stronger.
A comparison is not account management
Unknown fills remain null, observed zero stays a separate state, and below/above amounts retain their identities. A paired price-cost sum is not an investment return. The journals keep broker reconciliation, strategy validation and suitability null. They send no orders and change no native policy. A useful closeout states the supplied population and unresolved question rather than grant permission, recommend an allocation or promise that copying reproduces a leader's history.