What Is a Trading Decision Log? A Plain Definition, Field by Field

What Is a Trading Decision Log? A Plain Definition, Field by Field

A trading decision log is a dated record of what you decided before you placed a trade, and why.

That is the whole definition. Everything after it is bookkeeping.

The word doing the work is before. A log written after the position is open is not a decision log. It is a story about a decision, and stories get edited once the outcome is known. A log written before the fill commits you to a position in your own words, at a fixed date, with no knowledge of how it ends.

This is why a log can be audited and a diary cannot.

What a decision log is not

It is not a trade journal. A journal usually records what happened – entries, exits, profit and loss – and often gets written in a single sitting at month end.

It is not a watchlist. A watchlist says what you might buy. A log says what you decided to buy, at what size, against what evidence, and what would prove you wrong.

It is not a performance claim. A log says nothing about whether the decision was good. It only fixes the decision in time so that later, someone other than you can check it.

The fields, one by one

A useful log is narrow. Add fields and you stop filling it in. These are the ones that survive contact with a real process.

As-of date. The timestamp the entry is written. Not the trade date. The as-of date is the promise that nothing in the entry was known after that moment.

Instrument and direction. What was bought or sold, long or short.

Size. How much, and how that size relates to the rest of the book. A position with no stated size cannot be reconciled against anything.

Thesis. One or two sentences on why. If it takes a paragraph, it is not a thesis yet.

Evidence. What you actually read – a filing, a dataset, a methodology page. Name it. “It felt cheap” is a mood, not evidence.

Invalidation. The condition that would prove the decision wrong. This is the field most people skip, and it is the one that makes the rest checkable. A decision with no defined invalidation can never be marked wrong, which means it can never be marked right either.

Expected holding period. Weeks, months, years. A thesis with no horizon cannot be judged on schedule.

The vote or the reason. If one person decides, say so. If a committee decides, record the decision and any dissent. A log that hides dissent is a log that has been cleaned up.

Executed or not. A decision can be logged and then not taken. Recording the pass is as useful as recording the fill – it is the only way to see what you talked yourself out of.

Why the as-of date carries the weight

The as-of date is the one field that cannot be reconstructed later. Everything else can be rebuilt from memory, roughly, with the benefit of hindsight.

Fix the date and a strange thing happens: the entry stops being a record of what you believe now and becomes a record of what you believed then. Those are different documents, and only one of them can be graded.

The convention worth adopting is blunt: every number in the entry carries an as-of date, and no entry is ever revised after the fact. Corrections are added as new entries, dated, so the trail of thinking stays visible.

How to reconcile a logged entry against the fill

This is the step that turns a log into a control.

After the fill, place the two documents side by side: the entry you wrote before the trade, and the confirmation that followed it. Then answer three questions.

  1. Does the fill match the decision? Same instrument, same direction, same size band.
  2. Did the invalidation you named get touched at any point – and if so, did you act on it?
  3. Was the entry written before the fill? The dates settle it.

A log you never reconcile is a filing cabinet. A log you reconcile on a schedule is a feedback loop, and it is the only version that tells you anything about the process rather than the outcome.

One more discipline: publish the misses on the same schedule as the wins. An audit trail that only runs when the news is good is not an audit trail – it is a highlight reel with dates on it.

What a log lets a reader check

For someone evaluating a strategy, the log is the difference between a claim and a record. A track record without a log asks you to trust the summary. A log lets you test the summary.

You can look for entries dated before fills. You can look for the losing decisions sitting next to the winning ones, on the same page, with the same formatting. You can look for invalidation rules that were actually observed. And you can look for the decisions that were never taken.

None of that requires believing anyone. It requires a document with dates on it.

Diers Capital’s public log of every vote, dissent and fill stays free to read – no account, no paywall. The committee records decisions before the fill, dates every figure, and publishes losses on the same schedule as wins. Membership adds the logged-in view on top: current positions, full decision history and the cross-account picture. The log itself is the part we would rather you verified.

The short version

A trading decision log is a dated, pre-trade record of what you decided and why, with a stated invalidation and a size, kept in a form where it can later be checked against the fill that followed. Write it before the trade. Date what you know. Never edit it after. Reconcile it on schedule.

Then the log stops describing your decisions and starts testing them.

This article is educational and describes a method, not investment advice. It is not a recommendation to buy or sell any security. Figures referenced in any Diers Capital log are published with their own as-of dates and can change.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *