Chart Reporter

What evidence should I ask for when evaluating an automatic MT5 journal?

By Chart Reporter Reviewed 2 min read

The short answer

Evaluate an automatic journal by following a known trade through capture, reconciliation and review. Ask what must run, which records and costs are captured, how missing context is shown, what access is granted and how definitions are documented. A feature list alone does not answer those questions.

Verify capture using your intended workflow

If you trade from mobile, determine where any required reporter actually runs. If the system needs a desktop terminal or VPS, confirm the account match, network permissions and behaviour during disconnection. Automatic reporting still depends on its capture environment.

Use a known completed record rather than placing a live order purely for evaluation. Compare its ticket, times, volume, costs and partial-close history. Ask how the journal defines one trade and whether its displayed total already includes the attached execution events. This establishes a concrete reconciliation task.

Inspect definitions and missing-data behaviour

Read the definitions of net P&L, expectancy, R and drawdown. Check currency handling and whether the curve represents realised trade results or actual account equity. A plausible-looking value is not enough if its units or eligible sample are unclear.

Inspect a trade with incomplete replay history as well as an attractive demonstration. Determine whether the product exposes gaps, checks coarser intervals or implies detail it does not hold. A good evaluation includes limitations because they determine which review questions can be answered faithfully.

Check access boundaries and usable proof

Identify whether broker credentials are required, what the reporting key permits and what an AI integration can read or do. Verify each connection separately. Product storage, screenshot retrieval and MCP exposure are different capabilities, so ask about the actual returned fields rather than assuming that every feature reaches every integration.

Prefer a reproducible demonstration, clear documentation and genuine customer evidence over unsupported claims about time saved or performance improvement. Record the plan's effective history and feature access when comparing options. The result should be a documented fit for your workflow, not an expectation that any journal can guarantee better trades or future returns.

Sources and further reading

Related guides