CONNECT THE CALCULATION TO THE JOURNAL

Pre-trade ticket

Keep the assumptions you checked before a trade beside the result you reconcile afterwards. A stable trade ID links the plan, your six checks and the journal export.

This is a local record, not an order. Ticking every box does not establish readiness, guarantee an execution price or authorise a trade. Prices, costs and manual pip values are copied assumptions. Editing this ticket does not recalculate position size or risk.

This module does not send ticket fields to a server. Saving uses localStorage in this browser profile, readable by site scripts and people with access to that profile. Clearing site data removes the library; download backups. Other site scripts follow the site privacy policy.

Record the plan

Return to position sizing

Trade ID:

Unsaved plan

Pair / instrument

Account currency code

Setup / playbook label

Session label

Planned direction

Planned entry price

Planned stop-loss price

Planned target price

Copied calculation assumptions — verify before use

These fields keep the calculation context. They are editable notes, not a live calculation. A blank is unknown, not zero. Manual pip values are never converted or re-derived here; check the instrument, account currency, quote currency and source date in the original calculator.

Account balance

Planned risk (% of balance)

Stop distance (pips)

Volume (lots)

Modelled loss at SL (account units)

Modelled costs (account units)

Instrument units per lot

Pip size in price

Pip value source

Pip value per lot (account units)

Quote currency code

Rate: 1 quote unit in account units

Exchange-rate source date

Plan notes / specification source

Check the specific order

Mark only conditions you have checked for this plan. Saved checks document your earlier declaration; loading them does not verify current conditions.

Specification: instrument, pip size, lot size, costs and currency match the broker’s current contract. Stop loss: its level and execution convention follow the setup; a gap can exceed the modelled loss. Budget: volume, costs, existing positions and total planned risk are within the written limits. Margin: current equity, used margin, broker requirements and close-out rules have been checked. Events: relevant releases, session hours and execution conditions have been checked. Plan: the setup, direction and stand-aside rules match the playbook.

An incomplete plan can be saved as a draft. It has no realised P&L, closing time or R result and is excluded from completed-trade analysis.

After closing: reconcile the outcome

Use the actual closed position and documented costs, not the planned target. Net P&L and initial monetary risk must use the same account currency. Include commissions, financing and applicable conversion in net P&L according to one consistent convention.

Net realised P&L (signed account units)

Confirmed initial monetary risk (> 0)

Actual closing time (UTC)Enter UTC explicitly. This field does not convert your device’s local time.

I have reconciled a closed trade, its net P&L, original initial risk, currency and closing time against my records. These are realised results, not a hypothetical plan.

Only this action creates a completed record. R is calculated as net realised P&L / confirmed initial risk. Zero P&L is valid; an empty P&L or zero risk is not.

Local trade library

CSV uses r_net, pnl_net, initial_risk, pair, setup, session, closed_at, trade_id, trade_state, account_currency. Planned rows have blank outcome fields and trade_state=planned; the journal analyser rejects them. Completed-only export is the simplest route to analysis. Exports contain your entries and monetary amounts: review them before sharing.

Instrument / ID	State	Setup	Net R	Actions

Up to 2,000 records and 1 MB in this library/backup. A merge keeps the existing record when an ID is duplicated; it does not overwrite it with imported content. When another tab changes the library, reload before saving. Download your current draft first.

Record lifecycle and limitations

Version 1.0.0, 26 October 2026. A plan stores assumptions and self-declared checks. A completed record additionally requires finite net realised P&L, positive documented initial monetary risk, an actual closing timestamp and explicit reconciliation. Planned targets and modelled SL losses never become realised results automatically. The tool does not contact a broker, verify documents or prove that a plan was frozen before execution.

The calculator transfer is read from sessionStorage in the same browser tab. It must target this ticket, be no more than 20 KB and less than 24 hours old. The ticket copies its assumptions without recomputing them. It does not infer exchange rates for manual pip values. A trade ID uses crypto.randomUUID() where available, with a local random fallback; the ID is a join key, not evidence of a transaction.

JSON imports are schema-checked before merging and limited to 1 MB and 2,000 unique IDs. Labels are displayed as text, and spreadsheet formula prefixes in exported labels are neutralised. Backups and exports are local files. There is no synchronisation across devices or independent verification of completed status.