UCP Local Services Council Approved: What Happens Next for Bookings

Bookings now have a council on the way. On 4 November 2026, Amit Handa wrote on the Local Services charter that the UCP Governing Council "has reviewed and approved this charter". The next step is for the Governing Council to open nominations for the council's members.

That makes Local Services the third industry council approved after Food and Lodging, and the first for selling time rather than goods or rooms. There is still no services spec. Here is what was approved, how it got here, and what happens next.

#What was approved?

The Governing Council approved a charter for a Local Services Domain Tech Council: a standing council that will own how agents find, hold and book time with a business. Prasad Wangikar of Stripe filed it on 9 October 2026 as issue #922. It names Meta as the platform, and Wix, Housecall Pro, Squarespace, Jobber, HoneyBook, Stripe and Shopify as businesses.

The scope is appointments, group sessions, reservations of shared resources such as courts and tables, and rentals. Overnight stays stay with Lodging, meals with Food, and payment handling with the Payments Tech Council. We went through the charter itself in our post on what it proposes.

#How it got here

Two questions were settled along the way.

A council, not a working group. At the 16 October Shopping Tech Council, Ilya Grigorik asked which it should be. The minutes record the difference: a working group's results "get absorbed into existing councils", while a council is a permanent swim lane of its own. Services got the council. Agentic donations, discussed at the same meeting, went the other way, as a scoped working group under Shopping.

USP is a starting point, not the answer. The charter calls the Universal Scheduling Protocol, developed in Wix's GitHub organisation, "a strong initial starting point". The Governing Council's 16 October minutes describe it as "an initial sketch", with the plan that UCP for local services follows UCP's design principles.

#What happens next

The Tech Council election process sets the order. The Governing Council sets a date and shares a nomination form on the UCP announcement board. Organisations apply by the deadline. The criteria include commitment to an open, vendor-neutral ecosystem, contributions to the protocol through issues and PRs, representing a large established ecosystem in the domain, and bringing domain expertise the council needs. Members have to sign UCP's contributor licence agreement before the first meeting.

The other two industry councils give a sense of pace. Food's charter was filed on 15 June and its council seated on 16 July. Lodging's was filed on 24 June and its council seated on 11 August; its first capability merged as a draft six weeks later. Neither is a promise for services, but it is the path.

Once seated, the council starts on the charter's first phase: a service catalog, availability with time-limited holds, bookings with signed events, and a booking object on UCP checkout so the payment and the booking are confirmed together. Because that touches checkout and payment handlers, the charter commits to landing it only with Shopping and Payments council review.

#What it means for booking platforms and agent builders

For scheduling platforms: this is the window to take part. The nomination form decides who writes the spec. Wix, Squarespace, Housecall Pro, Jobber and HoneyBook are already named in the charter.

For businesses taking bookings: nothing changes yet. Paying in full, or a known deposit with the balance later through dev.ucp.common.payment.terms, already works through ordinary UCP checkout. Holds, no-show fees and paying at the counter wait for the council.

For agent builders: booking capabilities that exist today sit outside dev.ucp.*, under namespaces such as dev.usp-protocol.*. That is what UCP's namespace rules ask of anyone building ahead of a council. Read them as third-party capabilities until the council publishes its own.

#What we'll watch

• The nomination call on the UCP announcement board, and who is seated.
• Whether the council adopts USP as its starting point, and how its namespace maps into UCP.
• The first services capability filed as a PR, and the Shopping and Payments review of the booking object on checkout.
• The B2B Procurement charter (#947), still under Governing Council review.

Our UCP for Services page tracks it as it moves.

#FAQ

Is there a UCP Local Services council? It has been approved, not yet seated. The Governing Council approved the charter on 4 November 2026. Nominations for its members come next.

Who filed the Local Services charter? Prasad Wangikar of Stripe, on 9 October 2026. It names Meta as the platform, and Wix, Housecall Pro, Squarespace, Jobber, HoneyBook, Stripe and Shopify as businesses.

Does UCP support appointment booking yet? Not as a standard. There is no services namespace in the spec. Paying in full or a known deposit for a service can already go through ordinary UCP checkout and payment terms.

How do companies join the council? Through the Tech Council nomination process: the Governing Council posts a nomination form on the UCP announcement board, and organisations apply by the deadline it sets.

Is it a council or a working group? A full Domain Tech Council, a permanent swim lane in parallel to shopping. The Shopping Tech Council agreed that on 16 October 2026.

What happens to the Universal Scheduling Protocol? The charter names it as a starting point, and the Governing Council calls it an initial sketch. The council will decide how much of it becomes UCP.

#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

• Issue #922: [DTC Charter]: Local Services, UCP GitHub, filed 9 October 2026; approval comment, 4 November 2026
• UCP Governing Council minutes, 16 October 2026
• UCP Shopping Tech Council minutes, 16 October 2026
• UCP Governing Council minutes, 10 July 2026
• Tech Council election process, UCP GitHub
• Universal Scheduling Protocol: UCP-native deployment, usp-protocol.dev

Related coverage: What the Local Services charter proposes · UCP for Services · Lodging gets its council · UCP B2B procurement charter