Risk Management

Risk management layer

Risk per trade, max drawdown, daily loss, exposure and filters.

  • Rules enforced in codeNot left to the moment
  • Breach alerts and logsEvery rule crossing is recorded
  • Test scenariosBefore anything goes live
Risk Management

Scope

What this service actually covers

The scope is settled before work starts; the items below are part of this service.

Risk per trade

Size comes from the stop distance and the risk cap, not a fixed lot.

Daily loss and drawdown limits

When a ceiling is reached the system stops opening trades until the next window.

Position and exposure ceilings

Open trade count and total risk across several symbols are controlled.

Recording and alerts

Every rule breach is written to the log and raised as a notification.

Risk rules are enforced in code so execution never depends on an in-the-moment decision — built for prop accounts.

Three design questions are settled here: the drawdown reference (balance or equity), the trading-day window in server time, and what the system does once a cap is hit.

The output is usually an independent layer that can also be added on top of an existing EA.

Delivery

How this service is delivered

Four stages with defined output; nothing moves on without your approval.

  1. Define the risk rules

    Ceilings, percentages and system behaviour for each condition are fixed.

    Stage output Risk rules document
  2. Implement the risk layer

    The rules are enforced inside the system as controllable limits.

    Stage output Active risk layer
  3. Scenario testing

    Edge conditions and losing streaks are simulated and reviewed.

    Stage output Test report
  4. Hand over and monitor

    Setup guide, logs and the reset procedure are handed over.

    Stage output Operations guide

Handover

What you receive

What you receive at the end of the project.

3 items

  1. Risk rule configuration
  2. Rule violation alerts and logging
  3. Risk test scenarios

This list is part of the project scope; each item is handed over at the end of its stage, before final delivery.

Who it is for

Who this service is for

If one of these describes your situation, this is the right service.

An account that has seen drawdown

The strategy was not the problem; having no defined ceiling was.

A prop team with hard rules

Account limits must be respected technically and automatically, not by hand.

Questions

Common questions about this service

Short answers to what clients ask about this specific service.

Can the risk layer be added to an existing EA?
Answer

Yes. In many projects the risk layer is added to the existing system as an independent module.

Do I set the rules myself?
Answer

Yes. You set the ceilings; we implement and test how the system behaves under each condition.

How does the system resume after a stop?
Answer

The reset window is defined in the rules document: a time window, manual approval, or both.