Before you start: Sign in to Journal.

Getting started checklist

New journals show a setup checklist on Dashboard: create a trading account, optionally set Your lines, confirm an import or add a manual trade, and save a closed trade as reviewed. Sample trades do not complete the import or review steps. The checklist hides when all three required steps are complete. You can also hide it earlier. Return anytime through your account menu → Getting started; revisiting preserves your progress. Hiding the checklist and deferring Your lines are remembered across devices.

Steps

Use the navigation button in the top bar to collapse the desktop sidebar to icons; your preference is remembered on this device. On mobile, it opens a drawer. Close it with Escape, the close button, the backdrop, or by choosing a destination. The account menu contains Profile, Trading accounts, Preferences, Plan, Billing, Privacy, Getting started, Handbook, What’s new, and Legal. Choose Light or Dark in the Theme selector. Ops is shown there only for authorized administrators. Each destination shows only its own sections.

1. Open Dashboard. Choose Upload tradebook, Add manual trade, or Explore with sample data.
2. For your own trades, create a named account in Trading accounts and select it when adding trades.
3. Check the import result, then open Trades and review one trade.
4. Return to Dashboard to explore your results; check the date and account filters.

If something looks wrong

Sample data is the way to demo TradeTattva without uploading anything real. It is synthetic and visibly labelled. Use Remove sample data in the sample-data banner when finished. An empty filtered view does not necessarily mean the upload failed: clear filters and check account/date scope.

Related help

Review a trade · Trading accounts

Review counts in the sidebar

The Trades badge shows closed trades still awaiting review, not the total number imported. Sessions shows past or current sessions awaiting review. Each badge disappears when its queue is clear. Saving a trade review does not complete the session review: mark and save each separately.

AI Review

During the owner pilot, authorized accounts can open AI Review from the sidebar. Reviews, the Action queue and Investigations remain read-only until you explicitly generate or save a result; opening the screen never changes a trade or session. See AI Review and agent investigations for evidence requirements, limits and the weekly review.

Tavya

When available for your account, Tavya at the bottom of the sidebar opens help beside the sidebar. A compact sidebar shows its icon with a tooltip. Drag the desktop chat header horizontally to dock at either side, or use Left/Right arrows; Home returns beside the sidebar. Reopening always starts beside the sidebar. On mobile, open navigation and select Tavya for full-screen chat. Closing returns focus to navigation. The opening and closing morph respects reduced-motion preferences.

Use the header’s circular AI usage control to see usage, remaining allowance and reset time without taking up conversation space. The reset icon starts a new conversation; it does not reset your allowance. Availability and limits depend on your account and the deployment. Product-help chat does not automatically attach your journal records; AI trade/session review has a separate evidence preview.

Before you start: Identify which broker account owns each set of executions. A Journal trading account is a ledger identity, not a broker connection.

Steps

1. Open User menu → Trading accounts. Choose the add-account control, enter a name and broker, and choose Add account.
2. Select that account when importing or manually adding its trades. Use the top account selector to review one account or all accounts.
3. For unresolved old fills, find their label, choose the destination account and select Assign fills. Check the source label, destination and fill count in the dialog, then confirm.
4. Use the account’s edit control to rename it without changing its identity. Use the separate Archive button beside Edit on the account row and confirm. Archive keeps history but blocks new fills; use the Archived tab and Restore before adding new fills again.

If something looks wrong

Assignment applies to the unresolved fills under that label, not an arbitrary selection of trades. A label already assigned to another ledger cannot be silently moved. If the destination or count is wrong, cancel; do not reupload with a different label as a workaround. Capital must be set up separately under Your lines.

Related help

Account capital · Account-aware pairing

Before you start: Have access to your Zerodha Console account and know the segment/date range you need.

Steps

1. In Console, open Reports → Tradebook. Select the segment and dates, then request the report.
2. Download the tradebook as CSV or XLSX. Keep the original file. Zerodha’s help states a maximum of 365 days per download; use separate ranges for longer history.
3. In Journal, open Add trades → File upload, select the trading account and choose the file.
4. Check the preview’s broker, dates, symbols, account and new/duplicate counts. Choose Import … fills, wait for completion and open Trades.

If something looks wrong

Use the execution tradebook, not a holdings statement, tax P&L or contract-note PDF. Missing entries/exits can leave trades open. For unexpected duplicate counts, stop and check import history instead of repeatedly uploading.

Related help

Preview and errors · Duplicates and removal
Broker download source: Zerodha Support, checked 20 September 2026. Journal file support is verified separately against its importer.

Import Kite orders before the Console tradebook is ready

1. In Add trades → File upload, choose Zerodha, then Kite orders · provisional, and select the trading account. If no account exists, create one in Trading accounts first, then return to the upload.
2. Upload the original order-history CSV. Check the executed quantities, instrument, trading date and average prices in the preview. Orders contain average execution prices, not individual tradebook fills.
3. Confirm that there were no carried positions in the instruments covered. If there were, do not make that confirmation: use Console tradebook history covering the opening executions and subsequent activity instead.
4. Use the import confirmation only when the preview is valid. A short preview is not proof that the whole file contains only those rows; check the reported totals. Missing account selection, no new rows or reconciliation conflicts can block saving.

Important · Confirm your trades later. Upload the Console tradebook to the same trading account when available. Journal compares the executions with provisional orders; uncertain or differing matches require reconciliation rather than silently adding overlapping executions.

Provisional trades let you begin reviewing sooner, but remain labelled provisional until confirmed. Charges remain estimates. An unmatched exit may require earlier opening executions; do not invent an opening trade or use a different account to bypass a conflict.

Before you start: Have your original Upstox execution report. Journal supports its recognised Trade XLSX and a specific text-based F&O PDF layout.

Steps

1. Open your Upstox reports portal. Journal’s existing download guidance points to account.upstox.com → Reports → Trade; look for the execution report for your segment and period.
2. Download the original XLSX, or the supported Trade PDF. Do not substitute a Ledger or P&L summary.
3. Open Add trades → File upload in Journal, select the trading account and upload the file.
4. Check that the preview identifies Upstox and reads the correct dates, contracts and quantities. Confirm the import only after checking the new and duplicate fills.

If something looks wrong

The PDF reader supports a text-based, 15-column F&O Trade report and validates complete pages. Scans, other layouts and incomplete pages can be rejected. Try the original supported XLSX if a PDF is refused. The exact current Upstox download-button sequence has not been independently verified; if the portal differs, consult Upstox Help Center for the Trade report, rather than guessing another report.

Related help

Preview and errors · Missing exits and pairing

Before you start: Have access to m.Stock and the execution period you want to import.

Steps

1. In m.Stock, open Reports → Trade History and choose the relevant reporting period. Download the original report.
2. Use a recognised XLSX or text-based PDF Trade History file in Journal.
3. Open Add trades → File upload, select the trading account and choose the file.
4. Check the preview, including contracts, quantities, dates and duplicates; then confirm the import.

If something looks wrong

The supported PDF uses a seven-column layout; scans or other layouts are not interchangeable. This report does not provide execution time: Journal uses the exchange trade-number ordering, so do not treat its time-of-day output as observed execution times.

Related help

Preview and errors
m.Stock’s platform tour confirms Reports, Trade History and report downloads (checked 20 September 2026). File-layout support comes from Journal’s importer; the tour does not verify every current download control.

Before you start: This is the route for any broker TradeTattva does not read natively — Groww, Angel One, or an international tradebook. Use a non-empty UTF-8 CSV with column headings and executions. Arbitrary spreadsheets or PDFs cannot use this mapper.

Steps

1. Open File upload and select your CSV. An unrecognised CSV opens Match your CSV columns.
2. Map symbol, side, quantity, price and timestamp. Map trade ID, order ID and segment if present; inspect the sample values.
3. Select a trading account, or enter the required unresolved account label. Use the same account identity for later uploads.
4. Choose the timestamp format and CSV timezone for timestamps without an offset. Check day/month versus month/day carefully.
5. Choose Validate and import. If validation names a bad row, correct the source file and retry; the invalid mapped file is not partly saved.

If something looks wrong

Use whole-unit quantities and decimal-point prices; fractional quantities are unsupported. Times are converted to the India market clock. Missing trade IDs can duplicate on reupload. Importing an international symbol does not provide currency conversion or guarantee a suitable charge model.

Related help

Duplicates · Import errors

Start at Add trades → File upload. Choose the trading account and upload the original broker tradebook. A supported native file opens a preview before saving; another compatible CSV opens the column mapper.

Supported native reports

The table reflects Journal’s importer registry. Broker portal labels can change; see the broker-specific guides for source verification and report restrictions. For example, a compatible Groww CSV can use the mapper. Other XLSX/PDF layouts do not become supported through it.

Dhan contract-note PDFs

1. In Dhan, select your Profile icon, then My profile on Dhan.
2. Open Journal by Dhan → Statements and Reports → Contract note.
3. Select the trading date and download the contract-note PDF. Include all pages and the Trade Annexure.
4. In TradeTattva Journal, choose Add trades → File upload → Dhan, select a trading account and upload the PDF. Check the preview, then confirm the import.

If the PDF is password protected, unlock a copy locally before uploading. Journal does not ask for the PDF password or PAN.

Journal reads execution times, order IDs, trade IDs, quantities and prices from the annexure. The verified text layout supports NSE equity and options. Missing pages, unreadable rows, unsupported segments and product remarks reject the entire note. Summary tables are never imported as additional fills. Date-only P&L reports and scanned PDFs are not substitutes.

The preview reconciles execution amounts and reported charges. Confirming saves the charges and allocates each component by execution turnover within its segment. Covered executions use those allocations instead of estimates; uncovered executions keep rate-card estimates. Repeat uploads add no duplicate fills or charges. Re-uploading an older note can add charges to existing fills; the preview names this update. Conflicting execution or charge evidence is blocked. Prior CSV imports or future API imports are not automatically reconciled with these PDFs.

For a carried position, import its earlier executions into the same account. A contract note’s net cash obligation is not necessarily realized profit or loss. Contract notes are available after the broker issues them; this is file import, not immediate live sync.

Read the preview

1. Check the recognised broker, chosen trading account, symbols and execution times. If an account/broker mismatch is shown, correct it or explicitly confirm only when intentional.
2. Check the date coverage and readable rows. Open any row errors before continuing.
3. Compare New, already imported and Without a trade ID. Missing trade IDs mean repeat uploads may create duplicates.
4. Choose Import … fills only when the reading is correct. Wait for completion, then open Trades. Cancel leaves the preview unsaved.

Common errors

A file-size error reports the upload limit for this installation. For an unsupported PDF, download the supported original XLSX instead; renaming the extension or uploading a scan will not fix its layout. For an empty report, check the segment and date range. Native imports can report skipped rows and reject severely unreadable files; mapped CSV validation rejects the entire file when a row is invalid. If you opened the export in Excel and saved it again, upload the original file rather than the re-saved one: mapped CSV validation guesses neither a decimal locale nor a date order, so a price Excel rewrote with a decimal comma or in scientific notation is rejected outright, and a timestamp rewritten into Excel’s display format no longer reads as ISO — you can select the matching date format in the mapper, but a native report is better re-downloaded than repaired. The byte-order mark Excel adds is handled, so that is not the cause; nor is saving as a workbook, since a native XLSX report is read directly. The column mapper takes CSV text only. It selects columns, timestamp format and timezone; it does not edit price values or repair decimal formats. Correct invalid numeric values in the source CSV before uploading again. Check the result’s skipped-row details after importing.

Next steps

Use duplicates and import removal, CSV mapping or trading-account assignment.

Before you start: Check the file, account and prior imports before uploading again.

Steps

1. Open Trading accounts → Data sources and review import history.
2. For an overlapping export, inspect the preview’s already-imported and without-ID counts. Identified fills are skipped; missing IDs can be imported again.
3. To remove the wrong file, use its removal control and read the confirmation. It removes the fills added by that import, not every fill in overlapping source files.
4. Review the remaining Trades and account scope after removal.

If something looks wrong

Removing an import can also delete orphaned reviews and screenshots. Reimporting fills does not restore those records. Export first if you need a copy. Native broker trade-ID checks span your journal, so separate accounts with colliding IDs can be skipped; do not change IDs or repeatedly upload to force them in. Assign unresolved fills through Trading accounts instead of attempting to move them by reuploading.

Related help

Export and recovery limits · Assign old fills

Before you start: This is the route for a trade that is in no tradebook at all — a different account or platform, a missed export, a backfill — and that you therefore type in yourself. Know the symbol, side, quantity, entry price/time and the correct trading account.

Steps

1. Open Add trades → Manual entry.
2. Enter the symbol, buy/sell side, quantity, entry price and entry time. Times use the journal’s India market clock. Select the account.
3. For a closed trade, provide the exit price and time. Leave both exit fields empty for an open trade. Choose Add trade.
4. To correct it, open the trade in Trades and choose edit beside the manual badge. Change the fields and choose Save changes. Use Delete… only if you intend to remove the manual record and its associated review.

If something looks wrong

Broker-imported executions do not have this manual-edit workflow. A validation error can indicate missing paired exit fields, an invalid quantity/price or an exit before entry. Fix the stated field rather than inventing an execution.

Related help

Review a trade · Exclude an imported trade

Before you start: Import or manually enter a trade. This is where journalling begins rather than on the Dashboard: the numbers describe what happened, a review records why. Begin with one recent trade and work down the queue. A useful review records your decision and execution, separately from whether the trade made money.

Steps

1. Open Trades, choose the trade and select Review trade →.
2. In the Setup tab, choose or type a Setup / strategy, then return to Review. Grade your plan adherence: A — On plan, B — One deviation, or C — Off plan. A losing trade can still be A.
3. Under Your read, record what worked and what you would change. Open Entry review to separate the observable trigger from why the trade was worth taking and what affected the decision. Use Trade management for changes made while the position was open, then record the exit reason separately.
4. Open Add tags for repeatable labels, or Screenshots to attach evidence.
5. Open Plan & strategy rules to record the planned risk and target you actually had. A value marked from plan comes from the day’s plan; a value you enter on this trade overrides it. Leave unknown values unset rather than inventing a precise plan after the outcome.
6. Tick Mark reviewed, then choose Save review. Save & next › saves and advances through the review queue.

Saving and missing values

Review edits require a successful save. If an error appears, resolve it before leaving. Existing review history is retained and the latest saved version is displayed; the export includes annotation history. Trades without recorded planned risk cannot contribute a measured R result. Notes have a 2,000-character limit.

Related help

Tags and grades · Screenshots · Void or restore a trade · Strategies

Use the drawer’s four tabs

Overview summarises the trade; Select strategy opens Setup. Executions shows the fills and order timeline. Setup holds the strategy selector, saved rules and rule assessments. Its optional setup context accepts any method: instrument/timeframe, reference inputs and observed conditions. Record whether the plan existed before entry, was reconstructed afterwards or was not recorded.

In Review, expand Entry review, Exit review and Next-session action. Exit reasons include Target, Stop, Trailing exit, Invalidation, Time-based, Discretionary and Other. These are structured review choices, separate from your tags. Explain what actually triggered the exit; leave unknown reasons unset.

Plan & strategy rules includes planned risk/target and stop adherence: record the stop reference, original invalidation and any position/stop changes. Choose Followed, Broke, Not applicable or Not assessed based on what you know. A loss below planned risk does not prove that the stop rules were followed. On leaving with unsaved edits, use the in-app discard confirmation carefully.

Optional AI trade review

1. If the AI card is available, choose Generate AI review and inspect the evidence preview before generating. Access is currently restricted to the owner pilot; an admin role or plan label alone does not enable it.
2. The preview includes this trade’s execution summary, current drawer review fields and the selected strategy’s saved rules. Screenshots, account identifiers and order IDs are excluded; identifying details typed into notes are still shared as written.
3. Read the feedback and evidence, then save the AI review separately. The button becomes disabled Saved. Your own notes and grade still require Save review.
4. Use thumbs up/down for feedback. If relevant inputs change, a saved result can be marked outdated; regenerate when you want a new assessment. A failed regeneration does not replace the saved result.

AI cannot verify chart signals from fills alone, does not automatically grade the trade and does not replace your judgment. Generation and regeneration use the shared AI allowance; reading, saving and feedback do not.

Before you start: AI Review is an owner-only pilot in this release. Its reports use the trades, sessions, plans, grades, notes and rule answers you recorded. It does not read charts from fills, place orders, alter reviews or infer intent from profit and loss.

Reviews

1. Open AI Review → Reviews. Use the queue to choose a trade or session, then open its source and complete the personal review first.
2. Inspect the evidence preview before generation. Missing context remains visible; generation does not fill gaps with assumed facts.
3. Generate the review, read its evidence and next action, then save it separately from your personal review. Opening or reading a saved result consumes no AI response.
4. Use the pattern signals to distinguish recorded strengths from repeated improvement themes. Select a signal to inspect its source reviews rather than treating word size as proof.

Weekly review

The weekly card reviews the last completed Monday–Sunday week. It requires at least one closed trade and one completed trade or session review in that week. It can compare recorded results, review coverage, rule/risk answers, setups and process evidence, then proposes one measurable experiment. The current pilot permits up to five successful weekly reviews per subscription period; insufficient evidence and failed generation consume none. Weekly AI review is separate from the weekly email digest and does not subscribe you to email.

Action queue

The Action queue scans the current 30-day evidence and groups source-linked work into Act first, Complete evidence and Inspect pattern. Refreshing recomputes the queue from current records. It does not create a saved investigation or change the linked trade/session.

Investigations

1. Open Investigations, choose one bounded question, set its dates and optional strategy where offered, then preview coverage.
2. Run only after the preview shows sufficient evidence. A run freezes the scope and evidence hash, produces a source-linked report and leaves journal records unchanged.
3. Use Review completion for missing review fields; Risk-limit breach for entries after a recorded daily-loss crossing; Overtrading for entries beyond a dated trade cap; and Rapid re-entry for entries within 15 minutes of a losing exit.
4. Use Exit decisions, Setup outcomes, Session commitments, Playbook compliance and Discipline drift for their named recorded evidence. Each keeps missing, not-applicable and small-sample evidence separate.

Limits and troubleshooting

These reports describe recorded associations; they do not establish cause, emotion or strategy quality. Risk-limit results use cumulative closed-trade net P&L rather than unrealized intraday drawdown. Overtrading uses recorded entry order. Rapid re-entry timing does not prove revenge trading. Discipline drift needs enough graded trades and answer coverage. If generation is switched off, saved reviews and investigations remain readable.

Related help

Reviewing · Sessions · Strategies · Plan and AI allowances

Before you start: Open a trade’s Review panel.

Steps

1. Choose A (On plan), B (One deviation) or C (Off plan) based on the plan you followed, independently of profit or loss.
2. Open Add tags. Search for an existing tag or type one; press Enter or comma to add it. Use a small, consistent vocabulary such as late-entry or exit-rule.
3. Remove an unwanted tag using its remove control. Add a note explaining the event rather than using tags for the full story.
4. Choose Save review, then use the Trades filters to compare tagged or graded trades.

If something looks wrong

Tags use lowercase words separated by hyphens; up to 12 tags of 40 characters each. The editor normalises spaces/case and reports invalid or excessive tags. A grade does not automatically mean you have marked the trade reviewed; tick Mark reviewed when finished.

Related help

Review checklist · Setup versus strategy

Before you start: Have a PNG, JPEG, WEBP or GIF image. Each image may be up to 3 MiB, with at most 12 per trade or session.

Steps

1. Open a trade → Review trade → → Screenshots.
2. Choose + add image and select your chart image. Wait for its thumbnail or an error. Images upload separately from the review text.
3. Save any note/tag changes with Save review. For a day-level screenshot, use the attachment controls on the selected session note.

Revisit images in the gallery

Select a trade thumbnail to start on that image and browse screenshots across the current filtered trade list, in its displayed order, including other pages. Trades without images are skipped. If the opened trade is outside the current trade-list filters, the gallery stays on that trade. Images attached directly to a session note remain in a separate session-only gallery. Use the thumbnail strip, previous/next buttons or Left/Right arrow keys to browse; on touch screens, swipe horizontally while the image is fitted. The header updates with the current trade’s instrument and entry date/time in IST, or the session context, plus filename and image count.

Use + and − to zoom. Drag with a mouse or scroll with touch to inspect a zoomed chart, then use the zoom percentage button to return to Fit. Close with × or Escape to return to the original thumbnail. If an image cannot load, choose Retry. Add and remove images in the existing attachment area.

Within each trade or session, images appear in upload order. Labels, captions, manual reordering and side-by-side comparison are no longer offered. Any metadata saved previously remains in the ZIP export under attachments/index.json; CSV import does not restore screenshots or that metadata.

If something looks wrong

Crop or compress an oversized image. PDFs and files renamed to an image extension are not supported images. At the per-trade/session limit, remove an unwanted image before adding another. Plan-wide screenshot usage is advisory during beta; these file and per-target limits still apply.

Related help

Review a trade · Export screenshots

Before you start: Use voiding for a record that should be excluded from results while remaining visible with a reason.

Steps

1. Open the trade in Trades.
2. Choose Executions, expand Trade record actions, then choose Void….
3. Enter the reason, check the effect shown and choose Void trade.
4. To include it again, open the voided trade and choose Restore in the same controls.

If something looks wrong

Voiding is different from deleting a manual trade or removing an entire import. Keep genuine losing trades in your review; the grade/note fields capture mistakes without erasing the result. A voided record stays in the log and is excluded from performance calculations.

Related help

Manual records · Import removal

How to use this feature

Before you start: Have imported or manually entered trades for a session review.

1. Open Sessions and select the trading day. On mobile, use the session selector or previous/next controls.
2. Use Plan a session to choose the date/account and record your intended setups, context and limits; choose Save plan. Use a saved template when appropriate.
3. After trading, compare the plan with the day’s trades. Write what happened, what worked, a mistake or lesson, and one action for the next session.
4. Tick Session reviewed and choose Save session. Trade reviews are separate: open individual trades to review their decisions.

Limits and troubleshooting

Do not rewrite a past plan as though you knew the outcome beforehand. Session results use the available executions; an open trade has no final closed result. These limits record your intentions and do not stop broker orders.

Related help

Reviewing · Lines · Digest

A session is one trading day. You never create one — every day with a fill becomes a session automatically. What you add is the half the tradebook cannot contain: what you meant to do, and what you made of it afterwards.

Planning a session

Written before the open, a plan records your watchlist, the setups you will take, what would make you sit out, your bias and context, and the three numbers that matter — max loss for the day, max trades, and risk per trade.

You can plan today and the next seven days. A plan for a day that has passed stays readable and editable, because after the day the plan is the half of the review that says what you intended — and one that vanished at midnight would take the comparison with it. Weekends are allowed: the exchange occasionally trades on a Saturday, and a journal that argued with the exchange would be wrong.

Templates

If your plan is mostly the same every day, save it as a template and start from it. A template can be marked as the default, and can carry forward the fields you want repeated while leaving the rest blank.

Writing the day up

The session note is where the day gets a verdict. It sits beside the day's trades and the day's plan, so the three can be read together — which is the comparison the whole feature exists for: what you said you would do, what you did, and what you think about it now.

Complete the structured session reflection

1. Review the session’s individual trades first. Use the trade table to inspect decisions and return to the session.
2. Under Market context, compare observed conditions with the expectation you actually recorded. Leave missing pre-session expectations unknown.
3. In Execution & discipline, record what worked and what deviated, with related trades if useful. Under Risk review, assess declared rules only from available evidence and record changes or exceptions.
4. Decision state is optional. Do not infer emotions from P&L alone. Use Previous commitment to reflect on the earlier action where relevant.
5. Write the overall day summary and one checkable next-session commitment. Where shown, record what you got away with. Tick Session reviewed and choose Save session.

The session and trade reviewed flags are independent. Green P&L does not establish discipline; closed realised results do not show unrealised exposure. Keep retrospective reflections distinct from plans recorded before trading.

Optional AI session review

When the owner-pilot AI card is available, preview the evidence before generating. It covers all journal accounts, grouping trades by their entry date in IST; page filters do not narrow this scope. It includes execution summaries, saved trade reviews and strategy rules, recorded original/current session plans, and the current session reflection. Save trade edits first. Previously generated AI trade answers are not included.

Screenshots, account identifiers and order IDs are excluded; notes are shared as written. Up to 60 trades are supported, subject to the input-size limit; oversized sessions are rejected rather than silently truncated. Open outcomes remain unknown, and provisional orders still need Console confirmation.

Save the AI result separately from Save session. Reopening compares the saved evidence with current inputs; changed trades, reviews, rules, plans or reflection can make it outdated. Regeneration uses the shared allowance; saving, reopening and thumbs feedback do not. Account-specific plan limits must not be compared with combined all-account results.

Save your strategy rules and compare versions, with or without trades.

Quick steps

1. Open Strategies. Name a draft, add rows under Strategy rules with + or Enter, explain the change and Save as v1. Drafts stay on this device.
2. Saved rules are immutable. Create a new draft version to change them; Live stays intact until replaced.
3. Follow Draft → Backtest → Paper → Live. Entry, stop, target and a 10-character decision are required. Evidence is optional; add it later. Live needs explicit approval. Journal does not execute strategies or certify results.
4. Assign trades… accepts this strategy's or unassigned trades, never another strategy's. Unknown versions inherit no rules. Reassignment clears rule answers.
5. Compare versions: choose Baseline and Compare with for changed rules and assigned results.

Related help

Review a trade · Performance

Detailed guidance

Start with a draft

1. Open Strategies and enter a strategy name.
2. Under Strategy rules, add entry, invalidation / stop, target, session-window and skip rules. Each rule has its own row. Use the add-rule field and + button, or press Enter.
3. Explain why you are saving this version, then choose Save as v1. Until saved, the draft stays only on this device; it does not sync to another device.

For an older strategy, Start version history preserves its current rules as v1 Draft. It does not invent testing history or automatically assign earlier trades to a version.

Develop a new version

Saved rules cannot be edited. Create a new draft version from the saved version, change its rules and explain the change, then save. Your existing live version stays live until you explicitly approve a replacement. Choose a version in the history rail to inspect its rules, lifecycle, evidence, trades and history.

Record lifecycle decisions

Follow Draft → Backtest → Paper → Live, one stage at a time. Entry, stop and target rules are required for promotion. Record a decision and its limits using at least 10 characters. Evidence is optional at every stage and can be attached later to that same version. Live requires your explicit strategy-approval confirmation; Journal does not execute the strategy or certify profitability.

Promoting a replacement to Live archives the earlier live version as superseded. Earlier rules, trade assignments and decision records remain in history. Archive is available separately; to reuse archived rules, create a new draft version.

Assign trades to the version you used

Choose Assign trades… for the selected version. You can select trades from this strategy and optionally list trades with no strategy. Trades belonging to another strategy cannot be taken by this assignment. Record why this is the right version. Changing a trade's version clears its rule answers and keeps an assignment-history record; review it again against the correct rules.

Earlier trades without an explicit version remain version unknown; they do not inherit today's live rules. Removing a version assignment returns the trade to version unknown. A strategy with no assigned trades is valid: its rules and lifecycle remain usable, but there is no assigned-trade performance to assess. Check the period filter if expected trades are missing.

Compare versions

Under Compare versions, choose Baseline and Compare with. Inspect added and removed rules alongside results for the trades explicitly assigned to each version. Different dates, sample sizes and accounts mean this is not a controlled test. Small or empty samples do not establish that one version is better.

Add supporting material when useful

Use + Add evidence for notes, backtest or paper results, trade or session references, or charts. Evidence belongs to the exact version; it is not inherited by a new draft. Adding it later does not rewrite the evidence snapshot saved with an earlier decision. Journal does not run backtests or independently verify submitted results.

Related help

Review a trade · Tags and grades · Performance

How to use this feature

Before you start: Choose your own limits; Journal does not prescribe a risk percentage.

1. Open Your lines and select Overall journal or the intended trading account.
2. Check the capital basis before entering risk per trade, daily limit and trade cap. A trade cap is an integer count of trades. Amount/percentage/multiple modes apply only to the monetary risk fields where offered.
3. Read the calculated amounts and any validation messages, then choose Save the lines. Verify the effective date in the saved history.
4. Use a session plan for the relevant day’s commitments and review the resulting observations in Sessions.

Limits and troubleshooting

Limits are observational and do not block trading. Unset is not zero. Historical sessions use dated limits, not a new limit retroactively applied to the whole book. Check account scope and capital coverage if an amount differs from what you expected.

Related help

Capital · Sessions · Metrics

Three limits you can draw: a daily loss limit, a maximum number of trades per day, and a weekly R target. The journal then records how you did against them.

Choose the scope

In Your lines, check whether you are editing Overall journal or a specific trading account. Account ledgers and legacy overall capital are separate; check the effective date when saving risk settings. See Capital and account ledgers.

A limit that moves with your account

You can express a limit as a percentage of capital rather than a fixed rupee amount. When you do, the percentage is resolved into rupees and then frozen, with the date it was set.

That freezing is the whole design. A limit recomputed live would re-judge your entire history every time the account moved: days you held would become breaches and breaches would quietly become held days, and adherence would be a number that changed while you were not looking. Instead the journal keeps a record of what the line has been, and judges each day against the line that was in force on that day.

Raising a line

You can set a cadence and a step — how often the line may move and by how much — and require yourself to confirm a raise. Lowering a limit is always allowed; raising one is the direction that needs the friction.

Unset is not zero

A limit you have never set is absent, not a limit of zero. It is excluded from your Discipline score rather than counted as a rule you broke — you have not failed to keep a limit you never made.

How to use this feature

Before you start: Create the relevant trading accounts and know the dated balances or cash movements you intend to record.

1. Open Preferences → Your lines and check the account scope.
2. Record opening capital and its date, then deposits/withdrawals or a manual balance checkpoint as needed. Check each entry’s date and account before saving.
3. For old overall history, open Set up account balances from legacy history, select the account, enter its end-of-day INR balance/date, read the confirmation and choose Save account starting balance.
4. For a transfer, open Transfers between accounts, select different source/destination accounts, amount/date and choose Record linked transfer. Check both accounts afterwards.

Limits and troubleshooting

These are journal estimates and manual records, not verified live broker balances. Combined coverage can exclude incomplete accounts or unresolved fills. Legacy overall capital stays separate. Record a linked transfer once; do not duplicate it with separate deposit/withdrawal entries. Check future risk limits after capital changes.

Related help

Trading accounts · Lines · Your data

How to use this feature

Before you start: Have closed trades for outcome comparisons; some cards also need planned risk, targets, grades or sufficient history.

1. Open Performance and check the account and period controls beside the page title.
2. In Period vs period, choose baseline and comparison dates or a shortcut, then choose Compare. This is what answers “was this month better than last month”: last month is the baseline, this month the comparison.
3. Compare Winning days vs losing days for frequency, holding time, adherence and outcomes. Read Strategy mix beside it to see whether the two day groups contain different recorded setups; the bars share a 0–100% scale.
4. Use the remaining cards for charges, trade frequency, entry time, holding time, product and expiry breakdowns. Their associations describe the selected history and do not prove what caused the result.
5. Use the period-report entry point for a printable review, then the report’s print/save control to use your browser’s printer or PDF destination.

Limits and troubleshooting

Period vs period uses its own inclusive entry-session date ranges and the selected account; other trade filters do not apply. Only eligible closed trades contribute to net results. Rate changes use percentage points. Missing profit factor when there are no losses is not zero. Different cards can have different populations: read their scope notes.

Related help

Metrics · Saved views · Whatif

How to use this feature

Before you start: Have historical trades and any declared limits required by the scenario.

1. Open What-if Lab and choose a question or scenario rule.
2. Select the trades/rules to include, then inspect the baseline, changed trades and resulting historical comparison.
3. Read the method and unavailable-data explanations before drawing a conclusion. A rule requiring a daily loss limit needs the limit that applied on each relevant day.
4. Use the saved-scenario controls to name and revisit a scenario from any signed-in device. The saved question retains its account scope; its result is recalculated from the current journal.

Limits and troubleshooting

This is a calculation on recorded outcomes, not a candle backtest or prediction. It cannot price a different exit from market prices it does not have. Up to 12 saved scenarios and one active 20-trade forward test are stored with your account and included in your data export. A test completes automatically after 20 eligible closed trades; completed and ended-early tests remain in its history.

Related help

Performance · Lines

How to use this feature

Before you start: Use a verified email address and enable the weekly-review preference if you want delivery.

1. Open Your lines and find Weekly review email.
2. Choose Preview what gets sent to inspect the review before changing your preference.
3. Use the subscription toggle to enable or disable delivery. If the address is unverified, use Sign-in & security to request verification.
4. To stop future weekly reviews, disable the preference or use the unsubscribe link in a received digest.

Limits and troubleshooting

Delivery depends on the deployed mail service and schedule. An enabled preference alone does not prove that mail was sent. A week without closed trades sends no digest; an empty preview is not a missing journal. Previewing does not send an email.

The email digest and AI weekly review are separate. Enabling email does not generate an AI review, and generating an AI weekly review does not enable email. The AI review also requires a completed personal trade or session review for the covered week.

Related help

Sessions · Security

How to use this feature

Before you start: Decide whether you need an archive, selective clearing, or permanent account deletion.

1. Open User menu → Privacy and choose Download .zip to keep an archive before removing records.
2. For selective clearing, review the categories/counts, select only what should go, type CLEAR and choose Clear selected…. Read the final confirmation.
3. For account deletion, type the registered email in the delete confirmation and choose Delete… only if you intend to remove the account itself.

Limits and troubleshooting

There is no complete ZIP restore workflow. Reimporting fills.csv rebuilds executions/trades but does not restore review history, screenshots, capital ledgers or all settings. Clearing has no trash bin; account deletion has no undo. An archive preserves information, not a guaranteed in-app restoration path.

Related help

Import history · Voiding

How to use this feature

Before you start: Have trades in the journal; a saved view stores filter settings, not a frozen copy of results.

1. Open Trades or Dashboard. The header keeps period, current view, Filters and Save view together; choose the account from the global header.
2. Select the criteria, such as review status, grade, strategy or tags, and apply them. Check the current period and account too.
3. Choose Save view, enter a name and decide whether to include the current period/account. Save it.
4. Use Views to reopen a saved view. The examples Unreviewed options and Off-plan trades apply filters; save them if you want to keep them.

Limits and troubleshooting

If nothing matches, clear filters and check date/account scope. Multiple fields must all match; tag any/all/exclude modes change the rule. Saved views are stored with your account and update as underlying trades change.

Related help

Reviewing · Performance

Journal analyses recorded trades, not live market quotes. No setting enables a live-price feed.

How to use this feature

Before you start: Have enough eligible trades for the metric you are reading; coverage varies by metric.

1. Open Dashboard and check account, dates and active filters before reading totals.
2. Distinguish gross result from net after allocated or estimated charges. Open a trade’s Executions tab for its charge breakdown and source.
3. For R results, check whether planned risk was recorded or inherited from a session plan. Missing risk is not a zero-risk trade.
4. For Discipline and Edge, open the score explanation and read the available components, coverage and sample-size limitations.

What the headline stats mean

The stats strip is computed over closed trades only, and by default after allocated or estimated charges; the gross figures sit alongside them.

Win rate

Closed trades whose result is above zero, divided by all closed trades. A trade that came out exactly flat is neither a win nor a loss, but it still counts in the denominator — so a book with breakeven trades reads below 100% even with no losers.

Expectancy

The total result divided by the number of closed trades: what an average closed trade returned, not a prediction of the next one.

Profit factor

Gross winnings divided by gross losses. With no losing trade there is nothing to divide by, so it reads as a dash rather than as an infinite score.

Streak

The most recent unbroken run of wins or losses. A flat trade ends a run rather than extending it.

Max loss

The worst losing trade. A book with no losers shows a dash here, not a zero.

Limits and troubleshooting

A dash means unavailable, not zero — it is not a sign that the stats are broken or that anything failed. Open trades and trades without a supported charge estimate may be excluded from closed/net metrics. Score bands are not guarantees. Comparisons describe your recorded sample and do not establish what caused a result.

Related help

Glossary · Scores · Charges · Performance

Dashboard chart and tile borders

In What you actually trade, Long call, Long put, Short call and Short put separate option activity. Borders follow the calendar: green for positive net, red for negative net and neutral for break-even. Dashed not traded tiles mean no matching activity, not a measured zero result. Colours describe outcomes, not setup quality.

Open items and the Options desk

Open items is the recent session-review queue; Open positions lists imported trades without a recorded exit and does not pretend to price them. The number inside each tab is its pending count. The Options desk follows the global account, period and saved-view scope. It summarises recorded option trades by direction, type, product, expiry, premium, value, entry time and holding time; a visual association is not a recommendation or proof of causation.

How to use this feature

Before you start: A multi-leg position arrives as one trade per leg, because that is how it was filled — a four-leg iron condor is four separate rows. Grouping is how you read those legs as one position. Journal suggests simple vertical spreads from contracts, quantities and overlapping entry times; other structures you group by hand. Have at least two eligible option trades from the same account.

1. Open Option groups and choose the account.
2. In Review suggestions, inspect the contracts and legs before confirming a trading idea. Choose Keep separate for a suggestion you do not want.
3. For a manual group, select trades under Ungrouped trades and choose Group selected. Name the idea, review its members and choose Confirm group.
4. Open Confirmed groups to review the combined outcome and shared notes. Adjust members or ungroup when appropriate.

Limits and troubleshooting

Groups contain 2–50 same-account option trades. Suggestions are possible matches, not proof of your intent. Open/incomplete groups have no final combined result. Grouping neither duplicates trades nor changes account P&L; ungrouping preserves the trades.

Related help

Reviewing · Trading accounts

How to use this feature

Before you start: Be signed in to the Journal account you want to update.

1. Open User menu → Profile.
2. Edit your name, display name, time zone or display currency, then choose Save.
3. Use Upload photo for an avatar; wait for confirmation or the validation error. Use Remove to remove it.

Theme

Open the user menu and choose Light or Dark in the Theme selector above Profile. The choice is remembered in this browser. If you previously used Auto, Journal starts with your current system appearance and saves it as Light or Dark; later system changes do not switch the journal theme. If browser storage is unavailable, your choice lasts until the page reloads.

Limits and troubleshooting

Trade times remain on the India market clock; the profile time zone does not shift executions to local time. Display currency changes the symbol, not the stored amounts or their FX value. Do not combine currencies assuming conversion occurred.

Related help

Security · Metrics

How to use this feature

Before you start: Sign in to your own account to manage sessions or change your password. Access to the registered email is needed for email verification or a forgotten-password reset, not for signing out other sessions.

1. Open Sign-in & security to check email verification and active sessions.
2. Use the verification control if needed; follow the link sent to your registered email. If it expires, request a new one.
3. To change a password, enter the current and new password and choose Change. The new password must meet the displayed requirements.
4. Choose Sign out others to end other active sessions. If you cannot sign in, use the password-reset option on the login page.

Limits and troubleshooting

Sign out others and changing a password preserve the current session and end all other sessions; neither requires an email-verification link. Changing a password requires the current password. Completing a forgotten-password reset ends all sessions, including the current one. Active sessions are listed, but there is no individual-device sign-out control. Mail delivery requires a configured service. Google sign-in appears only when configured; do not expect a disabled provider to be available. Never share passwords or verification/reset links in a help conversation.

Related help

Profile · Digest

How to use this feature

Before you start: Read the current Plan screen for your account.

1. Open User menu → Plan. The AI usage card reads your current allowance from the server; refresh it after a generation. Daily pilot and subscription-month allowances are labelled separately.
2. Open Billing for billing status, recorded invoices and payment history. Checkout and invoice downloads are not yet available.
3. Check the current beta/access status, usage counts and whether limits are described as enforced or advisory.
4. Use the displayed comparison to understand planned tiers, keeping preview pricing separate from an available purchase.

Limits and troubleshooting

In this release billing is not live and tier prices are previews, not a checkout offer. Advisory account/screenshot allowances differ from enforced per-image and per-trade/session attachment limits. Unknown account usage can mean unresolved legacy labels; it does not mean one account. Do not provide payment details to a help chat.

Related help

Screenshots · Trading accounts

Shared AI allowance

For eligible, reconciled Flight subscriptions, the allowance is 100 successful AI responses per subscription month, shared by Tavya, AI trade review and AI session review. Regeneration uses another response. There is no rollover. Local guide answers, reading, saving and feedback do not consume responses.

Failed generation releases the Flight monthly reservation, but attempt and spending controls still apply. A successfully completed response may count even if the browser disconnects before receiving it. Owner/beta pilots can use a separate daily allowance; check the displayed period and reset time rather than assuming a calendar-month reset. The usage ring in Tavya opens the detailed counters.

An allowance does not itself grant access to an owner-only feature. Generation can also be disabled for the installation. Saved AI results remain separate from personal reviews.

Weekly AI reviews

The current plan design includes up to four successful weekly AI reviews per subscription period for Perch, Flight and Stoop. Weekly reviews use their own allowance and do not reduce Flight or Stoop on-demand responses. A completed week with insufficient evidence, or a failed generation, consumes no weekly unit. This entitlement is still restricted to the owner pilot; a plan label alone does not make the feature available.

Journal uses imported contract-note charges where available and published rate-card estimates for uncovered executions. The Executions tab labels each trade as contract-note allocation, mixed, or estimated. A contract note is the authoritative source of its reported totals; a per-trade allocation is our attribution of those totals, not an exact fee reported by the broker.

How contract-note charges are allocated

For supported Dhan notes, each charge component is shared by execution turnover within its segment. Rounding preserves every paisa. When a fill closes one trade and opens another, its charges are split by quantity. Open trades retain accrued allocations without a final net result. Charges outside the imported note are not included.

Re-upload an older Dhan note to the same trading account to add its charge evidence without duplicate fills. Removing that charge-only import restores estimates on the surviving executions. Changed note evidence requires reconciliation; it never silently replaces saved charges.

Taxes and exchange fees in estimates

STT, the exchange transaction fee, the SEBI turnover fee, stamp duty and the GST computed on top are set by the exchange and the government. Estimates use the supported rate-card assumptions; dates, rounding and special treatment can make the broker's reported totals differ.

The half your broker sets

Brokerage and the DP charge are prices, not taxes — and they differ by more than most people expect. The table below is printed from the same cards the calculation uses, so it cannot drift out of step with your numbers.

Which card your trade was priced on

Open any trade and the charge breakdown names its charge source. For uncovered executions, a recognised broker supplies the fallback rate card. Three cases cannot be answered that confidently, and all three say assumed rather than quietly picking:

A hand-mapped CSV

You told TradeTattva which column was which, which says nothing about who executed the trade.

A file whose broker was not identified

Read successfully, recognised as nobody in particular.

A trade whose fills came from two brokers

Possible when one account holds imports from both. There is no single right card for it, so TradeTattva does not choose one.

The breakdown names the assumed fallback card. Taxes and exchange fees remain estimates too.

Where the estimate is knowingly imperfect

• Brokerage is per executed order, not per fill. TradeTattva carries the real per-order values through pairing. A fill split across two trades by a zero-crossing counts its order in both — a slight over-estimate, and rare.
• Options exercised at expiry are understated. Exercise attracts STT on intrinsic value instead of the sell-side premium modelled here. A position squared off on the exchange is modelled exactly; one left to expire in the money is not.
• An open trade has no charge estimate at all. Not zero — absent. There is no round trip to price yet, and printing ₹0 would read as a free trade.
• Nothing here knows your broker's interest, pledge or payment-gateway fees. Those never appear in a tradebook and are not guessed at.

TradeTattva stores your fills — the individual executions your broker reported. It does not store trades. Trades are worked out from the fills every time you look at them, which is why a fix to the pairing rules improves your whole history at once instead of only what you import afterwards.

The rule

A trade runs flat to flat, per symbol. It opens when your position in that symbol leaves zero and closes when it returns to zero. Everything in between — adds, partial exits — belongs to that one trade, which is why a scaled-in position shows as one trade with pyramid adds rather than four separate ones. A pyramid add is counted only when another identified entry order increases the open position. Several executions of the same order, including a three-lot option order filled in parts, count as one entry. If the broker export omits order IDs, the journal cannot reliably label an add.

Order

Fills are sorted by execution time, then by the order they were imported. That second key matters more than it sounds: two fills stamped to the same second would otherwise come back in whatever order the database felt like, and which one came first decides whether a round trip reads as a long or a short.

Accounts never mix

Pairing runs separately by trading-account identity, or by the unresolved label when no identity is assigned. Explicitly linked labels for the same account can pair together. An exit in a different account does not close this account’s entry.

Crossing through flat

A single fill big enough to close your position and open the opposite one is split: the closing part finishes the current trade, the remainder starts the next.

Still open

A position that never returned to flat is shown with its exit fields empty, never dropped. An open trade you cannot see is worse than one you cannot score.

Inspect the executions

1. Open Trades and choose the trade.
2. Open Executions and inspect Order timeline: entry, adds, partial exits and final exit.
3. Compare the account and date coverage with your source reports. Import a missing supported report if an exit is absent; do not invent an exit to make an open trade appear closed.

What this means when something looks wrong

• Two trades where you expected one usually means the position touched flat in between. Check the fills in the trade drawer — they are listed with times.
• One trade where you expected two means it never did.
• A trade in the wrong account needs its account assignment checked. Use Trading accounts for unresolved fills. Reuploading with another label does not move already imported executions.
• A trade that is not yours at all — a broker glitch, a fill posted to the wrong account — can be voided rather than deleted. Voiding keeps the row and excludes it from every number on every screen at once.

The tradingsymbol is doing more work than it looks. It decides which rate card prices the trade, which exchange fee applies, whether the trade appears on the options surfaces at all, and how expiry and strike are read. Getting it wrong is not loud — it is the quietest failure in the whole pipeline.

What TradeTattva reads from a symbol

Option

Root, strike and CE/PE. NIFTY2610626300PE is NIFTY, 26300, a put.

Future

Root and expiry.

Equity

Everything else. A plain tradingsymbol is the cash instrument, so this is the honest default rather than a guess.

Exchange

Derived from the root: the SENSEX family trades on BSE, everything else on NSE. Equity defaults to NSE. This decides only the exchange transaction fee — the statutory pieces are identical on both.

The guard that catches it

Most broker exports carry a segment or exchange column next to the symbol. When that column says the row is a derivative and the symbol reads as plain equity, the two disagree — and TradeTattva refuses the import and names the row rather than accepting it. A file that is rejected costs you five minutes. A file that is read wrongly and accepted costs you your numbers.

The check knows venue-prefixed segments too, so a column reading NSEFO is understood as F&O rather than treated as an unknown value and waved through.

If your symbols are not recognised

• Upload the broker's own export, unmodified. Most symbol problems begin with a file that has been opened, edited and saved somewhere else.
• Check the trade drawer. It shows the instrument as TradeTattva read it — root, strike, expiry — so a misreading is visible on one trade before it is a pattern.
• An unrecognised derivative is worth reporting. The importer composes and checks tradingsymbols per broker, and a format nobody has seen is a gap in that list, not a fact about your trading.

Two scores, never averaged into one. Discipline is built only from things you declared — a grade you gave a trade, a limit you set, a risk you priced before entering, a plan written before the open, a session written up afterwards. Nothing in it is P&L. Edge is entirely outcomes, and carries a spread, because a small book cannot tell an edge from luck.

Reading the pair

The rules that keep it honest

• A part with no data is excluded, never scored zero. You have not failed to keep a limit you never set, and averaging a 0 in for it would drag the score down for a rule you never made.
• Equal weights, over whatever has data. Invented coefficients are what make every other score in this category a black box; equal is the only weighting that does not claim a precision nobody has measured.
• Two parts minimum. One part reported as a score is that part wearing a score's clothes.
• Every part shows its raw fraction, so the number is always decomposable into things you can go and look at.
• No letter grade and no adjective. A Discipline score is not a B and it is not "good" — it is how much of your own plan you kept.

Words this journal uses in a particular way. Where a term has a loose industry meaning and a precise one here, the precise one is what the numbers do.