LinkSports & Events

PRACTICAL EXAMPLE · ILLUSTRATIVE SCENARIO

One start time changes.
The whole operation must respond.

A delayed session keeps officials who are needed at another venue. Adjust the delay, explore dependencies and information feeds, and prepare a decision.

SoReady · Planning & conflicts

The contention engine: expose incompatible commitments.

One team, field of play or item of equipment cannot be available everywhere at once. SoReady compares time slots, capacity, travel, reset and preparation time. The calculation distinguishes a conflict, uncertainty and available buffer.

Calculated conflict

The resource will be ready after the required start.

To confirm

Availability, duration or source is unverified.

Available buffer

The slot fits within the stated assumptions.

End of assignment + release + travel + preparation ≤ start of next requirement.

Deterministic demonstration using illustrative assumptions. A relief team may resolve an overlap without proving its qualifications, availability or cost. Authorised managers decide.

Explore the conflict and options

01 / READ THE OPERATIONAL SCHEDULE

A delay here.
A conflict at the next venue.

Compare the baseline and the proposal on the same day. In this example, the two sessions share one team of officials.

Proposed delay at venue A

Officials allocation

Officials ready at venue B16:30
Scheduled start at venue B16:15
Conflict on this dependency chain15 min

Conflict to resolve

SoReady™ · Local times · one time zone
Approved baselineProposed scenarioUnchanged window
13:0014:0015:0016:0017:0018:00
Warm-up · venue A

Base 13:15–13:45 · Prop. 13:45–14:15

Competition · venue A

Base 14:00–15:00 · Prop. 14:30–15:30

Close-out · officials A

Base 15:00–15:15 · Prop. 15:30–15:45

Transfer · A to B

Base 15:15–15:45 · Prop. 15:45–16:15

Preparation · venue B

Base 15:45–16:00 · Prop. 16:15–16:30

Competition · venue B

Base 16:15–17:15 · Prop. 16:15–17:15

Media · reserved window A

Base 13:45–15:30 · Prop. 13:45–15:30

Decision pending14:00 → 14:30 · A

On mobile, scroll the schedule horizontally. Each row also includes its times in text.

The shared team would be ready after the scheduled start. Examine the options before making a change.

The proposed session fits the illustrative media window. Availability and commitments still need reconfirming.

How does the delay propagate?

End of session A + 15 min close-out + 30 min transfer + 15 min preparation = readiness at venue B.

The baseline has a 15-minute buffer before session B. Here, warm-up A follows the delay while retaining its duration. Sport, close-out, travel and preparation durations are illustrative assumptions, not standards.

The approved baseline stays unchanged. Proposed times support the review of an option; they are neither published nor applied.

Working assumption: delay confirmed

In this illustration, the relevant lead is assumed to have confirmed the signal. Availability, rules and durations still need checking.

02 / COORDINATE THE TEAMS

Every dependency
has an owner.

Choose a function: what must it check before a decision?

Maintain the required conditions for every competition.

Responsible lead

Sport management and officials leads

Checkpoint

Qualifications, assignments, warm-up, recovery time and applicable rules. A relief team cannot be assumed.

Information to connect

Teams and shift attendance; versioned sport rules in the document repository

Control and optimise the budget.

Control and optimise the budget at every decision.

Assess the net cost of the option using existing commitments, possible reassignments and new expenditure. A reliable budget follows the agreed scope and the resources actually needed.

Extensions

Staff time, reservations and services.

Shared resources

Reusable resources and avoidable commitments.

Net cost

To establish before approval; no assumed saving.

04 / PREPARE THE DECISION

One common version.
A decision you can trace.

The authorised lead decides after rules, resources and impacts have been checked. The approved version can then be shared with the relevant teams and systems. This demonstration produces a scenario note only.

LET’S DISCUSS YOUR EVENT

A need. A deadline.
A useful first conversation.

Tell us about your event, your role and the situation to examine. We can then agree the scope, deliverables and conditions for the next step.

Describe your needs without sending sensitive or confidential data.