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.
For a manual After pass opening, enter only milestones already completed. The $25K scenario also accepts 0–2 qualifying days toward its next milestone; a high peak alone does not prove that requirement. When enabled, consistency sizing 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
Signals start as Taken, except retired HTF SNIPE, which starts Not taken. Click a row’s participation button to switch it either way. Details retain the original log’s Took Trade value.
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 | Model trade | Size logged | Outcome | Stage | Decision | Contracts | Max allowed | Stop risk | P/L | Withdrawal | Result balance | Next balance | Peak | Floor | Drawdown |
Rules applied
- Retired setup: HTF SNIPE starts Not taken, but its participation button can model its logged outcome as Taken. 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. Other numeric-size rows count in both phases regardless of their original Took Trade flag; rows originally marked No remain counterfactual. Optional consistency sizing can still reduce or block a signal.
- Account presets: $25K uses a $1,500 challenge 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 a $3,000 challenge pass goal, $2,000 trailing limit before its first after-pass withdrawal, $760–$860 / $520–$620 stop-risk bands, at most 40 micros, and 2 for wide stops. Its after-pass target is $56,000. $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 at its balance goal. On $25K only, each after-pass level also requires three distinct trading days with at least $150 in modeled net profit per day since the preceding milestone. A day qualifies only after its last logged signal, so later losses on that date can remove its qualification. The count resets after each milestone and days cannot be reused; a balance above several levels can complete only one new milestone per three qualifying days. $50K and $100K have no minimum profitable-day requirement. The $50K after-pass target repeats at $56,000: each crossing models a $2,500 withdrawal, and the next crossing counts only after the carried balance falls below $56,000 and recovers. This repeats until a breach starts a new challenge. The $100K after-pass targets continue in $6,000 steps by default. A logged Exit Date is used when present; otherwise the signal date is a proxy.
- Participation: every signal other than HTF SNIPE is modeled as Taken by default, regardless of the original Took Trade column. HTF SNIPE starts Not taken; click its button to include it. Your choices are saved in this browser and remain in place when the linked sheet refreshes. A Not taken row retains its hypothetical size and risk but books no P/L, drawdown, or milestone.
- 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. On $50K, after the first $2,500 withdrawal, the breach floor becomes a fixed $52,100; a booked balance below it starts a fresh $50K challenge. 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. On each $50K after-pass $56,000 crossing, Result balance shows the amount before the $2,500 simulated withdrawal, and Next balance shows the amount carried forward after it. The withdrawal is separate from trade P/L. The $25K after-pass three-day test uses net P/L from modeled Taken trades, grouped by logged Exit Date where supplied or signal date otherwise; dates without a final exit record are proxies. 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.