Trading review
A 30-Minute Weekly Trading Review Process
A weekly review should end with one specific improvement, not a longer list of vague intentions.
The 30-minute checklist
| Time | Review |
|---|---|
| 0–3 min | Net P&L and number of trades |
| 3–7 min | Strategy performance |
| 7–10 min | Best and worst trade |
| 10–14 min | Mistakes and rule adherence |
| 14–18 min | Time of day and position sizing |
| 18–23 min | Costliest behaviour |
| 23–27 min | Replay one representative trade |
| 27–30 min | Choose one improvement |
- [ ] Net P&L reviewed after charges
- [ ] Strategies tagged consistently
- [ ] Best and worst trades opened
- [ ] Mistakes and rule adherence recorded
- [ ] Time, sizing and costliest behaviour checked
- [ ] One next-week rule written
Questions to ask
- Was the result driven by execution, setup, size or cost?
- Which rule was followed most reliably?
- Which behaviour had the largest avoidable effect?
- What would I repeat even if the result was negative?
- What one observable action changes next week?
Example weekly summary
Fictional summary: net P&L was ₹420 across 12 trades. The morning setup tag had the clearest sample, while late entries were the most common mistake. Rule adherence was strong in size but weak in stop placement. Next week's single improvement is to enter the planned stop before sending the order and review it after exit.
In TradeLore, a simple workflow is: sync or import trades, complete journal fields, review reports, replay one trade, and capture the next rule in your journal or playbook. This is a process suggestion, not a profitability promise.
Prepare before the 30-minute review
Do not spend the review rebuilding the data. Complete journal fields after each session, keep strategy and mistake tags consistent, and make sure imported trades have been matched. At the start of the weekly review, note the date range, number of trades and whether all charges are included.
If data is incomplete, use the first few minutes to identify what is missing, not to draw conclusions from a partial report. A clean smaller sample is more useful than a large sample with unknown gaps.
Questions for each checkpoint
| Checkpoint | Questions |
|---|---|
| Net P&L | Was the result gross or net? What was the largest contributor? |
| Strategy | Which tags have enough observations to compare? |
| Best / worst trade | Was the outcome and execution quality aligned? |
| Mistakes | Which action repeated and what did it cost? |
| Sizing | Did quantity match the written plan? |
| Time | Did time-of-day effects survive strategy controls? |
| Next week | What one observable behaviour changes? |
Suggested TradeLore workflow
Use the current app flow as a sequence: import or sync the broker data, review the matched trades, complete pre-market and post-trade journal fields, open reports for strategy and time breakdowns, replay one representative trade, and record the next rule in your journal or playbook. Keep the workflow short enough to repeat.
The review is for process learning. It does not promise profitability and does not replace the broker statement or a risk plan.
Keep reading
Make review part of your trading day
Finish the review with one action you can observe next week.
Start using TradeLore