When a proposed Domain Tech Council charter for Lodging landed in June, it named a committed core of participants and a phased roadmap — but a charter is a proposal, not a governing body. On 11 August that gap closed. Nominations for the Lodging Technical Council (Lodging TC) were finalised, its members were appointed and written into UCP's maintainers file, and the vertical now has a standing body with the authority to define the lodging spec.

The seven inaugural members are Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, and Trip.com — the same committed core the charter named in June, now formally seated.

#From a charter to a standing council

The distinction is more than procedural. The charter set out intent; the council is who carries it out. Its membership is finalised in governance, and it holds the authority to specify the lodging capabilities and steer the roadmap the charter sketched. UCP's lodging work has moved from waitlist and proposal to a standards body with named owners — the step where a vertical stops being an announcement and starts being built.

#Who's on it

The seven members cover the width of the lodging supply chain: global distribution and online travel agencies (Amadeus, Booking.com, Expedia, Trip.com), hotel groups (Hilton and Marriott), and Google as the consumer surface convening the effort. That spread matters. A hotel booking isn't a single system — it reaches into rate and availability, loyalty programmes, and the property itself — and the council seats each of those layers rather than letting one of them set the shape alone. For a standard that has to hold across the whole industry, who sits on the council tells you almost as much as what it eventually writes.

#Not the first — the second

Lodging is the second vertical council UCP has stood up this summer. The Food TC formed in July, with Block (Square), DoorDash, Google, Toast and Uber Eats. The pattern looks deliberate: rather than stretch one retail-shaped spec over every industry, UCP is spinning up domain-specific councils, each with a finite mandate. The Governing Council has been tightening that model in parallel — its late-July session set the expectation that domain working groups carry clear goals, explicit exit criteria and a time limit. Food and lodging are the first two verticals to get their own governed homes under it.

#What the council actually has to build

The lodging spec is still in progress. The charter's Phase 1 is the booking core — rate selection, availability confirmation, guest details, payment — with account linking and loyalty after it, and discovery left for a later phase. The council is who will now write it.

None of that is the easy part of a reservation. A hotel booking carries things a retail cart never does: a rate that can move between the quote and the confirmation, a cancellation policy that behaves like a contract, loyalty status that changes the price one guest sees. We've set out before why a room isn't a SKU, and what the same shift looks like from the hotelier's side of the desk. Seating a council is what turns those requirements from an outside read into spec work with owners attached to it.

#Where we sit

We measure UCP the same way in every vertical: what a business says it supports, and what actually happens when an agent tries to transact. Lodging is about to become new ground on that map — a spec taking shape, implementations landing unevenly across distributors and hotel groups, and a gap opening between what's advertised and what actually books. Watching that gap is the whole job, and it's why an independent reference earns its keep exactly as a vertical moves from charter to council to something live.

We don't sit on the council and we don't build the spec. We watch it, the same way for everyone, as it ships.

#About UCP Checker

UCP Checker is the independent validation and observability layer for the Universal Commerce Protocol. We crawl, validate and grade every public UCP manifest we can find, run the merchant directory, the UCP Score, live adoption stats, the vertical guides and the authority-bound vendor map, and track the spec as it evolves so you don't have to — measured from two vantages (what a business declares, and what actually happens when an agent transacts), the same way for everyone, without picking winners.

#Sources

• Discussion #714 — Announcing the new Lodging Tech Council members
• UCP announcements — Lodging TC formed (11 August 2026)
• Issue #543 — Lodging Domain Tech Council charter
• Discussion #593 — Food Technical Council formed
• Related coverage: UCP for Lodging got a charter · What UCP for Lodging needs to handle · A hotelier's guide to agentic booking · UCP for Lodging vertical guide