A Friday review turns an approval gate into a visible record of how you made decisions under real market conditions. In TraderCoach, compare every queued, approved, and rejected trade so you can see where your rules held, where you overrode them, and what still needs a decision.
In April 1970, Apollo 13 was on its way to the Moon when an oxygen tank exploded. The crew, Jim Lovell, Jack Swigert, and Fred Haise, had a growing carbon dioxide problem in the lunar module. The available scrubber cartridges did not fit the system they needed to use.
NASA engineers in Houston worked from the materials known to be on the spacecraft and developed an improvised adapter. The outcome was uncertain while the crew’s consumables and options narrowed. NASA’s Apollo 13 history documents how the ground team sent the procedure to the crew, who assembled it and brought carbon dioxide levels down.
The important part is the record. Engineers did not ask the crew to trust an invisible process. They worked through constraints, checked available materials, sent instructions, and observed the result. A trader’s Friday review carries the same discipline at a much smaller scale: make the reasoning inspectable before confidence turns into memory.
Start with the trades that never became orders
The rejected queue often has more to teach than the orders you approved.
A rejected trade may have failed because the position size exceeded your rule, the stop made the downside too large, the setup arrived after a sharp move, or you had already reached a daily loss limit. Those are decisions worth preserving. They show the moments when a rule protected you from acting on an alert simply because it appeared.
Review each rejection on Friday and write one plain sentence about why it stayed unapproved. Keep the language factual: “Risk was larger than my limit at this stop,” or “I had three losses already.” Avoid rewriting the reason after you know what the market did next. A trade you rejected can later move in the direction you expected. That does not make the rejection wrong if it violated the risk rule you set beforehand.
This is how a decision record becomes more useful than a list of missed opportunities. It separates process quality from outcome luck.
For a closer look at protecting a daily limit, read Eli's Daily Loss Limit Held. The Third Alert Stayed Unapproved.
Review approved trades against the decision you actually made
Approved trades deserve the same scrutiny, including profitable ones.
On Friday, pull up the trade idea, the risk you accepted, the stop placement, and the condition that would have invalidated the setup. Then ask whether the approval matched your plan at that moment. If you approved after widening a stop, increasing size, or ignoring a recent loss streak, record that plainly.
The purpose is not to punish a bad trade or celebrate a good one. It is to find repeated choices. A profitable trade that broke your position-sizing rule can teach the wrong lesson if you only review profit and loss. A losing trade that followed the plan may show that the loss belonged inside the risk you accepted.
TraderCoach keeps the final decision with you. That gives you something autonomous bots cannot provide by default: a clear point where you can examine what you knew, what you chose, and whether the choice fit your rules.
Use queued trades to spot hesitation and drift
Queued trades show the decisions still competing for your attention. At Friday review, look for alerts that sat too long, were repeatedly reconsidered, or no longer matched the conditions that made them interesting.
A queue can expose a common problem: treating an old signal as current simply because it remains visible. Markets move. A setup that made sense when it was generated may need a fresh review before approval. If the trade’s cancellation condition is unclear, write that down for the next week.
Also compare the queue with your approved and rejected decisions. If you repeatedly leave high-risk trades unresolved rather than rejecting them, that may be hesitation. If you repeatedly approve similar setups after losses, that may be drift from your daily limits. Both patterns are easier to address when they are visible.
The five-second check before approval should cover size, stop placement, downside, and invalidation. This practical checklist gives those checks a fixed order.
Make Friday review a rule, not a verdict
Set aside a consistent Friday window. Review the full week in three passes: queued, approved, rejected. Count patterns only after you have enough decisions to see one. One week can be noisy. Several weeks may reveal that a particular setup, time of day, or response to losses deserves a rule change.
Apollo 13’s solution mattered because it could be checked against the actual spacecraft and the crew’s actual constraints. Your review should have the same standard. Use the decision record to test your process against the risk limits you claim to follow.
Next Friday, choose one repeated decision pattern and make one narrow change. You might cap size after consecutive losses, require an explicit invalidation condition, or reject signals that arrive after their setup has changed. Then review whether you followed that change the following week.
Educational content, not financial advice.
Comments
No comments yet.