Market pulse
Loading indicative prices…
Trading journal

A journal for your copy-trading decisions

Keep a useful record of why you connected, what you expected and what you actually observed.

By HUNTX Editorial Sep 21, 2026 2 min read Updated Nov 13, 2026

Capture the original reasoning

When you connect a provider, record the date, allocation, sizing rule and reason for the decision. Include the questions that remain unresolved. A short note written before the outcome is known is often more useful than a detailed explanation constructed later, because it preserves the assumptions you actually used.

Trading review process: record context, compare expectations, inspect exceptions and document the decision.
HUNTX educational diagram; illustrative data

Make observations comparable

Use the same fields at each review: relevant account changes, strategy activity, delivery exceptions and any departure from your original limits. Keep source records linked where available. Consistent fields make it easier to identify a pattern across several weeks without having to reconstruct the story from memory.

Write down changes

If you adjust sizing, pause copying or end a relationship, record what evidence led to that choice. Describe the expected effect and the date for the next review. This helps separate a planned adjustment from an impulsive response and makes it possible to evaluate whether your reasoning improved with additional information.

Keep the journal practical

The journal should be easy enough to maintain during ordinary use. A page of clear observations can be more useful than an elaborate template that is rarely completed. Review the fields periodically and remove anything that does not support a decision. Protect account identifiers and never include passwords or connector tokens in your notes.

Continue with our guide to reading provider performance without promises.

Reference: FCA explanation of copy trading.

Risk note

Educational content does not guarantee trading outcomes. Review account, broker, platform and copy-control risks before enabling automated execution.