A Sunday rejection review turns skipped trade signals into evidence about your decision process. Review the ideas you rejected, record what happened next, then look for the market conditions in which your judgment becomes least reliable.
In September 1854, physician John Snow faced a cholera outbreak in London’s Soho district. The cause remained disputed. Snow plotted deaths by location and found a concentration around the public water pump on Broad Street.
The map changed the argument. What looked like separate tragedies became a geographic pattern.
A rejection feels different after the market moves
A rejected trade can become uncomfortable by Sunday.
Suppose an approval-gated trading assistant queued five ideas during the week. You rejected three. By Friday’s close, two had moved in the predicted direction.
The easy conclusion is that you interfered with valid signals. Regret supplies an even harsher version: the system was right, you were wrong, and next time you should approve faster.
That conclusion ignores the information available when the decisions were made. A favorable outcome does not prove that approval was sensible. A losing outcome does not prove that rejection was correct.
Snow faced a related analytical problem. A death near Broad Street did not establish the cause of the outbreak. The concentration became informative only after cases were placed together and compared by location. Steven Johnson documents the investigation and its contested context in The Ghost Map. The local Board of Guardians removed the pump handle, although the epidemic was already declining, so the intervention alone could not settle every causal question.
The trading equivalent is a map built from decisions rather than addresses.
Record the decision before judging the result
Start with the information that existed at the approval deadline. For every rejected idea, record:
- The proposed entry, stop, position size, and intended holding period.
- The reason for rejection in one sentence.
- The market condition at that moment, such as widening volatility, low liquidity, an opening gap, or correlated exposure.
- Whether the signal changed materially while it waited.
- What happened after rejection, including maximum favorable and adverse movement.
Keep the reason specific. “Didn’t like it” teaches you nothing. “Rejected because the wider stop increased planned loss beyond my per-trade limit” can be tested against later decisions.
Separate process quality from outcome quality. A disciplined rejection can be followed by a large move. A careless approval can make money. Confusing those categories trains you to reward luck and punish restraint.
This distinction matters when queued orders can become stale. When should overnight approval for a queued trade expire? examines why elapsed time can change the risk behind an otherwise valid signal.
Turn isolated rejections into a conditions map
After several weeks, group rejected ideas by condition. Do not begin by calculating missed profit. Begin with behavior.
You may find that your weakest decisions cluster during the first minutes after the open. Perhaps you reject normal setups after two consecutive losses, approve larger positions late in the day, or abandon your rules when several holdings depend on the same market move.
Numbers make those patterns harder to rationalize. Track the share of rejected ideas that violated a written risk rule, the share rejected because of fear or uncertainty, and the share that would have exceeded a portfolio limit. Also compare planned risk with the risk that existed when approval was actually possible.
The sample may be small. Treat the result as a hypothesis, not a discovery. Ten rejected trades cannot establish a durable edge. They can reveal a question worth testing across a longer period.
The goal is not to prove that every rejection was correct. It is to locate the conditions under which your process changes. That is the explicit bridge from Snow’s map to a trading journal: individual outcomes create anecdotes; grouped conditions expose concentrations.
Write one rule for the next week
Finish the review with one change you can observe.
If rejections cluster after losses, require a short written comparison between the queued signal and your existing plan. If position size causes repeated hesitation, set the maximum planned loss before the session begins. If overnight signals often arrive stale, define when they must return for review rather than carrying approval forward.
Do not rewrite five rules at once. That makes it difficult to identify which change helped.
An approval-gated assistant preserves this pause between a generated signal and a real order. The human still owns the decision. The record should therefore include both sides: what the system proposed and why the trader approved or rejected it.
On Sunday, review the map without scoring yourself by missed profit. Circle one recurring condition, write one rule beside it, and apply that rule to every relevant decision during the next week.
Snow’s map did not make every disputed fact disappear. It made the concentration visible. Your rejection review should do the same.
Educational content, not financial advice.
Comments
No comments yet.