Prop Firm Minimum Trading Days · reviewed October 2026
Prop Firm Minimum Trading Days
A minimum trading day requirement is the only rule that punishes good trading. Everything else in a challenge limits how much you can lose; this one limits how fast you can win. It exists to stop a single lucky session from becoming a funded account, and it catches disciplined traders more often than reckless ones. This guide covers what counts as a day, how the count resets between phases, and how to plan the count without adding risk you did not want.
Key takeaways
- A trading day is a day on which you trade, not a day on which the market is open. Days with no executed trade do not count.
- The count usually resets between evaluation phases, and often again before the first payout.
- Hitting the target early does not shorten the count. The account waits, and waiting is a risk decision, not a neutral pause.
- The cheapest way to complete a count is the smallest position that satisfies the definition — usually a single micro lot taken to the stop or left open briefly.
- Plan the count from the first week. Retrofitting it after the target is met is where traders give back profit.
Contents
- What counts as a trading day
- Where the count resets
- The arithmetic of finishing early
- The cheapest way to complete a count
- Why waiting is not free
- Planning the count across a 30-day cycle
- Three worked schedules
- The count before the first payout
- How the count is verified
- Counting on futures versus forex
- The count and the consistency rule together
- Three disputes and how they resolve
- Two plans, two counts
- Common questions
Most evaluation rules are constraints on the left tail. The drawdown, the daily stop and the consistency threshold all say the same thing in different ways: do not lose too much, too fast. A minimum trading day requirement is the only common rule that constrains the right tail. It says: do not win too fast either. That is why it feels unfair, and why it is worth understanding rather than arguing with.
The rationale is straightforward from the firm's side. A challenge completed in two sessions is indistinguishable from a well-timed streak. A challenge completed over ten sessions is a sample. The firm is buying evidence that the result came from a repeatable process, and it uses the calendar as a cheap proxy for the sample size it wants. The proxy is crude, but it is written down, and it is priced into the product you bought.
What counts as a trading day
The definition varies, and the differences are large enough to change a schedule. There are four common versions.
| Definition | What it requires | Practical effect |
|---|---|---|
| Any executed trade | At least one fill, however small, opened and closed | The easiest to satisfy; one micro lot is enough |
| Minimum trades per day | A stated number of fills, sometimes with a minimum duration | More expensive; requires deliberate activity |
| Position held for a period | A trade open for a minimum time, or held to the close | Penalises scalpers; a day of quick trades may not count |
| Realised profit or loss | A day that produces a settled result | Rare, but excludes flat scratch days |
The first version — any executed trade — is the most common and the easiest to plan around. The second and third are where traders get caught, because they assume the first version applies. A scalper who takes thirty trades a day can fail a minimum-duration definition, and a trader who opens one position on Monday and closes it Thursday may have recorded one day rather than four.
Two edge cases are worth checking in the terms rather than assuming. First, whether a day counts if the position is opened but not closed. Most definitions require the trade to be completed, which pushes the count to the closing day. Second, whether a day counts if the only activity is cancelling an order. Almost never, but a few plans define a trading day as any day with platform activity, and the difference matters if you are planning a quick finish.
Where the count resets
The count is usually per phase, and this is the most common planning error. A two-phase challenge with a five-day minimum in each phase requires ten counted days, not five. Add a payout requirement and the number can reach fifteen before the first withdrawal.
| Stage | Count applies | Reset behaviour |
|---|---|---|
| Phase one | Usually yes | Starts at the first trade after purchase |
| Phase two | Usually yes, sometimes lower | Restarts at zero when phase two begins |
| Funded account, first payout | Sometimes | Restarts at funding, or at the last payout |
| Later payouts | Rarely | Check whether the requirement is per cycle or once |
A plan that resets the count at every payout turns the minimum into a recurring cost. If the payout interval is short and the count is ten days, the requirement can consume almost the whole cycle, and a trader who wants to withdraw monthly has to trade on a schedule rather than on setups. That is a material product difference between two firms that both advertise "no time limit".
Phase two resets are the ones that surprise people. A trader who finishes phase one in twelve days and phase two in three arrives at the funding review with a phase-two count of three, not fifteen, and waits another two days. The wait is small; the surprise is the problem, because it usually arrives at the moment the trader has already mentally moved on to payout planning.
The arithmetic of finishing early
The cost of the rule is proportional to how fast you trade and how large your wins are. A model on a $100,000 account with an 8% target and a five-day minimum shows when the count binds and when it does not.
| Style | Average win | Days to hit target | Count required | Days idle |
|---|---|---|---|---|
| Position trader | 0.8% | ~14 | 5 | 0 — count already met |
| Swing trader | 1.2% | ~9 | 5 | 0 — count already met |
| Intraday trader | 0.6% | ~6 | 5 | 0 — just met |
| High-conviction scalper | 2.0% | ~4 | 10 | 6 days of extra activity |
| Single large session | 8.0% | 1 | 10 | 9 days, and a consistency problem |
The table makes the real issue visible. For a trader whose normal win is under 1% of the account, a five-day minimum is almost never binding, and a ten-day minimum is a minor scheduling issue. The rule bites hardest on traders with large average wins, which is exactly the group most likely to treat the requirement as an insult.
The last row is the more serious case. A single session that produces the whole target usually breaches a consistency rule as well, so the minimum trading day requirement is not the only obstacle. Adding days to satisfy the count does not repair a lopsided distribution; it only adds trades to a distribution that is already skewed. Fixing that requires adding winning days, which is the subject of the next section.
The cheapest way to complete a count
Once the target is met, the account has a new job: record days without endangering the result. The cheapest way to do that is a trade whose expected cost is close to zero and whose downside is a fraction of the remaining buffer.
The standard approach is a single minimum-size position, taken with a stop, held briefly and closed. It satisfies an "any executed trade" definition at the smallest possible risk. In practice, on a $100,000 forex account, one micro lot with a twenty-pip stop is roughly $2 of risk. Ten such days cost about $20 in expected loss across a count, which is a rounding error against the $8,000 target.
Three cautions apply. First, the trade still has to obey the daily loss rule, and even a small position can gap. Take it in a liquid instrument at a quiet hour rather than before a release. Second, some plans define a trading day by profit or by duration, and a scratch trade in a quiet hour satisfies neither. Read the definition before designing the filler. Third, the filler must not breach a conduct rule — an automated strategy, a pattern that looks like volume padding, or a trade in an instrument the plan restricts will cost more than the count is worth.
Where the definition requires a minimum duration, the cheap version is a small position held to the session close. That satisfies holding-based definitions without intraday activity, and it has the useful side effect of being a real position with a real stop rather than a token trade. The cost is a night's exposure, which the weekend rule may also constrain.
Why waiting is not free
The intuitive response to a count requirement is to stop trading once the target is met and wait for the days to pass. That is the right instinct and it is only partly right. Waiting has three costs.
The first is opportunity: the account is funded capital sitting idle, and the evaluation clock may still be running if the plan also has a maximum duration. A trader who finishes on day six of a thirty-day window can afford to wait; one who finishes on day twenty-eight cannot.
The second is the temptation to re-enter. An account that has hit the target and is waiting for days to count is in the most dangerous state in the whole process: it has nothing to gain from trading and everything to lose, and the trader is bored. Most post-target breaches happen on days that did not need a trade.
The third is the payout clock, which often starts at the last counted day rather than the day the target was met. A count that extends the evaluation also delays funding, and funding delays the seasoning period before the first payout. Each stage compounds the last, and the cost of a ten-day count can be three weeks of cash flow.
The practical conclusion is to treat the count as part of the plan from day one. If the target is likely to be met before the count, schedule the filler days into the strategy rather than bolting them on afterwards. That converts a rule that punishes speed into a schedule that a disciplined trader can execute.
Planning the count across a 30-day cycle
A workable schedule for a challenge with a thirty-day window, a ten-day minimum and an 8% target, assuming a trader whose average win is 0.7% of the account.
| Week | Trading days used | Cumulative profit | Count status | Note |
|---|---|---|---|---|
| 1 | 4 | ~2.4% | 4 of 10 | Normal setups only |
| 2 | 4 | ~4.8% | 8 of 10 | Count is close; no change needed |
| 3 | 3 | ~6.9% | 10 of 10 — met | Count satisfied before target |
| 4 | 2 | ~8.0% | Met | Target reached with room to spare |
This is the easy case: the trader's natural pace satisfies the count without any adjustment. The count only becomes a planning problem when the target arrives faster than the days, which is a function of average win size and win rate, not of skill.
A trader with a 2% average win reaches the target in about four winning days and needs six more. The schedule below front-loads the count so the filler days happen while the buffer is large, rather than after the target when every trade is pure risk.
| Week | Trading days used | Cumulative profit | Count status | Note |
|---|---|---|---|---|
| 1 | 5 | ~2.0% | 5 of 10 | Two main trades, three min-size days |
| 2 | 5 | ~5.0% | 10 of 10 — met | Two more main trades; count completed early |
| 3 | 2 | ~8.0% | Met | Free to finish at full size, count irrelevant |
This ordering is the important insight. Completing the count before the target means the final push is unconstrained. Completing it after the target means the final push is filler. Same number of days, very different risk profile.
Three worked schedules
Three traders, three definitions, three different plans. The point is that the definition, not the number of days, determines the schedule.
Any executed trade, five days, phase-specific. This trader needs ten counted days across two phases. The plan is simple: never zero-trade a weekday. One small position a day satisfies the count, and the evaluation can be finished at whatever pace the setups allow. Risk of missing the count is near zero as long as the trader does not take a week off.
Minimum two trades per day, five days. The count now costs ten trades rather than five. Those trades consume risk budget, so they should be real setups rather than filler, or the count becomes a source of losses. The plan is to hold the target at a level that leaves room for two extra trades a day, which is a size reduction rather than a calendar change.
Position held to the close, ten days. The count cannot be satisfied intraday, and a scalper's whole method fails the definition. This is a product mismatch, not a planning problem. Either the trader adopts a swing variant for the evaluation, which changes the strategy, or chooses a firm whose definition matches their style. That decision belongs before purchase, not after.
The count before the first payout
Where the requirement extends to the funded account, it interacts with seasoning and payout dates. Three clocks then run at once: the trading-day count, the seasoning period, and the payout cycle. The first payout lands at the latest of the three, and the difference between them can be a month.
Check whether the funded count is satisfied by the evaluation's days or starts fresh. A fresh count means the trader has to produce activity immediately after funding, before the first payout is even relevant, which is a different rhythm from the evaluation and often a lower-quality set of trades. The best structure is a count that carries over, and a few plans do allow this. It is worth a line in the comparison table.
Check also whether the count applies to every payout cycle or once. A recurring count is a permanent constraint on withdrawal frequency, and on a plan with a two-week cycle and a ten-day count, it means the account must trade nearly continuously to withdraw on schedule. For a swing trader, that is the difference between a usable product and an unusable one, and it is invisible on the marketing page.
How the count is verified
The count is one of the easier rules to verify because it is derived from the trade history rather than from a judgement. The firm does not need to interpret anything; it needs to count days on which at least one qualifying trade was recorded, within the phase window.
That has three practical consequences. First, the count is usually visible before review on platforms that surface a progress panel, so there is no reason to be surprised. Second, the evidence is the trade history export, which means a trader who believes the count is wrong can produce the same data the firm is using. Third, the definition matters more than the count: if the plan requires two trades a day and the trader took one, the day is correctly recorded as zero and no amount of explanation changes it.
Where the count is disputed, the argument is almost always about the definition rather than the arithmetic. The useful request is not "please recount" but "please confirm which days in the attached history qualify under the definition, and which do not". That question produces a specific answer, and a specific answer can be acted on.
Counting on futures versus forex
The same rule behaves differently in each market because a "trade" is a different unit and because the calendar is different.
| Dimension | Forex and CFD | Futures |
|---|---|---|
| Counting unit | An executed position, often one ticket | An executed contract, often several per idea |
| Weekend handling | Market closed; weekends never count | Sunday session can open the week; usually excluded |
| Minimum-duration definitions | Common, because scalping is common | Less common; a held contract is normal |
| Session structure | Nearly continuous from Sunday to Friday | Defined session hours with a daily settlement |
| Typical count | Five to ten days | Five to fifteen days |
The second row catches futures traders who use a Sunday session to get ahead of the week. If the plan counts only Monday to Friday, a Sunday evening trade does not register, and a trader who planned a five-day count around two Sunday sessions will be two days short at review. Check the session definition before using the weekend to accelerate a count.
The third row is the reverse case. A forex plan with a minimum-duration definition effectively excludes scalping from the count, which can make the requirement impossible for a scalper's normal method. On futures, a position that is held for any meaningful period satisfies the definition naturally, so the requirement is usually a simple calendar constraint.
The count and the consistency rule together
The two rules are usually described separately and interact badly. The minimum-day rule forces activity; the consistency rule caps how much of the profit can come from any one day. Together they define a corridor: enough days to satisfy the count, with profits spread widely enough to satisfy the share limit.
| Total profit | Best-day cap at 30% | Minimum profitable days needed |
|---|---|---|
| $8,000 | $2,400 | 4 days of $2,000 |
| $8,000 | $2,400 | 8 days of $1,000 |
| $8,000 | $2,400 | 16 days of $500 |
| $8,000 | $4,000 at 50% | 2 days of $4,000 |
The third row is where the two rules collide with a five-day minimum. Spreading profit over sixteen days is not compatible with finishing in a week, so a trader with small average wins has to either extend the schedule or raise the size. Raising the size to compress the distribution is the wrong response: it increases the chance that the best day breaches the cap and that a losing streak breaches the floor.
The workable answer is usually the middle of the corridor. Four to eight profitable days of similar size satisfies a 30% cap, and eight days comfortably exceeds most minimum counts. Building the target around that shape — rather than around a single large session — satisfies both rules at once and is the reason the two should be planned together.
Three disputes and how they resolve
A day with a single trade is counted as zero. This is usually a definition mismatch. If the plan requires a minimum number of trades and the trader assumed any trade would do, the firm is correct and the fix is to read the definition before the next phase. If the plan is silent on the number, the argument is about an ambiguity, and the dated terms plus the trade history are the case.
A position was held across several days but counted once. Most definitions count the day of execution, not each day the position was open. A trader who held from Monday to Thursday and expected four counted days has one. Where the plan defines a trading day as a day with an open position, the opposite applies, and the terms are the only authority.
The count appears satisfied on the dashboard but not at review. Dashboards sometimes count platform activity rather than executed trades, or count a phase that has since reset. Compare the dashboard with the trade history export and raise the difference in writing, with dates, before requesting a payout. A discrepancy found by the trader is a query; the same discrepancy found at payout is a hold.
Two plans, two counts
Two otherwise similar plans can differ by a count, and the difference is worth more than the fee. Compare a plan with a five-day minimum and a static floor against one with a ten-day minimum and a trailing floor, both on a $100,000 account with an 8% target.
| Factor | Plan A: five days, static | Plan B: ten days, trailing |
|---|---|---|
| Days of risk after the target | None for most styles | Five to six for a fast style |
| Extra trades needed | Rarely | Often, at reduced size |
| Chance of a post-target breach | Low | Higher, because the account keeps trading |
| Time to funding | Target date | Target date plus the count |
| First payout date | Sooner | Later by the same gap |
The count difference shows up twice in the cash-flow calendar: once at funding and once at the first payout, because the payout clock usually starts after funding. A five-day gap at funding can become a three-week gap at payout when a fixed cycle sits in between.
The trailing floor compounds the problem. A trader who keeps trading to satisfy the count is trading against a floor that follows peak equity, and every new high raises the floor. The combination of a ten-day count and an intraday trailing floor is the most demanding structure in common use, and it is worth checking whether the count applies after the target or is satisfied by the same days that produced it. Where the count is satisfied by the trading that hit the target, the trailing floor costs nothing extra. Where it requires additional days, the two rules multiply.
The comparison is not an argument for the cheaper plan. It is an argument for reading the count alongside the floor before pricing the fee, because the fee is the smallest of the three variables.
Common questions
Does a day with no trade count toward the minimum?
No. A trading day is a day on which you trade. A day when the market is open but you take no position is not counted, which is why an account that has hit its target can still be waiting.
Can I use a tiny position to satisfy the count?
Under the common "any executed trade" definition, yes — one minimum-size position is enough. Confirm the definition first, because plans that require a minimum number of trades, a minimum duration or a realised result are not satisfied by a token trade.
Does the count reset in phase two?
Usually yes. Most two-phase challenges apply the requirement to each phase separately, so a five-day minimum means ten counted days in total. Check whether the funded account has a third requirement.
What happens if I hit the target before the count is met?
The account is not eligible for review until the counted days are recorded. You keep trading at reduced size, or take minimum-size trades to complete the count, while the profit target is already satisfied and no longer needs risk.
Does a weekend or holiday count?
Not as a trading day, because no trade can be executed. Weekend holding rules are a separate constraint. Calendar-day seasoning periods, by contrast, do include weekends, so the two clocks are not interchangeable.
Is a minimum trading day rule the same as a time limit?
They are opposites. A minimum requires at least a set number of days; a time limit requires finishing within a maximum. Plans can impose both, which creates a narrow window in which the pass is both fast enough and slow enough.
Can a minimum trading day requirement be waived?
Rarely, and usually not in an evaluation. It is a compliance condition rather than a discretionary one. Ask support in writing if a personal circumstance makes the schedule impossible, but plan on the written rule rather than an exception.
Why do firms impose a minimum at all?
To require a sample rather than a streak. A very fast pass is hard to distinguish from luck, and the calendar is a cheap, verifiable proxy for the number of independent decisions the account represents.
Want the rulebook traded for you?
Flat $220, any firm, any account size, retries covered. We read the terms before accepting the job.
Related reading
- Passed challenges and certificates
- Client reviews of the service
- How long each payout stage takes
- The consistency rule guide
- Every clause in the challenge rulebook
- How to pass a challenge in 2026
- Passing services compared
ElitePropX is an independent service and is not affiliated with, endorsed by or sponsored by any proprietary trading firm. Minimum-day definitions and counts vary by firm and change without notice; verify them against the firm's own terms before purchasing an evaluation. Trading involves substantial risk of loss.