Copy Trading Account Setup: Group Design, Scaling Models and Limit Configuration

Published 3 Sep 2026 · 4 min read · Technology information, not financial advice

Copy trading behaves according to configuration you define: groups, scaling, limits and fees. Specify them explicitly, test them with edge cases and record the results as acceptance evidence.

Image placeholderblog-copy-trading-account-setup-guide-hero.webp · 1600 × 900

Confirm what the platform supports

Determine whether copying uses a built-in signals feature or a dedicated plugin or service, and which settings each exposes. Capture the supported scaling modes, limit options and reporting. This defines what you can configure.

Group design

Define separate trading groups for providers and followers, with symbol visibility, leverage and stop-out rules appropriate to each. Document the mapping between account types and groups.

Scaling models

Common models: fixed lot, ratio to provider, proportional to equity or balance. For each specify minimum and maximum lot, rounding behaviour, treatment of partial fills and instrument contract size differences.

Limits and protections

Specify per-follower maximum lot and exposure, drawdown pause threshold, tolerated delay and slippage, and the action on breach (skip, delay, close). See the risk control specification.

Fee calculation

Define fee type, calculation period, high-water mark behaviour, payout timing and how fees appear in CRM and statements. Include a worked example.

Test cases

• Provider opens and closes with different lot sizes and symbols.
• Follower with insufficient margin.
• Delayed or rejected follower orders.
• Provider removed mid-position.
• Fee calculation across periods.

Compare architectures in copy trading versus PAMM/MAM.

Configuration as code, or at least as a document

Keep the full configuration in a versioned document: groups, scaling parameters, limits, fee rules and the date and reason for each change.

If your platform allows exports, store them with the document. When behaviour surprises you, a version history shows what changed and when.

Platform capability check

Before design, confirm what the platform and plugin support: provider and follower account types, scaling modes, limit types, fee calculation models, reporting and API access. Document each capability with the source (specification, demo, written confirmation) and mark unknowns for follow-up.

Design against confirmed capabilities, not assumptions. Features that require custom development should be priced and scheduled as separate work.

Scaling model specification

Specify the scaling model precisely. Example for proportional scaling: follower volume equals provider volume multiplied by follower equity over provider equity, rounded down to the symbol step, with a minimum volume and a maximum cap. Define behaviour when the result is below the minimum (skip, round up or reject) and when margin is insufficient.

Each rule should have a test case with numbers. Store the specification as a versioned document and reference it in disclosure text.

Limits and protections configuration

Implement limits at the strictest level the platform allows, and test the action at breach, including notification.

Fee calculation specification

Define the fee model, the base, the schedule, the treatment of deposits and withdrawals, the high-water mark if used and the rounding. Provide worked examples with fixed numbers and compare them with system output in the test phase.

Fee statements must reconcile to the fee ledger and to the balance operations that move fees. Test the reconciliation for a full billing period.

Test plan and configuration records

Write a test plan with cases for copy open, modify, close, partial fill, rejection, margin shortage, symbol unavailable, provider stop, follower pause, limit breach and fee calculation. Run it on a staging environment and keep the evidence.

Export the configuration and store it with a date. See our risk controls guide for the control framework.

Worked example: scaling with a small follower

A provider opens 1.00 lot with 20,000 equity. A follower with 1,000 equity at proportional scaling should copy 0.05 lots. If the symbol step is 0.01 and minimum volume 0.01, the result is valid. For a follower with 150 equity, the result is 0.0075, which rounds down below the minimum; the rule must say whether to skip, round up to minimum or reject.

Choosing round up changes the risk profile of a small follower far beyond their intent; skipping may leave them out of the strategy. Decide, disclose and test. Each outcome should be visible in follower reporting.

Operational monitoring

Monitor copy latency, skipped copies by reason, limit breaches, fee ledger differences and follower complaints. Review weekly and record changes to parameters with reasons.

Add a periodic audit that samples follower accounts and verifies actual copied volumes against the specification.

Disclosure and documentation package

Prepare a documentation package alongside configuration: a plain-language description of how copying works, the scaling rules with examples, the limits and what happens at breach, the fee model with a worked example, the risk statement and the stop or exit process. Keep versions and dates.

Ensure that the screens, emails and statements use the same terms as the package. Inconsistency between product behaviour and documentation is a common root of complaints, and a consistent package makes disputes easier to resolve fairly.

Frequently asked questions

What should a copy trading specification include?

Account types, scaling rules, limits, fee rules, disclosures and test cases.

How do I handle volumes below the minimum?

Define the rule (skip, round up or reject) and test it.

How are fees tested?

With worked examples compared against system output and reconciled to the ledger.

How do I keep configuration traceable?

Export and version it with dates and reasons.