All insights

The end of the five-day operating model

Weekend trading has moved from thought experiment to launch plan. The batch window — the quiet period every fund operating model is quietly built on — is the next assumption to go.

By Nick Ross7 min read
Editorial illustration for: The end of the five-day operating model

What it is

The five-day trading week has been the silent assumption underneath asset management operating models since before most of their owners were born. Funds are priced once a day, but they are kept once a week: the reconciliations, corporate actions, cash and FX forecasts and client reports that constitute the bookkeeping layer of the machine are scheduled into the two days the market kindly stays shut. The weekend is not idle time. It is the batch window.

That assumption is now being tested by market structure, not by any single fund. On Tuesday 29 September, Bruce Markets announced an agreement, backed by investments from PEAK6 and Robinhood, to extend US equity trading through the weekend, subject to regulatory review and with launch expected in the coming months. Bruce ATS already runs the overnight session, 8pm to 4am ET, five nights a week. The weekend is the last uncontested block of time. Last month's SEC Innovation Exemption, permitting tokenised NMS stocks to trade on-chain through automated market makers, points the same direction. Market infrastructure is being built on the assumption that trading does not stop, and the exchanges themselves are planning 23-hour days gated on data-plan deadlines. The question is no longer whether the market's hours will stretch. It is when the operating model is expected to follow.

Why it matters now

The change arrives at the worst possible moment for the batch. The industry is already compressing settlement to T+1 across the UK, the EU and Switzerland on 11 October 2027, which removes a day from every post-trade process. Weekend trading removes the quiet period. The combination leaves fund operations with two shrinking buffers: less time to settle, and no weekend in which to catch up.

The sequence of what breaks is predictable. The batch window goes first. A fund that accepts a Saturday subscription against a market that is still trading has no quiet period left to reconcile against. The rota goes second: the exception queue that used to greet Monday's first cup of tea now has a Saturday shape, and the operating model has no owner for Saturday because the model never drew Saturday. The vendor layer goes third. Fund administrators and custodians price their SLAs on a five-day assumption, and their own weekend models are just as undrawn as their clients'. Weekend FX liquidity, thinner than any model assumes, becomes the constraint nobody budgeted for.

The honest counter is that overnight liquidity is still a fraction of the day session and this specific agreement is subject to regulatory review. But market structure changes arrive the way T+1 did: capability first, volumes later, and the operating model question lands on the desk of the COO who has not touched their calendar assumptions since 2019.

What firms should do

Three things, in order.

First, draw the weekend. Map every process that depends on the weekend batch window before anyone asks for Saturday service. If the map shows the dependency, the design conversation can start. If it does not, the first weekend trade will draw it for you, at the bottom of an exception queue.

Second, treat continuous operations as a design decision, not a staffing problem. A rota is the answer to a model that still has a closed book. A model that never closes needs different controls, different hand-offs, different SLAs, and someone who owns the 2am Sunday process. That someone needs to be named before the process exists.

Third, ask your vendors the weekend question now. What does your administrator's weekend model look like? Your custodian's funding window? The outsourcing contract that does not mention the weekend will be renegotiated the first time the market opens on one, and the negotiation will be conducted by whoever is on call.

The opmodal perspective

This is where the Architecture Canvas earns its keep. Drawn honestly, a canvas shows the weekend not as empty space but as a component: the batch runs, the start-of-day scripts, the hand-offs that assume nobody is moving anything. Most operating models have never been drawn that way, because the weekend was free and nobody invoices for free capacity.

The firms that will run continuous markets well are not the ones with the best weekend trading technology. They are the ones whose operating model can show the weekend as a designed component, with owners, controls and failure modes, so that when the market opens on a Saturday the machine already knows what it is supposed to be doing. The alternative is not chaos on day one. It is a quiet accumulation of undrawn processes, owned by nobody, until the first incident reveals how much of the bookkeeping had been living in the weekend all along.

Keep reading: Process ownership: the discipline that keeps operating models alive, and The business blueprint: one connected picture of how your organisation works.