A passed DXtrade challenge is worth almost nothing if you can’t tell yourself, in specific terms, how you passed it. The evaluation tests whether you can hit a target without tripping a rule — and then do it again on the funded account, cold.
What a DXtrade challenge demands beyond hitting a target
DXtrade is the platform a lot of CFD and multi-asset prop firms hand you for the evaluation. It’s a solid order ticket and a live position blotter — but it is not a journal. It shows you where your account stands right now, not the reasoning that put it there. A challenge stacks three layers of requirement on top of each other:
- The profit target — the obvious one everyone fixates on.
- The risk rails — a daily loss limit and a maximum (frequently trailing) drawdown that end the account the moment you cross them.
- The behavioural rules — minimum active days, consistency requirements, news or overnight restrictions.
Confirm the exact numbers with your firm, because they vary between firms and they get revised. For journaling purposes the takeaway is blunt: you can hit the target and still fail the account. So your record has to capture rule-state, not just profit and loss.
Building a per-trade record from DXtrade data
Every DXtrade fill gives you the raw material — instrument, direction, entry, exit, size, timestamps, realised P&L. The job is to turn each closed position into a structured row you can actually query later. A minimum useful record:
- Instrument and direction
- Entry and exit price and time
- Size in contracts or lots
- The planned stop and target you set at entry — logged at entry, not reconstructed from memory afterward
- Realised P&L
- Remaining daily-loss and drawdown headroom at the moment you opened the position
That last field is the one most traders skip and later regret. If you never logged how much rope you had left, you can’t see afterward that your worst trade of the challenge was taken with almost no buffer remaining. Manual transcription from the blotter into a spreadsheet is where most journals quietly die — it’s tedious, and a bad session is exactly when you least want to do it. Connecting the account so trades land in the journal automatically removes that failure point; auto-journaling means a skipped-because-I-was-tilted day never leaves a hole in your data.
R-multiple, expectancy and setup tagging
Raw dollars lie to you across a challenge because your size changes as your buffer changes. Normalise every trade to its R-multiple — the result measured in units of the risk you actually committed. A trade that made twice what you risked is +2R whether you were trading one contract or four. Suddenly you can compare a Monday scalp to a Thursday swing on equal footing.
Tag each trade with the setup that produced it — breakout, pullback, reversal, range fade, whatever your playbook calls them. Once you have a few dozen tagged, grouped trades, run the numbers through an expectancy calculator per setup. You will almost always find that one or two setups carry the account and one is quietly bleeding. On a timed challenge, that’s not academic — it tells you which trades to keep taking and which to cut for the rest of the evaluation.
| Field | Why it earns its place |
|---|---|
| R-multiple | Compares trades across changing size |
| Setup tag | Isolates which patterns actually pay |
| Headroom at entry | Reveals risk taken relative to buffer |
| Rule-state flags | Catches consistency / daily-loss creep early |
Documenting the process that passed (so you can repeat it)
The funded account is the same game with real payout consequences and, usually, the same rules. The traders who fail funded accounts right after passing the challenge almost always changed something they never wrote down — sized up, chased an extra session, abandoned the setup that got them there.
So treat the challenge as a documented experiment. When you pass, you should be able to answer, from the record and not from feel:
- Which setups produced the bulk of the profit
- What your average and worst R-loss actually were
- Which day was your largest, and whether that concentration would fail a consistency check
- The rules you came closest to breaking, and when
This is where a live view of edge health matters more than a static logbook. Shibiki tracks your win rate and expectancy as they accumulate and wraps them in a Wilson confidence interval, so a hot first ten trades doesn’t get mistaken for a proven edge — the interval stays honestly wide until the sample backs it up. On a funded account you can also push hard risk limits down to the broker so the daily-loss line you promised yourself is enforced mechanically, not by willpower at 3pm.
Review cadence during a timed challenge
A timed challenge rewards a tight loop. A workable rhythm:
- After every session — reconcile fills, confirm each trade is tagged, and note remaining headroom. Five minutes.
- Weekly — recompute expectancy per setup and check your largest-day share of total profit against the consistency rule.
- On completion — write the one-page process summary you’ll hand your funded self.
Compared to a general-purpose logbook like Tradervue, a challenge journal is narrower and more ruthless: it exists to answer “am I on track to pass within the rules,” not to archive everything forever. Keep it lean, keep it honest, and the funded account becomes a continuation rather than a fresh gamble.
Related: R-multiple explained · Expectancy calculator · FundingPips