GUIDE2,000 WORDS · PLAIN ENGLISH

Why UK local services need an open booking standard

The demand side is racing ahead. The supply side has no protocol. What happens next is a choice.

Home → Guides

Why do UK local services need an open booking standard? Because agent-mediated demand is arriving faster than supply can restructure, and without a shared protocol that demand will be captured by whoever builds a proprietary gate first. An open standard keeps the market plural, gets small firms into agent results on equal terms, and encodes UK regulatory reality — statutory certificates, scheme registrations, VAT — that global retail protocols will never prioritise.

What actually changed in the last eighteen months?

Assistants stopped being answer engines and started being errand engines. The retail world responded with agent-commerce protocols that let an AI complete a purchase end to end, and the early numbers — double-digit shares of shoppers already leaning on assistants for discovery and comparison — point one way. The purchase journey is compressing from "search, browse, compare, click, form-fill" to "state the goal, approve the result".

Local services are more exposed to this shift than retail, not less. Nobody enjoys ringing four gas engineers on a lunch break. The jobs are chores, the buying criteria are simple (credentialled, available, sensibly priced, actually turns up), and a large slice of the demand is literally mandated by law on a calendar. It is the single most delegable category of consumer spending — and the least delegable in practice, because there is nothing structured for an agent to act on.

Why can't agents just use existing websites and directories?

Three reasons. First, the data isn't there: a typical trade website has no machine-readable price, no live availability, and credentials as a JPEG of a certificate. An agent can summarise it; it cannot transact with it. Second, the directories that do aggregate trades are built to sell leads to tradespeople, not to expose bookable inventory — their business model depends on the phone call happening inside their walled garden. Third, scraping doesn't scale trust: an agent that guesses a price or promises a slot it cannot hold burns its principal once and never gets the errand again.

What does a booking standard have to get right for UK trades?

The unglamorous specifics. Coverage by postcode district, because "LS6 to LS8 and BD1" is how a Leeds engineer actually plans a day. Windows, not appointment times — AM, PM, all-day — because that is the honest shape of a trades diary. VAT treatment on every price, because £68 ex-VAT and £68 inc-VAT are different numbers and an agent must never blur them. And statutory credentials as first-class data: a CP12 without a Gas Safe reference is not a service, it is an offence. A retail protocol will never prioritise any of this; a local-services standard exists to prioritise exactly this.

Why open, rather than another proprietary platform?

Because the failure mode of this transition is a new gatekeeper. If agent-mediated bookings route through one company's closed API, every small firm in the country ends up paying rent to appear in results — the directory era again, with better branding. An open standard changes the physics: any provider can publish a manifest, any operator can host inventory, any agent can integrate, and competition happens on service rather than on access. Openness is also what makes adoption rational for the platforms that matter — lettings software, trade associations, franchise groups — none of whom will build on a competitor's proprietary rails.

Open does not mean unsteered. UKLSP pairs permissive licensing with accountable editorship: public proposals, recorded decisions, versioned schemas, and a certification harness whose reports are deterministic. The standard is a commons; the quality bar is not negotiable.

What do providers, platforms and agents each get?

Providers get demand without lead fees: a manifest is an afternoon's onboarding, and a Level 3 listing means the 8pm "is my certificate due?" panic becomes a confirmed Tuesday-morning visit booked while they slept. Platforms get a feature their customers will feel — compliance that books itself — without building booking infrastructure from scratch. Agents get what they cannot get today: quotes they can trust, slots they can hold, and credentials they can check against public registers rather than assert on vibes.

Where does this go next?

v0.1 proves the loop on landlord compliance — the recurring, deadline-driven vertical where auto-booking is most obviously valuable. v0.2 adds the operational endpoints live bookings demand: cancellation and amendment, completion webhooks that deliver the certificate back to the principal, and request signatures so hosts can distinguish accountable agents from junk traffic. Verticals after that are data additions: the drainage engineer, the roofer, the locksmith all describe themselves with the same six objects.

The window matters. Standards set early, by people close to the work, tend to encode the work honestly; standards set late, by whoever won the land grab, tend to encode the winner's margins. UK local services can still get the early kind. That is the case for doing this now, and doing it in the open — the spec is here, the demo inventory is live, and the door is open.