Trading Plan Template Notion: Multi-Account Build
MAV's articles are drafted with AI assistance and checked against each firm's published documents before publishing.
Key takeaways
- A Notion trading plan for multi-account prop traders works best as four databases: Accounts, Rules Matrix, Daily Plan, and Trade Log.
- Encode each firm's trailing drawdown, daily loss limit, and consistency rule as properties and formulas, not prose, so cushion left is visible before the open.
- A 3% buffer on a $2,500 daily loss limit flags the account at $2,425 realized loss, before the platform does.
- Notion has no native Tradovate, NinjaTrader, or Rithmic integration, so trades must be logged manually or paired with a dedicated journal.
- The full four-database build takes under an hour; the slow part is looking up each firm's exact rule wording.
A trading plan template in Notion works best as four databases: Accounts, Daily Plan, Trade Log, and a Rules Matrix holding each firm's trailing drawdown, daily loss limit, and consistency rule. This guide gives you every database, property, and page section so you can rebuild the whole thing in under an hour.
Why build your trading plan in Notion instead of a Word document?
A Notion trading plan template beats a Word file the moment you run more than one prop account. Word gives you a static page you read once; Notion gives you a database you update every session, per account, with rules that stay current as you add evals and funded accounts.
What a Word document does well
A Word file is fine for a one-page strategy statement: your setups, your hours, your max risk per trade. It prints well and takes ten minutes to write. If you trade a single funded account with one trailing drawdown, it can be enough.
Where Word breaks down for multi-account traders
Two to six accounts across Apex, Topstep, Lucid, and MyFundedFutures means different daily loss limits, trailing drawdowns, and consistency rules per account. A document can't track cushion left per account or flag which eval is closest to a breach. Most evaluations end in failure, often from a forgotten rule rather than a bad strategy (lunefi.com). A plan that lives next to your journal — the way MAV pairs planning with per-account review — catches what a document can't.
| Word doc | Notion | |
|---|---|---|
| Per-account rules | One page, manual edits | Filtered views per account |
| Daily updates | Rewrite or duplicate | Edit one row |
| Breach tracking | None | Properties + formulas |
| Pre-open checklist | Separate file | Same page as the plan |
What does a complete prop-firm trading plan need to cover?
A plan for eval and funded futures accounts needs four sections: strategy criteria, per-account risk rules, execution rules, and a review loop. Miss any one and you're back to paying reset fees.
Strategy and setup criteria
Define which contracts you trade (NQ, ES, MES, MNQ), the sessions you trade them in, and what qualifies as a valid setup. Write the invalidation condition for each setup, not just the entry trigger.
Risk rules per account
List every account separately: trailing drawdown, daily loss limit, consistency rule, scaling plan, and cushion left. With 2-6 accounts across Apex, Topstep, and MyFundedFutures, the rules differ per account and a plan that treats them as one number will breach.
Execution and psychology rules
Set hard stops on behavior: max trades per session, a shutdown rule after two losses, and no re-entry within a set window to kill revenge trading before it starts.
Review loop
Schedule a post-session review against the plan, not memory. An AI Coach that reads your own tape, like the one in MAV, makes this review concrete; in Notion, a linked review database does the same job manually.
How do you structure the Notion workspace for multiple prop accounts?
Build four pieces: two databases, one matrix, and one daily page. Notion databases let you define properties and formulas once and reuse them across every view, which is what makes one workspace work for 2-6 accounts.
The Accounts database
One row per funded or eval account. Properties: firm (Apex, Topstep, Lucid, MyFundedFutures, Tradeify, Earn2Trade, Bulenox), account size, status (eval or funded), platform (Tradovate or NinjaTrader/Rithmic), start date, and reset count. Each row links to a per-account page holding the payout rules and profit target.
The Rules Matrix database
One row per account-rule pair: trailing drawdown amount, daily loss limit, consistency rule percentage, scaling plan, and cushion left. This is the database you check before the open.
The Daily Plan page
A single template page with a date, pre-market bias, per-account max contracts, and a risk budget per session. Duplicate it each morning.
The Trade Log database
One row per trade, tied to an account and a daily plan entry. A journal like MAV ($18.99-$29.99/mo) automates this log from your tape; in Notion you enter trades manually, which is the trade-off.
Which properties should each Notion database have?
Accounts database properties
Keep it flat: Account Name (title), Firm (select: Apex, Topstep, Lucid, MyFundedFutures, Tradeify, Earn2Trade, Bulenox), Status (eval or funded), Profit Target (number), Trailing Drawdown (number), Daily Loss Limit (number), Start Balance (number), Platform (select: Tradovate, NinjaTrader/Rithmic), Reset Date (date), and Monthly Cost (number). The Cost property matters more than it looks. Traders running 2-6 accounts pay real money in eval fees and reset fees, and seeing cost per account next to cushion left changes which account you trade on a thin day.
Rules Matrix properties
One row per account-rule pair, not one row per rule. Properties: Account (relation to Accounts), Rule Type (select: trailing drawdown, daily loss, consistency, scaling), Threshold (number), Buffer % (number), and Breach Action (select: stop trading, half size, flat only). The Buffer % is your safety margin. A 3% buffer on a $2,500 daily loss limit means the Rules Matrix flags the account at $2,425 realized loss, before the platform does.
Trade Log properties
Date (date), Account (relation), Symbol (select: NQ, ES, MES, MNQ), Side (select), Contracts (number), Entry/Exit (numbers), P/L (number), Plan Followed (checkbox), Setup (select), Mistake Tag (multi-select: revenge trade, oversized, no plan, moved stop), and Screenshots (files). The two properties that make the log worth keeping are Plan Followed and Mistake Tag. P/L tells you what happened; those two tell you why.
Formulas worth adding
Three formulas carry most of the weight. Cushion Left: Start Balance minus realized P/L threshold math against the trailing drawdown. Daily P/L: a rollup summing today's Trade Log entries per account, so a glance shows room to breach before the open. Consistency check: best day P/L divided by total P/L, formatted as a percentage, so a 40%+ number warns you a consistency rule is at risk. If you swing trade micros alongside your eval scalping, the same property set works across timeframes; the structure at https://mavtradeapp.com/solutions/swing-traders/ follows the same logic of per-trade context over raw P/L.
How do you encode trailing drawdown, daily loss, and consistency rules in Notion?
Each firm publishes its rules differently, so build one "Rules" database with a row per account and typed fields per rule. That way a formula, not memory, tells you your cushion left before the open.
Trailing drawdown fields
Add properties: Account Max Loss (number), Trailing Type (select: trailing on unrealized, trailing on realized, end-of-day), Current Threshold (number, updated at your review), and a formula Cushion = Current Threshold − Account Equity. Trailing rules differ in how and when they lock in, so check each firm's wording before you set the type.
Daily loss limit fields
Store Daily Loss Limit, Realized P&L Today, and Open Risk (contracts × stop distance × point value). A formula Room = Daily Loss Limit − |Realized P&L Today| − Open Risk gives you room to breach in dollars, per account.
Consistency rule fields
Add Consistency Cap %, Best Day P&L, and Total P&L. A formula flags when your best day exceeds the cap of total profit, so a strong day stops you from over-trading the rest of the eval.
A pre-open checklist view
Create a filtered gallery view showing cushion, room, and consistency status per account. If a field is blank or red, you do not trade that account. Tools like MAV automate this per-account rule tracking, and Notion formulas can compute similar logic if you prefer building it yourself; Notion's formula syntax is documented in Notion's formula guide.
What does the daily plan page look like before the open?
Market context block
Start the page with four lines filled in before 9:00 ET: overnight range on NQ and ES, key economic releases with times, CPI/FOMC/NFP flagged in red, and whether Asia and Europe trended or chopped. This takes two minutes and sets whether you're hunting a trend day or fading extremes.
Levels and bias
Below that, a short table of levels: prior day high/low/close, overnight high/low, and one or two H1/H4 levels per instrument. Then a single bias line with a checkbox: long, short, or two-sided. If you can't write the bias in one sentence, you don't have one.
Risk budget for the session
List every account you're trading today with its daily loss limit, cushion left on the trailing drawdown, and max contracts. Add one line: the dollar amount that ends the session. When you know the exact number that breaches, cutting size at two losses stops feeling optional.
Post-session review block
Leave three fields empty until the close: followed plan (yes/no), rule breaches, and one sentence on execution. Filling these in daily is what turns the template into a journal. If you want auto-imported fills and an AI Coach reading your tape instead of manual notes, a dedicated tool like MAV handles that layer.
How do you run the plan across 2-6 accounts without breaching?
One plan, per-account risk sizing
Write the strategy once, then attach a per-account risk block to each account page. A 3-point stop on MNQ is a different dollar amount on Apex than on Topstep, so each account page carries its own contracts-per-trade cap, daily loss limit, and trailing drawdown figure pulled from the firm's rules. The plan stays one document; the numbers stay per-account.
Cushion tracking views
Build one gallery view filtered to accounts at risk: cushion left under 40% of the daily loss limit, or trailing drawdown within $200 of the threshold. Check this view before the open and after every session. A Word document has no filtered views or live properties, which is why a static plan file breaks down once you juggle more than two accounts.
When to skip an account for the day
Add a "Trade today?" checkbox per account with a rule: if the eval has 2+ breaches this week or cushion is thin, mark it skipped and trade the funded account with room instead. Skipping one account on a bad tape is cheaper than a reset fee.
Where does a Notion plan stop and a trading journal take over?
What Notion cannot pull in automatically
Notion holds your rules, your daily plan, and your pre-market checklist, but it cannot ingest fills from Tradovate, NinjaTrader, or Rithmic. Every trade you log by hand is a trade you may skip logging on a bad session, which is exactly when the review matters most.
Pairing the plan with MAV
A dedicated journal closes that gap. MAV pulls your tape across every prop account into one board, checks it against your plan before the open, and runs an AI Coach that reads your own execution rather than offering generic advice. Pricing runs $18.99–$29.99/mo.
Running the same criteria on MAV honestly
MAV does not replace the Notion workspace above. It handles execution data and post-session review; the plan, rule encoding, and morning ritual still live in Notion. TradeZella, TradesViz, Tradervue, and TrackyTrade occupy similar journal territory, so evaluate them against the same checklist you built earlier.
FAQ
Is Notion good for tracking prop firm drawdown and consistency rules?
Yes, if you encode the rules as properties and formulas rather than prose. Store trailing drawdown, daily loss limit, and consistency cap per account, then add formulas for cushion left and best-day-to-total ratio. A filtered pre-open view flags any account approaching a breach, which a written plan can never do.
Can I get a free trading plan template for Notion or do I have to build it?
Free templates exist, but most are generic journal layouts without per-account rule properties. For multi-account prop trading you'll want the four-database structure anyway: Accounts, Rules Matrix, Daily Plan, and Trade Log. Building it yourself takes under an hour and guarantees the fields match your firms' actual drawdown and consistency wording.
How long does it take to set up a Notion trading plan for multiple funded accounts?
Under an hour for the full build. The Accounts database takes about fifteen minutes, the Rules Matrix another fifteen, and the Daily Plan page template ten, with the Trade Log taking the remainder. The slow part is looking up each firm's exact trailing drawdown and consistency terms, not building the databases themselves.
Should I keep my trading plan in Notion, a Word doc, or a spreadsheet?
A Word doc works for one account and a one-page strategy statement. A spreadsheet handles numbers but not daily templated pages or linked trade logs. Notion sits between them: database math like cushion formulas, plus a duplicable daily plan page and per-account views. Past two accounts, filtered views are what keep you from breaching.
Does Notion connect to Tradovate or NinjaTrader to auto-import trades?
No. Notion has no native integration with Tradovate, NinjaTrader, or Rithmic, so every trade gets logged by hand, which is exactly what gets skipped on bad sessions. A dedicated journal like MAV pulls fills automatically and checks them against your plan, while Notion keeps the rules, morning ritual, and review structure.