SoReady™
International Case Study

The composite case combines a dense programme, more than twenty venues, dozens of sporting formats and a temporary organisation. The complexity comes from the interfaces: the same transport for several populations, the same technicians across several FoPs, the same build windows and security constraints. The figures illustrate a plausible scale; they serve to stress-test a coordination method, not to describe an existing event.

A green date on a schedule is not enough to open a venue. The LOC must demonstrate that obligations are known, means available, interfaces tested and reservations accepted by the right authority. SoReady turns this condition into an explainable gate. It connects discipline, FoP, infrastructure, workforce, transport, technology, security, budget and evidence, then surfaces the decisions still outstanding.

Documentary preparation feeds the model of venues and disciplines. This model feeds planning, BOM, budget, VIK, workforce and risk. Tests produce readiness evidence; during the event, EOS and EDF update the situation. The LOC thereby keeps continuity between what was promised and what is actually observed. The specialist tools stay in place, but their contributions become comparable and governable.

The LOC starts with the obligations, owners, reference data and external-flow contracts that condition the critical paths. It then adds planning, infrastructure and FoP to verify feasibility. Budget, BOM, VIK, workforce and risk give substance to the arbitrations. EOS, EDF, reporting, user assistance and the command centre come after this preparation, so that live signals can be interpreted in a reliable context. This sequence avoids a spectacular but disconnected cockpit.

Regulations, contracts, specifications and plans contain scattered requirements. Document management/OCR extracts dates, quantities, responsibilities and constraints, then matches them to the programme's objects. Owners see the extract, correct the interpretation and validate the fact. A document update triggers an impact analysis. The LOC saves time without giving up control of the information that conditions its commitments.

A session shift can hold officials longer, delay shuttles, reduce FoP turnover and move a broadcast window. The engine connects these consequences and distinguishes a certain conflict, a risk of conflict and available margin. It prepares several options: reschedule, add a resource, change scope or accept exposure. The LOC arbitrates with a shared view of cost, delay and risk.

A risk register becomes operational once every risk is linked to objects, treatments, a budget, an owner, a deadline and evidence. SoReady adds the signals that can change probability or impact. The readiness gate then takes into account the residual exposure and the authority that accepted it. The LOC does not remove uncertainty; it makes it visible, owned and revisable.

During the event, functions receive different and sometimes contradictory signals. The EDF admits, checks, timestamps, distributes and correlates them; the EOS projects them into a view suited to each responsibility. The command centre can understand the sequence, the domains affected, the freshness of the information and the evidence available. AI prepares a sourced brief, but the LOC keeps the decision and the official communication or action procedures.

The LOC must not discover during a crisis that a feed has no owner, no authority level and no recovery plan. Every integration is therefore run as a service: contract, source, sensitivity, expected frequency, quality, health, retention, degraded mode and reconciliation procedure. A team can isolate a failing feed without stopping the fabric, replay a window after an incident, and rebuild the timeline. Correlations consume only accepted, traceable events.

A storm, a shuttle delay and an abnormal density at the entrances can each seem manageable on its own. Combined, however, they change shelter capacity, the arrival of officials, medical pressure and the ability to hold the session. Correlation makes this cascade visible early enough to prepare options. It does not automatically prescribe a suspension: it gives the LOC a shared situation and explicit impacts.

The workflow starts with a traceable signal, then identifies the functions and objects affected. Experts qualify the situation; the AIs can summarise and challenge; the rules engine checks the constraints. The LOC authority chooses an option, assigns actions and validates the message. The system keeps the timeline and the elements that grounded the decision, which helps coordination and debrief.

A field of play's turnover concentrates planning, materials, consumables, workforce, cleaning, calibration and sporting validation. A delay at one step reduces the time available for the next. SoReady links the BOM to the expected configuration, checks team availability and gives substance to the reopening gate. The LOC can compare acceleration, an additional resource or rescheduling before the next session is compromised.

The LOC can use controlled services for translation or non-sensitive synthesis, a private environment for contractual and financial documents, then local engines for the command centre or isolated networks. Routing follows classification and continuity requirements. A governed MCP gateway can present the same resources and tools to the different engines, without giving them direct access to the core. AI proposes; rules compute; human validation keeps the authority.

The COO gets the opening conditions and pending arbitrations; the CFO connects options, budget, VIK and BOM; the CIO/CISO controls feeds, rights and deployment modes; sport and venue leads track FoP, transitions and evidence. The same platform does not replace their expertise: it gives them a common language and cuts the time spent reconciling diverging spreadsheets.

The cycle starts with the programme's obligations and architecture, continues with venues, means and budgets taking shape, then tests and gates. Games time adds observation and correlation. After the event, decisions, reservations and evidence are closed out and turned into reusable assets. This continuity avoids losing knowledge between temporary teams and successive editions.

The functional review checks that obligations, owners, means and evidence are complete. The technical review challenges security, resilience, integrations and degraded mode. The executive review examines residual exposure, options, cost and authority. The three views are not interchangeable: they stop an object looking ready just because one control discipline accepted it.

Public frameworks make it possible to distinguish event governance, risk, continuity, security, AI, provenance and accessibility. The case combines them to show a coherent method, without attributing to a standard something it does not cover. The volumes and scenarios remain illustrative. A real project must complete this base with sporting regulations, local legislation, contracts and the LOC's procedures.