Article
Draw First, Think Later: Naming Your Markup After the Fact
Plenty of chart work happens before the reasoning arrives. That is fine. The export is the deadline, not the drawing.
Advice about labelling your chart usually assumes you knew what you were doing when you drew it. Often you did not. You saw something, drew it fast, and worked out what it meant afterwards. That is a normal way to read a chart, and it does not stop the markup becoming a record.
The Order Most Advice Assumes
Have a thesis, draw the level that expresses it, label it, act. Tidy, and not how most sessions actually go.
The real order is often: notice something, draw it immediately before it disappears, sit with it, then realise what you were looking at. The drawing comes first because it is how you hold the thought still.
Why That Is Fine
Nothing in the loop requires you to know what a line means at the moment you draw it. The loop requires the line to be named by the time it becomes a file.
That gap, between drawing and understanding, is where the thinking happens. Forcing a name too early usually produces a worse one.
The Export Is the Deadline
The reason the deadline exists at all is that names get harder to write with every hour that passes. The reasoning is vivid at the end of the session and gone by the next morning.
So the rule is not draw, then name. It is: name before you export, and export before you close the session.
| When | What it costs |
|---|---|
| Naming as you draw | Sometimes a worse name, because the thinking is not finished |
| Naming before the export | A few seconds, while the reasoning is still in your head |
| Naming next week | Not possible, in practice |
The Lines You Cannot Name
Some drawings will not take a name when you come back to them. That is information, not a failure.
A line you cannot describe by the end of the session is usually one you drew because the chart looked a certain way, not because you concluded anything. Deleting it is the honest move, and it keeps the export from filling with markup you will never trust.
- If you can name it, keep it and export it.
- If you cannot name it but it still interests you, name what you are unsure about.
- If you cannot do either, delete it before it becomes a permanent record of nothing.
What Good Late Names Look Like
The names in the sample export were written this way, and none of them describe geometry. They describe what the trader was waiting for.
| Name | What it records |
|---|---|
| October High Break | Where the level came from, so it can be re-derived |
| Stop-in long above 212 | The condition, in the trader’s own rounding |
| Long above short below range break 276.75 | A two-sided rule at one price |
| Trend Line Break | An event, marked where it happened |
| Open Gap | The reason the line is there at all |
The Habit, Stated Once
Draw as fast as you like. Think for as long as you need. Then name everything you are keeping, delete what you are not, and export.
The loop does not care in which order you understood the chart. It only cares that the file leaving your machine says what you meant.
FAQ
Is it bad practice to draw before I know what I am looking at?
No. Drawing is often how the observation gets held long enough to think about. The loop only asks that the drawing is named before it becomes a file.
What if I genuinely cannot name a line?
Delete it. A line you cannot describe at the end of the session is one you will not trust at the start of the next.
Can I rename drawings later?
You can, but the names written while the reasoning was fresh are consistently better than the ones reconstructed a week later.
Does this change what the export contains?
No. The file carries whatever the drawings are called when you export. The habit is about making sure that is something worth reading.
Sample Structured Chart-Data Exports
Review how chart drawings, annotations, OHLC, volume, and execution context become reusable structured data.