The procurement instinct gets this wrong
In most categories of IT spend, the procurement instinct is to retender every couple of years. The logic is straightforward: pricing pressure, alternative options, vendor accountability. For most of enterprise IT — endpoint, productivity, infrastructure refresh, even managed services — the instinct is correct. Retendering produces better pricing and tighter contracts, and the switching cost of moving vendors is real but bounded.
Event IT is the category where the procurement instinct produces the wrong outcome. The reason is not nostalgia or relationship-building. It is that event IT operations have a measurable maturity curve that compounds with each successive engagement at the same venue, with the same broadcast partners, with the same regulators, and with the same operating team. Retendering resets the maturity curve to zero. The first year of a new vendor on the same engagement is a substantially harder operation than the third year of a continuing one.
IP Care has run five recurring event engagements over multiple consecutive years: UFC events in the UAE (2020 through 2025, six consecutive years), NBA Abu Dhabi Games (2022 through 2025, four consecutive editions), IIFA Awards (2022 through 2024, three consecutive editions), Ya Salam After Race Concert (2019 through 2024, six consecutive editions), and Saadiyat Nights (2024 and 2025, two consecutive seasons). Across those engagements, the same operational pattern has surfaced consistently: each successive year has been measurably calmer than the previous one, against a stable architectural baseline. This post unpacks why.
The four dimensions where continuity compounds
Operational continuity in event IT compounds across four specific dimensions. Each is hard to acquire from scratch. Each accumulates faster across consecutive engagements than across new ones.
Operating maturity in the team. Engineers who have been in the room before recognise patterns faster, escalate sooner, execute runbooks more confidently and remain calm during pre-show tension that surprises a freshly assembled team. The team running NBA Abu Dhabi in 2025 was largely the team that ran the inaugural edition in 2022. The team running the 2025 UFC events on Yas Island had been there since 2020. That is not coincidence — it is the deliberate result of treating the engagement as continuous, not transactional.
Runbook depth. The first year of any event-IT engagement produces a runbook. Subsequent years refine it. By year three, the runbook covers not only the standard operating procedures but also the specific failure scenarios that have actually happened at this venue, with this broadcast partner, in this regulatory environment. A year-five UFC runbook is a fundamentally different document from a year-one runbook for the same engagement; the depth is not replicable by any amount of pre-engagement preparation.
Venue, broadcast and regulator relationships. Event IT runs through a dense web of relationships — venue management, broadcast technical operations, sector regulators (TDRA, ADMCC, SIRA depending on geography), federation technical liaisons (NBA, FINA, WTA, WBA), and security forces. Each relationship has a learning curve. Year one is mostly relationship building. Year three is operating through standing relationships. Year five is institutional history that no new vendor can replicate in months.
Contingency depth. Every recurring engagement teaches the operating team what to pre-stage that they did not pre-stage last time. Year-one contingency packs are sized against the design model. Year-three contingency packs are sized against actual observed deviations from the design model. The cost premium of a deep contingency pack is the cheapest insurance in event IT, and the depth grows year-on-year only with continuity.
What the case studies actually show
The pattern is consistent across categories.
UFC in the UAE (2020–2025): the 2020 edition ran with a substantially larger on-site engineering team than 2025 because more had to be built and validated each time. By 2025 the operation runs against a near-permanent network footprint with periodic re-validation rather than rebuild. Event-week labour has dropped roughly 40 percent and the error surface is a fraction of where it was in year one.
NBA Abu Dhabi Games (2022–2025): year one required first-principles interpretation of the NBA technical operations standards document and a multi-day timing-system integration workstream. By year four the standards-document compliance is template-driven against a previous-year sign-off, and the timing-system integration is standing infrastructure that gets re-validated rather than rebuilt.
IIFA Awards (2022–2024): the 2022 edition revealed that the press density at IIFA exceeds typical international event press density by a wide margin, and the press centre LAN operated at higher tension than ideal. The 2023 baseline moved to a substantially higher capacity, and the finding has not recurred. The lesson lives in the runbook; the upgrade lives in the build template.
Ya Salam After Race Concert (2019–2024): six consecutive years of operating in the F1-adjacent window between Grand Prix teardown and concert build. The compressed build window is now a designed-for scenario rather than a contingency. The pre-validated PtP backhaul paths around the Yas Bay precinct accumulate operating history that no new operator can match.
Saadiyat Nights (2024, 2025): the 2024 inaugural season revealed faster environmental wear on beach-exposed equipment than the planning baseline anticipated. The 2025 baseline moved equipment to a higher environmental-rating tier from the outset. Year two ran with materially lower per-show operating tension than year-one shows did.
In every one of these engagements, the operating profile in the most recent year is materially calmer than in year one, against a stable architectural baseline. The improvement is not architectural; it is operational. And it is not replicable by changing vendors.
When retendering does make sense
The argument for continuity is not unconditional. Two scenarios justify retendering in event IT.
Persistent quality or commercial issues. If the incumbent has missed SLAs across consecutive editions, has produced visible operating tension during shows, or has failed to deliver against the contractual scope, retendering is justified. Continuity compounds when the incumbent is performing; it compounds badly when the incumbent is not. The signal is usually clear after one or two editions.
Material change in the technical envelope. If the event itself is changing in ways that exceed the incumbent's technical capability — for example, a sport adopting a new federation-grade technology stack the incumbent has not previously delivered, or a venue change that materially shifts the technical envelope — retendering may be justified to ensure the new envelope is met. Even in this case, the incumbent should typically be given the opportunity to demonstrate the capability before retendering.
Outside these two scenarios, retendering produces a worse outcome than continuing the incumbent engagement.
What organisers should ask the incumbent before retendering
Before retendering an event IT engagement that has run for two or more editions, organisers should ask the incumbent four specific questions. The answers reveal whether the operational maturity has actually accumulated or whether the engagement has been running on autopilot.
One. What is in the runbook today that was not there at the end of year one? A specific list of operational lessons captured into procedural form — not a generic statement that "the runbook has matured." If the incumbent cannot answer this question concretely, the runbook is not actually accumulating.
Two. Who on the operating team has been here every year, and who is rotating? A named list. Long-running engagements work when the team has continuity. If the operating team has turned over substantially across editions, the continuity argument is weaker than the headline tenure suggests.
Three. What is the pre-staged contingency pack today, and what triggered its growth? Specific items, with the specific findings or scenarios that justified their inclusion. The contingency pack is the operational memory made physical.
Four. What are the three things you would do differently if you were starting this engagement again today? An honest answer reveals whether the incumbent has been reflecting on the engagement or just running it. A vendor that cannot identify what they would change is one that is no longer learning from the engagement, which is itself a reason to consider alternatives.
The economic case
The continuity argument is sometimes treated as a soft one — relationship, comfort, risk-aversion. It is in fact an economic argument.
Year-one event IT engagements run at higher cost than year-three engagements at the same venue with the same vendor. The cost difference comes from initial design effort, broader on-site teams, larger contingency budgets, longer pre-event validation cycles and more friction in the relationships with venue, broadcast and regulators. By year three, the design effort is replaced by validation effort, the on-site team is leaner, the contingency budget is sharper, the validation cycle is shorter and the relationships are operational rather than transactional.
Retendering resets every one of these economies. The next vendor's year-one cost profile is broadly similar to the previous vendor's year-one cost profile. The savings claimed at the procurement stage are usually a function of the new vendor not having yet learned what the previous vendor learned through three editions of operation.
The honest comparison is not "incumbent year-three pricing versus new vendor year-one pricing." It is "incumbent year-three pricing versus new vendor year-one pricing plus the cost of the operational learning the new vendor has not yet acquired." That second cost is rarely visible at the procurement stage. It surfaces as event-day tension, P2 findings that should not have happened, longer pre-event validation cycles and the broader risk profile of an engagement still climbing the maturity curve.
Bottom line
Event IT is a category where the operational maturity curve is steep, real and not replicable through documentation alone. Five consecutive years of UFC, four consecutive editions of NBA Abu Dhabi and three consecutive editions of IIFA Awards point in the same direction: the right vendor in year five is materially different from the right vendor in year one. Treating the engagement as continuous rather than transactional is the single highest-leverage decision in long-running event IT programmes.
For organisers running recurring event programmes — whether sports tournaments, awards series, concert residencies or national celebrations — the procurement instinct of retendering every two years should be overridden in favour of structured continuity, with explicit periodic reviews against the four questions above. The operating profile of a continuously engaged event IT vendor in year four is the deliverable. It is also the hardest deliverable to replicate by switching vendors.
