Challenge → fresh account
Import more signals, replay from any date and account stage, and inspect progress through a chosen date. The ledger models target/stop outcomes in signal order; counterfactual results exclude commissions and slippage.
Scenario settings
Choose an account size to fill its drawdown, goal, and whole-micro risk bands.The $25K scenario caps trades at 15 micros and models wide-stop signals at 1 micro in both stages. Actual firm limits can differ.
Import trade-log CSV
Use the same Date, Time, Ticker, Setup, Trigger, Direction, Entry Zone, Target, Invalidation, Risk, Size, Took Trade, and Outcome columns as your log. Optional Exit Date and Override Contracts columns are also supported; other columns remain available under Details and in the full-signal export. Imported rows are saved in this browser; duplicate signals are ignored when appending.
Using the original 34-signal log.
Google Sheets auto-sync
Link a viewable Google Sheet containing the same trade-log columns. This page refreshes it every five minutes while open and when the tab becomes active. The sheet is read-only from this ledger; a failed refresh leaves the last good rows in place.
No Google Sheet linked. The sheet must be viewable by anyone with its link; private sheets need an authenticated connection.
Account state and consistency
Replay from the beginning, or choose a start date and enter your current stage, final balance, and highest final balance. For a new challenge after a reset, choose Challenge and enter the configured start balance for both balance and peak.
When enabled, the sizing plan limits a signal-date winning day to the selected share of the greater of the configured profit goal or current account profit. It uses each trade's potential target gain, even if the logged outcome is a loss. Actual consistency is shown as largest winning day ÷ profit since the last reset. Exit dates override signal dates when provided in the CSV; otherwise signal dates are a proxy.
Full signal ledger
Click “Details” to inspect prices, notes, and the reason a row did or did not affect each balance.
Date filters narrow the table; the “through” date also shows account progress as of that date. Exit timestamps are incomplete.
| Recorded signal | Whole-micro account ledger | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Date | Ticker | Setup | Took | Size logged | Outcome | Stage | Decision | Contracts | Max allowed | Stop risk | P/L | Result balance | Next balance | Peak | Floor | Drawdown |
Rules applied
- Retired setup: HTF SNIPE remains excluded. Size = NO TRADE is modeled at the account’s fixed wide-stop size in either stage, even when its stop risk exceeds the stage cap, except the October 12 MYM signal at 51996, which follows the selected stage’s risk band and account micro limit. Numeric-size rows count in both phases regardless of their Took Trade flag; rows marked No remain counterfactual. Optional consistency sizing can still reduce or block a signal.
- Account presets: $25K uses a $1,500 pass goal, $1,000 trailing limit, $380–$430 / $260–$310 challenge/after-pass stop-risk bands, at most 15 micros, and 1 micro for wide stops. $50K uses $3,000, $2,000, $760–$860 / $520–$620, at most 40 micros, and 2 for wide stops. $100K uses $6,000, $3,000, $1,140–$1,290 / $780–$930, at most 60 micros, and 3 for wide stops. Changing the account selector fills these values. The contract limits are this scenario’s limits; check your firm’s actual rules separately.
- Challenge sizing: use whole micro contracts targeting the configured stop-risk band. When no integer size fits, use the largest size below its cap and flag that its risk falls below the band. If even one micro exceeds the stop-risk cap, use the account’s fixed wide-stop size and flag the exception. Optional consistency sizing can reduce or block it.
- Friday signals: use the after-pass sizing band and highest whole-micro size under its cap, even while the account is in the challenge. The account remains in its actual stage for pass and reset tracking. Friday means the logged signal date, not a later exit date.
- On passing: record the balance that crossed the configured profit goal, then start the next signal with a fresh selected starting balance. For numeric-size rows after passing, use the highest whole-micro stop risk no greater than the configured cap or selected account’s micro limit; flag it if it falls below the minimum. Size = NO TRADE uses the account’s fixed wide-stop size in both stages, except the October 12 MYM signal.
- Milestone dates: each challenge pass is recorded. After passing, every crossing or recrossing of a gain level is dated ($1,500, $3,000, and so on at a $25,000 start; $3,000, $6,000, and so on at a $50,000 start when the gain target scales to 6%). A logged Exit Date is used when present; otherwise the signal date is a proxy.
- EOD breach: a booked final balance below the account's highest booked balance minus the trailing limit is highlighted and starts a fresh challenge on the next signal. Outcome timing in the source log is incomplete, so the breach date is modeled.
How to read the numbers
- Stop risk and target gain come from the logged price distances and micro contract multipliers. Where the target risk band cannot be reached by an integer number of contracts within the stop-risk cap and account micro limit, the ledger uses the largest permitted whole-contract size and labels the row Below band. If even one micro exceeds the stop-risk cap, the ledger models the account’s fixed wide-stop size and flags the over-cap exception.
- On a challenge pass, Result balance records the passing balance and Next balance shows the reset to the configured starting balance. The after-pass milestone does not reset or stop the ledger. Friday signals use the after-pass risk band regardless of account stage, based on the signal date. Size = NO TRADE uses 1 / 2 / 3 micros on $25K / $50K / $100K in both stages, except the October 12 MYM signal at 51996, which follows the stage’s risk band and selected account’s micro limit; the source Size remains visible in the table. Fixed sizes are flagged when outside the applied risk band. Took Trade = No rows are modeled as hypothetical fills.
- Consistency sizing is an optional planning rule: the winning-day budget is the selected percentage of the greater of the configured profit goal or current account profit. The per-row maximum is the smaller of the stop-risk cap and the remaining potential winning-day budget. If no micro fits, the row is not sized. A firm's official rule may use different timing or profit definitions; outcomes with missing exit dates are attributed to signal dates here.
- The Sept 24 MGC row logs $223 of risk, but its entry and invalidation imply about $260.77 for one MGC. The strict calculation follows the stated invalidation. Original logged risk and size appear in each row’s details.
- Some outcomes were reached in a later session. Dates identify signals, not verified exit times; the actual sequence of final balances could differ. Pending or Neutral outcomes can show planned contracts and stop risk when prices are present, but book no P/L. A missing entry, target, or stop prevents sizing.
- Contract values: MES $5/point, MNQ $2/point, MYM $0.50/point, M2K $5/point, MGC $10 per $1 price move, MCL $100 per $1 price move. See CME micro index specifications, CME micro gold, and CME micro WTI.