Direct Answer
Documenting a technical thesis means writing down the specific technical reasoning behind a trade or market view before acting on it, rather than relying on memory afterward. A complete thesis generally states the timeframe the analysis applies to, the key levels or signals the view depends on, the conditions that would confirm the thesis is playing out as expected, and the conditions that would invalidate it.
The value of doing this in advance is that it makes an objective after-the-fact review possible: whether the original reasoning was sound can be checked separately from whether the trade's outcome was favorable. This separation is commonly cited as a way to improve decision quality over time, independent of any single trade's result.
Key Takeaways
- A thesis is written before the trade, not reconstructed after. Reasoning captured in advance reflects what was actually known and believed at the time, before the outcome could color the memory of it.
- State the timeframe explicitly. The chart interval and expected holding horizon determine which levels and signals are relevant and over what period confirmation or invalidation should be judged.
- Name the specific levels or signals relied on. A vague view ("this looks bullish") is not reviewable; a stated level, pattern, or indicator reading is.
- Define confirmation conditions. What technical development, if it happens, would mean the thesis is playing out as expected.
- Define invalidation conditions before entry. What technical development would mean the original reasoning was wrong -- set in advance so it can't be adjusted after the fact to fit what happened.
- Review the thesis against the outcome afterward. This is what lets a trader ask whether the reasoning was sound, independent of whether the trade was profitable, which is commonly cited as improving decision quality over time.
What Is a Technical Thesis, and What Belongs in One?
A technical thesis is the practice of writing down the specific technical reasoning behind a trade or market view before acting on it. It is not a prediction made casually or held only in memory -- it is a short, specific record of why a trader believes a particular setup or level matters, written at the point the decision is made, before the outcome is known.
A documented thesis commonly includes four elements. The timeframe states which chart interval and holding horizon the analysis applies to -- a level that matters on a weekly chart may be irrelevant on a five-minute chart, so the timeframe frames everything else in the thesis. The key levels or signals are the specific technical basis for the view -- a support or resistance level, a moving average, a chart pattern, an indicator reading -- named precisely enough that another person (or the trader's future self) could check whether they held. The confirmation conditions describe what would happen if the thesis is correct -- the technical development that would support continuing to hold the position or add to it. The invalidation conditions describe the opposite: the specific technical development that would mean the original reasoning was wrong, defined before the trade so it cannot be quietly redefined after a loss to make the original call look more defensible than it was.
The reason this practice is commonly cited as useful is that it makes objective review possible. Without a written thesis, a trader evaluating a past trade is relying on memory, which is shaped by the outcome -- a losing trade is easily remembered as having been reckless from the start, and a winning trade as having been obviously correct, even when the underlying reasoning was similar in both cases. A dated, written thesis removes that distortion: the reasoning can be compared to what actually happened, and a trader can ask whether the process was sound even when the result was unfavorable, or whether a profitable trade actually reflected good reasoning or simply luck. There is no universally correct format for a thesis -- some traders use a dedicated trading journal, others a simple note attached to the trade -- but the four elements above are generally what separates a documented thesis from an undocumented hunch.
Hypothetical Example -- For Education Only
Suppose a trader is looking at a stock, referred to here only as "Stock X," on the daily chart. Before entering a position. The trader writes the following thesis:
| Element | Written thesis |
|---|---|
| Timeframe | Daily chart; expected to play out over roughly two to six weeks (swing horizon). |
| Key levels / signals | Price has tested a $50.00 support level three times over the past two months without closing below it; the 50-day moving average is trending up and sits just below current price at $49.20. |
| Confirmation condition | A daily close above the recent swing high of $54.00 would confirm the thesis -- support held and buyers are pushing through the prior resistance. |
| Invalidation condition | A daily close below $50.00 would invalidate the thesis -- the support level has failed and the reasoning for the trade no longer holds. |
Two months later, suppose the stock closes at $48.50 -- below the stated $50.00 invalidation level -- and the position is stopped out at a loss. Because the thesis was written down in advance. The trader can review it objectively: the support level and the invalidation condition were clearly defined, the trade was exited according to the plan when the level failed, and the loss reflects a thesis that did not play out rather than a process failure. This is a different, and more useful, conclusion than simply noting "the trade lost money" -- it evaluates the reasoning and the process, not just the outcome. Had the thesis not been documented, it would be easy to misremember the entry as based on a different, less specific level, or to judge the trade purely by the loss rather than by whether the original reasoning and exit discipline were sound.
How to Apply This, and Common Mistakes
Write the thesis before the order, not after
The entire value of the practice depends on the thesis being written before the trade is placed, or at the moment it is placed, not reconstructed afterward. A thesis written after the outcome is known is no longer a record of reasoning -- it becomes a justification shaped by hindsight, which defeats the purpose of documenting it in the first place.
Keep levels and conditions specific, not vague
"I think this stock looks strong" is not a reviewable thesis. A specific level, signal, or price is. Vague theses cannot be checked against what actually happened, so they cannot support an honest after-the-fact review.
Don't move the invalidation level after the trade is open
A common mistake is redefining the invalidation condition once price approaches it, to avoid admitting the thesis was wrong. This defeats the purpose of setting the condition in advance -- the invalidation level should be treated as fixed once written, even if the trader chooses to manage the position differently in real time.
Review sound reasoning and unfavorable outcomes separately
A well-reasoned thesis can still lose money, and a poorly-reasoned one can still work out. The point of documentation is to evaluate these independently over a series of trades, rather than judging every decision purely by whether it happened to be profitable.
Match the thesis to the trader's actual process
There is no universally correct format or level of detail -- a brief note on a dedicated trading journal is sufficient for some traders, while others prefer a more structured template. What matters is that the four core elements (timeframe, key levels or signals, confirmation, invalidation) are present and written before the trade, in a format the trader will actually keep up with consistently.
Memory Rewrites, Documents Do Not
The reason to write a thesis before acting has less to do with discipline than with how recall works. After an outcome is known, the reasoning that led to a winning trade is remembered as sharper than it was, and the reasoning behind a losing one is remembered as more tentative. A note written before the outcome existed is the only account of what you actually believed, and it is the difference between reviewing your process and reviewing a story about it.
Four things make a thesis reviewable. The timeframe, since the same chart supports different conclusions at different horizons and without it there is no way to judge whether the view had time to play out. The specific levels or signals relied on, because this looks bullish cannot be evaluated later. What would confirm it. And what would invalidate it.
The invalidation line is the one that does the work. Deciding it in advance means the exit is a rule rather than a judgment made while a position is moving against you, and it also makes the review honest: either the stated level held or it did not.
Keep it short enough that you will actually write it. A few lines naming the timeframe, the level, the confirmation and the invalidation is worth far more than a detailed document you skip when you are in a hurry, which is exactly when the reasoning is most likely to be thin.
FAQ
What is a technical thesis?
A technical thesis is the specific technical reasoning behind a trade or market view, written down before acting on it. It generally includes the timeframe being traded, the key levels or signals the view relies on, the conditions that would confirm the thesis is playing out, and the conditions that would invalidate it. Writing this down in advance is commonly cited as a way to review decisions objectively afterward, independent of how any single trade turns out.
Why document a thesis before entering a trade instead of just after?
Reasoning written down before a trade reflects what was actually known and believed at the time, unaffected by the outcome. Reasoning reconstructed after the fact is vulnerable to hindsight bias -- a losing trade gets remembered as reckless, a winning trade gets remembered as obviously correct, even when the underlying analysis was similar. Documenting a thesis in advance is what makes an honest after-the-fact review possible.
What should an invalidation condition include?
An invalidation condition is the specific technical development that would mean the original reasoning was wrong -- for example, a close below a stated support level on the stated timeframe, or a signal reversing. It should be defined in the same terms used to build the thesis, before the trade is placed, so it can be checked objectively rather than adjusted after the fact to fit what happened.
Does documenting a thesis guarantee better trading results?
No. Documenting a thesis does not change the odds of any individual trade working out, and a well-reasoned thesis can still be wrong. What it is commonly cited for is improving decision quality over time, by making it possible to separate whether the reasoning was sound from whether the outcome was favorable -- a distinction that is difficult to make from memory alone.
How is a technical thesis different from a general trading plan?
A trading plan is typically a broader, standing set of rules covering position sizing, risk management, and the setups a trader looks for across many trades. A technical thesis is narrower and specific to a single trade or market view -- the timeframe, levels, and confirmation/invalidation conditions for that particular idea. A trading plan can require that a documented thesis exist before a trade is taken.
What timeframe should be included in a documented thesis?
The timeframe is the chart interval and holding horizon the analysis is based on -- for example, a daily-chart swing thesis expected to play out over several weeks, versus an intraday thesis expected to resolve within a session. Stating it explicitly matters because a level or signal that is meaningful on one timeframe may be noise on another, and it sets the horizon over which confirmation or invalidation should be judged.
Should the thesis record a falsifying condition separately from the stop?
They are different things and both are worth writing down. A stop is a price at which the position is closed for risk reasons. A falsifier is the condition under which the reasoning was wrong, which might be a failure to break a level within a stated number of bars, or a move in a related instrument. A thesis can be invalidated without the stop being reached, and recording only the stop loses that.
How do you avoid writing a thesis that cannot be wrong?
By requiring it to name in advance an observation that would refute it. A thesis phrased so that a rise confirms strength and a fall confirms accumulation accommodates every outcome and therefore carries no information. The test is simple: read the document back and ask what would have to happen for it to be judged incorrect. If nothing qualifies, the thesis needs rewriting before the position is sized.
Is documentation less necessary for a systematic approach?
A systematic rule is already documented, in the sense that the code specifies exactly what it will do. What is not documented is why the rule exists and what evidence justified each condition, which is the part that decays when the rule is later modified. A discretionary read has neither, which is where writing it down adds the most. Both benefit; the gap is larger for the discretionary case.
References
Disclaimer
This article is for educational and informational purposes only and does not constitute personalized investment, financial, or legal advice. The hypothetical example above uses illustrative numbers and does not represent a recommendation to trade any specific security. Trading involves risk, including the possible loss of principal.