The answer

The answer: a trading risk management plan fixes your own limits and stop conditions, not a safe number

Most people who search for a risk management template want one right answer — some safe percentage to risk per trade. What you actually need is different: to fix, before you trade, the limits you have chosen, how you measure them, how exceptions are handled, and what you halt at a limit and on what condition you resume. No number is universally correct, and the value of a plan lies in letting you operate the decisions you already made on the same basis even in the middle of a moving market.

For that reason, this trading risk management plan template recommends no particular rate. Instead it shows how to write limits across the per-trade, concurrent, daily, weekly and monthly layers, give each a threshold, denominator, evaluation time and breach action, and then check that the limits do not contradict one another. If, for example, the daily loss limit is smaller than the per-trade loss limit, a single stop-out already breaches the daily limit and the plan fails from the start. Removing those contradictions first is the heart of building the plan. Deciding the quantity itself belongs to the FX and CFD lot size calculator guide, and where this template sits among the others is mapped in the financial document templates guide; this article concentrates on documenting which limits that quantity runs inside.

Every figure and diagram below is fictional educational data. It is not a real trader, account or track record. The template is a drafting aid, not investment, legal or tax advice, and not a substitute for any review or audit. Read it not for the size of the amounts but for the procedure of aligning limits and removing contradictions.

Terms and purpose

Terms and purpose: what a risk management plan template is

By “risk management plan” this article means a document, written before you begin trading, that records the loss limits you accept and the procedure for operating them. To avoid confusing it with adjacent terms, here are the roles.

• Risk management plan: the policy document collecting limits, measurement methods, exceptions, and stop and restart conditions. This article’s subject.
• Per-trade risk: the loss you expect if one trade reaches its stop. An input to sizing; in the plan it is treated as a limit.
• Open risk: the combined loss if every position held at once reached its stop. Managed by the concurrent limit.
• Threshold, denominator, evaluation time: the value of the limit itself, the base its percentage is calculated on (account balance or usable margin, for example), and the moment you measure. A limit only becomes operable when all three are present.
• Stop rule / restart rule: what you halt when a limit is reached, and on what condition you return to trading. Always held as a pair.

A risk management plan also differs in role from a trading plan or a journal. Individual entry rationale and scenario work belong to the trading plan template, and the actual records and weekly reviews belong to the trading journal template. The risk management plan sits beneath both, fixing first which limits the whole operation runs inside. The figure below sets out how it divides labor with sizing, cost and testing.

Hierarchy

The risk hierarchy: from a single trade to concurrent, daily, weekly, monthly and abnormal conditions

A risk management plan does not hold a single “loss limit” but a hierarchy of limits spanning different windows and scopes. The pyramid below stacks that hierarchy from a narrow scope (one trade) to a broad one (monthly), supported by margin and liquidity, with abnormal conditions handled apart.

The role of each layer follows below. From narrow to broad, the limits should grow in turn — that is the baseline of consistency.

• Per-trade loss limit: the most a single trade may lose. Used when designing the stop before entry — the layer that bites most often.
• Concurrent open-risk limit: the cap on the summed stop-out loss of all positions held at once. Confirmed before opening a new position.
• Daily loss limit: the cap on realized loss in one day. Once reached, stop new trades for the day.
• Weekly and monthly loss limits: caps on realized loss over longer windows — the brake for a run of bad days or bad weeks.
• Margin and liquidity: separate from the loss budget, the foundation of maintenance rate, stop-out and fill quality.
• Incidents and abnormal conditions: gaps, shocks, system failure, excess slippage. Handle apart from the limits, in a separate box with stated assumptions.

Summing concurrent open risk rigorously — down to currency concentration and correlation — is the territory of the lot size calculator’s multi-position analysis. In the plan template, keep a field for total open risk and its main common factors, and hand the detailed summation to the lot size calculator guide.

Field design

The fields each rule needs: threshold, denominator, evaluation time and breach action

A limit cannot be operated on a number alone. It becomes a document you can act on without hesitation only when each rule carries the full set below. Picture writing one limit as a “rule card.”

The two most often overlooked are the denominator and the evaluation time. If one limit uses account balance and another uses usable margin as its base, the same “3%” points to different amounts and the two cannot be compared. Aligning the base and the timing across all limits is the precondition for the consistency check that follows. On unrealized P&L and costs, there is no correct choice — deciding one and keeping it uniform is what matters. When you want the actual cost figures, the trading cost calculator guide helps.

The case

One consistent case: Case Trader A’s self-selected limits

From here, a single fictional case runs consistently through the tables, figures and checker defaults that follow. Case Trader A is a fictional individual trader with an account balance of 1,000,000 JPY. Every rate below is a value A chose, not a recommended or “correct” one. Set your own limits according to your capital, strategy and tolerance.

Rather than listing the five as bare numbers, A phrased each as “how many losses will I tolerate.” Taking the per-trade 1.0% as the unit, the daily is about three of them (3.0%), the weekly is two bad days (6.0%), and the monthly reaches further (10.0%) — each upper layer defined in units of the layer below. This makes each limit’s rationale explainable and, when it is time to review, adjustable by “how many losses.” The next section checks whether the five are logically consistent.

Consistency

Risk-budget matrix and consistency: removing contradictions between limits

Once the limits are gathered, build a risk-budget matrix that lines up each one’s threshold, denominator, evaluation time and breach action. Case Trader A’s matrix follows. Note that the denominator and evaluation time are aligned.

Checking consistency advances a long way just by inspecting the ordering of adjacent layers. The baseline relations are per-trade ≤ concurrent, per-trade ≤ daily, and daily ≤ weekly ≤ monthly. A’s reconciled version meets all of them. The next table shows A’s original draft (before review), which contained contradictions. Setting the before and after side by side shows what was fixed.

The draft held two contradictions. First, the daily limit of 1.5% was below the per-trade limit of 2.0%, so a single stop-out would exceed the daily limit. Second, the concurrent limit of 3.0% was twice the daily limit of 1.5%, so if several positions opened together were stopped out, one event could breach the daily limit. After review, the per-trade limit was lowered to 1.0%, the daily raised to 3.0% to match the concurrent limit, and the weekly and monthly arranged as a staircase. Contradictions like these can be flagged mechanically with the checker below.

Check procedure

Risk-policy consistency checker (educational mini tool)

Enter your own per-trade, concurrent, daily and weekly limits (in %) and whether unrealized loss and costs count toward the limits, and the checker below reports logical contradictions between the limits and definitions to add to the document. The output is not a recommended number or a pass/fail verdict. It does not propose a workable rate, or convert results into a risk score or a trading decision. Nothing is sent or saved; everything is processed in your browser. The defaults are Case Trader A’s reconciled version. If JavaScript is off, the static table just after it shows the same inputs and how to read them.

Stop and restart

Pair stop rules with restart rules: preventing discretionary overrides

A stop rule, which decides what you halt when a limit is reached, is always built as a pair with a restart rule. If you decide the stop but not the restart, you will resume right after the limit on the feeling that you are “close to winning it back,” and the plan becomes a dead letter. The flow below shows the stages from stopping to returning to normal operation.

The key is to set the restart condition by completing a procedure, not by time. Rather than “resume the next day,” phrase it as “record the cause, write a prevention step, resume first at below-normal size, and return if clean” — which curbs the urge to win losses back. The stop and restart records also feed the compliance check and validity review covered next. Running the actual records is easier when combined with the trading journal template.

Review

Separate the compliance check from the validity review

When reviewing the plan, the important thing is not to mix two kinds of question. One is the compliance check — “did I keep the limits I set?” The other is the validity review — “are those limits themselves reasonable?” Loosening a limit right after a loss without separating the two tends to become after-the-fact justification, blurring whether you simply failed to comply or the design no longer matches reality.

• Compliance check (short cycle): daily and weekly, confirm whether a limit was exceeded and, if so, whether you acted per the stop rule. Do not change the limit values.
• Validity review (long cycle): at a calm point such as month-end, consider whether the levels, denominators and evaluation times still fit reality. If you change them, keep a history.

When you change a limit, record the value before, the value after, the reason and the effective date. That lets you review later which regime you relaxed a rule in and what happened next. Statistics that underwrite a limit’s validity — losing-streak distributions and maximum drawdown — are out of scope here and are handled in the TradingView backtesting guide. The plan template provides the “decide, comply, review” framework, while the merit of specific numbers is verified with other tools. If you want to deepen the design of version control and approvals themselves, the document version control, approvals and audit trail article is a useful reference.

Avoiding pitfalls

Common failures and how to check

Failures in building a risk management plan cluster into a few types. If any sound familiar, that item is your entry point for a review.

• Writing the limit but omitting the measurement: a threshold exists, but with no denominator or evaluation time you cannot judge whether it was reached.
• A daily limit below the per-trade limit: the design lets a single stop-out breach the daily limit. Always check the ordering of adjacent layers.
• Denominators not aligned: one limit uses account balance, another uses usable margin, so the same % means different amounts.
• Vague treatment of unrealized loss and costs: not deciding to include or exclude them, so the basis shifts every time you total up.
• A stop with no restart: no defined way back after halting, so you resume on emotion and it becomes a discretionary override.
• Mixing compliance and validity: loosening a limit when you merely failed to comply, turning it into after-the-fact justification.

As a checking procedure, before you begin trading, run through each once: (1) does each limit carry the six fields (threshold, denominator, evaluation time, unrealized P&L and costs, exception approval, breach action); (2) are adjacent layers ordered consistently; (3) are stop and restart paired; and (4) are the compliance check and validity review kept apart. This is not an audit that guarantees a pass or safety, but a self-check to reduce oversights.

Maturity

Using the Hub: confirm the structure free, move repeated use to Pro

Here is how to take the plan-building above through the SG Group Financial Templates Hub, by stage. First, use the free risk-management and pre-trade risk templates to confirm the structure; when you find yourself running the same checks repeatedly, consider Pro for professional use. Feature names, scope and pricing can change, so treat the plan comparison page as the single source of truth for the latest.

This article’s plan template suits confirming the structure free first. At the point where you want to reuse the same pre-trade risk check or money-management policy repeatedly, and run output and history as part of your work, consider the Pro scope. QA, history and output formats assist document drafting; they do not certify legal compliance, safety or an audit result.

Summary

Summary: documenting a trading risk management plan and the next step

A trading risk management plan is not a document that hands you a safe number; it fixes, in advance, your self-chosen limits, how you measure them, exceptions, and your stop and restart conditions. The essentials are to write per-trade, concurrent, daily, weekly and monthly as distinct layers, give each a threshold, denominator, evaluation time, treatment of unrealized P&L and costs, exception approval and breach action, and arrange them so the limits do not contradict one another. In the fictional Case Trader A, a draft whose daily limit sat below the per-trade limit was reconciled after review.

In practice, (1) split limits by layer, (2) give each rule the six fields, (3) remove contradictions by the ordering of adjacent layers, (4) pair stop and restart, and (5) separate the compliance check from the validity review — hold these five and several rules come together as one money-management policy. Route quantity to the lot size calculator, cost to the trade cost calculator, and losing-streak testing to backtesting, and fix the documentation with this template.

Related articles

Related reading

Browse other English topics from the article index. For financial advertising presentation and client-facing documents, see the financial advertising review checklist, the advisor client meeting notes template and the introducing broker onboarding templates; multilingual work is covered in the multilingual financial document templates guide.