Real-work map · 11

Hospitality and guidance integration

Measure whether people reach the right place or service, including language, accessibility and staff escalation.

Evidence statusService decision framework · site and user validation requiredLast reviewed: 14 August 2026
11

FUURAA thesis

Durable value comes from reducing confusion without adding staff burden.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

Request

Handle language, noise, ambiguity and out-of-scope needs.

02

Journey

Confirm pace, accessible route, arrival and handover.

03

Staff

Define escalation, queue ownership and correction.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Did the person reach the service?

  2. 02

    Who is excluded by assumptions?

  3. 03

    How often does staff intervene?

  4. 04

    Does the robot obstruct routes?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Request-to-arrival record

  2. 02

    Evidence package 2

    Accessibility findings

  3. 03

    Evidence package 3

    Staff-work measurements

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.