Trading notes and execution evidence
Obsidian Trading Journal
Keep one Markdown file per trade, with stable properties for finding records and a body for execution evidence. The starter below works as note text with the core Templates workflow. Bases can organize and calculate from properties; a note file alone does not reconcile your trades.
A reusable Obsidian trade note
Put this Markdown file in your vault’s template folder. It uses the core Templates title/date variables and plain YAML properties; no community plugin or .base file is included. The created date is the note date, not the execution date.
This original starter is free to download. It contains blank prompts, not trading records or investment recommendations.
Download Obsidian template (.md)Set up the workflow
- 1
Choose a folder for trade notes
Keep trade notes and their attachments in a deliberate folder structure. Name files with a stable trade ID rather than a title that changes when the outcome changes.
- 2
Configure core Templates
Enable Templates if needed and select its template folder in Settings. Save the downloaded file there and edit template variables in Source mode.
- 3
Insert into a new note
Use Templates: Insert template. Fill the empty properties, then record execution timestamps in the body. The title/date variables describe the note.
- 4
Build views only after the fields are consistent
Use core Bases to view, sort and filter files by properties. Test any added formula on known records; the download does not include a preconfigured performance dashboard.
Fields to keep consistent
| Field | Store as | Review purpose |
|---|---|---|
| trade_id / account_alias | Text | Keep a stable link to the execution ledger without putting account credentials in notes. |
| symbol / quote_currency | Text | A ticker or currency label is not a data feed or FX conversion. |
| status / setup | Text | Use consistent values such as open, partial and closed. |
| created_on | Date | The template inserts the note creation date; keep actual execution times in the body. |
| tags | Tags list | Use trading for scope; add setup tags only after defining their meaning. |
| net_result (optional later) | Number | Only add a reconciled number with a known currency and accounting convention. Blank is not a loss or zero. |
Native properties and Bases change the comparison
Obsidian properties support structured values such as text, numbers and dates. Bases provides database-like views and formulas over file properties. It is inaccurate to describe the app as incapable of calculations or multi-note organization.
The accounting still needs a definition. A property called net_result does not establish whether costs, contract multipliers or FX were included. Keep its calculation reference in the note and distinguish missing results from a measured zero.
Keep the archive portable and the evidence connected
The supplied note uses plain Markdown and YAML. Keep statement and chart filenames in the evidence section, and confirm those references still resolve after moving the vault. Copying note text alone does not copy a separately stored attachment.
For a partial exit, add the execution to the linked ledger and record the remaining quantity. Do not mark the position closed just because one profitable exit occurred. Keep historical edits traceable with a review date and revision reason.
Plugins are optional extensions, not part of this download
This starter needs no Dataview query or third-party code. If you later add a plugin or external importer, evaluate its current behavior and data access separately. A plugin-generated chart still needs a reconciled input sample.
Retain the original vault before migrating. This guide does not provide a generic Markdown-to-Pineify trade importer, and a linked note is not a validated trading strategy.
Keep calculations connected to the note
Use the same trade ID in your note and numerical ledger. The Excel journal template provides a separate formula workbook with explicit units and costs. Check its assumptions before relying on the results.
For an account-based workflow, compare Pineify Trading Journal with a small reconciled sample. Its current Import History control is marked Coming Soon. This guide supplies no automatic note archive importer or one-click conversion of a trade log into a validated strategy.
Frequently asked questions
Does this template require Dataview?
No. It contains Markdown and YAML properties with core Templates variables. You can add Bases views or other tools later; no plugin query or performance dashboard is included.
Can Obsidian calculate statistics across notes?
Bases supports formulas and views over file properties. Whether your chosen setup calculates a trading statistic correctly depends on its fields, formula and included records. Obsidian is not limited to unstructured text.
Why does the template leave trade dates blank?
The created_on variable records the note date. A trade may have opened or closed earlier or in another time zone, so enter those execution timestamps from the source record.
Can I migrate this vault directly into Pineify?
There is no direct vault importer supplied here. Preserve the Markdown files and attachments, then manually check a small mapped sample if you choose a structured journal.
Setup references
Published by Pineify, which sells trading software. These are original starter notes based on the linked documentation, not vendor-endorsed templates or a hands-on ranking. Application plans and client features can change. A journal records evidence; it does not establish a trading edge.