Topstep Combine vs funded automation: what should change in the bot

When this topic matters

• You are about to automate during an evaluation stage
• You just moved stages and are tempted to “keep everything the same”
• Your bot’s size was chosen for vibes, not the stage budget you are actually in
• You feel pressure to overtrade because the evaluation clock is loud in your head
• You want a promotion checklist that treats stage changes as first-class events

What usually stays the same

• The core setup definition (trigger, invalidation, stop, target)
• Preference for repeatable, rule-based behavior over discretionary overrides
• Need to stay inside prohibited-conduct / responsible-trading boundaries
• Value of historical replay before promotion
• Need for local supervision and emergency controls
• Credential hygiene and connection-health awareness

In other words: the integrity of the process stays. The numbers around risk often must be reviewed.

What often needs to change

1) Risk budget relative to the stage

Evaluation and funded stages can have different loss/drawdown economics. Confirm current Topstep terms rather than relying on memory or a blog summary. Re-size the bot to the stage you are actually in. See daily loss limit automation.

2) Frequency and “prove it” pressure

Evaluation pressure tempts traders (and bots) into overtrading. A good automation posture still includes stand-down and session windows, even when you feel behind. Software should not inherit your scarcity panic.

3) Promotion criteria

A strategy that “almost” survived evaluation noise is not automatically ready for funded live size. Use a deliberate promote path: promote strategy from replay to live.

4) Supervision intensity

New stage = higher attention. Day one of a new account stage is not the day to go fully hands-off. Botfolio is marketed for supervised automation for a reason.

5) Instrument sizing choices

Micros may still be the right lab even after you feel “ready” for minis. Stage change is not a dare. See micros vs minis.

What not to automate differently

Do not invent a “game the Combine” mode and a “real trading” mode. Topstep guidance around prohibited strategies and responsible trading exists for a reason. If a behavior only works because of an evaluation quirk, do not wrap it in code and hope.

Automation amplifies whatever it is pointed at — including rule violations.

Stage-aware automation checklists

Before evaluation automation

• Setup written in exact rules
• Replay across varied sessions
• Micros sizing considered for precision
• Daily loss stand-down configured
• Session window matches tested behavior
• Emergency controls practiced
• Official API / conduct pages reviewed

Before funded automation

• Re-confirm current funded rules on official Topstep pages
• Re-validate size vs daily / trailing constraints
• Re-test flatten / kill paths
• Confirm credentials still stored safely (credentials how-to)
• Decide whether strategy logic, size, or both are being promoted
• Schedule supervised early sessions (first session checklist)

Hypothetical example (not a result)

Phase 1: Trader runs a VWAP reclaim style ruleset on micros during evaluation with tight stand-downs. Replay looked acceptable; live supervision is high.

Phase 2: Account stage changes. Trader copies the same contract count onto a larger tick-value instrument because “now it’s real.” Daily budget math breaks. Stand-downs that used to fire after a recoverable sequence now fire after an account-threatening one — or worse, do not fire in time.

Better Phase 2: Same logic, fresh risk review, maybe still micros for another supervised stretch, promote size only after evidence and comfort with controls.

No phase in that story guarantees profit. It illustrates process discipline.

Common failure modes at stage transitions

1. Celebratory size increase without replay under new risk assumptions
2. Turning off stand-downs “just until I rebuild confidence”
3. Ignoring that psychological pressure changed even if the chart setup did not
4. Assuming API access / eligibility details are unchanged without checking official docs
5. Treating funding as proof the strategy is finished evolving

Where Botfolio fits across stages

Botfolio’s public positioning is the same loop at every stage: train with replay → promote tested rules → supervise Topstep-compatible execution from a local command center. The product does not replace reading stage-specific rules; it helps you execute your approved playbook with more consistency.

CTAs stay purchase-oriented on the live site (/#purchase). There is no claim that buying software alters Topstep outcomes.

Operator checklist: stage change day

• Official rules page opened and skimmed the same day
• Bot risk parameters reviewed against the new stage budget
• Stand-down thresholds updated if needed
• Contract/size choice re-justified in writing
• Protective-order / flatten expectations reconfirmed
• Supervision block booked on calendar
• Demotion criteria written (what sends this back to replay)

Deeper stage thinking: psychology is a risk input

Account stage changes the trader’s nervous system. Evaluation scarcity can push overtrading. Funded relief can push overconfidence. Neither emotion belongs in the order router.

A useful automation posture treats psychology as an input to controls:

• When pressure is high, stand-downs should be harder to disable casually
• When confidence is high, size promotion should still require evidence
• When boredom appears, session windows should still win

Write those preferences down before the stage change, while you are calm.

Risk parameter review template (fill with your real numbers)

Copy this into your notes and replace brackets using official Topstep terms and your tested stop distances:

1. Stage name: [evaluation / funded / other]
2. Relevant day-loss constraint: [from official sources]
3. Other drawdown constraints that matter this stage: [from official sources]
4. Max risk per trade: [dollars or ticks × contracts]
5. Max losers before stand-down: [N]
6. Session window: [start–end + blackouts]
7. Contract choice: [e.g., micros first]
8. Supervision plan for first five live sessions: [calendar blocks]
9. Demotion trigger: [what sends strategy back to replay]

If you cannot fill this without guessing platform rules, stop and open official docs.

Coordination with Botfolio’s promote loop

Stage change is a promote event even if strategy logic is unchanged. In Botfolio’s marketed loop, promotion is where account, sizing, and risk settings are made explicit before supervised live execution. Do not skip the paperwork because the chart pattern looks familiar.

Field notes from supervised operators (composite, not testimonials)

These are composite lessons distilled from common prop-automation failure patterns — not customer quotes, not verified Botfolio case studies, and not performance claims:

• The bot that lacked a day-level stand-down did not fail dramatically; it failed by a thousand cuts.
• The operator who skipped flatten drills discovered that “I know where the button is” is not the same as using it under adrenaline.
• The strategy that looked robust until session windows were segmented was actually a one-hour idea wearing an all-day costume.
• The stage transition that reused old size settings turned a previously tolerable loser into an outsized budget event.

Use them as warning signs in your own review meetings.

Putting the education into a Botfolio-shaped operating cadence

Even when this article is mostly about trading process, the practical cadence still maps to Botfolio’s verified loop:

1. Encode the rule changes you just designed.
2. Replay before granting live-order privileges.
3. Promote only with account/sizing/risk settings explicit.
4. Supervise from the local command center with emergency actions reachable.
5. Demote back to replay when live behavior disagrees with the story you told yourself.

That cadence will not make a weak edge strong. It will keep weak process from impersonating a strategy.

Compliance reminder you should re-read often

Automation does not create a special exemption lane. If Topstep classifies a behavior as prohibited conduct or a prohibited strategy, doing it via software is still doing it — usually faster. Keep official help pages in your weekly ritual, especially around API access, prohibited conduct, prohibited strategies, and responsible trading. This site’s older checklist post remains useful as a prompt, not as a substitute for primary sources: Topstep automated trading rules checklist.

Quick takeaways

• Often the strategy logic can, while sizing, limits, and stand-downs need stage-specific review.
• Botfolio does not claim to improve pass rates or guarantee evaluation success.
• Not impulsively. Re-validate risk first. If the setup was never robust, a stage change will not fix it.
• Do not assume. Confirm current official Topstep API, prohibited-conduct, and account-stage guidance. Third-party blogs (including this one) are not the source of truth for platform policy.