Reference pattern ยท Hospitality

Sense the stay, act before they ask.

This reference pattern shows how approved property, room, and guest-request context could inform a human-reviewed comfort or service proposal. It is not a live Fibric hotel deployment.

Soft 3D scene: a hotel front desk where a robotic arm slides a tagged key card into a guest slot
Joined contextreservation, room, request
Before arrivalpre-conditioning proposal
Supported actionsproposed, reviewed, recorded
What it senses

The whole stay, in one picture.

In this reference pattern, supported records would be normalized for review while retaining their source and tenant context.

PMS

The reservation and the guest

Approved arrivals, departures, room assignments, and special requests could supply the operational context for a proposal.

Room systems

Locks, climate, lighting

Selected door, thermostat, and lighting state could arrive through validated connectors. Changing a room-system vendor would still require capability parity and property commissioning.

Requests & energy

What guests ask, what rooms draw

Approved service requests, messages, and metered energy could put comfort and cost evidence beside one another for review.

How it reasons

From signal to a plan worth confirming.

The AI could propose a bounded plan. Managed policy and human authority would approve or block any supported action.

Prepare

Review the room before arrival

An approved arrival record could support a proposal to bring a room to temperature before the guest reaches it.

Predict

Surface a possible issue

A repeat request, unstable thermostat, or late-checkout conflict could be presented with its source evidence for staff review.

Balance

Compare comfort and cost

The pattern could compare comfort and energy evidence without assuming that either objective has universal priority.

What it acts on

Review room and service actions on record.

A managed deployment starts propose-only. Any room action requires explicit scope and human approval; idempotency controls reduce duplicate effects, and recovery depends on the connected system.

Precondition

Propose a room state

A validated deployment could propose approved climate or lighting changes. Policy, staff authority, and local room controls determine whether dispatch is allowed.

Dispatch

Route a task for review

The pattern could prepare a maintenance or housekeeping task with supporting context for the responsible team.

Follow up

Close the loop

The pattern could check a reported outcome and preserve the proposal and review trail. Any compensating action depends on the connected hotel system.

Prepare the room the moment a guest is on the way.

Request a managed review of property sources, guest-data authority, approved room actions, human oversight, and local equipment safeguards.