Financial Market Tools for Traders, Investors & Finance Professionals
Financial Templates Hub — Document Operations Series 04
A trading risk management plan is not a document that hands you a safe number. It is where you fix, in advance, the limits you have chosen, how you measure them, how exceptions are handled, and the conditions under which you stop and later restart. This guide walks one fictional case all the way through, showing how to write per-trade, concurrent, daily, weekly and monthly limits as distinct layers, give each a threshold, denominator, evaluation time and breach action, and keep the limits from contradicting one another. It recommends no particular rate; it concentrates on documenting the limits you choose without internal conflict.
Key takeaways
The answer
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
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.
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
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.
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
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
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.
| Layer | Threshold (%) | Threshold (JPY) | Meaning (A’s phrasing) |
|---|---|---|---|
| Per-trade loss limit | 1.0% | 10,000 JPY | Cap on what a single stop-out may cost |
| Concurrent open-risk limit | 3.0% | 30,000 JPY | Up to about three 1% positions at once |
| Daily loss limit | 3.0% | 30,000 JPY | Three losing trades halt the day |
| Weekly loss limit | 6.0% | 60,000 JPY | Two bad days halt the week |
| Monthly loss limit | 10.0% | 100,000 JPY | A run of bad weeks halts the month |
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
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.
| Layer | Threshold | Denominator | Evaluation time | Breach action |
|---|---|---|---|---|
| Per-trade | 1.0% / 10,000 JPY | Account balance (period start) | When designing the stop before entry | Reduce size or skip the trade |
| Concurrent | 3.0% / 30,000 JPY | Account balance (period start) | Before opening a new position | Skip the new position |
| Daily | 3.0% / 30,000 JPY | Balance at day start | Daily, realized basis | Stop new trades for the day |
| Weekly | 6.0% / 60,000 JPY | Balance at week start | Weekly, realized basis | Stop for the week, review |
| Monthly | 10.0% / 100,000 JPY | Balance at month start | Monthly, realized basis | Stop for the month, validity review |
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.
| Layer | Before (draft) | After (reconciled) | Reason for the fix |
|---|---|---|---|
| Per-trade | 2.0% / 20,000 JPY | 1.0% / 10,000 JPY | Shrunk to remove the clash with the daily limit |
| Concurrent | 3.0% / 30,000 JPY | 3.0% / 30,000 JPY | No change |
| Daily | 1.5% / 15,000 JPY | 3.0% / 30,000 JPY | Was smaller than per-trade and broke the plan; raised |
| Weekly | 4.0% / 40,000 JPY | 6.0% / 60,000 JPY | Aligned to two daily limits |
| Monthly | 6.0% / 60,000 JPY | 10.0% / 100,000 JPY | Adjusted to exceed the weekly limit |
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.
A risk management plan template documents limits and stop conditions, but it does not calculate how many lots each trade can actually place or how much margin it needs. Turning your per-trade loss limit into a quantity and a margin figure is the lot size calculator’s job. Once the limits are set, size the trade there separately, and confirm before entry that the calculated amount fits inside the plan’s limits.
Check procedure
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.
| Input (Case Trader A, reconciled) | Value | How to read the consistency check |
|---|---|---|
| Per-trade loss limit | 1.0% | At or below daily? (1.0 ≤ 3.0) → holds |
| Concurrent open-risk limit | 3.0% | At or above per-trade, level with daily (no clash) |
| Daily loss limit | 3.0% | At or above per-trade? (3.0 ≥ 1.0) → holds |
| Weekly loss limit | 6.0% | At or above daily? (6.0 ≥ 3.0) → holds |
| Count unrealized loss | Exclude | Added definition: state it is managed via margin maintenance |
| Count costs | Include | Costs folded into the loss figure, kept uniform |
| Overall | No clash | No numeric contradiction found. Consistency does not guarantee validity |
Stop and restart
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
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.
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
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.
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
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.
FAQ
Summary
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.
Read next
FH05: Investment Thesis Template — Research Notes, Disconfirming Evidence and Decision Logs — how to keep an individual investment decision with disconfirming conditions and an update history.
References
Disclaimer
