After a big loss, the first job is not recovery—it is permission control. Stop adding risk, verify the account and every open order, preserve the evidence, then decide whether the next session is no trade, review first, reduced risk, or normal under rules written before the loss. A calendar cannot make that decision for you.
What to Do in the Next 15 Minutes
- Freeze new orders. Do not use another trade to diagnose the previous one.
- Verify exposure. Check open positions, working orders, linked OCO orders, copy accounts, margin, balance, equity, and the account’s current loss limits.
- Preserve evidence. Save executions, timestamps, fees, screenshots, platform messages, and the plan that existed before entry.
- Classify the event. Was it a planned loss, an execution deviation, an account-rule breach, a data/platform issue, or still unknown?
- Apply the written stop rule. If the rule says the session is over—or the account state is uncertain—the decision is already made.
A position-size calculation should enforce an existing loss budget. It should never answer “How large must the next trade be to get back to breakeven?” Recovery P&L is not a valid sizing input.
If you are still deciding whether the session should end, use the loss-stop decision guide to separate account rules, execution deterioration, and ordinary variance.
Define “Big” Before You Interpret It
A large dollar number is not enough. The useful definition is relative to the plan and account. Treat the loss as operationally significant when one or more of these is true:
Planned-risk breach
Realized or open loss exceeded the recorded loss budget, or size/stop behavior did not match the plan.
Account-rule pressure
The event consumed material room under a broker, exchange, personal, or funded-account daily/max-loss rule.
Behavior change
Re-entry speed, size, trade frequency, setup quality, or willingness to follow the checklist changed after the loss.
Evidence uncertainty
Open exposure, fills, fees, currency conversion, copy state, or platform data cannot yet be reconciled.
A fully planned stop-out can be large in money and still be a valid strategy observation. A smaller loss can be serious if it breached a hard rule or triggered uncontrolled follow-up risk. Classify first; do not rewrite the strategy from the size of the feeling.
The Math of Drawdown Recovery
Drawdown recovery is asymmetric because the gain is measured from a smaller remaining balance:
5% drawdown
Recovery required: approximately 5.26%.
10% drawdown
Recovery required: approximately 11.11%.
20% drawdown
Recovery required: 25%.
30% drawdown
Recovery required: approximately 42.86%.
50% drawdown
Recovery required: 100%.
The arithmetic does not predict how many days recovery will take and does not justify a target return. A fixed “1% per day” timetable assumes the result it claims to forecast. Use the number to understand why additional loss has increasing recovery cost, then return to the account’s actual risk limits. The broader risk-management framework covers loss budgets, open exposure, and drawdown controls.
Two Risky Responses: Chasing and Indefinite Avoidance
“Revenge trading” is often used as a motive label. A trade log cannot read motive. It can show observable sequences: a fast next entry after a loss, increased size in the same account/instrument unit, more trades than the trader’s own baseline, weaker setup tags, or worse net outcomes after losses. Those patterns justify review; they do not prove anger or causality.
The opposite problem is avoidance with no re-entry condition. Not trading is the correct action while exposure is unclear, a hard stop applies, or the trader cannot follow the plan. It becomes operationally unhelpful when the pause has no purpose, evidence task, or objective return gate. A good pause has an owner, a checklist, and a condition that ends it.
No-trade state
Use when a hard loss rule is hit, exposure is unresolved, platform data is unreliable, or the written plan cannot currently be followed.
Review-first state
Use when trading permission depends on reconciling the event, clearing review debt, or identifying whether a rule was broken.
Reduced-risk state
Use only when a prewritten plan defines the reduction and the account still permits it. Do not invent “half size for a week” after seeing the loss.
Normal state
Return only when the account is verified, hard rules permit it, the next setup is eligible, and the normal process—not recovery urgency—sets size.
For the deeper sequence audit, see the revenge-trading evidence guide. It treats the label as a hypothesis to test against behavior rather than a diagnosis.
A Gate-Based Recovery Protocol
Seven days, two trades per day, or a 50% size cut may be reasonable personal rules when registered in advance. They are not universal. Recovery should progress when evidence gates clear, not because the calendar moved.
Gate 0: Account Safe
Confirm every position and working order, account equity, loss-limit state, copy/sync status, and whether the venue has restricted the account. If any value is unknown, place no new risk. Resolve operational uncertainty before analyzing psychology.
Gate 1: Event Reconciled
Build one factual record: planned entry and invalidation, intended size, actual fills, stop changes, partial exits, fees, timestamps, and any outage or rejection. Separate what the plan allowed from what occurred. If the loss spans multiple trades, reconstruct the chronology rather than reviewing only the largest ticket.
Gate 2: Cause Classed Without Hindsight
- Valid planned loss: keep it in the strategy sample; do not “fix” the setup from one outcome.
- Execution deviation: name the first observable deviation and the guard that would have blocked it.
- Account-rule breach: stop and resolve the exact account consequence before any return plan.
- Platform/data problem: preserve logs and obtain the venue’s status before attributing the result to strategy.
- Unknown: retain the unknown; do not turn missing evidence into a confident story.
Gate 3: Return Rule Registered
Write the exact eligible setup, maximum allowed risk from the existing plan, session stop, maximum concurrent exposure, and evidence to capture. Simulation or observation can test whether the checklist is executable, but a simulated win does not certify emotional readiness or future profitability.
Gate 4: Process Verified on a New Window
Judge the return by rule adherence and evidence quality before P&L. Do not require “green days” as proof of readiness: a compliant loss may be more informative than a lucky violation. Restore normal permission only under the prewritten rule and only after enough new evidence exists to evaluate it; there is no universal number of trades or days.
Red Flags That Block New Risk
- You cannot state current total exposure and every working order.
- The next position size is derived from the amount you want to recover.
- You are adding instruments, timeframes, or setup exceptions that were not in the plan.
- You are hiding, deleting, or postponing review of the loss.
- You intend to widen a stop, remove a daily cap, or add another trade “just this once.”
- Your plan requires fields or rule values you cannot currently verify.
- You feel unable to stop even though a hard account or personal rule says stop.
If the loss creates distress that feels unmanageable or raises a safety concern, stop trading and seek appropriate professional or emergency support in your location. A trading workflow is not mental-health care.
Journal Prompts for a Big-Loss Review
- Facts: What positions, orders, sizes, prices, timestamps, costs, and account values can be verified?
- Plan: Which rule version and setup definition applied before entry?
- First divergence: What was the earliest observable difference between plan and execution?
- Sequence: What happened immediately before and after each loss, including re-entry gap and size?
- Counterfactual: Which one prewritten guard could have changed the sequence without using future information?
- Return gate: What evidence must exist before permission changes from no trade or review first?
Use the trade-review workflow to keep setup validity, execution quality, account constraints, and outcome separate.
Turn the Loss Into an Inspectable TSB Decision
Trader’s Second Brain can connect the imported chronology, the plan that governed the trade, the observed post-loss sequence, and the next permission rule. Leak Map’s deterministic behavior layer can surface post-loss re-entry, size escalation after a loss, and unusual frequency relative to the trader’s own evidence. It compares like units and explicitly states that timing is observational—it does not infer motive.
1. Reconcile
Import the executions, verify open/closed state, and attach the loss to its account, setup, plan, and review evidence.
2. Detect
Inspect the exact post-loss trades, re-entry gaps, size comparisons, daily frequency, and field coverage instead of assigning a psychology label from memory.
3. Decide
Ask AI Coach for Loss Streak, Revenge, Tilt Risk, Drawdown Guard, or Risk Mode. The lens uses the selected evidence set and exposes limitations.
4. Focus
Carry one supported guard into Current Focus—such as review first after a defined trigger—and inspect the next evidence window against it.
Coach is especially valuable after a loss because it separates urgent narrative from recorded sequence. Its post-loss lenses can compare immediate-after-loss P&L, timing, size, trade count, drawdown, setup, and review signals; the answer remains linked to the underlying trades. When timestamps, comparable size units, or reviewed setup evidence are missing, Coach shows the gap rather than pretending it knows why the trader acted.
TSB has processed 600K+ imported trades across its import history, and its source registry recognizes 328 exact broker, exchange, platform, and prop-export profiles. Those values mean imported trades and recognized source routes—not users, guaranteed compatibility, or trades analyzed by Coach. Reconciliation and field coverage still control each conclusion.
Reconcile the loss in Journal Inspect the post-loss sequence Set evidence-based Risk Mode
The Bottom Line
Do not trade the recovery target. Freeze new risk, verify the account, preserve the chronology, classify the event, and let the written account and session rules determine permission. A planned loss, execution breach, rule breach, and unresolved platform event require different responses.
The goal is not to feel fearless or to manufacture a green streak. It is to make the next decision reproducible. TSB makes that standard practical: exact trades, comparable sequences, honest evidence gaps, a strong Coach decision, and one Current Focus rule stay connected from loss to return.
Disclosure: Trader’s Second Brain is our product. Its post-loss re-entry and size-escalation detectors, AI Coach lens contracts, sequence observations, evidence limitations, Current Focus handoff, and canonical public-truth values were checked against the local codebase on September 10, 2026. This guide is educational risk-process information, not medical, psychological, legal, or individualized investment advice. See our editorial methodology.