BluSky Rolling 7-Day Payout Cap: A Request-by-Request Planner

BluSky Rolling 7-Day Payout Cap: A Request-by-Request Planner

BluSky Trading Company advertises frequent payout access for eligible Sim Funded accounts, but frequent access does not mean unlimited withdrawal capacity on every day. The operational rule traders need to understand is the rolling seven-day payout cap. It behaves differently from a weekly allowance that resets every Monday.

This guide explains the rolling-window logic, shows how to maintain a simple payout ledger and turns the rule into a repeatable withdrawal routine. It is a non-promotional rules guide: the objective is to help a trader protect account liquidity and submit requests with realistic expectations.

Facts were checked against BluSky’s official Sim Funded Accounts Rules and Rules Help Center on September 4, 2026. The dashboard, account agreement and current help-center wording control if a product version differs.

What “rolling seven days” actually means

A calendar-week cap would clear on one fixed day. A rolling cap continuously looks backward from the moment a new request is assessed.

BluSky’s official example explains that each approved payout remains inside the calculation for seven days. It then drops out individually, freeing that portion of capacity. Therefore, two payouts approved on different dates do not replenish at the same time.

The useful mental model is:

Available capacity = account’s current rolling cap − payouts still inside the prior seven-day window

The account-size cap must be taken from the trader’s current rule card. Do not borrow a number from a different BluSky size, stage or legacy plan.

Why traders misread this rule

Mistake 1: expecting a Monday reset

If a payout was approved late in the prior week, Monday does not automatically restore the amount. The approval remains inside the lookback window until its own seven-day anniversary.

Mistake 2: tracking submission date instead of approval date

BluSky’s official explanation describes capacity returning seven days after a payout was approved. A request submitted on one day and approved on another should be entered in the ledger using the controlling approval timestamp.

Mistake 3: treating several payouts as one block

A $400 approval and a later $600 approval mature separately. When the first leaves the window, only $400 of capacity returns. The second stays counted until its own release point.

Mistake 4: confusing payout eligibility with cap capacity

Meeting the account’s profit, buffer, consistency, minimum-request, flat-position, identity and compliance conditions does not erase the rolling cap. Eligibility and remaining cap capacity are two separate checks.

Build a payout ledger in four columns

A trader does not need complex software. Record four items for every approved withdrawal:

• Approval date and time
• Approved amount
• Date the amount is expected to leave the seven-day window
• Remaining rolling capacity after approval

Use the timezone displayed in the BluSky dashboard or official confirmation. Consistency matters more than the spreadsheet format.

A worked example

Assume—only for illustration—that a trader’s dashboard shows a $1,200 rolling cap.

• A $500 payout is approved on Tuesday.
• A $300 payout is approved on Thursday.
• The ledger now shows $800 counted in the window and $400 potentially available.
• The following Tuesday, the first $500 reaches its release point.
• The Thursday payout remains counted until its own seven-day anniversary.

This example explains the mechanism, not a promise that every account has a $1,200 cap. Use the actual cap in the selected account.

A safer request-planning routine

Before requesting

Confirm the account is flat and review the live balance, drawdown threshold, required buffer, minimum withdrawal and payout-period consistency. Then total only the payouts still inside the lookback window.

At approval

Save the confirmation and write the approved amount and timestamp into the ledger. Recalculate the remaining cap immediately.

Before the next session

Remember that a withdrawal can reduce the financial cushion above the account’s loss threshold. A request that fits the rolling cap can still leave too little room for the next trading day.

When capacity should return

Do not assume the ledger estimate is final. Check the dashboard after the expected seven-day release time. Processing cutoffs, timestamps and product rules can affect what is currently available.

Payout access is not a risk target

The existence of frequent requests can tempt traders to withdraw every dollar as soon as it becomes eligible. That may be poor risk management.

A practical decision should consider three amounts:

1. The maximum the rolling cap currently permits.
2. The maximum the account rules permit after buffers and other conditions.
3. The maximum that leaves enough trading cushion for the trader’s normal risk.

The smallest of those three is the sensible ceiling. Many traders will intentionally request less.

How to handle overlapping payouts

Overlapping approvals create a “capacity ladder.” Each rung becomes available on a different date.

Plan around the exact release sequence. If the ledger shows that $250 leaves the window Tuesday and another $600 Friday, submitting a request sized for Friday on Tuesday is premature. This is the main reason a rolling ledger is more reliable than a note saying “weekly cap.”

Other BluSky checks that still apply

The cap is only one part of payout eligibility. Depending on the account, traders may also need to confirm:

• The account is in the correct Sim Funded or brokerage stage.
• The requested amount meets the current minimum.
• The account remains above its required loss threshold and buffer.
• Any plan-specific consistency test is satisfied.
• Positions and working orders are closed when required.
• KYC, tax and payment details are complete.
• Trading complied with account ownership and prohibited-strategy rules.
• The number of active funded accounts remains within the current policy.

Never interpret an unpublished condition as “no condition.” Obtain the exact term from support when the dashboard is unclear.

A five-minute weekly audit

Once a week, compare the ledger with the payout history inside the dashboard. Check every approval amount, date and release date. Flag discrepancies before placing a new request.

This audit is also useful after a partial approval, rejection or adjustment. The amount that counts should match the firm’s official record, not the amount originally typed into a form.

Who benefits most from this approach

The ledger is especially useful for traders who request several smaller payouts, operate more than one eligible BluSky account or plan cash flow around specific dates. A trader making infrequent requests may have little overlap, but should still check the live cap.

Bottom line

BluSky’s rolling seven-day cap is a moving lookback calculation. Every approved payout consumes capacity until that individual approval reaches its release point. Track approvals separately, verify the dashboard before every request and preserve enough drawdown cushion to keep trading after the withdrawal.

The rule becomes manageable once it is treated as a sequence of expiring entries rather than a weekly reset.