Trade copying & account control
A follower account has its own balances, instruments and execution state. Build a copying workflow that applies explicit rules to those differences and makes divergence visible to the operator.
Illustrative account flow. No connected accounts or live copying activity.
01 / SCOPE
Start with the authority to operate each account and the exact meaning of a master instruction.
Document account owners, operator permissions and the approved master-to-follower relationships. Scope whether the system mirrors orders, fills or target positions, and how manual activity is distinguished from activity it controls. Access and permitted automation require verification.
Agree fixed, proportional or other specified sizing rules, rounding and exposure caps per follower. Map symbols, contract sizes and account behaviour explicitly. A missing instrument or insufficient balance needs a defined skip, pause or escalation response.
02 / SCOPE
Master and follower activity should remain traceable when execution differs.
Specify how entries, partial closes, stop changes and cancellations propagate. Track follower acknowledgements and fills separately from the master. Decide what happens when a follower rejects an instruction or receives a later update before the earlier action is resolved.
Reconcile actual positions after a restart before sending new instructions. Define whether an existing difference is corrected automatically, left untouched or escalated. Operator controls can pause one follower without silently changing the policy for every other account.
FROM BRIEF TO HANDOVER
List ownership, platform, account permissions and intended relationships without sharing passwords or API secrets.
Agree sizing, mapping, manual-trade treatment and the permitted response to each kind of divergence.
Test unequal balances, unavailable symbols, partial fills and disconnected accounts in an appropriate environment.
Deliver per-account controls, reconciliation reports, configuration guidance and documented onboarding and removal procedures.
Software tests and operational controls do not guarantee trading returns. Live access, deployment and operating limits are agreed separately.
BEFORE WE BEGIN
That cannot be promised. Timing, prices, account conditions and sizing differences can produce different positions and outcomes.
Only an explicitly scoped, authorised arrangement can be assessed. Ownership, permissions and applicable requirements must be established before implementation or access.
That can be scoped, but attribution and synchronisation rules must distinguish those trades so recovery does not alter unrelated positions.
CONNECTED SERVICES
YOUR NEXT STEP
Share the market, platform, existing system and behaviour you need. Please do not include credentials or account secrets.
