A reserved capacity commitment whose contract term has lapsed without renewal or replacement, exposing the underlying workload to on-demand pricing. Expired reservations are a planning failure rather than an optimisation failure: the workload itself may be perfectly utilised but is now paying the higher on-demand rate. The federation requires reservation expiry to be visible at least sixty days in advance, with renewal decisions made through the procurement governance process. UFMS-001:2.4(d) governs the renewal cadence and exception documentation.
A compound of expired, from Latin expirare, and reservation, an English commercial term that entered cloud vocabulary with the AWS Reserved Instance launch in 2009.
Federation members publish a reservation expiry calendar with at least sixty days of forward visibility. Decisions to let reservations lapse are documented in the procurement log. Lapses without a documented decision are reported as governance debt under MEV-Annex:3.2.
@misc{ifo4_glossary_expired_reservation,
title = {{Expired Reservation}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{expired-reservation}}},
year = {2026},
url = {https://ifo4.org/glossary/expired-reservation},
note = {Category: Waste; key: ExpiredReservation}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.